Engagement Models & Rates
Structure moves total cost more than hourly does. Two clients paying identical rates can end up 40% apart on total spend — the difference is which engagement model carries the delivery risk.
The short version
| Model | What you're buying | Cost |
|---|---|---|
| Retainer | Monthly capacity, priorities can shift freely | Lowest effective rate |
| Time & Material | Hours at rate, scope fully open | Base market rate |
| Specific Deliverables | Defined deliverables on a defined date | Highest — 15–30% risk premium |
Engineer $125–185/hr · Senior $185–275/hr · Principal architect $350–500/hr · Blended team $200–300/hr · Advisory $500–700/hr or $3,000–4,500/day.
Most mature clients run a standing retainer with specific-deliverables phases layered on top — buying certainty only where certainty is worth paying for.
01/The three models
fixed effort
Reserve a defined block of our capacity each month, applied to whatever you've prioritized. Priorities can change monthly without renegotiating anything.
Lowest effective rate of the three models for ongoing work.
fixed rate
You pay for hours worked at agreed rates. Scope is fully open.
Base market rate. The purest reflection of what the work costs.
fixed outcome
We commit to defined deliverables, a defined date, and a defined price. If it takes longer than we estimated, that's our problem.
Highest of the three — a 15–30% risk premium above our internal estimate, more when the timeline is compressed.
Terms we state up front, because ambiguity here causes most retainer disputes
| Priority setting | You set priorities at the start of each cycle. Changing them mid-cycle is fine; we'll tell you what it displaces. |
| Unused capacity | Does not roll over. Capacity is reserved whether or not you use it. |
| Exhausted capacity | Work stops at the cap. We flag when you're approaching it. Additional work is billed at T&M or moves to the next cycle. |
| Production emergencies | Covered within the cycle, and they displace planned work. Sustained incident load is a signal to resize the retainer. |
| Between cycles | Unfunded periods are not covered. We don't carry unpaid work forward as goodwill — that habit ends badly for both sides. |
02/Fast · good · cheap — pick two
We don't quote the third combination. In regulated or production-critical systems, "not good" isn't a discount tier — it's a defect you pay for later with interest.
Retainer
You give up: Speed. Work lands in priority order at a sustainable pace.
Specific Deliverables, compressed timeline
You give up: Cost. Aggressive dates mean adding people, which means premium pricing — not margin, the actual cost of compression.
Not a tier we sell
Why not: Quality — which in production systems is a defect you pay for later. Compliance failures, security findings, and reconciliation errors all cost more to fix than to prevent.
03/Rates
Most engagements blend several roles.
| Role | Rate |
|---|---|
| Principal architect | $350 – $500 / hr |
| Senior engineer | $185 – $275 / hr |
| Engineer | $125 – $185 / hr |
| Typical blended team rate | $200 – $300 / hr |
Short-form advisory — architecture review, technical diligence, fractional CTO, strategy sessions — runs $500–700/hr or $3,000–4,500/day. You're buying judgment rather than delivery capacity, priced accordingly.
What moves the rate
04/Choosing
| Your situation | Model |
|---|---|
| Ongoing product work, priorities shift monthly | Retainer |
| Scope unclear, still in discovery | Time & Material |
| Clear scope, stable requirements, need budget certainty | Specific Deliverables |
| Need a specific outcome on a hard date | Specific Deliverables, with timeline premium |
| Need an expert opinion, not a delivery team | Advisory / day rate |
| Long-term partnership with occasional fixed milestones | Retainer with specific-deliverables phases |
That last row is the most common structure for mature clients: a standing retainer for continuous work, with discrete specific-deliverables statements of work for phases that need date certainty.
05/Before you sign anything
If your budget and your requirements disagree by more than about 40%, no engagement model fixes that — the scope isn't defined yet, and a specific-deliverables contract against an undefined scope guarantees change orders.
Moving from retainer to fixed-outcome transfers risk to us and reprices accordingly. That's not opportunism; it's the same work under different terms. If you anticipate needing fixed delivery later, tell us early so we can structure for it.
Reserved capacity you don't direct is capacity you paid for. We'll tell you when utilization is low rather than quietly banking it.
06/FAQ
Moving roadmap → retainer. Undefined scope → time & material. Hard date and stable scope → specific deliverables. Most mature clients run a standing retainer with specific-deliverables phases layered on top — buying certainty only where certainty is worth paying for.
The Specific Deliverables model includes a 15–30% risk premium above our internal estimate — higher on compressed timelines. We'd rather state that premium than hide it. If the project goes smoothly, you paid for insurance you didn't need. If it goes badly, you didn't pay for it — we did.
Retainer gets you good and cheap — you give up speed. A compressed Specific Deliverables engagement gets you good and fast — you give up cost. We don't quote fast + cheap: in production systems, "not good" isn't a discount tier, it's a defect you pay for later with interest.
Engineer $125–$185/hr. Senior $185–$275/hr. Principal architect $350–$500/hr. Typical blended team $200–$300/hr. Short-form advisory — architecture review, technical diligence, fractional CTO — runs $500–$700/hr or $3,000–$4,500/day.
If they disagree by more than about 40%, that's a scoping problem, not a pricing problem. No engagement model fixes it — signing a specific-deliverables contract against an undefined scope guarantees change orders. The scope needs defining first.
Further reading
We publish diligence guides on what software actually costs in regulated industries — written for buyers, including buyers who don't hire us.
Tell us your roadmap, how stable it is, and what your risk tolerance looks like — we'll tell you which model fits, including when the answer is that you don't need us yet.