How a project runs

We write the plan before the code. Every project goes through the same steps, and you can see where yours is at any time.

1. Brief

A call, then a one-page summary of what you need, who it is for, and what “done” looks like. If we are not the right team, we say so and suggest who is.

2. Proposal and SOW

A written scope, a price and dates, agreed before work starts. The signed SOW sets the payment terms; our usual schedule is 40% on signature, 40% when testing is signed off and 20% at handover. Nothing starts before it is signed by both sides.

3. PRD

A requirements document that says exactly what will be built, screen by screen and rule by rule, with acceptance criteria you can test. You approve it before we write code. We write any change after that into a short change note with its cost, for you to approve.

4. Build

Weekly demos on a live preview link that works on your phone. We test on a mid-range Android phone on mobile data, and we test payments, email and forms with real transactions before launch.

5. Launch

A checklist, not a hope: performance, accessibility, security headers, backups, monitoring, legal pages.

6. Handover

At handover, the accounts (domain, hosting, database, payments, email) are in your name, with us as a collaborator only if you want us to stay. You get a runbook that says how it all works and what to do when something breaks.

7. Maintenance

Optional monthly retainer: updates, monitoring, small changes, and a person to call. The SOW sets the notice period to end it.

What we do not do

Free pilots, unlimited revisions, or hosting your system on our accounts. Those habits end badly for both sides.