Embedded-specialist pricing has a long history of looking simple and being deceptive. Two vendors quote different hourly rates, the cheaper quote wins, and months later part of the work has been redone. The hourly rate is rarely the metric that matters.
The four factors that matter
- Effective seniority. What the engineer can ship in a day, not what their CV says. Ask for a working session or a code review, not a résumé walkthrough.
- Replacement terms. When a placement isn't working, how long does a replacement take, and who bears the cost of the gap? Get the answer in writing before you sign.
- Onboarding overhead. In the first weeks, an embedded engineer costs the team some velocity before adding to it. Decide up front who absorbs that cost.
- Coordination. A service lead who handles contracts, payroll, and time-off is real value. Without one, your engineering manager absorbs the vendor administration.
What an honest agreement makes visible
A clear agreement states the fee per role, how onboarding is handled, what happens when a placement is not working, and who your accountable contact is. Anything more complex is usually obfuscation.
Where rates stop being comparable
Rates are only comparable when seniority, scope, time zone, and language coverage are comparable. A low rate can hide a seniority gap. A high rate can hide a brand premium. Compare the total cost to your team, not the number on the quote.
When fixed scope beats embedded specialists
Embedded specialists win when scope is changing weekly. Fixed scope wins when the deliverable is well understood and the client wants risk transferred. Many automation programs end up running both at once: fixed scope for the first bot, embedded specialists for the long tail.