What's the right way to model deal desk approval workflows in Salesforce — flow, approval process, or external tool — and how does that decision change at $50M vs $500M ARR?
How to Model Deal Desk Approval Workflows in Salesforce: Flow vs. Approval Process vs. External Tool
At $50M ARR, native Salesforce Flow Orchestration handles 90% of deal desk approval needs — discount thresholds, multi-level sign-offs, legal flagging — without external tooling. At $500M ARR, that changes fast: pricing complexity, SOX audit trails, and multi-channel revenue models push you into purpose-built CPQ platforms like DealHub or Salesforce Revenue Cloud as the system of record, with Salesforce as the CRM shell.
---
THE DETAIL
#### The Three Options, Honestly Ranked
1. Classic Salesforce Approval Process (legacy) Use only if you're pre-Series B, have a single approval tier, and your admin can't build flows. Legacy approval processes were built on a rule-based engine that lacks flexibility and modern automation features. It breaks the moment you need parallel approvals, conditional routing, or audit-grade recall.
2. Salesforce Flow Orchestration (current standard) Salesforce introduced Flow Approval Processes in the Spring '25 release — an evolved version of the classic approval process model, powered by Flow Orchestrator, bringing unprecedented flexibility with dynamic, multi-level, and logic-driven approval workflows that are entirely declarative.
This is your default tool at $20M–$150M ARR when:
- Discount thresholds trigger VP/CFO review
- Deal size buckets require different approver chains
- Legal needs a flag on non-standard terms
Flow Approval Processes use decision elements to create conditional paths based on specific criteria — for example, if a contract exceeds a certain dollar amount, it can require additional approvals from senior management.
Unlike legacy approval processes, Flow Approvals support advanced logic, better error handling, recalls, and enhanced debugging.
One real limitation: Taking one whole chunk of automation — approving, routing, field updates, email alerts, record creation — and putting it in Approval Processes instead of Flow makes debugging more difficult when there are inevitable issues. Build it all in Flow Orchestrator from day one.
3. External CPQ Platform (DealHub, Conga, Salesforce Revenue Cloud) Once you cross $150M ARR — or earlier if you have multi-product pricing, ramp structures, usage-based billing, or co-terming — native Salesforce approval tooling becomes a liability.
In Salesforce Revenue Cloud, the GTM (quote/CPQ) logic tends to live in backend code, meaning development or technical teams are required for changes. In DealHub, RevOps owns the GTM logic via no-code rules, which allows faster updates without waiting on Dev/SI.
DealHub supports multi-level approval chains based on discount percentage, deal size, or custom criteria, with pricing governance that RevOps can configure and enforce.
At $500M ARR, you likely need SOX-compliant audit trails: built-in ASC 606 and IFRS 15 compliance engines automate revenue recognition across complex scenarios like co-terming, prorated upgrades, and multi-element arrangements, while maintaining complete audit trails that satisfy SOX requirements.
---
Decision Matrix by ARR
| ARR | Recommended Stack | Why |
|---|---|---|
| <$20M | Classic SF Approval Process | Low complexity; no RevOps admin bandwidth |
| $20M–$100M | SF Flow Orchestration | Multi-tier routing, no-code, declarative |
| $100M–$250M | Flow Orchestration + CPQ layer | Pricing complexity, AE scale, legal velocity |
| $500M+ | External CPQ (DealHub, Revenue Cloud) + SF shell | SOX, multi-channel, RevOps-owned logic |
---
Visual
---