How an engagement works
From first conversation to handoff. We keep it straightforward because a complicated process is usually hiding an unclear one.
First call
A 30-minute conversation to understand what you're trying to solve and whether we're a good fit. We'll ask about the problem, the users, the existing setup, and what you've already tried. No slides, no proposals on this call.
Discovery
One to two weeks where we dig into the problem properly. We talk to the people who will use the software. We look at existing systems and workflows. We ask the questions that usually get skipped. The output is a written spec: what's in scope, what's explicitly out, what we know, and what we don't yet.
Scoping and estimate
We turn the spec into a timeline and cost range. Not a point estimate , a range, because pretending we know exactly how long something will take is a way of lying about uncertainty. You'll know what you're getting into before we start.
Build
We work in short cycles, usually one to two weeks. You see working software regularly, not a big reveal at the end. We'll flag problems early rather than discover them late. Scope changes go through a deliberate conversation, not through quiet drift.
Review and iteration
You use the software with real data and real workflows before we call it done. Things will need adjusting. That's expected, not a failure. The review phase exists precisely for this.
Handoff
You get the code, the infrastructure, the documentation, and a handoff session where we walk through everything. The goal is that your team can maintain and extend what we built without coming back to us for every small change.
A few things worth knowing
We work with a small number of clients at a time. If we're not available immediately, we'll tell you. We'd rather be honest about our calendar than overpromise.
We charge for discovery. Some studios offer free proposals. We don't, because a real discovery phase takes real time, and doing it honestly is what prevents expensive mistakes later. The cost of discovery is credited toward the build if we proceed.
Scope changes mid-project are not forbidden, they just get scoped. If something important comes up during the build, we'll estimate it, tell you what it pushes, and let you decide. We won't silently absorb it or silently ignore it.