The hourly rate is the number every vendor leads with and the one that matters least. Two engineers quoted at the same rate can differ by a factor of three in what they actually cost you, once ramp-up, management load, and utilisation are counted honestly.
This is a breakdown of the full cost structure, aimed at someone holding a proposal and trying to work out whether it’s reasonable.
How augmentation is priced
Hourly. You’re billed for hours worked, usually against a monthly cap. Flexible, and the right structure for part-time or spiky needs. The risk is administrative: someone on your side has to review timesheets, and nobody ever wants that job.
Monthly rate per engineer. A flat fee for a full-time allocation. Simpler, easier to budget, and the dominant model for engagements beyond a couple of months. Watch the definition of full-time — the number of working days differs across markets, and public holidays in the delivery country are usually excluded.
Retainer for a capacity block. You buy a pool of hours across several people. Useful when the work genuinely varies. It’s also the model where money quietly evaporates if nobody tracks consumption, so insist on monthly burn reporting.
For most engagements, monthly-per-engineer is the cleanest to compare and the hardest to game.
What drives the rate
In rough order of impact:
- Seniority. The gap between a mid-level and a senior engineer is the single largest factor, and usually the best money you’ll spend. Senior engineers cost more per month and frequently less per outcome.
- Delivery location. The largest structural difference. Rates in India, Eastern Europe, Latin America, Western Europe, and North America occupy genuinely different bands.
- Scarcity of the skill. Mainstream stacks — React, Node, Python, .NET — sit at the market rate. Specialised work such as machine-learning engineering, embedded, or regulated-domain experience carries a real premium.
- Engagement length. Longer commitments earn better effective rates, because the vendor amortises recruitment and bench risk over more months. Three, six, and twelve-month commitments typically step down in price.
- Team composition. A quoted “team rate” that bundles QA or a delivery lead isn’t comparable to a bare engineer rate. Normalise before you compare.
Published rate ranges vary so widely by source, seniority definition, and date that quoting a single figure would be misleading. Get two or three real quotes for your stack and seniority; that’s the only benchmark that means anything.
The four costs that don’t appear on the invoice
1. Ramp-up
An engineer joining an existing codebase is not productive on day one. For a documented codebase with a ready backlog, expect meaningful output inside two weeks. For an undocumented one, four to six is realistic.
You pay full rate throughout. On a three-month engagement, a four-week ramp means you’re paying for three months and receiving roughly two — which is exactly why very short augmentation engagements are poor value, and why vendors who agree to them without comment aren’t doing you a favour.
2. Your own management time
Augmented engineers are directed by your managers. If a lead spends six hours a week on planning, review, and unblocking for three augmented engineers, that’s a meaningful slice of a senior salary consumed by the engagement, and it never appears in the comparison.
Count it. If your lead has no spare capacity, augmentation may cost more in delivered value than a dedicated team that brings its own coordination.
3. Idle capacity
Under a monthly model you pay whether or not there’s work ready. Gaps appear during specification delays, design bottlenecks, or a long review queue on your side. Utilisation below 70% is common in poorly-prepared engagements and it doubles your effective rate.
4. Knowledge that leaves
When a contract ends, context goes with it unless you’ve deliberately kept it. The cost lands six or twelve months later, when something needs changing and nobody in your building understands why it was built that way. Mitigate it during, not after: written decision records, pairing on anything critical, and your own engineer reviewing the pull requests.
Comparing against a permanent hire
The honest comparison isn’t rate versus salary. It’s fully-loaded cost versus fully-loaded cost, including the things a hire brings that a contractor doesn’t.
| Augmented engineer | Permanent hire | |
|---|---|---|
| Direct cost | Monthly rate | Salary + employer taxes + benefits |
| Recruitment | Included | Agency fee or internal recruiter time |
| Time to start | Days to weeks | Months, including notice period |
| Equipment, software, workspace | Vendor’s cost | Yours |
| Time off, sickness | Vendor absorbs | You absorb |
| Cost to stop | Notice period | Redundancy process |
| Retention risk | Vendor’s problem | Yours |
| Long-term context | Leaves at contract end | Compounds year on year |
A permanent hire is almost always cheaper over a multi-year horizon and always slower to start. That’s the actual trade: augmentation buys speed and reversibility, and you pay a premium for both. When the need is genuinely long-term and the role is core to your product, hire. When it’s a capacity gap, a deadline, or a skill you need for nine months, augmenting is usually the better economics even at a higher headline rate.
Questions that expose a weak quote
- What exactly is included in “full time” — how many days a month, and whose public holidays?
- Is the named engineer allocated to us exclusively, or shared across accounts?
- What’s the notice period, in both directions?
- What happens if the engineer leaves the vendor mid-engagement — who pays for the replacement’s ramp-up?
- Is there a discount at three, six, or twelve months, and what triggers it?
- What’s the rate for a genuine senior versus the mid-level you’ve quoted?
The last one is worth asking even if you don’t intend to buy senior. A vendor who can’t articulate the difference is selling you bodies, not engineers.
Frequently asked questions
Is staff augmentation cheaper than hiring? In the first year, usually yes, because there’s no recruitment cost and no idle notice period. Over three years, a permanent hire is normally cheaper. Choose on how long the need genuinely lasts, not on the monthly figure.
Why do vendors quote monthly instead of hourly? It’s simpler to budget and removes timesheet overhead for both sides. It also means you absorb the cost of any idle capacity, so it rewards you for keeping the backlog ready.
Should I pay a deposit or advance? A first-month advance is common and reasonable. Multi-month prepayment in exchange for a discount is a bet on the relationship working — worth taking only after you’ve seen a month of delivery.
What’s a realistic minimum engagement? Three months. Below that, ramp-up consumes too much of the term for either side to get value — which is also why a vendor happy to sell you four weeks isn’t necessarily doing you a service.
Internal links: #1 engagement models, #6 developer cost by region, #8 fixed price vs T&M, /services, /contact. External references: your own market quotes; national statistics offices for employer on-cost percentages when modelling the permanent-hire column. CTA: “Want a straight quote for your stack and seniority? Tell us what you need.” → /contact