The deal amount and the quote disagree
A rep builds a quote, the buyer changes the configuration, and the deal record still carries yesterday's number. Forecasting on a deal amount that no quote supports is forecasting on a guess.
HubSpot · CPQ & Document Automation HubSpot quotes got you this far.
HubSpot quotes got you this far.
Then the deals got complicated.
Native HubSpot quotes are fine until you need optional products, tiered discounting, an approval gate before a number reaches a buyer, and line items that stay true when the customer changes the configuration. PandaDoc CPQ runs that workflow inside Sales Hub and syncs it back to the deal both ways. Twopir designs the catalogue, the rules and the sync so the deal record and the signed quote never disagree. Configure, price, quote, sign — without leaving HubSpot.
2-way
1
0
Native
Trusted by 500+ organizations — including revenue, sales operations and legal teams running document generation, quoting and e-signature on Salesforce and HubSpot with Twopir Consulting.
Built for HubSpot Revenue Teams
- HubSpot Partner
- PandaDoc Implementation
- Sales Hub
- CPQ for HubSpot
- Deal Line Items
- E-Signature
- Quote-to-Cash
- RevOps
Where HubSpot quoting runs out of road
These are the six frictions that send a HubSpot team looking for CPQ. None of them is a HubSpot fault — they are the point at which a quoting tool has to become a quoting system.
Discounting has no gate
Nothing stops a rep sending 30% off on a Friday afternoon. By the time finance sees it, the buyer has already been given a number and taking it back costs the relationship.
Configurable products do not fit a flat quote
Bundles, optional add-ons, usage tiers and quantity breaks need rules. Expressed as a static line-item list, every complex deal becomes a manual build and a manual check.
Reps rebuild the same quote three times
Negotiation means versions. Without a quote that regenerates from the configuration, each revision is retyped, and each retype is a chance for the terms and the pricing to drift apart.
Document activity never reaches the timeline
If sent, viewed and signed events do not land on the deal, nobody can build a workflow on them — no follow-up task when a buyer opens the contract, no alert when a quote goes cold.
Quote-to-billing is a copy-paste job
The customer signs, and somebody re-enters the same line items into the billing system. Every mismatch between what was signed and what was invoiced starts right here.
What PandaDoc Is
PandaDoc CPQ is a quoting engine that lives inside HubSpot
PandaDoc is a document automation, quoting and e-signature platform. PandaDoc CPQ for HubSpot is its configure-price-quote layer running natively inside HubSpot Sales Hub: reps configure products through guided selling, the rules engine applies pricing and discount logic, approvals route automatically, and the buyer signs the resulting quote. PandaDoc publishes it as the native end-to-end CPQ solution for HubSpot Sales Hub, with two-way data sync between deal line items and PandaDoc pricing tables.
Keeping three things distinct matters here more than on most pages. HubSpot is the system of record for the company, the contact and the deal. PandaDoc provides the quoting engine, the rules, the signature and the document analytics. Twopir designs the catalogue, writes the pricing and approval rules, and builds the sync so both systems describe the same deal. We implement PandaDoc; we do not make it.
It is the right move when your commercial model has genuine configuration — optional modules, tiers, bundles, usage-based components — or when discounting needs governance before a number reaches a buyer. It is the wrong move when native HubSpot quotes already cover the job; adding a CPQ layer to a simple price list buys complexity and no speed.
We help growing and mid-market companies solve complex CRM, integration, and business system challenges, and enterprise teams running HubSpot alongside other platforms. For PandaDoc CPQ on HubSpot the usual profile is a Sales Hub team with a real product catalogue and a finance function that wants discounting under control.
Implement, configure, or build past the connector
Three services, three buyers, one boundary that most vendors leave vague. Here is where each one stops.
Implement
Connecting the two platforms and getting a first real quote through the whole flow — configure, approve, send, sign, sync.
- PandaDoc app install and HubSpot OAuth connection
- Product library mapped to the PandaDoc catalogue
- Deal, company and contact token mapping
- First quote template built from your real pricing
- Deal line-item sync switched on and validated
- Sandbox build, UAT and a tested production cutover
Configure
Turning your commercial policy into rules the platform enforces — all inside PandaDoc's and HubSpot's own surfaces.
- Guided selling questionnaire driven by deal context
- Pricing rules: bundles, tiers, volume breaks, optional products
- Conditional approvals on discount, margin or deal value
- Conditional content so one template covers many deal types
- HubSpot workflows triggered by document events
- Quote versioning and renewal templates
Build On
Everything the app cannot reach. Development work, scoped and maintained as development work.
- Custom object quoting via the PandaDoc REST API
- Webhook services driving downstream billing or provisioning
- Bulk and scheduled renewal generation
- Embedded quoting inside a customer portal
- Pricing logic the rules engine cannot express
- Middleware to ERP, subscription or payment platforms
| Requirement | Native HubSpot quotes | PandaDoc CPQ for HubSpot | Custom build |
|---|---|---|---|
| Simple flat-rate price list | Sufficient | Overkill | — |
| Optional and bundled products | Manual | Yes — rules engine | — |
| Discount approval before send | Not enforced | Yes — conditional approvals | — |
| Two-way deal line-item sync | N/A | Yes — including added and removed items | — |
| Guided selling for a large catalogue | — | Yes | — |
| Document events on the deal timeline | Limited | Yes — workflow-triggerable | — |
| Quoting from a custom object | — | Not reachable | Yes — API build |
| Quoting embedded in your own portal | — | Not reachable | Yes — API build |
The honest read: if your first two rows describe your business, stay on native quotes and spend the budget elsewhere. CPQ earns its keep from row three down.
The boundary, in one sentence: configuration covers anything the rules engine can express against a HubSpot deal — and stops at objects the app does not surface and logic the WHEN/THEN model cannot state. Quoting from a custom object, or embedding the quote in your own product, is API work. We will tell you which side you are on during discovery.
The quoting surface we actually build on
Six areas of work, each one something we configure or extend for you — not a feature list lifted from the vendor.
Product Catalogue & Guided Selling
The foundation everything else rests on. A catalogue modelled wrong makes every downstream rule fragile.
- HubSpot product library mapped to the PandaDoc catalogue
- SKU structure, tiers and currency handling
- Guided selling questionnaire pre-filled from deal context
- Bundle and compatibility rules
- Catalogue change process so pricing updates are safe
Pricing Rules & Quote Builder
Where the commercial policy becomes something the system enforces rather than something a manager remembers.
- Volume breaks, tiered and usage-based pricing
- Optional products the buyer can select in the quote
- Margin and floor-price guardrails
- Multi-year and ramped deal structures
- Interactive quotes the buyer configures themselves
Approval & Discount Governance
Conditional approvals configured on the template, so the policy applies to every quote — not only the ones somebody remembered to route.
- Thresholds on discount percentage, margin or deal value
- Multi-step routing across sales management, finance and legal
- Approval status visible on the HubSpot deal
- Locked clauses and controlled edit rights
- An audit trail a finance review will accept
Deal Line-Item Synchronisation
The connection that keeps the forecast honest: what the buyer selected becomes what the deal says, in both directions.
- Added, removed and optional items synced both ways
- Quantity, discount and configuration changes reflected on the deal
- A documented rule for which system holds the authoritative total
- Currency and tax handling that matches finance's model
- Reconciliation reporting for quotes versus deals
Workflow Triggers on Document Events
Sent, viewed, commented and signed events land on the deal timeline, where HubSpot workflows can act on them.
- Follow-up tasks when a buyer opens a quote
- Alerts when a quote stalls past a threshold
- Stage automation on signature
- Renewal sequences driven by contract dates
- Handoff to onboarding the moment a deal closes
Governance, Roles & Template Control
The layer that stops a template library growing to sixty items nobody owns.
- Workspace and folder structure matched to the business
- Role design mapped to HubSpot teams and permissions
- Template ownership and change control
- Brand lock so quotes stay consistent
- Licence and plan-tier review against real usage
What moves between HubSpot and PandaDoc, and in which direction
For each connection: both platforms named, the business purpose, and the data that actually moves which way.
HubSpot → PandaDoc
Company, contact and deal properties populate quote variables at creation, so customer detail and deal context come from the CRM rather than a rep's memory.
Line items ↔ Quote Builder
Deal line items and PandaDoc pricing tables synchronise in both directions, including items added, items removed, and optional products the buyer selects during review.
Document events → Deal timeline
Sent, viewed, commented and completed events post to the HubSpot activity timeline, where they become triggers for workflows and sequences rather than inert history.
Approval chain → Deal record
Approval state and approver identity land on the deal, so a discounted quote carries visible evidence that it cleared its gate.
REST API & webhooks
For what the app does not cover: custom-object quoting, bulk generation, and event-driven sync where a webhook fires your middleware on a status change.
iPaaS — Zapier, Workato, Celigo
Narrow event-triggered jobs on lighter plan tiers. One trigger, one action, no CPQ depth — useful for edge workflows, not a replacement for the native app.
Billing & subscription platforms
Signed configuration drives subscription or invoice creation downstream, and billing status returns to the deal so renewals are not a surprise.
Slack, Teams & internal comms
Approval requests and signature notifications routed to the person who has to act, rather than broadcast into a channel.
From native quotes to a governed quoting system
Five phases. The catalogue work in Phase 02 is the part teams under-estimate and the part that determines whether everything after it is stable.
Commercial & Quoting Audit
We map how deals are actually priced — including the exceptions nobody documented — and catalogue every product, discount practice and approval that exists in practice rather than in policy.
Catalogue & Rules Design
We model the product catalogue, the pricing tiers and the bundle logic, then specify the approval thresholds. This is where a quoting system is won or lost; a catalogue modelled loosely makes every later rule brittle.
Quote & Template Build
We build the quote templates, the guided selling flow and the conditional content, then wire approval routing. One template covers several deal shapes so the library stays ownable.
Sync, Timeline & Workflow
We configure the two-way line-item sync, validate it against real negotiation scenarios, and build the HubSpot workflows that fire on document events — including the failure paths.
Launch, Adoption & Optimization
Rollout with rep training, a parallel run through one full cycle, then review against the Phase 01 baseline. Quoting systems are judged at quarter-end, so we are there for it.
What changed when quoting became a system
Real engagements, with the scope each number was measured against.
Quote-to-Cash Document Automation
40–150 sales users · 500+ documents per month · delivered in 8 weeks across 5 phases
100%
Transaction data auto-populated
<60s
To a branded, data-accurate proposal
0
Manual exports or copy-paste steps
Real-time
Document status in the CRM
Proposal creation used to take a rep 45 minutes of copying data, fixing formatting, and hoping nothing was wrong by the time it reached the customer. Now they click one button inside the CRM and a fully accurate, branded document is ready to send in under a minute. The eSignature alone has cut our average close cycle by days.
CRM · Chargebee · PandaDoc
Connecting the configured quote, the signature and the subscription into one flow
3
Systems on one quote-to-cash path
1
Authoritative deal value
Native
CRM writeback
Zero
Re-keying between quote and billing
Engagement scope: the accepted PandaDoc quote drives subscription creation in Chargebee and billing status returns to the CRM, so sales, finance and the customer read the same agreement. Outcome metrics for this engagement are being confirmed with the client before publication.
The HubSpot teams that get the most out of this
If two or more of these describe your quarter, the quoting model is the constraint — not how hard the team is working.
RevOps leaders on HubSpot
You own the forecast and you cannot defend a deal amount that no current quote supports. You want the line items on the deal to be the ones the customer actually chose.
Sales leaders with a discounting problem
Margin is leaking through discounts nobody approved, and the only control you have is asking people nicely. You need the gate inside the tool.
Teams that outgrew native HubSpot quotes
The product line got configurable. Every complex quote is now a manual build, and the spreadsheet a rep uses to price it is the real system of record.
Finance teams reconciling quotes to invoices
You spend the first week of every month explaining the difference between what was signed and what was billed. The fix is upstream of your team.
Companies running HubSpot alongside Salesforce
Different regions or business units on different CRMs, and you need document and quoting practice that is consistent across both.
Teams live on PandaDoc but not on CPQ
You send documents from HubSpot already, but quoting is still manual. That is usually a short engagement with a fast payback.
Revenue architects who speak HubSpot and finance
CPQ projects fail on the catalogue and the approval model far more often than on the software. Those are the parts we are strongest on.
We model the catalogue before we touch a template
Products, tiers, bundles and currency come first. Most failed CPQ projects trace back to a catalogue that could not describe the business it was built for.
We design the approval model with finance in the room
Thresholds that sales will actually live with and finance will actually trust. A gate everybody routes around is worse than no gate.
We are a HubSpot Partner and a Salesforce Partner
Which matters when you run both, or when you are moving between them. We have built this workflow on each and we will tell you honestly where each one is stronger.
We build the whole quote-to-cash path
Quoting is rarely the only gap. We have connected quoting, signature, billing and subscription management in one engagement, so the handoffs are designed rather than improvised.
40+ consultants, 500+ clients
Across the US, Canada, UK, UAE, Australia and New Zealand, over 12+ years of CRM and revenue-systems delivery.
We stay after go-live
PandaDoc ships a new editor and new CPQ capability; HubSpot ships continuously. Managed support keeps the quoting system current instead of quietly drifting out of date.
What HubSpot teams ask before committing to CPQ
The questions that decide whether this is the right project.
Native HubSpot quotes handle a straightforward price list well, and if that describes your business you should keep the budget. PandaDoc CPQ earns its place when you have genuine configuration — optional products, bundles, tiered or usage-based pricing — or when discounting needs an approval gate before a number reaches a buyer. We assess this in discovery and we will tell you to stay on native quotes when that is the right answer.
Yes. PandaDoc CPQ for HubSpot includes two-way sync between HubSpot deal line items and PandaDoc pricing tables and Quote Builder, covering items added, items removed and optional products. When a rep or the buyer changes a quantity, applies a discount or alters the configuration, that change flows back to the deal's line items — which is what keeps the deal amount and the quote describing the same thing.
Yes. Document events — sent, viewed, commented, signed — appear on the HubSpot activity timeline, and from there they can trigger workflows. In practice that means a follow-up task when a buyer opens a quote, an alert when a quote stalls, stage automation on signature, and renewal sequences driven by contract dates. Designing which events deserve an automation, and which are just noise, is part of Phase 04.
The document platform is the same; almost everything around it differs. HubSpot's deal and line-item model, its product library, its workflow engine and its permission model are not Salesforce's, and the PandaDoc app for each is a different piece of software with different capabilities. If you run Salesforce, our PandaDoc Salesforce consulting page is the right starting point. If you run both, we cover both in one engagement.
CPQ capability sits on PandaDoc's higher plan tiers, and the exact gating and pricing change often enough that we will not publish a figure here that goes stale. We confirm your current licence position with you during discovery and model the total cost — seats, plan tier and any API usage — before you commit to the project.
For a single product line with straightforward rules, a few weeks. For a configurable catalogue with multi-step approvals, multi-currency pricing and a billing integration, a few months. The two variables that move the timeline most are the number of distinct pricing rules and how much of the current pricing practice is undocumented — which we find out in Phase 01, not at UAT.
Usually, and it is the more common engagement. We audit the catalogue mapping, the template library, the approval rules and the sync configuration against how the team really sells, then fix what is broken and retire what is unused. A rebuild is only the right call when the product model underneath has changed beyond what the original build described.
A HubSpot admin with permission to install and connect the app, a PandaDoc workspace admin, somebody who owns pricing policy — usually sales ops or finance — and a few reps for UAT. The biggest ask is Phase 01: we need an honest account of how deals are really priced, including the exceptions.
Next Step
If your deal amounts and your quotes tell different stories
Bring us your product catalogue and your real discounting practice. We will show you whether native HubSpot quotes still cover it, what PandaDoc CPQ would change, and what — if anything — genuinely needs custom development.
12+ years · 500+ clients · 40+ consultants · Salesforce Partner · HubSpot Partner
