Last November I sat across the table from the managing partner of a 200-person consulting firm in Chicago. They’d just closed their best quarter ever. Revenue up 18%. And their margins? Down. Again.
He pulled up a spreadsheet, the same one they’d been using for six years, and walked me through their pricing process. A partner eyeballs the scope. Multiplies headcount by rate. Adds a buffer that’s either too generous or too thin depending on how badly they want the deal. Ships the proposal.
No reference to what similar engagements actually cost to deliver. No adjustment for the complexity signals sitting right there in the requirements doc. No feedback loop from the last thirty deals they priced the same way.
They were growing their way into lower margins. And they aren’t alone.
The 15-20% Problem
I’ve seen this pattern play out across dozens of firms. Most consulting shops underprice their engagements by somewhere between 15% and 20%. Not because they’re bad at math. Because they’re making pricing decisions without the data that would tell them they’re leaving money on the table.
The culprits are predictable:
- Scope creep gets baked in. Teams know the client will ask for extras, so they informally plan for it. But they don’t price for it. The “buffer” becomes the profit margin that evaporates.
- Rate cards are fiction. Every deal gets a custom discount. After a while, nobody actually charges rack rate, but the pricing model still assumes they will.
- Complexity is invisible. A data migration for a 50-person company and a 5,000-person company get the same pricing template. One takes three weeks. The other takes three months. The original estimate assumed something in between.
- Winner’s curse is rampant. Firms that win on price tend to have underpriced. But nobody tracks which deals were won at what margin, so the pattern repeats.
The Hidden Cost of Bad Pricing
Underpricing doesn’t just hurt margins. It cascades.
Underpriced engagements mean overworked teams. Overworked teams mean lower quality. Lower quality means unhappy clients. Unhappy clients mean harder renewals. Harder renewals mean more pressure to win new deals. More pressure to win means more aggressive pricing. And the cycle continues.
I’ve watched firms lose their best consultants because margins were too thin to pay competitively. I’ve watched firms turn down good work because they were stuck delivering underpriced engagements. I’ve watched firms acquire other firms just to get the pricing discipline they couldn’t build internally.
Bad pricing isn’t a finance problem. It’s an operational death spiral.
Why Spreadsheets Can’t Fix This
I know what you’re thinking. “We have a pricing spreadsheet. It works fine.”
It doesn’t. Here’s why.
A spreadsheet captures a formula. It doesn’t capture context. It can tell you that a senior consultant costs $250/hour and the engagement needs 400 hours. It can’t tell you that the last five engagements scoped at 400 hours for this type of work actually consumed 520. It can’t flag that the client’s industry has a 30% higher change-request rate. It can’t pull in the actual delivery data from your PSA to show you the gap between what you estimated and what happened.
A spreadsheet is a calculator. What you need is a pricing system that learns.
What CPQ Actually Means for Consulting
CPQ — Configure, Price, Quote — came from manufacturing. You’re configuring a product, pricing it based on components and options, and generating a quote. The concept translates to services, but the implementation has to be completely different.
For a consulting firm, CPQ means:
- Configure: Define the engagement. What service lines are involved? What’s the scope? What are the deliverables? What resources are needed? This isn’t a blank text field. It’s a structured definition built from your service catalog.
- Price: Apply pricing logic that accounts for role rates, complexity factors, historical actuals, and margin targets. Not a single formula, but a model that reflects how your firm actually delivers work.
- Quote: Generate a professional proposal that’s consistent, accurate, and audit-ready. Not a Word doc that every partner formats differently.
The power isn’t in any one of these steps. It’s in connecting them, and connecting them to what actually happens after the deal is signed.
The Feedback Loop Nobody Has
Here’s the part that kills me. Most firms generate pricing estimates, deliver the work, and never connect the two. The estimate lives in a proposal doc. The actuals live in the PSA or time-tracking system. Nobody closes the loop.
So the partner who consistently underestimates by 20% keeps doing it. The service line that always runs over on a particular type of engagement keeps running over. The complexity factors that should be adjusting your pricing model don’t, because nobody’s feeding delivery data back into the pricing engine.
This is where CPQ for consulting gets interesting. When your quoting system is connected to your delivery system, every completed engagement makes the next estimate more accurate. You start to see which types of work are actually profitable, which clients have a pattern of scope expansion, and which delivery teams estimate well versus poorly.
“The firms that price well aren’t smarter. They just remember what happened last time.”
Unpopular Opinion
Most consulting firms don’t have a pricing problem. They have a memory problem.
The information needed to price accurately already exists in your organization. It’s in completed timesheets, project retrospectives, change orders, and the heads of your delivery leads. The problem is that none of it flows back into the pricing decision for the next deal.
So we keep reinventing the wheel. Every new proposal starts from scratch, as if we’ve never done this type of work before. We have. Dozens of times. We just can’t remember what it actually took.
What Good Looks Like
A firm with functioning CPQ doesn’t price from gut feel. Here’s what their process looks like:
- A partner opens the engagement builder and selects service components from a catalog that the firm maintains. Not a blank page. A structured starting point.
- The system suggests resource requirements based on historical delivery data. Not a guess, but an informed starting point that the partner can adjust.
- Pricing is calculated against margin targets, with flags for anything that falls below threshold. The partner can see, in real time, what the engagement will actually yield.
- The proposal is generated consistently, branded, and professional. Minutes, not days.
- After delivery, actuals flow back into the system. The catalog gets smarter. The next estimate is better.
This isn’t theoretical. This is what happens when you treat pricing as a system instead of a spreadsheet exercise.
Bottom Line
Here’s what you can do tomorrow: pull the last ten engagements your firm delivered. Compare the original estimate to actual hours and costs. Calculate the real margin on each one. I’d bet you find at least three where the margin was half what you expected. And you’ll be able to see exactly why.
That gap between expected and actual margin? That’s the cost of not having a pricing system that remembers. And it’s compounding every quarter.
Ready to encode your services?
See how Servantium brings CPQ discipline to professional services.