What is an engine, in plain words?

It is the part of the system that keeps working after launch: the speed checks, the search-structure upkeep, the enquiry counting and the plain report. A site without engines launches and rots; a system with engines is measured, maintained and shown its own numbers on a schedule.

Do the engines need a monthly subscription?

No. The engines are built into the system and the accounts are the client's. What the business pays for is the build, scoped and priced in writing. There is no monthly rent for holding the site, and the reporting does not stop because a platform changed its pricing.

How does the owner know the engines are working?

Because the system shows its own numbers: load measured on a real phone, enquiries attributed to the page that earned them, and a plain report on a schedule. An engine that cannot show its numbers is decoration, and the scope says so.

Engines: the parts of the system that keep working after launch

A site launches once and then quietly rots. An engine is the part that does not: the checks, the updates and the reporting that keep the pages fast, the search structure true and the enquiries counted, long after the build is handed over.

Scope mechanics

A written scope and fixed price before work starts, naming which engines are included: speed, search structure, enquiry tracking, and the reporting that shows whether any of them is working.
Pages that load fast on real cellular data, with the speed measured on a real phone in the town served — not a lab score from a desktop on fibre.
Enquiries counted from day one: where they came from, which page earned them, and what happened after. An engine that cannot show its own numbers is decoration.
Ownership of every account the engines touch, in the client's name, so the reporting does not die the day a platform changes its terms.

How the funnel works

The visit. A buyer lands from a search or an answer engine, on a page that loads before the truck leaves the driveway. Speed is not a feature here; it is the first thing the visitor judges.
The enquiry. The booking, quote or call path captures the enquiry and records which page earned it. The business learns what its pages are worth instead of guessing.
The check. Scheduled checks watch the things that rot first: load on real connections, broken paths, search structure drifting from what the business actually does. Problems surface in the report, not in a lost month of enquiries.
The report. A plain-language report the owner can read without a dashboard course: visits, enquiries, what changed, what needs attention. If the report cannot be read, the engine is not finished.

Engine parts

The speed engine: performance measured on real devices and real connections in the served town, fixed where it actually fails, re-measured after.
The search engine: titles, headings and service descriptions kept true as the business changes, so the structure does not drift away from what is actually offered.
The enquiry engine: every booking, quote and call attributed to the page that earned it, so the business knows which pages pay.
The reporting engine: one plain report, on a schedule, in the owner's language — visits, enquiries, changes, and the next thing to fix.

Artefacts you keep

The speed record: load measured on a real phone connection, before and after, kept with the build paperwork.
The enquiry log: every enquiry with the page that earned it, reviewable by the owner at any time.
The maintenance schedule: what is checked, how often, and what happens when a check fails.
The plain report: visits, enquiries and changes in words the owner can act on, delivered on a schedule.

The field guide: Engines

The problem

A site launches once and then quietly rots. The launch is measured, photographed and handed over with a certain pride. Then the business changes: new services, new areas, new hours, a staff member editing the homepage, an image uploaded at four times the size it should be. The pages slow down on cellular data in the town they serve. The headings no longer match what the business actually does. Enquiries still arrive, or they stop arriving, and nobody can say which page earned the calls that did come. This is the normal life of a site without engines. Nothing dramatic breaks. The system simply drifts away from the business it was built for, while the owner is told the site is live and therefore working.

How it works

An engine is the part that does not rot: a scheduled loop that keeps the system true after launch. The speed engine measures load on a real phone on a real connection in the served town, fixes what actually fails, and re-measures after. The search engine checks that titles, headings and service descriptions still match what the business offers and where it serves, and reports what drifted. The enquiry engine attributes every booking, quote and call to the page that earned it, so the owner learns which pages pay instead of guessing. The reporting engine turns those checks into one plain report the owner can read without a dashboard course: visits, enquiries, what changed, and the next thing to fix. If an engine cannot show its own numbers, the scope treats it as decoration, not as a feature.

Worked example — HVAC in Victoria

A Victoria HVAC firm and the checks that survive the busy season

