RevOps playbook · AI Employee: Rev

Closed-Won Cascade

Time from close to kickoff halved

Install this playbookBack to marketplace
The problem

The moment a deal closes-won is a coordination frenzy. Provisioning fires (or doesn't), billing gets set up (or doesn't), CS gets the account (or doesn't), the AE writes the celebration Slack post. Every step matters; every step gets missed by a different team. "We closed Acme two weeks ago but they still don't have production access" — that's the failure mode.

At a glance
Trigger
CRM event
Approvals
None (rule-based)
What it does
Writes to your systems
Systems
Salesforce · HubSpot · Finance · Provisioning · CS platform
How it feels in production

An hour-by-hour walkthrough.

Tuesday 4:47pm. Priya (AE) closes-wins the Acme deal in Salesforce. Stage change fires the cascade. 4:47pm + 5 sec. Rev reads the deal: $120k ARR, 12-month contract, product SKUs = [Platform Pro, Add-on Analytics]. Fires the provisioning webhook to the platform team's queue with account details. 4:47pm + 10 sec. Rev creates the customer record in the billing system (Chargebee) with contract terms, MRR, plan SKUs. Initial invoice scheduled for the contract start date. 4:47pm + 15 sec. Rev assigns the CS owner per territory rules (Alex is the SF-region CSM). Creates the customer record in the CS platform (Gainsight) with account context, deal size, key contacts. 4:47pm + 20 sec. Rev schedules the customer kickoff meeting on Priya (AE) + Alex (CSM) + the customer's key contacts' calendars for the following week. 4:47pm + 25 sec. Rev posts to #wins Slack channel: "🎉 Acme closed! $120k ARR, 12-mo. AE: Priya. CSM: Alex. Kickoff scheduled Thu. Welcome!" Total elapsed: 25 seconds. No dropped balls. No follow-up emails between five teams. The AE moves on to the next deal; the CSM gets a prepared account; the customer gets a smooth handoff. If any downstream step fails (provisioning webhook 500s, billing account already exists, CSM out of office), Rev routes to the appropriate exception queue with context. Nothing silently fails.
How it works

Step by step.

  1. 01

    Read deal event

    Salesforce / HubSpot webhook for stage=Closed-Won. Rev extracts: deal size, contract term, product SKUs, primary contact, secondary contacts, sales-cycle notes.

    Salesforce · HubSpot
  2. 02

    Trigger provisioning

    Webhook to platform team with account creation details. Auto-provisioning where possible; ticket for manual provisioning where required. Provisioning status tracked.

    Provisioning API · Internal platform
  3. 03

    Set up billing

    Create customer record in billing system (Chargebee / Stripe / Zuora) with contract terms + payment schedule. Initial invoice scheduled per contract start date.

    Chargebee · Stripe · Zuora · NetSuite
  4. 04

    Assign CS owner

    Per territory + segment rules, assign CSM. Create customer record in CS platform (Gainsight / ChurnZero / Vitally) with full account + deal context.

    Gainsight · ChurnZero · Vitally
  5. 05

    Schedule kickoff

    Kickoff meeting on AE + CSM + customer contacts' calendars. Meeting agenda template populated from deal notes + customer's stated priorities.

    Google Calendar · Outlook · Zoom
  6. 06

    Notify and celebrate

    Post to #wins Slack channel with deal summary + team credits. AE + CSM + provisioning team + billing team all tagged. Marketing gets notification for case-study prospecting.

    Slack · Teams
Systems and wiring

What you connect to make this run.

Salesforce · HubSpot

trigger

Stage-change webhook on Closed-Won. Rev reads deal + account + contacts + notes to feed downstream.

Chargebee · Stripe · Zuora

write

Customer + subscription creation via API. Contract terms mapped to plan SKUs; first invoice scheduled.

Gainsight · ChurnZero · Vitally

write

Customer record with full deal context. Enables CSM to prepare without asking AE for context.

Slack · Teams

write

Wins celebration + team notifications. Customer-specific channels created for larger deals.

Google Calendar · Outlook

write

Kickoff meeting scheduled with agenda + attendees. Handles time-zone conversion + attendee availability.

What changes

Before and after, honestly.

Time from Closed-Won to full cascade complete
Before
3-10 business days
After
Under 1 minute for automated steps; kickoff scheduled within 24h
Provisioning failures caught before customer notices
Before
40-60% (customer often reports the issue)
After
> 95% (automated verification + exception queue)
AE time on closed-won handoff
Before
1-2 hours per deal across 3-5 hand-off emails
After
Zero for standard deals; time only for exception cases
Customer time-to-first-value
Before
2-4 weeks post-close
After
1-2 weeks (faster kickoff + provisioning enables faster value)
Related

Playbooks that pair with this one.

RevOps

Pipeline & Deal Lookup

Complementary — the lookup pattern that AEs use during the sales cycle.

RevOps

Closed-Lost Cascade

The inverse — different downstream actions but similar coordination challenge.

RevOps

Renewal Pipeline Review

Downstream — every closed-won becomes a renewal deal in 11 months.

RevOps

Deal Stage Gate Enforcement

Stage-gate ensures required fields (contract terms, contacts) are set before Closed-Won fires the cascade.

Frequently asked

Answers about this playbook.

What if a provisioning step fails?

Rev routes to the exception queue with the failure context. Platform team gets a Slack notification. Customer isn't notified of the failure — Rev retries the provisioning or the platform team resolves manually before the kickoff meeting.

Can we customise the cascade per deal size?

Yes — enterprise deals may trigger additional steps (dedicated Slack channel with customer, exec sponsor introduction, custom onboarding plan). SMB deals use the standard cascade.

How does this handle multi-year contracts?

Contract terms determine renewal-schedule creation. 3-year contracts create three renewal events with different SLA windows for each. Rev + Fin coordinate on multi-year revenue recognition.

What about deals with implementation services?

Additional cascade step for services-included deals: assign implementation manager, schedule kickoff with services team + customer stakeholders, create SOW record in the services PSA tool.

Can we prevent the cascade for test / demo deals?

Yes — flag deals as "internal / test" to skip the cascade. Rev respects the flag; useful for POCs that convert to real deals separately.

See it run on your data.

Free plan, no credit card. Connect the systems this playbook needs and run it against a past event first.

Book a demoMore RevOps playbooks