Services — Web
Web builds are scoped enough to publish a price.
Systems engagements are scoped around the system, not a package — that's still true, and it's why they're priced in a diagnostic. Web work is different: it's productized enough to publish a starting point.
Presence
Editorial sites, single-location restaurants, boutique studios — the Maison Lacroix and STADT class of build.
2–4 weeks
- Includes
- Up to 6 pagesEditorial design system in your brandContact / inquiry flowResponsive down to mobileBasic SEO + analytics setupPerformance + accessibility baseline
- Not included
- CMS / self-editingMultilingual routingCustom backend logicOngoing content updates
Operating site
Catalogues, multi-page operators, multilingual sites — the Atlas & Argan class of build.
4–8 weeks
- Includes
- Up to 20 pages, CMS-drivenMultilingual or catalogue routingStructured inquiry funnelAnalytics + conversion trackingPerformance + accessibility baselineA content model built so a new page is a data edit, not a rebuild
- Not included
- Third-party integrations beyond formsERP or internal toolingOngoing content updates (unless retained)
Custom / systems-adjacent
Bespoke applications, ERP or third-party integrations, internal tooling.
Set in the diagnostic
- Includes
- Scoped case by case, against the actual system
What every build includes
How a build runs
Diagnose
We map what the site actually needs to do — reserve a table, earn a consultation, convert an inquiry — before we design a single screen.
Architect
We design the content model and routing first: pages, CMS structure, and how content grows without a rebuild.
Build
We ship in working increments, not one reveal at the end. You see the site as it's built.
Operate
At handover you own the code and the domain outright. If you want us to stay on, that's a separate, explicit retainer — never assumed.
Ongoing
Questions
What changes the final price?
Page count, whether the site needs a CMS, multilingual or catalogue routing, and any integrations beyond a contact form. The “starts at” figure assumes the simplest version of that tier.
What does the timeline actually look like?
Diagnose and architect happen up front — that's where the page count and content model get fixed. Build ships in working increments you can see as it happens, not one reveal at the end.
Who owns the code and the domain?
You do, outright, at handover. We don't hold the domain or gate the codebase behind a subscription.
What happens after launch?
You get the full codebase, credentials, and a walkthrough. Ongoing changes or monitoring are a separate retainer if you want one — nothing is assumed.
Are copy and photography included?
Structure and design are ours. Copy and photography are yours unless we scope them in explicitly — we'll tell you upfront if a tier assumes you're supplying them.
Can a Presence site grow into an Operating site later?
Yes, but it's usually a rebuild of the content model, not an upgrade — we'll tell you honestly if that's coming during the diagnostic.
Begin an inquiry