Most companies get the tech stack conversation half right. They talk about CRM. They talk about ERP or billing. CPQ rarely gets mentioned, and that’s exactly the gap that causes problems.
Here’s how the three actually work together.
CRM owns the relationship. It tracks the lead, the contact history, the pipeline stage. It answers the question: who are we selling to, and where are they in the journey.
ERP or billing owns what happens after the deal is signed. Provisioning, invoicing, revenue recognition, the operational side of delivering what was sold.
CPQ sits in the middle, and it’s the part most companies underbuild. It’s the layer that turns “we have a customer who wants something” into “here is the exact, correct, approved offer for that customer.” Configuration, pricing, discount rules, approval flow. Without it, that middle step gets done by hand, usually in Excel, usually by someone senior enough to know the pricing rules by memory. Multiple spreadsheets open at once, numbers copied between tabs, totals recalculated manually every time something changes. Hours go into work that produces no new value, just the risk of one wrong cell breaking the whole offer.
That’s the real cost of skipping CPQ. Not that the CRM or the ERP is missing something. It’s that the handoff between them has no system of its own, so the business builds one out of habits, tribal knowledge, and manual work in spreadsheets that were never meant to carry that much weight.
A CRM tells you who to talk to. An ERP tells you how to deliver and bill. Ofca CPQ is what makes sure the thing in between, the actual offer, is fast, accurate, and consistent every time, so the handoff from sales to operations doesn’t depend on who happens to remember the rules that day.
If your stack has a CRM and an ERP but nothing connecting them, that gap is where deals slow down and quietly go wrong. It’s worth asking what’s actually filling it today.