Skip to main content

Approval workflows

Approvals are where deal velocity usually goes to die. Dealops keeps them fast by deriving the right approval chain from the deal itself, letting approvers act where they already work, and skipping approvals that have effectively already happened.

How a chain is built​

When a quote is submitted, Dealops evaluates your approval rules against the deal and assembles a chain of approval groups — teams like Deal Desk, Finance, or Legal, each with its own assignees.

Rules can trigger on the dimensions that matter to each group:

Rule familyExamples
DiscountsDiscount beyond a threshold, on a product, category, or the whole deal
ProductsA specific product selected; a custom product added; volume above a limit
Deal shapeTotal value, net-new ARR, margin, term length, non-standard payment terms
TermsA specific term value or range — e.g., a non-standard SLA selection
Deal contextOpportunity type, CRM field values, customer segment

Different deals produce different chains: a clean in-guidance quote may need no approvals at all, while a deep-discount multi-year ramp routes through management and finance.

Acting on approvals​

Each step in the chain is assigned to its group's approvers, who can:

  • Approve or reject in Dealops or directly from Slack, with comments threading back into the deal.
  • Discuss in context — questions and answers happen on the quote (or its Slack thread), not in side-channel DMs.

Reps see live status per step. If the deal changes materially, the rep can recall the submission, revise, and resubmit — and smart approvals make resubmission cheap, because steps whose concerns are unchanged auto-pass.

Admins can override a step when needed; overrides are recorded as such.

Transparency before submission​

The deal summary shows which rules a quote will trip before the rep submits — the discount that needs a VP, the custom product that needs deal desk. No submitting blind and waiting to find out.

Audit trail​

Every approval event — request, decision, recall, override, and where it happened (web or Slack) — is recorded on the quote and emitted to the platform event stream, giving revenue operations a complete, queryable history of who approved what, when, and why.