Boringly predictable, on purpose

Most people arrive here having been burned: by an agency that went quiet, a freelancer who vanished, a project that doubled in price halfway through. So here is exactly what happens, in order, and exactly how the money works.

The process

1/6

Discovery Five short questions through the form, then a proper conversation. You get a considered reply within 48 hours; thoughts, not a sales pitch.

2/6

Scope, in writing A fixed proposal in plain English: what's being built, what it costs, what's included and, just as clearly, what isn't. No line items you don't understand.

3/6

Build, in the open A staging link from week one, so you watch it take shape. A short written update every week: what got done, what's next, anything blocking. You'll never wonder what's happening.

4/6

Review & fix You test everything against the scope. What's wrong gets fixed, without negotiation; that's what the scope was for.

5/6

Launch Domains, DNS, analytics, monitoring and backups, done properly. Launch day is a checklist, not a drama.

6/6

Handover & aftercare Documentation a non-engineer can follow, a walkthrough call, and a 30-day window for anything that snags. Then you choose: run it yourself, or have the studio keep it running.

Three ways to work together

Not a pricing table; a framework. Which one fits depends on your cash flow, how much you want to own, and whether you want a long-term engineering partner or a finished thing.

MODEL A

Licence

Lower upfront cost, then a monthly fee covering hosting, maintenance and small changes. The studio retains the code and IP; you get a system that's always looked after.

suits · cash-conscious starts

upfront · lower

ongoing · monthly

ownership · studio retains

MODEL B

Buyout

One fee, and everything is yours: code, accounts, IP, documentation. Walk away free, host it anywhere, hand it to any developer. An optional retainer is there if you want it.

suits · businesses that want full control

upfront · higher, one-off

ongoing · optional

ownership · yours, outright

MODEL C

Retainer

Ongoing monthly engineering: hosting, updates, maintenance, managed automations, and a standing claim on the studio's time when something new is needed.

suits · systems that must keep running

upfront · none

ongoing · monthly

ownership · per original model

unsure which fits? that's a discovery question, and the honest answer is sometimes "none of them yet".

Step one is five questions.

everything above starts the same way.

Begin discovery →