ServicesSpecification
Everything it takes to ship a web product.
Strategy, interface, application, data and infrastructure — planned by the same team that writes the code and stays to look after it.
- 01InterfaceWebsites, storefronts and product UI4 services
- 02ApplicationBusiness logic, accounts, billing, workflows3 services
- 03Data & integrationsAPIs, pipelines and third-party systems2 services
- 04InfrastructureHosting, monitoring, performance, security3 services
Fig. S1 — a web product, exploded into its four layers
01The catalogue
What we build, in detail.
Choose a service to see what's included, how long it usually takes and when it's the right fit. Use the arrow keys to move through the list.
Service 01
Websites & content platforms
Design and development of marketing sites, documentation hubs and content platforms on a headless CMS — structured so editors can publish without a developer and pages stay fast as content grows.
Deliverables
- Content model and CMS setup
- Component library for page building
- SEO, analytics and consent foundations
- Localisation (if needed)
- Typical timeline
- 6–10 weeks
- Usual stack
- Next.jsSanity or ContentfulVercel
- Layers
- Interface(included)Application(not included)Data & integrations(not included)Infrastructure(included)
A good fit ifYour current site is slow, hard to edit, or built on a theme you've outgrown.
Discuss this service02Engagement models
Three ways to work together.
Pick the shape that fits where your product is today. Many clients start with a fixed-scope build and move to a care plan after launch.
Model 01
Fixed-scope build
A defined product, start to finish
- Best for
- A new site, store or first product release
- Team
- 2–4 people, led by one engineer
- Typical length
- 6–16 weeks
- How it's billed
- Fixed price after discovery
- You get
- A launched product, docs and a handover
Model 02
Embedded team
Extra senior hands inside your team
- Best for
- Teams with a roadmap and not enough people
- Team
- 1–3 engineers working in your repo
- Typical length
- 3 months, renewable
- How it's billed
- Monthly, per person
- You get
- Shipped features and knowledge that stays
Model 03
Care plan
Ongoing health for a live product
- Best for
- Products already in production
- Team
- A named engineer plus backup
- Typical length
- Rolling, cancel any month
- How it's billed
- Fixed monthly retainer
- You get
- Upgrades, monitoring and a monthly report
03Delivery
From brief to launch, in five stages.
Stage 01 · 1–2 weeks
Discovery
Workshops, a technical audit and user interviews where they help.
- Written scope
- Fixed estimate
- Risk list
Stage 02 · 1–2 weeks
Architecture
Data model, hosting plan and a prototype of the riskiest flow.
- Architecture notes
- Clickable prototype
Stage 03 · 2–3 weeks
Design system
Tokens and components built in code, reviewed in the browser.
- Component library
- Page templates
Stage 04 · 4–10 weeks
Build sprints
Two-week sprints with a preview link for every change and a demo every other Friday.
- Working software
- Tests
- Sprint notes
Stage 05 · 1 week
Launch & handover
Staged rollout, monitoring, documentation and a recorded walkthrough.
- Live product
- Runbook
- 30-day warranty
04Technical FAQ
Questions engineers ask us.
We start from what your team can maintain after we leave. If you already have a stack, we build on it. If not, we recommend boring, well-supported tools and explain the trade-offs in writing.
Yes. We start with a short paid audit — architecture, dependencies, tests and hosting — and give you a prioritised list before committing to any larger work.
In accounts you own. We usually suggest Vercel or AWS, but we are happy to deploy to your existing cloud provider.
Every build targets WCAG 2.2 AA. We run automated checks on each pull request and a manual keyboard and screen-reader pass before launch.