Pricing · Engagement models

Scope first. Then a number.

There is no checkout on this site and no package you have to fit into. We do not publish figures here because a number quoted before we have looked at your site is a number that gets revised — and a revised quote is worse than a slower, accurate one.

What we can be exact about is the process, and how the three ways of working differ. That is what this page is.

Ways of working
03

The process

How a price gets decided.

Pricing is supplied once the scope is understood, in a written proposal. The order matters: each step below only makes sense after the one before it.

  1. You tell us the situation

    The site, the service you want more of, and what is not currently happening. Enough for us to know whether we are the right people at all.

  2. We look before we quote

    We read what engines can currently read, and where the enquiries are being lost. This is what stops a quote from being a guess — and it is usually where the shape of a project changes.

  3. Scope gets agreed in writing

    What is being delivered, and what is not. Written down and agreed before any work starts, so neither side is working from an assumption.

  4. The proposal carries the price

    One document with the scope and the cost of that scope, on the model that suits the work. Whether that is a fixed project price or a monthly engagement depends on what is being done, not on which is easier to sell.

Three ways of working

The model follows the work.

Not every service is bought the same way, and forcing them into one shape is how people end up paying monthly for something that finished in March. Which services sit under which model comes from each service's own record.

Project-based

A defined scope, agreed up front, quoted as one fixed price.

How it works
We agree what is being built before anything is quoted. The price covers that scope and does not change unless the scope does, so there is no hourly meter running and no invoice that surprises you. When the work is delivered, the engagement ends.
Suited to
Work with a finish line — a build or a rebuild, where you can say what "done" looks like.

Bought this way (3 services)

Ongoing monthly

Continuous work on things that compound, billed monthly.

How it works
Some work does not finish. Visibility is contested every month, and an automation is only as good as its upkeep. These engagements are rolling with a short notice period rather than a fixed term, because a retainer that only survives on a contract is not one worth having.
Suited to
Work that degrades if it stops — search and answer-engine visibility, and live automation.

Bought this way (3 services)

Custom-scoped

Shaped around constraints that do not fit either shape above.

How it works
Multi-site, multi-market or multi-language operations usually arrive with existing systems, existing agreements and their own constraints. We scope against those rather than around them, and the model follows the work instead of the work being bent to fit a model.
Suited to
Operations where the constraints, not the deliverables, decide how the work has to run.

Scoped case by case, so no service sits under this by default.

Before anything starts

What the proposal settles.

Scope, before work begins
Deliverables and scope are confirmed before anything starts. Nothing is built against an assumption that was never written down.
Inclusions and exclusions, in writing
The written proposal records what is included and what is not. Both halves matter: an exclusion nobody wrote down is an argument waiting to happen.
Third-party costs, identified
Where an engagement depends on a cost payable to someone other than us, that cost is identified in the proposal rather than discovered later.

Side by side

The differences that matter.

How the three engagement models differ, by how work is agreed, how it is billed, and how it ends.
 Project-basedOngoing monthlyCustom-scoped
ScopeFixed and agreed before work startsReviewed as the work continuesShaped around existing constraints
BillingOne fixed price for the agreed scopeMonthly, rollingSet by the scope, in the proposal
CommitmentEnds on deliveryShort notice period, no fixed termAgreed per engagement
Typical workA build or rebuild with a finish lineVisibility and live automationMulti-site, multi-market operations

Pricing FAQs

Still have questions?What people ask first.

Is there a contract or lock-in?

Project work is fixed-scope, so it ends when it is delivered. Monthly engagements are rolling with a short notice period — no long lock-ins, because a retainer that only survives on a contract is not one worth having.

How fast will I see results?

Build and automation work has immediate effect: a faster site and an enquiry pipeline that stops dropping things. Ranking and answer-engine gains compound more slowly and typically become visible across about 90 days.

Do you work with our existing tools?

Yes. We integrate with the CRM, booking and marketing tools you already use rather than migrating you onto something new. Replacing a working system is a separate project with its own risks.

Who owns the work?

You do. On handoff you own the site, the content and the automations outright, including the accounts they run on. Nothing is held hostage to keep you on a retainer.

Ask us directly

Tell us what you are working on.

Send the site and the service you want more of, and we will review the details and come back on scope.

Start a conversationSee what we do →