Spec first. Shipped every Friday.
Four steps, in this order. Each one ends with something you receive, so you can check the work instead of taking our word for it.
Four steps. Each ends in something you hold.
Software projects fail because of communication, not technology. So the process is fixed and written down.
Step 1
Discovery
A written spec before any code.
We learn how your business works before we write anything. The result is a written technical specification: what gets built, how, and what it depends on. You read it and sign it off before development starts.
What you receive
- A written technical specification, before any code
- A fixed price, quoted in writing before we start
- A spec that is yours to keep, even if you build elsewhere
- A dedicated technical lead who answers for the work
Step 2
Development
Two-week sprints. A link every Friday.
Work runs in two-week sprints. Every Friday you get a deployable link: the software running, not a status report. If a Friday will slip, you hear it from us first, with the reason.
What you receive
- A deployable link every Friday
- One accountable contact: your technical lead
- A written reply within 24 hours, on working days
- A message from us first whenever a Friday is at risk
Step 3
Testing
If it breaks, it breaks here, not in production.
Automated end-to-end tests run against the work as it is built. A failure shows up in our pipeline, not in front of your users.
What you receive
- Automated end-to-end tests for the flows in the spec
- Every change checked by the suite before it reaches your link
- The test suite kept in your repository
Step 4
Handoff
Keys, documentation and training.
At the end you hold everything needed to run the software without us. We keep nothing that blocks you from running it, so leaving is a handover, not a negotiation.
What you receive
- Repository, cloud accounts and domains already in your name
- Documentation for the system as built
- Training for the people who will run it
- The IP, assigned to you on full payment
The Friday link
Every Friday you get a link you can click. If we miss one, you hear it from us first.
What we won’t do. Five commitments.
Each line is a commitment you can hold us to, not a preference.
- We won’t start without a written spec. Work begins once the spec exists, so scope is on paper before it is in code.
- We won’t hold your code. Your repository, cloud accounts and domains are yours from day one.
- We won’t hide a slipped Friday. If a link will be late, you hear it from us first, with the reason.
- We won’t ship a change the tests have not seen. Every change runs the automated suite before it reaches your link.
- We won’t make leaving hard. The handover is written so that someone other than us can run the system.
Begin with the spec. Or tell us what you’re building.
The spec is the first step: fixed price, quoted in writing before we start. If you would rather describe the project first, start there.