Published
How Resource-Based Estimating Changes What a Proposal Is Worth
Most studios price proposals based on gut feel and market rates. Resource-based estimating inverts this: the fee is derived from what delivery actually costs. This shifts everything.
Author:
Alice Hart
Estimated reading time: 9 minutes
A hospitality client requests a proposal. The brief is clear: 5,000 sq ft restaurant fit-out, concept through detailed design and tender documentation. You sit down to price it.
You think through the project phases. You estimate it'll take 4 months. You check what similar projects cost historically. You adjust for complexity and client expectations. You factor in what competitors might charge. You land on a fee: £180,000.
The proposal goes out. The client signs. The project starts.
Six months later, the project is 80% complete. Your team has logged 2,400 hours. At your studio's blended rate, that's £240,000 worth of time. Against a £180,000 fee. The project is 33% over budget.
This wasn't poor execution. The team did excellent work. The client is happy. But the proposal was underpriced from the start. You just didn't know until it was too late to fix.
Resource-based estimating prevents this. Instead of pricing from market intuition, you build the fee from delivery reality: the roles required, the hours per phase, the rates that generate target margin. The proposal goes out knowing exactly what it costs to deliver - and whether the fee covers it.
"Your proposals aren't connected to what it actually costs to deliver."
This is the realisation that drives studios to resource-based estimating. Not "we need better pricing strategy" — but "we need to know if we can deliver at this fee before we agree to it."
The Problem: Most Studios Price Backwards
Here's how most design studios price proposals:
Start with a fee that feels right - based on project size, historical precedent, or market rates
Check if it's competitive - adjust down if it seems high relative to what competitors might charge
Send the proposal - hope the fee is adequate
Build the resource plan after winning - figure out how to deliver at the agreed fee
Discover margin erosion mid-delivery - realise too late that the project costs more than anticipated
This is pricing backwards. The fee is set before delivery planning happens. If the resource model shows the project can't be delivered profitably at the contracted amount, the studio has three bad options: compress scope (lower quality), ask the team to work unpaid overtime (unsustainable), or absorb the margin hit (profit leakage).
Resource-based estimating inverts this sequence:
Build the resource plan first: Estimate hours by role, by phase, at defined rates
Calculate the fee from the plan: Derive total cost from actual delivery requirements
Check if the fee is deliverable: Verify the project can be executed at target margin
Send the proposal with confidence: Know exactly what the fee covers
Track actual vs estimated during delivery: Course-correct in real time if variance appears
The fee isn't a guess. It's a calculation. And because it's derived from resource reality, the studio knows — before the proposal goes out — whether the project is profitable.
What Resource-Based Estimating Actually Looks Like
The mechanics are straightforward. The shift is structural.
Step 1: Break the Project into Phases
Every design project moves through phases. A typical commercial project includes Mobilization, Briefing, Concept Design, Schematic Design, Detailed Design, Tender Documentation, Construction Supervision, and Client Handover. Each phase has different resource requirements: Concept Design is design-heavy, Detailed Design is CAD-intensive, Tender is documentation-focused, Construction Supervision requires site presence.
Step 2: Estimate Hours by Role, by Phase
For each phase, estimate how many hours each role will contribute. Example for a 5,000 sq ft restaurant fit-out:
Role | Mobilization | Briefing | Concept | Schematic | Detailed | Tender | Construction | Handover |
|---|---|---|---|---|---|---|---|---|
Director of Design | 6h | 8h | 20h | 15h | 10h | 5h | 12h | 4h |
Senior Designer | 12h | 20h | 60h | 80h | 60h | 20h | 30h | 8h |
CAD Junior | 4h | 8h | 20h | 60h | 120h | 80h | 40h | 8h |
Visualizer | 0h | 4h | 30h | 40h | 20h | 0h | 0h | 0h |
Technical Manager | 4h | 8h | 10h | 20h | 40h | 60h | 20h | 8h |
Phase Total | 26h | 48h | 140h | 215h | 250h | 165h | 102h | 28h |
Total project hours: 974
This isn't guesswork. Studios that track time properly know, from historical data, approximately how many hours each role spends per phase on comparable projects. The estimate is evidence-based.
Step 3: Apply Cost and Billing Rates
Each role has a cost rate (what it costs the studio per hour) and a billing rate (what the studio charges clients per hour). The difference is margin.
Role | Total Hours | Billing Rate | Billable Value |
|---|---|---|---|
Director of Design | 80h | £150/h | £12,000 |
Senior Designer | 290h | £95/h | £27,550 |
CAD Junior | 340h | £60/h | £20,400 |
Visualizer | 94h | £80/h | £7,520 |
Technical Manager | 170h | £110/h | £18,700 |
Project Total | 974h | £86,170 |
Proposed fee: £86,170 — Total cost: £50,530 — Gross margin: £35,640 (41.4%)
This is the actual fee calculation. It's not market-driven. It's resource-driven. The studio knows exactly what delivery costs, and what margin the fee generates.
Step 4: Validate Against Market and Client Expectations
Now the studio has a resource-justified fee. The next question: is this deliverable in the market context?
If the client's budget is £60,000 and the resource model says £86,000, the studio has options:
Option A: Adjust scope — reduce phases, limit deliverables, narrow responsibilities. Build a £60,000 project that's actually deliverable at that fee.
Option B: Adjust resourcing — shift more hours to junior roles, reduce senior oversight, optimise efficiency. This lowers cost but may impact quality.
Option C: Walk away — if the project can't be delivered profitably at the client's budget, it's a bad deal. Politely decline.
What the studio does NOT do: quote £60,000 without adjusting the resource plan, then absorb the margin hit mid-delivery. That's the pattern resource-based estimating breaks.
Studios using CRM for interior design studios with built-in estimating tools report making this validation before the proposal goes out, not after — because the resource model and the opportunity record are in the same system.
Step 5: Track Actual vs Estimated During Delivery
Once the project starts, the estimate becomes the baseline. As the team logs time, the studio sees in real time whether delivery is tracking to estimate or running over.
Role | Estimated Hours (50%) | Actual Hours Logged | Variance |
|---|---|---|---|
Director of Design | 40h | 44h | +4h (+10%) |
Senior Designer | 145h | 162h | +17h (+12%) |
CAD Junior | 170h | 158h | −12h (−7%) |
Visualizer | 47h | 52h | +5h (+11%) |
Technical Manager | 85h | 78h | −7h (−8%) |
Midpoint Total | 487h | 494h | +7h (+1.4%) |
The project is tracking slightly over estimate — 1.4% variance at midpoint. Not alarming, but worth monitoring. If variance hits 10–15%, there's still time to course-correct.
This is the operational shift studios report when they move to project management software for interior designers that connects estimating to time tracking: profitability visibility exists during the project, not after.
What Changes When Estimating Connects to Pricing
Resource-based estimating doesn't just improve pricing accuracy. It changes the entire relationship between sales, delivery, and financials.
Proposals Are Defensible |
|---|
When a client pushes back on price, the studio can explain exactly what the fee covers. "This project requires 974 hours across these roles and phases. Here's the breakdown." The conversation shifts from "you're too expensive" to "what scope adjustments would bring this to your budget?" The studio isn't justifying a number that feels right. They're explaining a resource model. |
Margin Is Visible Before the Deal Is Won |
|---|
Most studios discover profitability after delivery. Resource-based estimating surfaces margin before the proposal goes out. If the model shows 15% margin and the target is 35%, the studio knows immediately: either the fee needs to increase, the scope needs to reduce, or the opportunity isn't worth pursuing. This prevents studios from winning work they can't deliver profitably. |
Underpricing Becomes Visible |
|---|
When studios price from market intuition, systematic underpricing is invisible. Each loss feels like bad luck or tough competition. Resource-based estimating reveals patterns: "We've lost four hospitality projects this year because our pricing is systematically 20% below what delivery costs. Either we adjust pricing or exit that sector." The pattern is only visible when proposals connect to resource reality. |
Senior Time Is Allocated Strategically |
|---|
Without resource-based estimating, senior time goes to whoever asks loudest. With it, studios see exactly where senior capacity is allocated and what return it generates. If the Director of Design is spending 40 hours per quarter on proposals that don't convert, that's visible — and fixable. Studios running on interior design management software with resource visibility report better allocation of senior effort: less time on low-probability opportunities, more time on high-value delivery and strategic pursuits. |
Delivery Teams Know the Target |
|---|
When a project starts without resource context, the delivery team is blind. They don't know how many hours were estimated, what margin the project is targeting, or where they should be cautious about scope. Resource-based estimating gives delivery teams the baseline from day one: "This project estimated 290 hours for Senior Designer, 340 for CAD Junior, 170 for Technical Manager. We're tracking against that." The team delivers to a plan, not a hope. |
Why Studios Resist (And Why Resistance Fades)
Objection 1: "It takes too long." |
|---|
Building a detailed estimate feels like it adds hours to the proposal process. Why spend 6 hours estimating when you could just quote a fee in 30 minutes? The answer: because the 6 hours spent estimating properly are recovered tenfold in reduced rework, fewer over-budget projects, and better margin control. Studios using resource-based estimating inside their CRM report that the process accelerates after the first few proposals. Once roles, phases, and rates are standardised, building an estimate is a 20-minute exercise, not a 6-hour project. |
Objection 2: "Clients don't care about our resource model." |
|---|
Correct — clients care about outcomes, not hours. But the resource model isn't for the client. It's for the studio. It ensures that the fee quoted is actually deliverable at target margin. The client sees the final number and the scope. The studio sees the logic behind it: the hours, the roles, the phases, the margin. This protects both parties: the client gets realistic pricing, and the studio avoids committing to unprofitable work. |
Objection 3: "We'll price ourselves out of the market." |
|---|
This is the hardest objection because it's grounded in real competitive pressure. If resource-based estimating reveals that a project costs £120,000 to deliver but the market expects £90,000, the studio faces a choice: walk away, or compress scope to fit the budget. Walking away feels like lost opportunity. But winning work that can't be delivered profitably is worse — it consumes capacity without generating margin. The studio is busy, but not profitable. Studios that internalize resource-based estimating stop competing on price and start competing on value. They win fewer opportunities, but the ones they win are profitable. Growth becomes sustainable instead of exhausting. |
The Pricing Rule That Changes Everything
Price from capacity reality, not market pressure. If the fee doesn't cover the resource investment at target margin, the project is a bad deal — even if the client is prestigious.
This rule is uncomfortable at first. It means walking away from opportunities that would have been pursued historically. It means telling potential clients "we can't deliver that scope at that budget." It means accepting that some projects aren't worth winning.
But studios that follow this rule consistently report something unexpected: higher win rates on the opportunities they do pursue, because they're only pursuing deals where they can confidently deliver excellent work at healthy margin. The paradox: pricing more carefully leads to winning more often.
Stop Pricing in the Dark
Most design studios price proposals the same way they priced them five years ago: gut feel, historical precedent, market intuition, competitive pressure. This works until it doesn't — and the failure is invisible until the project is delivered and the margin is gone.
Resource-based estimating inverts this. The fee is derived from what delivery actually costs, not what the market might bear. This doesn't make pricing slower — it makes it accurate. And accuracy compounds into profitability over time.
If your studio consistently runs projects over budget, if proposals are priced from instinct rather than data, if leadership doesn't know whether a project is profitable until after delivery — that's not a discipline problem. It's an infrastructure problem. And infrastructure can be fixed.
See how resource-based estimating works in practice. Book a free 30-minute Sales Process Audit and we'll map exactly how to connect your pricing to delivery reality — with no obligation to proceed.
