Questions
The process, plainly
Straight answers to the questions we hear most often.
What does "we survey it before we build it" mean?
The scope is agreed in writing before any code is written. The first week or two is a structured conversation, not a sales call — by the end, both sides know exactly what's in, what's out, and what it will take.
What do I get at the end of the survey?
A written proposal: what we recommend building, in what stages, what each stage delivers, and how long it takes. It's yours to keep, whether or not you go ahead.
How is an engagement structured?
In stages. Each one is agreed before it begins, so you decide how much to take on at a time — never one all-or-nothing commitment.
How long does a build take?
Most builds run weeks 3–12, with working software you can open at every milestone — real deployments, not mockups. If something needs to change mid-build, it's agreed together.
What happens at handover?
Everything becomes yours: domain, hosting, database, code. Whether we stay involved afterwards is your call, not a default.
What if my idea isn't fully formed yet?
That's exactly what the survey is for. You don't need a finished spec — the conversation turns a rough idea or an open business problem into a clear, agreed scope.
Do you name your clients?
Only with your written permission. By default we describe the work, never the client.
Ready when you are