Three ways to work together
Software scope varies too much for a price list. These are the shapes an engagement takes. The number comes after a scoping call, and it holds.
Discovery Sprint
For when the problem is clear but the solution isn't.
- Technical feasibility review
- Architecture and stack decision
- Scoped build plan and estimate
- Working prototype where it helps
Ends with a plan you can build with anyone, including someone else.
Request a scopeFixed-Scope Build
For a defined product or system with a known finish line.
- Agreed scope, milestones, and price
- Design, build, test, deploy
- Weekly demos against a live environment
- Handover with documentation
The price is agreed before we start and it holds unless you change the scope.
Request a scopeSupport & Iteration
For keeping what we built healthy and moving.
- Bug fixes and maintenance
- Feature enhancements
- Monitoring and incident response
- Rolling monthly terms
Month to month. No lock-in, no notice period games.
Request a scopeWhat every engagement includes
- A kickoff workshop and written scope
- A shared channel with the people doing the work
- Weekly progress against a live environment
- Code and infrastructure in your accounts from day one
- Documentation and handover at the end
What sits outside the fee
Third-party services
Cloud hosting, model API usage, and SaaS tooling are billed to you direct by the vendor, with no markup from us.
Scope added mid-engagement
New scope gets re-estimated and agreed in writing before it starts, rather than turning up as a surprise invoice.
Ongoing support after handover
Covered separately under Support & Iteration, so you are not paying for it while you do not need it.
Questions about cost
Why are there no prices on this page?
Because a number without scope is a guess, and a guess you plan around is worse than no number. A short scoping call gets you a real figure, usually within a couple of days.
How do you estimate?
We break the work into the pieces we can name, price those, and flag the parts that carry genuine uncertainty rather than padding the whole thing to cover them.
What happens if the estimate turns out to be wrong?
On a fixed-scope build, an estimating error on our side is ours to absorb. A change on your side gets re-scoped openly. The distinction is agreed up front.
Want a real number?
Tell us what you are building and where it currently stands. We will come back with a scope and a figure you can take to your board.