Software development outsourcing cost guide: rate cards, hidden costs, and TCO
What you actually pay to outsource software — the pricing models, the costs that never appear on the rate card, and a total-cost-to-ship framework that stops you optimising for the wrong number.
- There are four common pricing models — fixed price, time & materials, dedicated pod, and ODC — and they allocate risk differently. The right one depends on how well-defined and how long the work is.
- The hourly rate is the most-compared and least-useful number. Hidden costs — rework, management overhead, ramp time, churn — often dwarf the rate difference.
- Compare on total cost to ship and run, not rate. A low rate with high rework is the expensive option.
- Fixed price suits small, fully-specified scopes; T&M suits evolving work; a dedicated pod suits ongoing products; an ODC suits scaling a function long-term.
The rate is not the cost
Outsourcing pricing looks simple — an hourly or monthly rate — which is exactly why teams optimise the wrong number. The rate is the most visible figure and the easiest to compare across vendors, so it dominates decisions. But what you ultimately pay is the *total cost to ship and run the software*: the rate, plus everything around it that the rate card never shows.
This guide covers the four pricing models you'll be quoted, how each allocates risk, the costs that hide beneath the rate, and a simple way to compare offers honestly. It pairs with how to choose an engagement model — the model and the pricing are two sides of the same decision.
The four pricing models
Each model moves risk between you and the partner differently. Match the model to how well-defined and how long-lived the work is.
| Fixed price | Time & materials | Dedicated pod | ODC | |
|---|---|---|---|---|
| You pay for | A defined scope, one price | Actual time and effort | A standing team, monthly | A managed function, per head + ops |
| Best for | Small, fully-specified scopes | Evolving or uncertain work | Ongoing products and roadmaps | Scaling a whole function long-term |
| Who carries the risk | Partner (priced in) | You (you fund changes) | Shared | Shared, lowest per-head |
| Flexibility to change scope | Low — change orders | High | High | High |
| Cost predictability | Highest up front | Lower — varies with effort | High — fixed monthly | High at scale |
| Watch out for | Padding + change-order friction | Scope creep without a cap | Paying for ramp/idle if mismanaged | Churn erasing the saving |
A total-cost-to-ship framework
- Start with the quoted rate or monthly cost — the visible number.
- Add expected rework: how much gets redone? Strong process and seniority push this down.
- Add your management overhead: hours your team spends coordinating, multiplied by their cost.
- Add ramp: weeks to productivity per engineer, and how often you'll pay it (a function of churn).
- Compare the totals, not the rates. The lowest total cost to ship almost never has the lowest rate.
How we price, and why
We've delivered under all four models since 2008, and we pick the one that fits the work rather than the one that looks cheapest on paper. Fully-specified, bounded scope can take a fixed price; evolving work runs on time-and-materials with a clear cap; an ongoing product runs as a dedicated team on a fixed monthly pod rate; scaling a function runs as an offshore development centre. In every case we optimise for low rework and retention, because that's what makes the total cost low — not the headline rate.
If you want a straight read on what your build should cost and which model fits, book a 30-minute call. No sales pitch — an engineer's estimate and the trade-offs.