Scoping call
What the project has to do, who it has to satisfy, and what done means.
Service
Enterprise and bespoke website projects
Larger projects, scoped properly and quoted as a fixed price before anything starts.
Scoped and quoted
The problem
Bigger website projects fail in predictable ways: scope agreed verbally and remembered differently, an hourly arrangement that makes every question expensive, and a build that depends so completely on one agency that leaving becomes unthinkable.
The technical debt is usually the smaller problem. The bigger one is that nobody wrote down what done meant.
How we approach it
Scope first, in writing, with a fixed price agreed before work starts. Not because estimating is easy, but because the alternative moves all the risk onto you.
Then built so you are not trapped. Integrations sit behind an abstraction rather than wired directly to one vendor, the stack is documented, and everything transfers to accounts you control. If you outgrow us, that should be a decision rather than a project.
Deliverables
What we deliver
- A written scope, and a fixed price agreed before anything is built
- Custom functionality — booking, quoting, portals, calculators and internal tooling
- CRM, payment and booking integrations behind a provider-agnostic layer
- Redesign and conversion work on an existing site, with URLs and rankings preserved
- Accessibility and performance treated as build requirements rather than a later audit
- Documentation, so another developer can pick it up without reverse-engineering it
- Retained design and development afterwards, month to month, if you want it
How it runs
The process for this work
The same sequence on every project, which is why the timeline can be honest.
Written scope
Requirements and a fixed price, agreed before any work starts.
Architecture
Structure, integrations and data decided before code.
Build
Delivered in stages you can see, not one reveal at the end.
Test
Every path including the failure paths, across devices and browsers.
Hand over
Documented, transferred, and yours.
Questions
Enterprise & bespoke — the common questions
Have you delivered enterprise projects before?
Not yet, and we would rather say so. The three live builds are a Shopify storefront and two local service sites. What this page describes is how a larger engagement is scoped and run with us — written scope, fixed price, documented handover — not a claim about work already delivered. Judge it on the three sites you can go and use.
Why is there no price on this page?
Because a published figure would be a guess. The work depends entirely on what has to be built, what it integrates with and how many people have to sign it off. It is scoped on a call and then quoted as a fixed price before anything starts.
Can you work alongside our existing team?
Yes. That is often the sensible arrangement on a larger project — we take the design and front-end build, your team keeps the systems they already run, and the integration points are agreed in writing up front.
What happens if we want to move to another agency later?
Everything transfers to accounts you control, and the stack is documented rather than held in someone's head. We would rather you stayed because the work is good than because leaving is painful.
Related
What usually goes with this
Scoped and quoted
Ecommerce
Premium ecommerce experiences designed around product discovery and conversion.
Read moreScoped and quotedAI & automation
Connect websites to CRM, booking, payments and lead workflows.
Read moreScoped and quotedConversion optimisation
Improve the journey from visitor to enquiry or customer.
Read moreDiscuss your project.
Tell us what you are trying to achieve and we will tell you what it takes — including if the honest answer is that you need less than you think.