How HubSpot and DealHub fit together

When HubSpot's own quotes are enough

HubSpot can build quotes from a deal's line items, using the products in your product library. For many B2B companies that's all they need:

• A short product list with simple, fixed prices.

• Discounts a rep can apply without anyone signing off.

• One or two quote templates.

• Orders and invoices handled by a small finance team who can work from the quote.

If that's you, keep quoting in HubSpot, clean up the product library and spend the effort on the handoff to finance instead.

Signs you need a CPQ

A CPQ (configure, price, quote) tool earns its place when quoting rules get complicated enough that reps make mistakes or wait on someone else:

• Products depend on each other: bundles, required add-ons, options that only work together.

• Pricing has rules: volume tiers, ramped multi-year deals, customer-specific price lists, several currencies.

• Discounts need approval at different levels, by different people.

• Quotes need different terms, templates or legal language by product, region or deal size.

• Finance keeps correcting orders because the quote didn't match what can actually be delivered or billed.

DealHub is a CPQ built to sit alongside a CRM such as HubSpot, so reps keep working from the deal while the quoting rules live in one place.

How HubSpot and DealHub connect

A typical flow, using DealHub's HubSpot integration:

1. The deal starts in HubSpot, with the company, contacts and expected value.

2. The rep opens DealHub from the deal and builds the quote there, so the customer and deal details come across automatically.

3. DealHub applies the rules: which products can be sold together, the right prices, and the discount limits.

4. Exceptions go for approval in DealHub, to the right approver for the discount level or terms.

5. The customer receives and accepts the quote, signing where needed.

6. The approved quote's details come back to the HubSpot deal: amount, line items, quote status and a link, so pipeline and forecast reports use the real numbers.

7. The accepted quote becomes an order in your ERP, through a connector, middleware or a custom integration.

The CRM stays the place sales and leadership look for deal status. DealHub owns how a quote is put together. The ERP owns what happens after signature.

Decide who owns the product catalog

Prices that live in two places will drift. Pick one owner before you build anything:

Either way, products need the same identifier in every system, so an order created from a DealHub quote maps to the right ERP items.

What to sync back to HubSpot

HubSpot should show what was actually quoted and approved, not what the rep guessed when creating the deal:

• Deal amount set from the approved quote total.

• Line items, so revenue can be reported by product.

• Quote status, approval status and a link to the quote.

• Discount given, so you can see where margin goes.

• The date the quote was accepted or signed.

Common mistakes

• Building quotes on a messy product catalog. Clean up items, names and prices first, or the CPQ automates the mess.

• Deal amount and quote total disagreeing. Decide which wins, and set it automatically.

• Approval rules that don't match the real policy. If people approve over Slack anyway, the rules are wrong.

• Forgetting renewals and amendments. Design how a change to an existing contract is quoted before launch, not after the first renewal.

• Nobody owning it after launch. Products and prices change; someone needs to own keeping DealHub, HubSpot and the ERP in step.

From quote to order

The step after signature is where most of the manual work hides. See how to connect HubSpot and NetSuite for the order and invoice side, and the B2B quote-to-cash integration guide for how all the pieces fit together.

Setting up CPQ and connecting it to your CRM and ERP is part of our quote-to-cash service.