
Key takeaways
- Fixed price suits a clear, stable scope.
- A dedicated team suits a product with a long, changing roadmap.
- Time and materials suits discovery, maintenance and open-ended work.
- You can switch models as the project matures.
Before code, there is a contract. The engagement model decides who carries the risk when requirements change, how much control you have day to day, and how easy it is to adjust course.
Fixed price
A written scope, a fixed quote and a delivery date. You know the cost up front; the partner carries the risk of estimating correctly.
- Fits: websites, well-defined modules, integrations, an MVP with a firm feature list.
- Watch for: changes need a change request, so invest time in the specification.
Dedicated team
Engineers who work only on your product for a monthly fee, directed by you. Maximum flexibility and continuity.
- Fits: SaaS products, long roadmaps, ongoing development. See hire dedicated developers and SaaS development.
- Watch for: you need someone on your side to set priorities.
Time and materials
You pay for the time actually spent, usually with a monthly cap. Good when the work cannot be specified up front.
- Fits: discovery, research, maintenance, DevOps and support.
- Watch for: agree a cap and weekly reporting.
Moving between models
A common path: a fixed-price discovery and prototype, a fixed-price first version, then a dedicated team as the product grows. Agencies often use fixed price per client project, with a retainer when volume is steady; see white label development.
What should not change with the model
Code in your repository, IP assigned to you, written updates and regular demos. Read questions to ask a development partner before you sign.