Consider a Victoria HVAC firm as the illustration. The busy hour is a January night when the furnace stops, and the buyer searching for help is on a phone, probably in a cold house. The speed engine knows whether the emergency page loads on cellular data before the truck can move, because it measures that page on a real device and files the record. The search engine watches the seasonal pages, furnace, air conditioning, maintenance, as the firm adds the Peninsula or changes its hours, and rewrites nothing silently; it reports the drift first. The enquiry engine records which page earned each service call, so the owner sees whether the emergency page or the maintenance page is carrying the month. The plain report arrives on a schedule and names the next fix. The site still launches once. The engines are what keep the launch true.

Checklist

Measure speed on a real phone in the served town, before handover and again after changes, and keep the record.
Attribute every enquiry to the page that earned it, and review that log with the owner.
Check the search structure on a schedule against what the business actually offers and where it serves.
Deliver one plain report the owner can read: visits, enquiries, changes, and the next thing to fix.
Hold every account the engines touch in the clients name, so reporting survives any platform repricing.

Launch once, and keep the system honest long after.

Ask about engines that keep working

Direct answers

What is an engine, in plain words?: It is the part of the system that keeps working after launch: the speed checks, the search-structure upkeep, the enquiry counting and the plain report. A site without engines launches and rots; a system with engines is measured, maintained and shown its own numbers on a schedule.
Do the engines need a monthly subscription?: No. The engines are built into the system and the accounts are the client's. What the business pays for is the build, scoped and priced in writing. There is no monthly rent for holding the site, and the reporting does not stop because a platform changed its pricing.
How does the owner know the engines are working?: Because the system shows its own numbers: load measured on a real phone, enquiries attributed to the page that earned them, and a plain report on a schedule. An engine that cannot show its numbers is decoration, and the scope says so.

What arrives for a business

Ten things, every build. The list is the ceiling, not a marketing sentence — if it is not on this list it is not in the price.

A written scope and one fixed price
Agreed before any work starts. The number you sign is the number you pay.
The words, written for the customer
Every page answers what a buyer asks, not what the owner wants to say.
The design, from a system already live
Not a template you fill in. A layout built from the same system as every other build, adapted to the trade.
The build, fast on a real phone
Tested on cellular data, not on the studio's wi-fi.
The enquiry path
Form, notification, and a record of what came in — wired in, not bolted on.
Local search structure
Real headings, structured data, a sitemap, and the town named in the words.
The launch
Domain pointed, certificate checked from outside, redirects in place.
One revision round, in writing
A list of changes, agreed, done, and closed — not an open-ended tab.
The handover
Code, design, content and logins, in the business's name. Nothing held back.
Changes after launch, through the portal
Queued and done when we are in there. No retainer required to ask.

The full list, tier by tier →

What it costs, line by line

These are the published prices, in Canadian dollars before tax, from the same table the plan page charges from. A build is quoted as one fixed number against a written scope — this is what the lines add up to, not an offer.

Published line prices for a Nimos build.
The site	$2,500
The site plan	$450
A funnel	$450
Local search setup	$350
Care	$150
Site Watch	$49

Price your own build →No card, no call, no email required to see a number.

What you can check before you call

There are no testimonials on this page, because there are none to show. What there is instead is four things you can open in another tab and judge for yourself.

The build log

Every change this studio ships to its own site, dated, with the commit behind it.

Read the log →

The work

Five real builds, named, with what was actually done on each one.

See the work →

The accessibility rules

The contrast, type and motion limits this site enforces on itself, stated publicly.

Read the rules →

The status page

What is up, what is down, and what changed — not a badge that always says green.

Check the status →

LATELY, ON THIS SITE

2026-11-06The field, named — Sixty-six tools and people get a page each, and every city gets a hub.
2026-11-04The local engine — Twenty trades across a hundred and eighteen cities, from one data file.
2026-10-20The build table — The six numbered steps become one table of real handoffs — HELLO to LIVE.

Nothing on this page is a claim we cannot point at. The four links above are the evidence, and every one of them is a click away.

Two ways to start, and neither is a sales call.

Price your system line by line on the plan page, or run the free leak report on the site you have now and read the findings yourself. Neither one is a sales call.

Price it in 90 seconds Run the free leak report