Native HubSpot quoting
What HubSpot's native quoting does, and where it stops
If your quoting is straightforward, native HubSpot may already be enough. This page is a reference for what it handles well, what is gated by tier, and what it does not do at any budget. Every limit below is cited to HubSpot's own documentation.
What native HubSpot handles well
Native HubSpot quoting is strong when the workflow centers on standard products, list pricing, straightforward approvals, signature and payment, and a clean handoff inside the CRM. In practice that covers:
- A product library holding up to 100,000 products, with flat, tiered and stair-step pricing and price books
- Quote templates with branding, module arrangement, and locking so reps cannot break the layout
- Standard approvals — up to ten approvers, filtered on quote properties such as discount amount or acceptance method
- E-signature, click-to-accept, countersigners, payments through HubSpot payments or Stripe, and invoice and subscription creation from the quote
- Engagement tracking on the quote itself: views, downloads, prints, and an activity log
If that describes your quoting, you do not need a third-party CPQ and the rest of this page is about limits you will never reach.
Where native stops, capability by capability
| Capability | Native HubSpot | Quotivity |
|---|---|---|
|
Standard products and multi-currency prices
|
Yes. Products are a core part of HubSpot CRM.
|
Quotivity uses HubSpot's native product library.
|
|
Rule-based quote approvals
|
Yes, with Revenue Hub Enterprise.
|
Yes, completely configurable.
|
|
Configurable products and bundles
|
No. There is no native bundle object for handling advanced configuration logic.
|
Bundles, Configurator, and product compatibility rules are a core part of Quotivity.
|
|
Guided selling
|
No. Requires custom code and recurring maintenance.
|
Yes. Create branching surveys and use responses to drive quote automation to streamline quote creation and eliminate quoting errors.
|
|
Calculated pricing
|
No. Deal properties can calculate, but that is not the same as setting line-item prices.
|
Yes. Excel-style formulas allow nearly unlimited flexibility.
|
What is gated by tier
Two capabilities exist in native HubSpot but only above the entry tier, which matters when you are pricing the move rather than assessing it.
- Advanced approvals — workflow-driven, logic-based routing on quote properties — require Revenue Hub Enterprise. Standard approvals sit below that, and you cannot run both at once.
- Quote rules — guardrails covering product combinations, quantities and discount limits — also require Revenue Hub Enterprise. Worth being precise about what they do: a rule has two possible outcomes, show a warning or block publishing. It checks a quote that has already been built rather than constraining how the rep builds it.
Quote rules also carry an ownership cost that is easy to miss when they are counted as configuration. Each rule is authored in a domain-specific language, or drafted by HubSpot's AI assistant and then edited in that language. Creating and editing rules requires Super Admin permissions, and HubSpot recommends testing them against sample data in a sandbox before they go live. Maintaining a rule set is closer to looking after code than to changing a setting.
HubSpot has renamed these subscriptions over time and some articles still say Commerce Hub. Check the requirement on HubSpot's own pages before you build a business case on it.
What native does not do at any budget
These are not tier gates. No subscription unlocks them.
- Configurable products. There is no bundle object. A product cannot carry options, option groups, or compatibility constraints, and the workflow action that adds a line item to a deal adds it at a fixed quantity and list price — it cannot set a discount, edit the line, or remove it.
- Calculated pricing. Calculated properties do arithmetic on a deal. They do not set line item prices on a quote.
- Guided selling. There is no feature. Something guided-selling-shaped can be built as a custom quote module, and working prototypes exist — but that is a build you maintain, not a capability you configure.
What needs code, and what that means to own
Where native stops, HubSpot's extension point is the custom quote module: a React component you build, deploy, and maintain inside the quote template. It can display information, show content conditionally, pull external data at render time, and collect buyer input.
What it cannot do is edit the underlying line item records. The default line item module has to stay on the quote, because it is the only thing that can. A custom module sits alongside it rather than replacing it.
The part worth pricing is not the build. It is the ownership: a codebase with no product roadmap, maintained by whoever wrote it, that needs attention whenever HubSpot changes something underneath it or the person who built it moves on. The same question applies, in smaller form, to a quote rule set written in HubSpot's rule language.
Who native HubSpot is right for
If you sell a catalog of standard products at list or price-book prices, your discounts are percentages or quantity bands, and your approvals route on a discount threshold, native HubSpot covers you. Buy the tier that includes the approvals you need and configure it. You do not need a third-party CPQ, and we would rather say that here than after you had paid us.
The boundary is narrower than it sounds, and it is about structure rather than size. A large catalog is fine. What native cannot hold is a product that has to be configured rather than selected, a price that has to be calculated rather than looked up, or a discount that depends on a total rather than a line.
Coming from Salesforce CPQ? The migration guide maps every construct you have built to where it lands in HubSpot, and the free analysis counts them in your own org.
Not sure whether native covers you? The Quoting Audit measures your quoting process against the places native stops and tells you which side of the line you are on.