Fixed price, retainer or staff augmentation: how to hire a software team

Fixed price

You agree what will be delivered, for how much, by when. The supplier carries the risk that it takes longer than expected.

• Good for: marketing sites, a defined first version, a migration, any project where you can describe the result in advance.
• The benefit: you know the cost before you commit.
• The catch: changes. Anything outside the agreed scope has to be discussed and priced, which slows things down if your requirements are still moving.

Fixed price works when both sides have understood the scope the same way. Time spent on a clear specification before signing is repaid several times over.

Monthly retainer

You buy an agreed amount of a team's time each month and decide, as you go, what it is spent on.

• Good for: a live product that keeps developing, where next month's priorities depend on this month's results.
• The benefit: you can change direction without renegotiating.
• The catch: it needs someone on your side to set priorities. Without that, a retainer drifts.

A retainer rewards a long relationship. The team learns the product and the business, and gets faster the longer it works with you.

Staff augmentation

Engineers join your team and work under your leads, on your process, for a period.

• Good for: an in-house team that needs capacity for a deadline, or a skill it lacks.
• The benefit: you keep full control of what gets built and how.
• The catch: you also keep the responsibility. Direction, review and delivery remain yours.

This model assumes you have technical leadership. Adding engineers to a team with no clear direction produces more activity and no more progress.

Where each one goes wrong

• Fixed price on an unclear scope turns every conversation into a negotiation about what was included.
• A retainer with nobody setting priorities spends money steadily on whatever is nearest.
• Staff augmentation without leadership leaves capable people waiting to be told what to do.

In each case the people and the code may be perfectly good. The model was wrong for the work.

How to choose

• Can you describe the finished result today? Fixed price.
• Will priorities shift as you learn? A retainer.
• Do you have a team and a technical lead, and need more capacity? Staff augmentation.

Many working relationships use more than one. A fixed-price first version followed by a retainer to develop it is common, and it fits how products actually grow: a defined start, then continuous change.