Working method
How we deliver
A written scope, a fixed price per milestone, a running demo every week, the code in your repository from day one, and a documented handover. The same four moves on every project, whether it is a five-page site or a multi-tenant platform.
What the first three weeks look like
Same shape on every project. The content changes; the rhythm does not.
Week 1 — scope in writing
A scoping call, then a written scope: what we are building, what we are explicitly not, the assumptions we are making, and a fixed price per milestone. Nothing starts until you have that document and have agreed it.
Week 2 — something you can click
Not a status report. A running build in a staging environment you can open, plus a note on what changed and what is next. If a week produces nothing demoable, you hear that too, with the reason.
Week 3 onward — milestones and reviews
Work proceeds milestone by milestone against the agreed price. Each completed milestone is demoed and accepted before it is invoiced, and the source is in your repository from the first week.
What we commit to
These are contractual, not aspirations.
A fixed price per milestone
For the agreed scope, the price does not move. If we misjudged our own effort, we absorb the difference — that is our estimating error, not a change order.
Your code, your accounts
The repository is yours from week one, and so are the domains, cloud accounts and third-party services. There is no point at which we are holding your product hostage.
A written answer within one business day
Questions get answered the next working day, in writing, not "let us jump on a call" as a way of avoiding a paper trail.
A documented handover
Architecture notes, environment setup, deployment steps and credentials, written so a different developer can pick the work up without us.
Thirty days of aftercare
Bugs caused by our own work are fixed at no charge for thirty days after handover. This is separate from any ongoing retainer.
Honest scoping on the first call
Ten minutes with the people who would build it. You get a written outline — scope, milestones, price, risks — whether or not you hire us, and whether or not the answer is that another studio suits you better.
Run by engineers, audited by us first
The checks we run on your site are the ones we run on our own
The method is the product
Everything we sell, we run on ourselves first — and the results are published where you can read them.A six-layer site audit before we quote
Technical crawlability, the AI protocol layer, structured data, content coverage, entity consistency and outcome measurement. You get the findings as a written document — the same format you can see published on our own corporate site.
AI visibility measured, not assumed
We query the major assistants and search engines on a fixed question set, record the raw answers, and track whether your brand appears in them. The same questions each period, so the comparison means something.
Security and GEO shipped as standard
Hardened HTTPS, security response headers, source and backup files blocked, login lockout, structured data, llms.txt, sitemaps and an AI assistant on the site. These are part of delivery, not line items you buy back.
You get the full working system, not a handover note
Source in your repository from week one, architecture and environment documentation, deployment steps and credentials — written so your own developer can take it forward, and so you can switch studios without losing a month.
Change control
How scope changes are handled
No hourly meter, in either direction
You are not billed for our slowness, and you do not get a discount for our speed. The milestone price is the price.Changes are quoted before they are built
If you want something the agreed scope does not cover, we price the addition and you approve it in writing. No work happens on a change until that is done, and no invoice arrives for something you did not approve.
Estimates are ranges, not promises, before scoping
If you ask "roughly what would this cost" before a scoping call, you get a range with the reasoning shown. It becomes a fixed number only once the scope is written down.
Cutting scope is allowed, and it reduces the price
Removing a milestone removes its cost. We would rather build less of the right thing than all of the wrong one.
Ready to scope your project?
Send us what you are building and we will come back with a written outline within one business day.
No cost, no obligation, and no sales sequence afterwards.