Quote approvals slow HubSpot deals for five reasons. Every quote gets routed. The rules live in someone's head. Approvals go to one named person who's out that week. A small edit after sign-off sends the quote back to the start. And the approver can't see why the request came in. Fix those five and approvals stop being the slowest step in your sales cycle.
It costs deals. In Conga's March 2026 survey of more than 1,200 commerce and contracting decision-makers, 45% said they'd lost a deal in the previous six months because approvals took too long.
And the wait is long. Everstage's Approval Queue Report surveyed 195 VP-level revenue leaders this summer and found 47% of companies take three days or more to clear a pricing exception. The people waiting feel it more: 51% of sales leaders said three days or more, against 42% of RevOps leaders.
Most teams blame the approver. Usually the setup around them is the problem.
Everything gets routed. When approvals were first turned on, somebody decided it was safer to review every quote. Say the VP of Sales now gets 40 requests a week and 35 of them are standard pricing. The 5 that matter wait behind the rest.
The 35 don't get a careful look either. BabelQuest, a HubSpot partner, calls it approval fatigue: managers start signing off without reading.
One week in the VP's queue
40 requests. 5 need a real decision.
Real exception Standard pricing, routed anyway
Illustration of the example above, not customer data.
The rules aren't written down. "Anything big goes to finance." How big? Which finance person? Reps guess, approvers guess, and quotes bounce back with a question in Slack.
Routing points at people, not roles. Approvals assigned to Dana work great until Dana is on vacation. HubSpot added team-based routing to advanced approvals in October 2026, which helps if you're on Enterprise.
Edits restart the clock, too. The buyer asks to swap the signer or move the start date, and the quote goes back through approval even though price and terms didn't change. Do that twice and you've added a week.
RevOps Co-op walks through how this plays out. The change re-fires the whole chain. The CFO ignores the new notification because they approved the deal yesterday. Three days pass.
And the approver often can't see the reason. If the request shows up somewhere other than the quote, they have to go find the deal, the discount and the context. So they ask the rep. The rep answers tomorrow.
This is the step teams skip, and it's the one that matters most. Before you configure anything in HubSpot, write the approval policy as a list of plain sentences. Real thresholds, real approvers.
Here's what that looked like for one advertising company we spoke with. They wanted three rules: no discounts at all on campaigns shorter than a month, media discounts capped at 10% unless a manager signs off, and production discounts below a set floor routed for approval. Before that, all three ran on the honor system in a spreadsheet.
Three sentences. Each one has a property (term, discount percent, product type), a threshold and an approver. That's the format you want, because every one of them becomes a rule you can build.
Anatomy of a rule
Three sentences, three buildable rules
| The rule as written | Property | Threshold | Who decides |
|---|---|---|---|
| No discounts on campaigns shorter than a month | Term | Under 1 month | No one. The discount isn't allowed. |
| Media discounts capped at 10% unless a manager signs off | Discount % on media | Over 10% | Manager |
| Production discounts below a set floor go for approval | Discount on production | Below the floor | The approver you name |
Every rule needs all three: a property, a threshold and an approver. If one is missing, the rule isn't ready to build.
When you write yours, you'll probably find two things. There are more rules than anyone thought. And two of them contradict each other. Better to find that on paper than in a deal.
HubSpot has two approval systems for quotes, and you can't run both at once.
Standard approvals come with Revenue Hub Professional and Enterprise. You set filters on quote properties, and only quotes that match need sign-off. You can add up to 10 approvers and require all of them or any one.
Advanced approvals need Revenue Hub Enterprise. They're built in a workflow, so rules can use quote and line item properties, user attributes and related records like the deal. You can run up to five sequences with ten approvers each, and since October 2026 you can assign a step to a team.
HubSpot's list of commonly used approval properties includes discount percent, total discount, quote amount, margin, net payment terms, billing frequency, currency and country. Anyone creating or editing quotes needs a Revenue Hub seat.
If you're on Revenue Hub Enterprise and your rules are about discount, amount and who's asking, that covers a lot of teams. Start there.
Side by side
HubSpot standard vs. advanced approvals vs. Quotivity
| HubSpot standard | HubSpot advanced | Quotivity | |
|---|---|---|---|
| Plan | Revenue Hub Professional or Enterprise | Revenue Hub Enterprise | Term and margin routing on every plan |
| Rules can use | Filters on quote properties | Quote and line item properties, user attributes, related records like the deal | Discount, total, segment, flagged product, contract term, margin |
| Approvers | Up to 10, all or any one | Up to 5 sequences of 10, team steps since Oct 2026 | Multi-stage routing, in order |
| Contract term in months | Not supported, per HubSpot | Not supported, per HubSpot | Yes |
HubSpot details from its quote approval use-case page, updated September 23, 2026. You can't run HubSpot's two approval systems at once.
HubSpot is upfront about a few. Its own use-case page (updated September 2026) lists things approval properties can't do, including setting a specific term length in months and handling one-time fees.
Term length matters for SaaS teams. A common rule: anything over 24 months goes to finance. Multi-year deals are where a bad discount costs the most, so that's an awkward one to be missing.
The other gap is tier. Workflow-based routing that uses line items, deal data and sequences sits on Enterprise. A Professional team gets filters on quote properties, which handles a rule like "over $50,000 goes to the VP."
1. Route the exceptions only. If a quote is inside policy, it should send without waiting. Your written rules define "inside policy," and everything else skips the queue.
2. Route to a role. Use a team, or a role that more than one person can cover. One approver per rule is a single point of failure.
3. Put the reason on the quote. The approver should see the discount, the margin and the rule that triggered the request in one place, on the quote, next to the deal. If they have to ask the rep, you've added a day.
Then decide which edits should re-trigger approval. A new signer or a changed contact usually shouldn't. A new discount or a longer term should. Write that down with the rest of your rules. While you're at it, only use sequential approval (manager, then finance) where the order actually matters, like a big multi-year deal. For a simple discount check, one approver is faster.
Write this down too
Which edits should send a quote back?
Usually shouldn't re-trigger
Price and terms didn't change
Should re-trigger
The deal changed
Last, watch time in approval. Pull the quotes that went through approval last month and look at how long each one sat. If most of them came back approved with no changes, your threshold is probably too low.
We built approvals into Quotivity for teams whose rules go past what HubSpot's built-in approvals cover, or who aren't on Revenue Hub Enterprise.
Approvals route on HubSpot's own quote records, and the approval sits on the quote next to the deal it belongs to. A quote routes when it trips a condition you set: a discount past a threshold, a total, a segment, a flagged product, a contract term past your limit, or a margin under your floor. Term and margin routing work on every plan. Quotes inside policy send straight through, and multi-stage routing gets approvals in order when a deal needs more than one.
By default, an approved quote that gets edited goes back to approval, so nobody sends a changed quote on an old sign-off. On the Enterprise plan, you can turn on Smart Approvals, which lets a re-issued quote skip the approvals it already cleared.
Renée Durrance, Senior Director of Business Systems at Aptarro, put the reason governance works this way: "Sales reps are incentivized to stick to price book because they can get their deal out the door much faster." In Aptarro's case study, average time in negotiation went from about 29 days to about 6 after they moved quoting into HubSpot with Quotivity.
Aptarro, average time in negotiation
29 days → 6 days
About 79% less time after moving quoting into HubSpot with Quotivity. Read the case study
If every quote gets the same single sign-off, or none, conditional routing won't save you anything. Turn on HubSpot's standard approvals with one filter and move on.
And if you're on Revenue Hub Enterprise and your rules are only about discount and amount, HubSpot's advanced approvals already handle that. You'd be adding a tool to solve a problem you don't have.
If your rules include contract term length, book a demo and bring your written rules. We'll show you which of your recent quotes would have needed an approval.
Usually because every quote gets routed, the approval rules aren't written down, approvals go to one named person, and edits after approval restart the process.
Yes. Standard approvals come with Revenue Hub Professional and Enterprise. Advanced approvals, which are workflow-based and support sequences and team routing, need Revenue Hub Enterprise. You can't run both at the same time.
HubSpot's approval use-case page says approval properties can't set a specific term length in months. Quotivity can route approvals on contract term length on every plan.
Yes. Margin is one of HubSpot's commonly used approval properties. Quotivity also routes on margin, on every plan, so a quote under your margin floor goes for approval before it can be sent.
In Quotivity, an edited approved quote goes back to approval by default. On the Enterprise plan, Smart Approvals lets it skip the approvals it already cleared.