How we run it
Four stages.
No black box.
You see working software early and often. The alternative — a month of silence and then a reveal — is how projects end up finished and wrong at the same time.
Nothing here is unusual. It is written down because "agile" has come to mean anything at all, and you deserve to know what the weeks actually look like before you commit to twenty of them.
01 · Discovery
One to three weeks, paid, and you own the output. We map the data model, the integrations and the decisions that have already been made for you by systems you already run. It ends with a specification, an architecture and a fixed quote — all yours, including if you take them elsewhere.
02 · Design
Real screens with real data, not lorem ipsum over a grid. We design the difficult states first — empty, error, loading, too much data — because those are what determine whether software is pleasant to use, and they are what a pretty mockup always omits.
03 · Build
Two-week cycles, each ending with something you can click on staging. You are never more than two weeks from seeing where your money went. Changes are normal and are priced as they arrive, rather than accumulating into an awkward conversation at the end.
04 · Run
Launch is the start of this stage, not the end of the project. Monitoring, patching, backups and the next set of features, on a retainer with agreed response times. The same engineers — that is the point of the whole arrangement.
Questions people actually ask
How long does a project take?
A marketing site is typically 3 to 12 weeks. A web application or a native app runs from about 6 weeks for something tightly scoped to 8 months for a platform. The worked examples on the pricing page are real engagements at the faster end. Discovery gives you a real date rather than an optimistic one, which is most of why it is worth paying for.
What do you need from us?
One decision-maker who can actually decide, roughly two hours a week, and content. Content is the single most common cause of a slipped launch — not engineering.
What happens when we change our minds mid-build?
It gets scoped and priced when it comes up, and you decide. Changes are expected; what we avoid is a pile of unpriced changes surfacing as a dispute in the final week.
Tell us what you are trying to ship.
A real technical opinion back within two business days — not a sales call.