Home / Process
How we work.
A custom software project fails in the gap between what was said and what was understood. Our process exists to close that gap early, in writing, before it becomes expensive.
Scoping call
45 minutes, free
We ask what your team does by hand, what systems you already run and what a good outcome looks like in twelve months. If a custom build is the wrong answer for you, we will say so on this call and point you at the product that fits. We would rather lose the project than sell you the wrong one.
Discovery sprint
Two weeks, $4,500 fixed
We interview the people who will use the system, map your data and your workflow, and produce a written architecture, a data model, an integration plan and a clickable prototype. It ends with a fixed-price quote for the build. Everything produced is yours to keep and to take elsewhere.
Build increments
Two-week cycles
Development runs in two-week increments, each ending in a working demo of real software on a staging environment. You give feedback while changes are still cheap. There is no phase where we disappear for three months and hope.
Migration & launch
One to two weeks
We move your existing data across, reconcile it against the source, run the old and new systems in parallel where it makes sense, and launch on a date you choose. Training is delivered live and recorded.
Handover
On final milestone
You receive the source code, database schema, deployment runbook and documentation. Infrastructure sits in accounts you own. Nothing about your ability to run the system depends on us being reachable.
Support
Ongoing, optional
Choose a maintenance plan or take it in-house. If you take it in-house and something breaks a year later, you can still call us — we do not refuse to help a former client.
Working with us
What we ask of you.
The projects that go well have the same thing in common: one decision-maker who can answer a question within a day. That is genuinely most of it.
- One accountable owner on your side who can make a call without a committee.
- Access to the people doing the work — the person in the spreadsheet knows more than the org chart does.
- Read-only access to current systems early, so we can see the data instead of guessing at it.
- Feedback inside a week on each increment. Silence is the only thing that reliably delays a project.
