ENGAGEMENT MODEL / 02
On-Demand Projects
A defined piece of work, delivered on a defined date, against written acceptance criteria.
- Duration
- 3–16 weeks
- Team
- 2–4 people, sized to the scope
- Budget
- Fixed scope, fixed price
- Warranty
- 30 days of bug fixes after delivery
On-Demand Projects exists for work with clear boundaries that needs to land once, on a date. A new module, an integration, an interface overhaul, a data migration, an AI feature bolted onto an existing product — if the scope can be described, it fits this model.
We start with scope and acceptance criteria. What the word "done" means gets written as a list of conditions, so nothing is left to argue about at delivery. The price is built on those conditions, not on hours.
The team adapts to your codebase and your process: your repository layout, your review rules, your deployment pipeline. For 30 days after delivery we fix bugs inside the agreed scope at no cost.
What's included
Scope and acceptance criteria
The conditions under which each deliverable counts as done, written out item by item.
Technical discovery
We read your codebase, data model, and integrations first, so the risks land in the estimate rather than in the sprint.
Engineering and code review
Pull requests raised under your rules, so your team can review every step as it happens.
Testing and QA
Unit and end-to-end tests, with verification against every acceptance criterion.
Release
A release plan, a rollback path, and support through the go-live window.
Handover and 30-day warranty
Documentation, a handover session, and 30 days of free bug fixes after delivery.
Who it's for
The right model when
- The work can be described and has clear boundaries
- You need a fixed budget and a firm delivery date
- You have a team, but not the capacity for this piece
- It's a one-off migration, integration, or overhaul
Another model fits better when
- Priorities shift week to week
- You're looking for ongoing engineering capacity
- The product idea hasn't been validated yet
- Scope will only become clear once work is underway
PROCESS
How a project runs
FAQ
About On-Demand Projects
After technical discovery, once the acceptance criteria are written, we give a fixed quote. There's no hourly billing — as long as the scope holds, so does the price.
A change is priced as a written scope addition and starts only after you approve it. No surprise invoices.
Yes, most projects are exactly that. The discovery step exists for this reason: we read the codebase, the tests, and the pipeline, and reflect the risks in the quote.
We work inside your repository and project tools. A weekly progress report, open pull requests, and a shared channel are standard.
Bugs inside the agreed scope are fixed free for 30 days. After that you can continue with another project or move to a Dedicated Product Team.
Let's scope it and put a fixed price on it
A short call and a discovery pass give you a firm date, a firm budget, and written acceptance criteria.