Home / Process
How we work
Scope it, build it, hand it over
Small studios usually ask you to trust them. We would rather show you the sequence: what happens at each step, what you get at the end of it, and how long it takes. Scope is agreed in writing before anything is built, and every project ends with you owning the code.
- 01
Scope call
30 minutes
Thirty minutes on how the work happens today: who does what, in which spreadsheet, and what breaks at month-end. We ask about the deadline you are actually working to, and about what already exists.
You getA straight answer on whether we are the right studio for this, and a rough shape in weeks.
- 02
Written scope
A few days
We write down phase one: the screens, the roles, the documents, the integrations. Just as important, we write down what is not in phase one, so nothing is assumed in either direction. A fixed quote comes with it.
You getA written scope and a fixed quote you can compare to anyone else's.
- 03
First release
About 4 weeks
We build phase one and put your real data in it. You see the working system every week, not a slide about it. Feedback in week two is cheap; feedback after launch is not.
You getA working system your team can log into, with your own history imported.
- 04
Phases
2 to 4 weeks each
Once people are using it, you know what the next release needs better than any plan written before launch. We agree the next batch, quote it in weeks and ship it.
You getA shipped batch of work every two to four weeks, agreed before it starts.
- 05
Handover
1 week
The repository, the accounts, the environment and a written handover document: how it is deployed, how to add a user, what to do when something looks wrong. Then a support window while your team settles in.
You getThe code, the documentation and a support window. You own all of it.
Scope in weeks
How long things take
Every quote is written for the scope we agree, so the numbers below are ranges from past work, not a price list.
| Scope | Weeks | Example |
|---|---|---|
| Marketing site or landing page | 1 to 2 weeks | A company site rebuilt from your own content and photos. |
| Internal tool, first release | About 4 weeks | Delta Solutions: trips, manifests and monthly reports for about 200 sites. |
| Payments or subscriptions | 2 to 3 weeks | Subscriptions with intro pricing, receipts, and access that switches off on cancel. |
| AI or reporting automation | 1 to 2 weeks | A scheduled agent that ranks production errors and files tasks into Slack. |
How we work
Principles we do not bend
The engineer is in the room
You talk to the person writing the code, at every step. Nothing is translated through an account manager, so nothing is lost on the way to the keyboard.
Your data, from day one
We import your spreadsheets during the first release. A system that opens empty is a demo; a system that opens with your last two years in it is a tool.
Rules in code, with tests
The calculation exceptions your team keeps in their heads get written down, in code, with tests around them. That is what makes a report trustworthy on the first of the month.
You own it
The repository is yours at handover, whether or not we keep working together. No lock-in, no hostage hosting, no platform you have to keep renting from us.