Your AS 1851 customers and your project customers are not the same market

What are the two markets?

Recurring compliance service, and capital projects. The first is scheduled by an obligation the building owner carries. The second is specified, tendered, and won on capability. They share a trade and almost nothing else.

AS 1851 is the Australian standard covering routine service of fire protection systems and equipment, and the reason it matters commercially is that it turns maintenance into a calendar rather than a decision. The building owner is not weighing whether to do it. They are working out who does it and whether the paperwork will stand up.

Capital project work behaves in the opposite way. It appears when a building changes, when a consultant specifies something, when a tender opens. The buying committee is larger, the cycle is longer, and price is decided against a specification rather than against a schedule.

Most contractor websites present these as one offer, usually under a heading like fire protection services. That page is trying to answer two questions with completely different shapes, and it typically answers the project question, because project work is the more impressive thing to talk about.

How differently do they actually behave?

Different trigger, different searcher, different timeline, different proof. Once you see them side by side it is hard to justify sending both to the same page.

The last row is the one worth acting on. Routine service is the revenue that compounds and the revenue most contractors market least, because it feels ordinary next to a large installation.

What does the compliance buyer actually want to know?

Whether working with you will make their obligation go away cleanly. Not your equipment brands, not your history. Whether the service happens on schedule and the records arrive in a form that satisfies whoever asks for them.

This is the part that gets left off contractor websites, and it is the entire decision. A property manager responsible for a portfolio is being asked to produce evidence to somebody. Their fear is not that the extinguisher fails. It is that the documentation is late, incomplete, or in a format that does not travel.

So the useful page says what the service covers, how the schedule is managed, what the client receives afterwards, in what format, and how quickly. It reads as operational rather than promotional, which is exactly why it converts a buyer who has been burned before.

Note the boundary carefully. Requirements are set by the standard and by state legislation, they differ between states, and they change. Your job on the website is to be clear about what you deliver, not to publish an interpretation of anyone's statutory obligations. Point to the standard and the relevant state authority and let those be the authority.

How do the two search differently?

Compliance searches carry the vocabulary of the obligation and the asset. Project searches carry the vocabulary of the specification. Ranking for one tells you almost nothing about the other.

The practical consequence is that a contractor with one services page competes for the project vocabulary by default, because that is the language the page is written in. The recurring revenue then arrives entirely through referral and renewal, which is fine right up to the point a competitor starts capturing it in search.

Write the compliance pages in the building owner's language. That instinct feels like dumbing it down to a technical business. It is the difference between being found by the person who signs the contract and being found by their contractor.

• Compliance queries name the routine, the asset, and often the city, and read like someone checking a box
• Compliance queries are frequently typed by someone who is not in the trade, so they use the building owner's words rather than yours
• Project queries name systems, standards, and scale, and are often typed by someone technical
• Project queries are far lower in volume and far higher in value, which makes them easy to over-invest in
• Emergency and fault queries are a third, smaller stream, and they convert faster than either

Why does a national page lose to a smaller local one?

Because this demand is city-shaped. A facility manager in Brisbane is not looking for a national provider, they are looking for someone who can attend. A single page covering the whole country signals neither presence nor accountability.

When we looked at this market the visibility was fragmented city by city rather than held nationally, with different names surfacing depending on the location in the query. That is a very different competitive picture from a market one national brand dominates, and it is much better news for a mid-sized contractor.

It also means the honest version wins. A page for a city you genuinely service, naming the areas you attend and the response you can commit to, outperforms a national page listing every capital. A page for a city you do not service is worse than nothing, because the enquiry arrives and you decline it.

This is where most contractor sites either do too little, one page for all of Australia, or too much, forty thin location pages that say the same thing with the city name swapped. The second is more work and performs worse.

What should the site actually look like?

Two routes from the homepage, not one. Then a small number of honest location pages under the service route, and evidence under the project route.

That last one is the cheapest change on the list and usually the highest return. One generic contact form means an urgent fault, a tender enquiry, and a routine service question all land in the same inbox with the same priority, and the urgent one is what you lose.

• A route for recurring service, written for the person holding the obligation
• A route for projects and installations, written for whoever holds the specification
• A separate, obvious path for faults and emergencies, because that visitor will not read anything
• Location pages only for places you actually attend, with the areas and response commitment stated
• Project evidence tied to the service it demonstrates rather than in a general gallery
• An enquiry form that asks which of the three the visitor is, and routes accordingly

How do you know whether it worked?

Split the enquiries by type before you change anything, then again ninety days later. If you cannot say today what share of enquiries are recurring service against projects, that is the first thing to fix, and it costs nothing.

Most contractors we speak to have a strong intuition about this mix and no record of it. The intuition is usually wrong in an interesting direction: project work is more memorable, so it feels like more of the pipeline than it is.

Track enquiries by type, by city, and by how the person found you. Three fields on a form. Ninety days of that data will tell you which of the two markets your website is actually serving, and it will almost certainly not be the one you assumed.

Then be patient with the compliance side. That demand is tied to a calendar rather than to interest, so the enquiry arrives when the obligation does, not when you publish. The compounding is the point.