Six things we do, and when you need each one.
Fixed price against a written scope, built by the people you met on the call. If your stage doesn't call for a line item yet, we say so.
DAY 1–3
Scope, written
DAY 4–9
Design, argued over
DAY 14
Clickable build
EVERY PUSH
CI gates pass
HANDOVER
Repo is yours
PRICING
Fixed, per scope
SUBCONTRACTORS
None
CODE OWNERSHIP
100% yours
REPLY TIME
1 business day
01
Custom builds
A production app designed and built end to end — typed, tested, and running in your own accounts.
Infrastructure provisioned as code
CI gates for performance and accessibility
Runbook your next hire can follow
What we hand over
Interface
TYPED · TESTED
API layer
SCHEMA-VALIDATED
Data
MIGRATIONS IN REPO
Infrastructure
YOUR ACCOUNTS
EVERY LAYER TRANSFERS AT HANDOVER — NOTHING LOCKED TO US
Signup funnel — illustrative
+38% finish
Landed
100%
Explored a page
64%
Started signup
31%
Finished — before
13%
Finished — after
18%
WE AGREE THE ONE NUMBER FIRST, THEN DESIGN AGAINST IT
02
UX/UI design
Flows, screens and interface copy aimed at one metric you've agreed to move — with real content and real states.
Audit with the drop-offs named and measured
Empty, loading and error states included
Handoff your developers can build from
03
Design systems
Tokens, components and docs so your team ships faster after we leave — and stops rebuilding the same button.
Tokens for colour, type, spacing and motion
Accessible components with documented states
Contribution rules, so it survives year two
Related reading
The ROI of a design system for a 5-person startup →One token set, every surface
36
Components
1
Source of truth
AA
Contrast tested
Core Web Vitals — typical engagement
ALL PASSING
LCP
4.1s → 1.4s
INP
310ms → 90ms
CLS
0.24 → 0.02
04
Speed optimisation
Measured on the devices and networks your customers actually use, then locked in with budgets that fail the build on regression.
Field-data baseline by device and route
Render path, image and third-party remediation
Before-and-after report in numbers
Related reading
How we hit 100 on Lighthouse - every single time →05
Technical SEO
Architecture, rendering strategy, schema and internal linking — decided at build time, where they're cheap.
URL plan mapped to real search intent
Structured data, sitemaps and canonical rules
A content brief your team can write against
Related reading
The technical SEO checklist we run before launch →Structure, planned not audited
/
Home
/services
6 child pages
/works/[case]
Schema: CaseStudy
/blog/[post]
Schema: Article
SERVER-RENDERED · CRAWLABLE WITHOUT JS
Review checklist
OWASP Top 10
Access control & session handling
Injection & input validation
Secrets, headers & CSP
Dependency & supply chain
2 to fix
Re-test after your fixes
Included
FINDINGS RANKED BY RISK — SENDABLE WITH A QUESTIONNAIRE
06
Security review
Pen testing, OWASP review, dependency scanning and auth hardening — with a remediation plan written for a buyer, not just for engineers.
Authenticated pen test against staging
Auth, session and access-control review
Re-test once your fixes are in
The gates every release passes
Not upsells — the checks that block a release on our pipeline, and that you can run yourself after handover.
GATE 01
PASS
Types & tests
Strict TypeScript, validated boundaries.
GATE 02
PASS
Speed budget
LCP under 1.8s on 4G, enforced in CI.
GATE 03
PASS
WCAG 2.2 AA
Keyboard paths, contrast, semantics.
GATE 04
PASS
Observability
Logs, error tracking and alerts at launch.
Answered here, so you don't need a call to find out.
How do you price work?
A fixed number against a written scope. The ranges above are where most projects land; you get a specific figure after one conversation.
Who actually writes the code?
We do. Nothing is subcontracted, and the people on your kickoff call are the people in your repo.
Do we own the code and infrastructure?
Entirely. Repo, accounts and documentation sit in your name from day one, not transferred at the end if things go well.
What if scope changes mid-build?
We price the change before doing it and tell you what it displaces. Nothing reaches an invoice you haven't approved.
Not sure which of these you need?
Describe the problem in a paragraph. An engineer replies within one business day with a number, a question, or an honest reason we're not the right studio.