Think Build Implement Repeat
London, UK +44 7367 067226
WhatsApp FOLLOW f in X
  1. Home
  2. Blog
  3. Staff Augmentation Versus a Fixed Price Project
Software Strategy

Staff Augmentation Versus a Fixed Price Project

Two ways to buy the same engineering. Which one fits depends on how well you can define the work and who should carry the risk of being wrong.

Updated 2 min readBy SpiderHunts Technologies

Free estimateNo obligation

Get a free estimate

Tell us what you need. A senior engineer reads every enquiry.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →

Quick answer — TL;DR

Fixed price suits work you can specify precisely and will not change. Augmentation suits work that will evolve. Buying fixed price for evolving work produces change requests and an adversarial relationship, which costs more than either model.

The short answer

Can you specify what is being built precisely enough that both sides would agree whether it was delivered? If yes, fixed price is available and transfers risk to the supplier. If no, fixed price will produce a change request every fortnight and both sides will be unhappy.

Most product work falls into the second category, which is why augmentation and time-based models dominate it.

What each model actually buys

Fixed priceAugmentation
Who carries scope riskSupplierYou
Flexibility to change directionLow, via change requestsHigh
Cost certaintyHigh, for the agreed scopePredictable rate, variable total
Specification effort up frontHighLower
Incentive on the supplierFinish efficientlyBe useful enough to retain
SuitsDefined, stable workEvolving work

The incentive row is worth reading carefully. Fixed price rewards finishing quickly, which is aligned with you on scope and not always on quality. Augmentation rewards staying, which is aligned on quality and not on speed. Neither is inherently better.

Where fixed price works well

  • A defined integration with a documented third party
  • A migration with an agreed end state
  • A website or marketing site with an approved design
  • A specific piece of infrastructure with clear requirements
  • Anything you have done before and can describe exactly

What these share is that both sides can tell whether it is finished. That is the test, and it is more demanding than it sounds.

Where it goes wrong

Fixed price for a product still being figured out. The specification is a guess, reality intervenes, and every adjustment becomes a commercial negotiation rather than a conversation.

The visible symptom is a relationship where both sides are reading the contract. That is expensive in time and worse in goodwill, and it usually costs more than the flexible model would have.

A hybrid that works

  1. Fixed price for a short discovery, producing a specification and an estimate.
  2. Decide at that point whether the work is definable.
  3. If it is, fixed price the build against the specification you now have.
  4. If it is not, move to augmentation with the discovery as the starting point.
  5. Either way you have paid a small amount to remove the largest uncertainty.

This is usually the honest answer when neither side can yet say how big the work is.

The question to ask a supplier

Ask which model they would recommend and why. A supplier who always recommends the same one regardless of the work is telling you about their business model rather than about your project.

A good answer engages with how well defined your work is, and is willing to say that fixed price is not appropriate here even though it sounds more reassuring.

FAQ

Frequently asked questions

The questions readers ask us after this guide.

Still have a question?

Ask us directly — a senior engineer will get back to you.

Ask about your project

Is fixed price safer?

It transfers scope risk, which is valuable when scope is stable. When scope moves, it converts every change into a negotiation, which is its own cost.

Can we start fixed price and switch?

Yes, and a fixed-price discovery followed by a decision is a common and sensible shape.

Why do suppliers prefer time-based models?

They carry less risk, and for genuinely undefined work that risk is large. A supplier pricing undefined work fixed will add contingency you pay for whether or not it is needed.

What about milestone payments?

They work with either model and are worth having. They give both sides a checkpoint without requiring the whole scope to be fixed.

Keep reading

More on Software Strategy

Software Strategy

Machine Learning Myths That Waste Budgets

Eight beliefs about machine learning that quietly inflate project costs, what is actually true instead, and how to spot each one in a proposal.

Start here

Thinking about adding developers to your team?

Tell us what you are building, what your team looks like now and where the gap is. We will come back with an honest view on whether augmentation fits, how many people it would take and what it costs. If hiring directly would serve you better, we will say so.

  1. You tell us what you needTwo minutes on the form, or a message on WhatsApp.
  2. A senior engineer reviews itAnd comes back with questions, a realistic range and an honest view on fit.
  3. Free 30-minute scoping callWe talk through scope, options and a realistic estimate — with no obligation.
Free estimateNo obligation

Talk to someone who builds this

Send a short brief and we will come back with an honest view and a realistic range.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →