Changes
Scope changes
Anything outside the signed scope is quoted as a written change order before work starts. You approve the cost and the timeline impact first. No change is absorbed quietly and billed later.
Home / Process
A process built so you always know what happens next.
Six stages, run in the same order on every project, each with a written output before the next begins.
The sequence
Each stage produces the input the next one needs.
A build that starts before the scope is signed is a build that will change price. A design that starts before discovery is a guess with a nice typeface.
Stage 01
30 minutes
Discovery call
We ask what the software has to do, who has to use it, what it must connect to, and what deadline you are working to. No sales deck. If the project is outside what we do well, we say so on this call and point you elsewhere.
You leave with a shared written problem statement.
Stage 02
Within 48 hours
Scope document and fixed estimate
We write down every screen, business rule, and integration, plus everything explicitly excluded, and attach a fixed price. The document is yours whether or not you hire us. Taken to another developer, it will still save you money.
You leave with a scope document and a fixed price.
Stage 03
1 to 3 weeks
Design and prototype
Wireframes first, then a clickable prototype you can put in front of a real user before development starts. Changing a screen in design costs an afternoon. Changing it after it is built costs a sprint.
You leave with an approved clickable prototype.
Stage 04
Bulk of the timeline
Build in two-week blocks
Development runs against the signed scope. At the end of every block you receive a working build and a written update covering what shipped, what is next, and anything at risk. Nothing is reported as a percentage.
You leave with a working build every two weeks.
Stage 05
1 to 2 weeks
QA, launch and handover
Testing on real devices and current browsers, not just emulators. Store submission or deployment, then the part most agencies are vague about: transferring every repository, server, and account into your business name.
You leave with a live product and every credential.
Stage 06
Ongoing, optional
Support and iteration
Thirty days of fixes on in-scope work are included. After that you can move to a monthly support plan, or take the documentation and run it with your own team. Both are fine with us.
You leave with software that stays current.
Ground rules
How we handle the things that usually go wrong
Timelines
Delays
If a block is going to slip, you hear it in that block's update, not at the end of the project. We would rather deliver an uncomfortable message early than a surprise late.
Payment
Milestones
Billing is milestone-based against delivered work, agreed in the contract before the project starts. Final repository transfer happens on final payment.
Privacy
Confidentiality
We sign your NDA, or ours if you do not have one, before the discovery call if you prefer. Your idea, data, and documents are not shared or reused.
Quality
Testing
Every build is tested on real devices and current browser versions. You also get a staging environment so your own team can test before anything reaches customers.
Exit
Ending early
If you want to stop, you receive the code and documentation for everything paid for to date. There is no lock-in clause and nothing is held back.
Start at stage one.
A short discovery call costs nothing and ends with a written problem statement you can use anywhere.