An 8-step approval chain that takes 2 weeks to clear is killing the deal. The instinct is to remove approvers, which is governance-unfriendly. The better fix is to restructure the flow so it preserves controls without serializing every signature.
An enterprise deal needs to go through eight approval steps: discount approval, deal desk review, legal review, finance review, regional VP, global VP, CFO, CEO. Each step takes one to three days. Two weeks pass before the quote is signed. The customer has moved on or asked for a different vendor. The deal is dead, killed not by the price or the product but by the approval process.
The instinct from leadership is often to remove approvers. This is a governance-unfriendly fix that introduces real audit risk. The better fix is to restructure the flow so the controls are preserved but the signatures do not have to be serial.
Salesforce CPQ Advanced Approvals and RLM Smart Approvals both support multi-step approval chains. The default behavior is serial: step 1 must complete before step 2 begins, step 2 before step 3, and so on.
For an 8-step chain with average 1.5 days per step, the total clock time is 12 days. That number assumes every approver responds same-day, which is optimistic. Realistic clock time is 2 to 3 weeks.
Most approvals do not actually need to be serial. The CFO does not need legal to finish before the CFO can review. Regional VP and global VP often review the same data independently. Serializing them adds latency without adding signal.
The single biggest improvement: identify approval steps that are logically independent and run them in parallel.
RLM Smart Approvals supports parallel routing natively. CPQ Advanced Approvals requires more work to configure parallel branches but it is possible.
A typical 8-step chain restructured for parallel routing:
Discount approval (1 step)
↓
Parallel branch:
- Deal desk review
- Legal review
- Finance review
↓ (all three must complete)
Parallel branch:
- Regional VP
- Global VP
↓ (both must complete)
CFO
↓
CEO
The serial path through this structure is: discount approval (1.5 days) → max of (deal desk, legal, finance) (3 days) → max of (regional VP, global VP) (1.5 days) → CFO (1.5 days) → CEO (1.5 days) = 9 days.
Versus 12 to 18 days serially. The savings are visible without removing any approver.
Most approval steps gate on a threshold. Discount approval gates on discount percentage. CFO gates on deal size. The thresholds exist because risk scales with magnitude.
Below the threshold, the approval is procedural. The approver always says yes. The step adds latency without adding decision value.
Auto-approval below threshold: configure the approval rule to bypass the step when the criteria are clearly below the threshold. CFO step skipped for deals under $500K. CEO step skipped for deals under $2M. Discount approval skipped for discounts under 5 percent.
The risk: the threshold is wrong, and a deal that should have been reviewed slips through. The mitigation: log every auto-approved decision with the criteria values for audit, and review the threshold quarterly. Adjust based on what should and should not have been auto-approved.
Done well, auto-approval cuts the average deal's chain length in half while preserving the human review path for the deals that actually need it.
Not every deal needs every approval. A renewal of an existing customer does not need legal review (legal is in the master agreement). A net-new logo with custom terms does. Routing each deal through the right subset of approvers eliminates wasted steps.
Smart Approvals supports conditional routing through approval rule criteria. The rule fires only when the conditions match. Different deal types route through different chains automatically.
A practical conditional routing matrix:
| Deal type | Required approvals |
|---|---|
| Renewal at standard terms | Discount approval (if any), Auto-approve |
| Renewal with negotiated terms | Discount approval, Legal review |
| Net-new logo, standard contract | Discount approval, Finance review, Regional VP |
| Net-new logo, custom contract | Full 8-step chain |
| Large net-new logo (>$2M) | Full 8-step chain plus CEO |
The matrix encodes the actual decision rights. Renewals do not need executive sign-off. Custom contracts do. Configure the routing to match.
For repetitive deal shapes, package the configuration into a template that has been pre-approved.
Example: a standard new-customer deal at the published price with no custom terms. If this configuration is pre-approved as a category, then any deal matching this shape skips most of the chain. The first approver checks "matches template," approves, done.
Templates work when deals have repeatable shapes. They do not work for genuinely custom enterprise deals where every contract is bespoke. Build templates for the high-volume midmarket motion, keep the full chain for the strategic enterprise motion.
An approval that has not been responded to in N days escalates. The approver's manager picks it up. Then the manager's manager.
Configuring escalation prevents the dead-air case where an approver is on vacation, on leave, or otherwise unreachable. The deal moves regardless.
The escalation should not be punitive. The intent is to ensure deals keep moving when individual approvers are unavailable, not to call out specific people. Communicate the policy ahead of time, set reasonable thresholds (3 to 5 days for most approvals, longer for executives).
Sales reps cannot fix what they cannot see. A queue view that shows every quote in approval with the current step and time-in-step is a forcing function for the approver community to clear the queue.
Add SLA reporting: average time per approval step, by approver, over the past quarter. The data exposes the bottlenecks. The conversation moves from "why is the deal stuck" to "the CFO is the bottleneck and we need to either increase CFO bandwidth or restructure the chain."
This is governance-friendly: it preserves all the approvals but adds transparency about who is causing latency.
A practical sequence for a team facing slow approvals:
Sapota has run this sequence on enterprise CPQ engagements where chains went from 14-day clock time to 5-day clock time without removing any approver. The deals close, the audit trail is intact, the governance is preserved.
Restructuring approval chains in Salesforce CPQ or RLM? Sapota's Salesforce team holds the Revenue Cloud Consultant credential and handles Smart Approvals design on production engagements. Get in touch ->
See our full platform services for the stack we cover.
Other posts in the same topical cluster. The pattern in the post above usually shows up alongside the patterns below, either because they live on the same surface of the platform or because the same engagement type runs into both. Pick the one closest to the problem in front of you and start there.
Revenue CloudMay 23, 2026
Salesforce CPQ ships five pricing methods. Most implementations pick one and apply it everywhere. Real product portfolios need different methods for different product lines, and the wrong method produces quotes that are technically correct and commercially wrong.
Read More
Revenue CloudMay 17, 2026
Salesforce is sunsetting CPQ Classic. Every org running it has to plan a migration to Revenue Lifecycle Management. The work splits cleanly into four phases. The mistakes happen when teams compress phases that need their full duration.
Read More
Revenue CloudMay 20, 2026
Salesforce has signaled the direction. CPQ Classic is the past, RLM is the future. The question for every team running CPQ is not whether to migrate but when. Five org signals that should drive the decision.
Read More
Revenue CloudMay 24, 2026
Enterprise deals produce quotes with hundreds of line items. The CPQ page that loads in 2 seconds for a 10-line quote takes 30 for 200 lines. The bottleneck is usually one of five places, and the fix preserves the pricing logic.
Read MorePosts on the Sapota engineering blog are written by the engineer who shipped the pattern, not by a marketing copywriter. The byline above maps to a verifiable LinkedIn profile on the team page; click through and you will see the same author with a link back to recent posts. Posts that reference internal projects describe the relevant architecture and the gotchas in enough detail to be useful while keeping client-confidential specifics out of the public version.
If a pattern in this post matches what your team is currently building, the engineers who wrote it are usually available to scope an engagement. Sapota's engagement model starts with a two-week no-commitment trial scoped to a concrete deliverable, with named senior engineers from day one. Direct pricing starts at $1,800 per engineer per month, no agency markup, monthly rolling. Reach out via the contact page with a short description of the project and the rough timeline.
For more on the platforms Sapota ships on, see the services hub, which links to dedicated pages for Salesforce, Power Platform, Retool, Shopify, AI and machine learning, custom software, web app development, and mobile app development. For more posts in this topic area, browse the relevant category linked at the top of this page or use the blog index for a full chronological view.
Sapota is a senior-only engineering bench based in Đà Nẵng, Vietnam, working directly with global businesses and as the engineering tier behind 30 plus Vietnamese IT service firms. Direct pricing starts at $1,800 per engineer per month, with a two-week no-commitment trial that opens every engagement. No agency markup, no minimum commitment, no bait-and-switch between proposal and kickoff. The same engineers who run the trial continue the project if the fit is right. The about pagecovers the company-level context, the engagement model, and the operating principles that shape every project. The FAQ page answers the practical questions that come up in the first conversation with a prospective client.
One more note on how to use the patterns described above. Most posts intentionally stop at the pattern itself: the decision framework, the failure mode, or the configuration walkthrough. The post does not try to map onto a specific client engagement because the same pattern applies across very different project contexts. If you read a post and think "yes, this is what we just hit," that is the intended reaction; the next step is usually a quick scope conversation about whether Sapota can help, what team composition would make sense, and how the two-week trial would be structured around your specific deliverable. That conversation lives at the contact page and replies typically come within one business day.
We build trust by delivering what we promise – the first time and every time!
We'd love to hear your vision. Our IT experts will reach out to you during business hours to discuss making it happen.
"Collaborate, Elevate, Celebrate where Associates - Create Project Excellence"
SapotaCorp beyond the IT industry standard, we are
