Fixed Price, Dedicated Team or Advisory: Which Engagement Model Fits?
The right engagement model depends on how well you know what you are building. Know it precisely and fixed scope works. Discovering as you go favours a dedicated team. Needing direction rather than hands favours advisory.
The short answer
Choose fixed scope when you can describe the finished product precisely and want a known price. Choose a dedicated team when the product will evolve and you want steady capacity. Choose advisory when you already have engineers and need senior direction, review or architecture rather than extra hands. Most disagreements about cost and quality trace back to using the wrong model for the situation.
Fixed scope
In a fixed-scope engagement the vendor agrees to deliver a defined set of features for a set price and date. It gives you predictability, and the vendor carries the risk of misjudging the effort. That risk has a cost: vendors add a buffer to the price, and anything outside the written scope becomes a change request.
When it works
- The requirements are stable and written down in detail
- The technology is well understood, with few unknowns
- You need a fixed budget for approval
- The project is bounded, such as a marketing site, a migration or an integration
Where it breaks
Software rarely stays still. If you learn something during the build, which you usually do, a rigid scope turns each learning into a negotiation. Teams then stop proposing improvements, and you can end up with exactly what was specified and not what you need. The remedy is a thorough discovery phase before the fixed price is set.
Dedicated team
A dedicated team is a group of engineers, and often a designer and a tester, working on your product on a monthly basis. You set priorities and can change them every sprint. The vendor is accountable for the quality and pace of the team, not for a fixed list of features.
When it works
- The product is new and learning is part of the job
- You expect continuous development after launch
- You want one group to build up knowledge of your domain
- You have a product owner who can prioritise weekly
Where it breaks
Without a clear owner on your side, priorities drift and the team works on whatever is loudest. Budget is also open-ended unless you set a ceiling and review it. The cure is a named product owner, a visible backlog and a regular demo.
Advisory
Advisory engagements put senior engineers alongside your own team for a defined purpose: an architecture review, a security assessment, a technology selection, a plan for scaling, or interim technical leadership. You pay for judgement, not for output volume.
When it works
- You have developers but lack senior experience in one area
- A major decision, such as a rewrite or a cloud move, needs a second opinion
- You want a check before committing to a vendor or a design
Where it breaks
Advice that nobody has time to act on is wasted. Agree up front who will implement the recommendations and when they will be reviewed.
| Fixed scope | Dedicated team | Advisory | |
|---|---|---|---|
| Best for | Well-defined, bounded projects | Evolving products | Decisions and reviews |
| You pay for | A defined outcome | Team capacity each month | Senior time |
| Flexibility | Low, changes are negotiated | High, reprioritise each sprint | High |
| Main risk | Building the wrong thing precisely | Drift without a product owner | Advice not acted on |
| Your effort | Up-front specification | Weekly prioritisation | Making time to act |
Mixing the models
The best engagements often combine them. A common pattern is a short fixed-price discovery that produces a specification and a plan, followed by a dedicated team that builds against it, with an occasional advisory review at key points such as before launch. Another is a fixed-scope first release to reach the market, then a smaller dedicated team to iterate.
This is also how we usually work: discovery first, so scope and risk are understood before anyone commits to a larger number. The three pathways we offer are set out on engagement models, and the delivery cadence is on how we work.
How to choose in five questions
- Can you describe the finished product in enough detail to test it? If yes, fixed scope is possible.
- Will you learn things during the build that change the plan? If yes, favour a dedicated team.
- Do you have a person who can prioritise every week? If not, a dedicated team will drift, so appoint one or choose fixed scope.
- Is the real need a decision or a review? If so, advisory is cheaper and faster than a build.
- Is there a hard budget ceiling? Then a fixed price or a capped team size fits better than open-ended capacity.
If you are unsure, start with a small paid discovery. It will show which model fits, and it is a low-risk way to see how a vendor works. Talk to us through the contact page when you want to compare models for your project.
Which model is cheapest?
It depends on how well the scope is known. A fixed price is cheapest when the scope is genuinely stable. When it is not, change requests and rework can make it more expensive than a team that adapts.
Can we move from fixed scope to a dedicated team later?
Yes, and many projects do after the first release. Keep the repository and environments in your own accounts so the change of model does not require a handover.