The Blended Rate Illusion
Every multi-tier delivery organisation reports a blended rate to its clients: a single number that averages onshore, nearshore, and offshore costs into one per-hour or per-FTE figure. The blended rate is convenient. It's also a margin trap.
Consider a standard three-tier engagement:
| Tier | Client Rate | Delivery Cost | Margin | FTE Mix |
|---|---|---|---|---|
| Onshore (lead, governance) | $165/hr | $136/hr | 17.5% | 30% |
| Nearshore (execution) | $95/hr | $62/hr | 34.7% | 45% |
| Offshore (volume work) | $55/hr | $28/hr | 49.1% | 25% |
| Blended | $106/hr | $73/hr | 31.5% | 100% |
The blended margin is 31.5%. Looks healthy. But the onshore tier — which carries governance, client management, and escalation work — runs at 17.5%. Offshore subsidises onshore. The “healthy” margin exists only in the aggregate.
Bottom Line
A healthy blended rate can mask an underwater tier. If you don't track margins per delivery tier, you can't see where money actually goes.
Where Money Disappears in Blended Models
Four patterns consistently erode margin in multi-tier delivery. All are invisible at the blended level.
Pattern 1: Tier Drift
Work sold as nearshore or offshore gradually migrates onshore. A “quick” client call becomes a regular governance meeting. An offshore developer joins onshore standups daily. The FTE mix shifts from the quoted 30/45/25 toward 40/40/20. Each percentage point of drift toward onshore reduces margin because onshore has the lowest margin of the three tiers.
Pattern 2: Rate Leakage
Contract rates don't reflect actual delivery costs. Senior resources bill at mid-tier rates because the contract was written for “consultant” level. Onshore rates don't account for the fully-loaded cost of benefits, management overhead, and facility allocations. The gap between contract rate and actual cost widens over time as costs increase but rates stay fixed.
Pattern 3: Contractor Stacking
When internal capacity is full, contractors fill the gap. But contractor rates often exceed internal costs — an contractor might cost $145/hr while the billable rate to the client is $165/hr. The margin on contractor-filled positions is 12% versus 25% for internal staff. If contractors fill 20% of onshore positions, the tier margin drops further. This pattern is especially dangerous because it's invisible in headcount reporting — a role is “filled” regardless of whether it's internal or contractor.
Pattern 4: SLA Penalty Exposure by Tier
SLA penalties typically attach to the engagement, not the tier. But when a breach occurs, the root cause is usually tier-specific: onshore response time missed, offshore resolution quality below threshold. Without per-tier SLA tracking, penalties hit the engagement P&L as a lump cost with no attribution to the tier that caused the breach.
Bottom Line
Tier drift, rate leakage, contractor stacking, and unattributed SLA penalties are the four margin killers in blended delivery. All four are invisible at the blended rate level.
What Per-Tier Visibility Looks Like
Per-tier visibility means tracking revenue, cost, and margin at the delivery tier level, not just the engagement level. Compare the two views:
| Metric | Blended View | Per-Tier View |
|---|---|---|
| Margin | 31.5% blended, looks healthy | 17.5% onshore, 34.7% nearshore, 49.1% offshore, with onshore at risk |
| Cost driver | $73/hr average with no actionable insight | $136/hr onshore, where contractor stacking is the specific driver |
| Mix drift | Invisible, total FTEs unchanged | Onshore mix increased from 30% to 38% over 3 months |
| SLA impact | $12K penalty at engagement level | $12K caused by onshore response time, tied to a specific tier and metric |
| Pricing decision | Blended rate of $106 seems competitive | Onshore rate needs to be $175+ to hit margin target |
Bottom Line
Blended view = “we're at 31.5%, fine.” Per-tier view = “onshore is at 17.5%, contractor stacking is the driver, and we need to renegotiate the onshore rate or rebalance the mix.”
Building Per-Tier P&L: Three Structural Requirements
Requirement 1: Delivery party attribute
Every cost and revenue line item needs a “delivery party” tag identifying which tier produced the work. This is the foundational data attribute that enables per-tier reporting. Without it, all costs aggregate at the engagement level. The delivery party connects to a rate hierarchy and enables cost attribution by tier.
Requirement 2: Rate hierarchy per tier
Each tier needs its own rate structure: contract rates (what the client pays), internal costs (what you pay your people), and contractor rates (what you pay external staff). Blended models typically have one contract rate per role level. Per-tier P&L requires rate granularity: onshore senior developer at $165/hr client rate and $136/hr internal cost versus nearshore senior developer at $95/hr and $62/hr.
Requirement 3: Trigger-based cost calculation
When hours are logged against a delivery tier, the system should automatically calculate the cost using the tier-appropriate rate, not the blended rate. This is where most manual processes break down — someone has to manually apply the right rate to each set of hours. Automated triggers (hours × tier rate = cost) eliminate this friction.
Bottom Line
Per-tier P&L requires three structural elements: delivery party tagging, tier-level rate hierarchies, and automated cost calculation. These are data model decisions, not reporting decisions.
The Portfolio Impact
Per-tier visibility becomes even more powerful at the portfolio level. When you can compare tier performance across engagements, patterns emerge:
- Which engagements have the healthiest delivery mix? Some maintain the quoted 30/45/25. Others have drifted to 45/35/20.
- Where is contractor stacking concentrated? If three engagements use heavy contractor onshore, that's a capacity planning issue, not an engagement issue.
- Which tiers consistently underperform? If onshore margin is below target across 70% of engagements, the onshore rate is wrong, not the individual engagements.
Portfolio-level tier visibility changes the strategic conversation from “how do we fix this engagement” to “how do we fix our onshore pricing model” or “how do we reduce our contractor dependency in tier 1.”
How DigitalCore Supports Per-Tier Visibility
DigitalCore implements per-tier P&L as a core data model feature, not a reporting overlay.
Delivery party attribute
Every plan, measure, and cost line carries a delivery party tag: onshore, nearshore, offshore, or custom tiers.
Rate hierarchy
Contract rates, internal costs, and contractor rates defined per tier per engagement. Rate lookups follow the hierarchy automatically.
Trigger-based calculation
Capacity hours × tier-appropriate rate = cost. Cross-domain triggers fire automatically when actuals are recorded.
Mix drift tracking
Compare actual vs planned FTE mix per tier over time. Alerts fire when drift exceeds thresholds.
Portfolio tier analysis
Compare tier margins, contractor ratios, and mix patterns across all engagements in one view.
FAQ
What is the blended rate problem in multi-tier delivery?
A blended rate averages the cost and revenue across all delivery tiers into a single number. This creates a “healthy” margin number that can hide individual tiers losing money. An engagement showing 31.5% blended margin might have an onshore tier at 17.5% while offshore subsidises the difference at 49%.
What is tier drift and how does it affect profitability?
Tier drift occurs when work gradually migrates from lower-cost tiers to higher-cost tiers. Nearshore work moves onshore for client convenience. Offshore developers join onshore ceremonies. Each percentage point shift toward the highest-cost tier directly reduces margin because onshore has the lowest margin percentage.
How do I implement per-tier P&L tracking?
You need three structural elements: (1) a delivery party attribute on every cost and revenue line, (2) rate hierarchies defined per tier per engagement, and (3) automated triggers that calculate costs using tier-appropriate rates. These are data model decisions, and you can't add them through reporting alone.
How does contractor stacking erode margins?
Contractors typically cost more than internal staff ($145/hr vs $110/hr internal), but bill at the same rate to the client. If a contractor fills an onshore slot billing at $165/hr, the margin drops from 33% (internal) to 12% (contractor). At 20% contractor fill, the tier margin can drop by 4-5 percentage points.
Can per-tier visibility help with multi-tier pricing?
Yes. Per-tier data reveals whether your onshore rates cover your actual costs. Many organisations discover their onshore rate needs to be 10-15% higher, or their mix commitment needs to be more aggressive toward offshore. The Pricing Blended Delivery Models guide covers the pricing methodology in detail.
Related Guides
Pricing Blended Delivery Models
Set per-tier rates that protect margin while remaining competitive.
Automated P&L Per Engagement
Live engagement profitability without month-end spreadsheet assembly.
Client Profitability Analysis
See which clients generate margin and which erode it.
Total Cost of Delivery
See the full cost picture: labour, vendors, infrastructure, SLA penalties, overhead.