Most mid-stage B2B SaaS teams I meet are quoting badly, and the conclusion they have already drawn is that they need Salesforce CPQ. They have a quote template that does not match the deal, line items that do not match the quote, a product list that everyone treats as a suggestion, and a discounting practice nobody can describe in one sentence. The diagnosis they have arrived at, that quoting complexity has outgrown the CRM, is almost always wrong. The complexity is product-library debt, not configuration logic. The fix is a CPQ-lite stack, HubSpot line items as the source of truth, PandaDoc as the rendered quote, a disciplined product library, and three approval rules. Below a certain size threshold, that stack outperforms a CPQ rollout on time-to-value and total cost. The mistake is buying the heavy tool to cover for a light problem.
Why this matters now
Quoting is where the loose ends in a sales motion become visible. Discounts that were supposed to be exceptions become the policy; line items that were supposed to be standard become whatever a rep typed in last week; the document the customer signs becomes a small fiction reconciled with the CRM after the fact. As Jason Lemkin has argued on SaaStr, sales discounting is not eliminated by tooling: it is controlled by structure, trusted reps, marked-up list prices, automated low-end concessions, and procurement discounts modelled into the deal. A CPQ-lite stack is how you make that structure operational without buying CPQ. The cheaper version of the discipline beats the more expensive version of the chaos every time.
The CPQ trap, buying tooling for a process problem
The standard escalation path is recognizable. Reps complain that quotes take too long. Finance complains that bookings do not match invoices. A founder reads a comparison post about CPQ and the next conversation is a Salesforce CPQ scoping call. Six months and a meaningful budget later, the team has the same product-library mess, now wired into a more expensive system that nobody on the revenue team fully understands.
The honest diagnostic is shorter. If your quotes are wrong because reps are typing in custom line items rather than picking from a clean product list, CPQ does not fix that, the product list does. If your quotes are wrong because discounts are unbounded, CPQ does not fix that, three approval rules do. If your quotes are wrong because the document does not match the deal, CPQ does not fix that, a two-way sync with PandaDoc does. CPQ is the right answer for genuinely configurable products with dependencies, eligibility logic, and bundling rules. Most B2B SaaS quoting is not that.
The four primitives of CPQ-lite
The architecture has only four moving parts. The discipline is in keeping them in their lanes.
1. The product library
Every priced thing the company sells gets a HubSpot product record. No exceptions. No "custom" line items as the workaround for a SKU you forgot to create. The product library is the master list, owned by one person, usually a RevOps lead or a finance partner, and changes go through that person. The library carries the canonical name, SKU, list price, billing frequency, and any relevant product family taxonomy. Everything else hangs off this.
2. Line items on the deal
Line items live on the HubSpot deal and are pulled from the product library, not typed in by hand. The deal total is the sum of line items, full stop. If the deal value and the line-item total disagree, the line items are right and the deal value is the wrong number to trust. Reporting, forecasting, and bookings all read from line items.
3. The PandaDoc quote document
PandaDoc is the rendered output, not the source of truth. The quote template pulls line items from the deal via the two-way HubSpot integration, renders them in a document the customer can sign, and writes the final accepted state back to the deal. The customer never sees the CRM. The CRM never has to look like a contract. Both systems do the job they are good at.
4. The three approval rules
Three approval triggers cover the variation, discount over a defined threshold, term length over twelve months, and any line item flagged as custom. Each routes to a named approver before the document goes out. Three rules will feel insufficient for about a week. Then it will feel about right for a year.
Product-library discipline, what gets a SKU, what doesn't
The single most common failure mode of CPQ-lite is allowing custom line items as a quiet escape hatch. A rep needs to quote something the library does not have, types it in as a one-off, and the quote goes out. Two months later, that one-off has become a phantom product family with three variants and no owner. The discipline that prevents this, anything that gets quoted twice gets a SKU. Anything quoted once with custom pricing routes through the third approval rule and triggers a product-library review. The library is small, deliberate, and edited often.
What gets a SKU: the standard tiers, the named add-ons, the services packages, the implementation fees, the recurring overages. What does not, per-deal credits, one-time concessions, and bespoke negotiated terms. Those go in the discount field or as a flagged custom line, where the approval routing catches them.
Pattern from the field
A B2B SaaS team in DACH at roughly Series A came in convinced they needed Salesforce CPQ. The trigger was a quoting backlog: every quote took two days to assemble, half required a rebuild after legal review, and the bookings number reconciled to the contract only after a manual cleanup at quarter-end. The team had already scoped a CPQ rollout. The proposal we put forward was a six-week alternative, clean the product library, set up the PandaDoc–HubSpot two-way line-item sync, define three approval rules. By the end of week six the average quote was assembled in under an hour, the bookings number matched the contract on the first pass, and the CPQ project came off the roadmap. The legitimate CPQ trigger arrived eighteen months later, when product configurability genuinely outgrew the rules, at which point CPQ-lite was the bridge that had bought the time to scope CPQ properly.
Resolution, a CPQ-lite playbook
If you are reaching for CPQ and the symptom is messy quoting rather than configurable products:
- Audit the product library. Every priced thing gets a SKU, a list price, and a billing frequency. Anything quoted in the last twelve months that is not in the library either gets added or gets retired. One owner.
- Make line items the source of truth. Reporting, forecasting, and bookings all read from line items, not from the deal value field. Train the team that the deal total is a derived number.
- Set up PandaDoc as the renderer. Two-way line-item sync, one canonical quote template per motion, accepted state writes back to the deal. The customer signs the document; the document matches the deal.
- Define three approval rules. Discount over a defined threshold, term over twelve months, any custom line item. Name the approver for each. Resist the pull to add a fourth rule for at least two quarters.
- Pick the migration trigger in advance. A clear threshold for when CPQ-lite stops covering the use case: typically a function of rep headcount, SKU count, and genuine product configurability, written down before the stack is in place. The trigger is not a vibe.
- Review quarterly, not weekly. The library, the templates, and the approval thresholds get a quarterly review. Out-of-cycle changes are how the discipline erodes.
- Document the operating model, not just the configuration. The discipline is the asset. Write down who owns the library, who approves what, and how a new SKU gets added. Without that, the stack rots inside a year.
Where Checkpoint comes in
Most of the CPQ projects we get pulled into either get rebuilt as CPQ-lite or get scoped properly because CPQ-lite was tried first and the genuine threshold was hit. Both outcomes are fine. The bad outcome is a heavyweight CPQ rollout that papers over product-library debt with configuration complexity. If you are evaluating quoting tooling, talk to us before the procurement conversation, we will run the line-item audit, scope the HubSpot implementation work, fit it into the broader RevOps operating model, and tell you honestly whether the CPQ-lite stack covers your case or whether you have aged into a real CPQ migration. If a platform move is on the table, our CRM migration practice handles the brownfield work alongside the quoting redesign so you only do it once.
Sources
- Lemkin, Jason. "The Confounding Logic of Discounting." SaaStr. saastr.com
- Mohammed, R. "The Art of Discounting." Harvard Business Review, May 4, 2026. hbr.org