How a project actually goes.

You tell us what is broken, or what you wish existed. We ask annoying questions until we both know what the job is. It takes about half an hour, it is free, and you don't need a brief.

You get: A straight answer on whether we are the right people, and what we would do first.

We write down what we will build, what we won't, the dates and the cost. If something is unclear, we ask before we guess. Nothing starts until you have agreed to it.

You get: Scope, dates and a quote in writing, and a contract that says the work is yours once it is paid for.

Layouts come first, while changing your mind is still cheap. We draw every state of a screen, including the empty and broken ones. If it is wrong, say so. Better now than a month from now.

You get: Layouts or a clickable prototype to react to, before any of it is built.

We build in small pieces and put each one on a test version you can open. How the code is reviewed and tested is on How we work.

You get: A test link that keeps growing, and short updates at a rhythm we agreed at the start.

After a last round of testing we put it live and stay around, because real users always find something we didn't. After that we look after it under a support agreement, or your own developers take over.

You get: The live product, documentation for the next developer, a list of every account and who holds it, and a walkthrough call.