Scoping sprint
For teams who need a real number before they can ask for budget.
- Technical discovery and risk register
- Clickable prototype of the core flow
- Costed build plan, yours to take anywhere
Every engagement is cancellable with thirty days' notice and quoted before we start. No change-request theatre.
For teams who need a real number before they can ask for budget.
A full cross-functional team owning delivery end to end.
Named engineers inside your team, on your board, under your lead.
Move the controls. The number updates live using the same model we use internally to quote work — so what you see here is what turns up on the proposal.
Focused MVP — one core job, done well
Estimates assume a single-language release and no regulated-industry audit. The two-week scoping sprint replaces this range with a fixed figure.
Send this to an engineerIf yours is not here, write to us. We answer scoping questions properly whether or not you end up hiring us.
Ask us directlyA focused first release usually lands between $80,000 and $220,000 depending on platform count, backend complexity and compliance load. The estimator above uses our real internal model, and the two-week scoping sprint turns that range into a fixed figure.
You do, from the first commit. Work happens in your repository and your design workspace wherever possible. There is no licence to buy back and no vendor lock written into the contract.
Often, yes. We start with a paid two-week audit covering architecture, test coverage, dependency health and store standing, then tell you plainly whether to continue the codebase or replace it.
Yes — listings, screenshots, privacy declarations, review responses and the staged rollout. It is included in the squad engagement rather than billed as an extra line.
Two weeks of pairing with whoever inherits the app, then your choice: a light support retainer, a reduced squad for the next release, or a clean exit with documentation and a recorded walkthrough.
Four hours of guaranteed overlap with your working day, written into the agreement. Everything else runs asynchronously through written updates, recorded demos and a shared board you can read at any hour.
We ask for these six months after the final invoice, when the honeymoon is over and the app is somebody else's responsibility.

The handover pack was the part that surprised me. Our two in-house engineers picked up the codebase in a week and have shipped four releases since without calling anyone.

They cut a third of our feature list in the scoping week and were right about all of it. That one conversation saved more money than the whole engagement cost.

Our compliance team is famously difficult. Nimblestack turned up to the review with the audit trail already written. First submission, no findings.

Every second Thursday there was a build on my phone. After eleven years of agency slides, that alone was worth the rate.
Send a paragraph about the idea and where it is stuck. You will get a reply from an engineer, not a form response — usually inside one working day.