four steps and one document
The problem with a software project is almost never technical. It's that nobody wrote down where it ends. That's why the document weighs as much as the code.
01
Call
Thirty minutes with the person who’ll build it. You tell us the problem, not the solution. If we’re not the right shop for it, you’ll hear it on that call — and we’ll tell you who to look for.
02
Proposal
In writing: fixed price, dates, what’s included and what isn’t. You sign it before we write a line.
03
Build
You see real progress you can open and try, not status reports. Changes of direction get decided early.
04
Handover
Published and working, with the code, the domain and the keys in your name. If you want to take it to someone else tomorrow, you don’t have to ask us.
Every proposal includes
“What’s not included”
It’s the shortest section and the most important. Without it, scope grows without anyone deciding, and the one who ends up paying that difference is always you.
Critical
“What we need from you”
Photos, copy, access, a signature from someone who decides. Whatever can actually delay the project is marked critical from day one, with a date.