Build
Software your team stops working around
Most internal tools get abandoned because they were scoped once and never revisited. We ship in stages and rewrite the plan when the work says to.
Discovery is fixed price and ends in writing
§ 01 / 06The problem
The spreadsheet became the system
It started as one file. Now three people maintain it, two of them differently, and nobody will touch the formulas. Reporting takes a day and is wrong by the time it lands.
Companies whose operations have outgrown spreadsheets and off-the-shelf tools.
- The same number appears differently in two places
- Onboarding a new hire means teaching them a file, not a process
- Nobody can answer a question without exporting something first
§ 02 / 06What you get
What is included
- Discovery
- Three days, fixed price, written findings
You keep the document whether or not we build.
- Architecture
- Written down before code, in plain language
Including what we deliberately chose not to build.
- Build
- Staged releases, each one usable on its own
- Repository
- Yours from the first commit
Hosted on your account. No licence to renew.
- Handover
- Written runbook and a working session with your team
Not sure which parts you need? Take the free build plan and we will tell you which to skip.
§ 03 / 06Timeline
How the work is sequenced
Each stage ends with something you can check. If a stage cannot end that way, it is scoped wrong and we re-cut it.
- 01
Build plan · 30 minutes
We map what your team does by hand today and what it costs in hours.
- 02
Discovery · 3 working days
We open the real data and write down what the system actually has to do.
- 03
First release · 4 to 6 weeks
The narrowest version that removes the most manual work. In use, not in staging.
- 04
Iteration · 2 week cycles
Each cycle ends with something your team can use and judge.
§ 04 / 06Commitments
What we hold ourselves to
§ 05 / 06Price
Starts at $18,000
Scope, number of integrations, and whether data has to be migrated.
§ 01 / 01Questions
Before you ask us
What if we stop working with you?
The repository is on your account and the runbook is written for someone who has never met us. That is the test we hold handover to: another developer picks it up without calling us.
Can you work with our existing codebase?
Yes. Discovery covers reading it. If the honest answer is that a rewrite costs less than the repairs, we will say so and show the arithmetic.
Industries
Solutions
Read on the topic
Start with the plan, not with a quote
Thirty minutes on software development. You keep the written order of work either way.
Free, 30 minutes, no slide deck.