I've heard more than one partner consultant say that CPQ doesn't come up with clients. The need comes up constantly. It just shows up wearing different words.A partner principal said it plainly on a call last month: "We don't hear about CPQ coming up often."
That's worth sitting with, because every company he serves sends quotes. All of them. Quoting is not an optional function that some businesses have and others skip. If money changes hands for something that isn't priced off a public menu, somebody built a quote.
So the demand is there. The phrase isn't.
Clients don't have a word for this
CPQ is a category name. Analysts use it. Vendors use it. The person who spent Thursday afternoon rebuilding a pricing spreadsheet does not use it, because nobody ever taught them there was a name for the thing that was wasting their Thursday.
Worse, the acronym signals scale and complexity. "CPQ" sounds adjacent to ERP and procurement and eighteen-month implementations. A 200-person manufacturer with four reps hears three capital letters and assumes the conversation is for somebody bigger — or has PTSD from their last ERP implementation. That assumption is wrong, and it's the reason the words never make it into a QBR.
Compare it to how the same client talks about the same problem in their own language. "Quoting takes forever." "We had another pricing mistake go out." "Dave is the only one who knows how the discounts work and he's on vacation." Those are CPQ conversations. They're just not labeled.
What the ask actually sounds like
Here's the translation layer. The left column is what clients say out loud. The right is what it means underneath.
|
What the client says |
What they're describing |
|---|---|
|
"Our quotes take too long to get out." |
No product library, no reusable configuration, every quote built from scratch |
|
"We had another pricing error." |
Pricing rules live in a spreadsheet or somebody's head, not in the system |
|
"One person knows all our pricing." |
Tribal knowledge, and a business risk if that person leaves |
|
"Reps are discounting too much." |
No approval thresholds, no guardrails, margin exposed to the whole team |
|
"We're not sure why we lost that deal." |
Quote data outside the CRM, so nothing is reportable |
|
"Finance wants to review every quote now." |
An approval workflow exists, it just runs through email |
|
"We're building something custom in HubSpot for this." |
The client has already accepted the problem and picked the hardest fix |
None of those sentences contain the word CPQ. Every one of them is a client telling their partner the quoting process broke and they don't have a name for what would fix it.
The verbatim language from our own customer calls sounds exactly like this. "We've got one guy in the company that controls all the bolts." "We do our quoting in Word, PowerPoint, and Excel." "Spent nearly six hours quoting this and getting errors." Nobody in those conversations opened with a category. They opened with a bad afternoon.
Some of them already looked, and quietly decided no
There's a second reason the topic stays silent, and it's the one that costs partners the most.
A share of these clients did go looking. Maybe two years ago, maybe during the HubSpot implementation the partner ran. They asked whether HubSpot quoting could handle tiered pricing or a real approval chain, got a straight answer that it couldn't, and filed the whole idea under things that aren't possible here. Then they went back to the spreadsheet and stopped bringing it up.
Read that client as low demand and you'd have it backwards. They priced out the options once, concluded there wasn't a good one, and made peace with the workaround. Their silence reads like satisfaction, and it isn't.
The market changed underneath that conclusion. Native HubSpot quoting still stops at the same place it always did, but the answer to "what happens after that" is different now, and it no longer means moving the client off HubSpot or building custom modules the partner has to maintain forever. Nobody sends out a memo when an old objection expires. The client is still operating on 2024 information.
Stop waiting for the phrase, start asking the question
The practical fix is small. If clients won't name the category, the partner names the symptom.
Five questions surface it without pitching anything. Are reps keeping their own pricing spreadsheets next to HubSpot? Do approvals happen in email or Slack instead of in the system? Is there one person who knows how pricing really works? Have they asked for something native quoting can't do, like conditional pricing or multi-stage approvals? Do they sell configurable products, bundles, or anything with options?
Two yeses and there's a real conversation. Three and the client has been living with a problem they assumed was permanent.
Notice what these questions don't require. No product positioning, no demo, no category education. The client describes their own process, hears themselves describe it, and usually gets to the conclusion faster than a pitch would have taken them there.
Where this starts
Pull up the client list. Not all of it, just the HubSpot clients selling something configurable, where the implementation shipped a while back and the engagement has settled into maintenance.
Pick the one where quoting came up in passing and nobody followed the thread. That conversation is sitting there right now, unlabeled, waiting for somebody to ask the second question.
That's usually where a CPQ service line actually begins. One client, one honest discovery conversation, one problem that turns out to have a name after all.
