The post-sale workflows library

Workflows for sales and expansion

Expansion PQLs, second-department land-and-expand, support-sourced pipeline and win-backs — the revenue motions that live inside accounts you already closed.

7 workflows · free, no gate
YOUR EXISTING EVENT STREAMAPISALES-READYNOT YETSIGNAL · ACCOILEngagement hits 85+ with seatsnear the plan limitEngagement scoreSeat utilization %Feature-limit usageAccount segmentSCORE · ACCOILQualify against your expansionprofilePQL scoreExpansion typeChampion contactCurrent ARR & planDECISIONSales-ready or still building thecase?ACTION · HUBSPOTCreate the expansion opportunityin the CRMACTION · SLACK Alert the account owner in#expansionHUMAN STEPAE runs a usage-groundedexpansion callACTION · INTERCOMShow upgrade prompts at thelimit momentsOUTCOMEExpansion closed on observedvalue
SalesSuccess

Expansion Signal to PQL Handoff Playbook 2026

Expansion revenue hides in usage data long before anyone asks for a bigger plan. Catch accounts that cross your expansion threshold — engagement high, seats nearly full, limits being hit — qualify them against a written PQL profile, and hand the sales-ready ones to an AE with the evidence attached. Everyone else gets in-app prompts instead of a pitch.

+1Intermediate
YOUR EXISTING EVENT STREAMAPIADD-ONSEATSSIGNAL · ACCOILFeature adoption crosses theadd-on thresholdFeature-by-featureusagePower users perfeatureSeat growth trendPlan & entitlementsSCORE · ACCOILMap usage against what theyactually pay forEntitlement gapsBest-fit add-onWho'd champion itValue evidenceDECISIONAdd-on attach or seat true-up?ACTION · HUBSPOTOpen the add-on opportunitywith evidenceHUMAN STEPAM demos the add-on insidetheir live dataHUMAN STEPAM brings the seat true-up to theQBROUTCOMEUpsell attached to value alreadyproven
SalesAccount Management

Seat & Feature-Adoption Upsell Playbook 2026

Accounts tell you what they'd pay more for by how they use what they have: a feature worked to its limit, seats stretched past the contract, power users deep in add-on territory. Read feature-by-feature adoption against the plan they pay for, find the entitlement gaps, and route each to the right motion — an evidence-backed add-on demo or a seat true-up at the QBR.

Intermediate
ON TRACKSTALLEDSIGNAL · HUBSPOTDeal hits closed-won in the CRMContract & planPromised use casesStakeholder mapSales call notesACTION · SLACK Post the handoff brief to#cs-handoffsHUMAN STEPCSM runs kickoff within sevendaysSCORE · ACCOILWatch the first-30-dayengagement baselineDays to first valueSeats active vs. soldActivation %Momentum vs. cohortDECISIONMoving like a healthy cohort byday 14?HUMAN STEPCSM reworks the plan with thechampionOUTCOMEFirst value delivered inside 30days
SuccessSales

Sales to CS Handoff Playbook 2026

The riskiest moment in a customer's life is the week after the signature, when sales moves on and CS starts from a blank page. This play moves the deal context to the CSM automatically, captures a day-zero engagement baseline the moment events start flowing, and checks the account against a healthy cohort at day 14 — so a stalled start gets re-planned in week two, not discovered at the first QBR.

Starter
PRODUCT GAPPRICINGSIGNAL · HUBSPOTChurn completes with a loggedreason codeReason codeARR lostMost-used featuresExit-interview verbatimSCORE · ACCOILClassify winnability from the exitevidenceWinnable classWatch triggerCooling periodDECISIONWhich unlock reopens the door?ACTION · BEAMERBWatch the changelog for the fixthat matchesACTIONWatch pricing and packaging forthe unlockACTION · CUSTOMER.IO Send the win-back: you leftbecause X; X shippedHUMAN STEPAE answers any reply personallywithin a dayOUTCOMEResurrection revenue on its ownreporting line
GrowthSales

Churned-Account Win-Back Playbook 2026

Every churned account is a lead with a documented objection, and your changelog eventually answers many of them. This play logs a reason code at churn, classifies winnability from the final engagement snapshot, watches for the unlock that answers the objection, and fires a win-back that says "you left because X; X shipped last month" to the person who made the call.

BStarter
YESNOSIGNAL · USERGEMSNew economic-buyer executivelands at the accountNew exec role & titleStart dateSCORE · CLAYEnrich the exec: background,stack, prioritiesPrevious company'sstackPublic prioritiesRenewal distanceSCORE · ACCOILCheck audit exposure: is yourvalue visible?Exec-visible usageValue doc freshnessChampion strengthDECISIONRenewal inside the exec's first 6months?HUMAN STEPAM runs the 90-dayre-onboarding of the new execACTION · SALESFORCE Refresh the value narrativebefore it's requestedACTIONRun the champion-departure playon the old execOUTCOMERenewal survives the audit; anew sponsor emerges
Account ManagementSales

New Executive, New Rules Playbook 2026

A new CFO or CTO runs a tool audit in their first 90 days, and tools they didn't buy die first — your renewal was decided the day they were hired. This play catches the hire the week it happens, enriches who they are and what stack they came from, scores how visible your value is to someone who wasn't there for the sale, and puts the AM in front of them — in their frame — before procurement asks.

Intermediate
YOUR EXISTING EVENT STREAMAPISTICKINGNOT YETSIGNAL · ACCOILUsage cluster appears outsidethe home departmentNew-team user countInviter identityFeature mix vs hometeamNew-cohort growthrateSCORE · ACCOILQualify the beachhead onweek-2 retentionNew-cohort retentionSeats on current planAccount healthDECISIONBeachhead sticking?ACTION · SLACK Alert the AE in #expansion withthe cluster mapACTIONWatch the cohort; recheckretention in 30 daysHUMAN STEPAE asks the champion for thewarm introACTION · APPCUES Launch department-specificonboardingACTION · SALESFORCE Open a second-departmentopportunityOUTCOMEA second department on its ownuse case
SalesAccount Management

Second-Department Expansion Playbook 2026

Usage spreading across team boundaries is visible in the product data weeks before anyone asks for seats. This play detects the new-team usage cluster, qualifies the beachhead on week-2 retention, gets the champion to make the warm intro, onboards the new department onto its own use case, and books the deal as a second-department expansion — not a seat upsell.

Intermediate
YESNOSIGNAL · ZENDESKTicket tagged feature-request orlimit-hitTicket topicRequester roleRequests acrossaccountCurrent planSCORE · ACCOILQualify the request withengagement contextEngagement scoreActive-seat trendFeature the ask mapstoPlan gapDECISIONExpansion-qualified?ACTION · SLACK Route to the AE as a PQL with theticket verbatimACTIONFile to product feedback withaccount contextHUMAN STEPAE opens the expansion talkwithin 5 daysACTION · SALESFORCE Log the opportunity with asupport-sourced codeOUTCOMEExpansion pipeline sourced fromsupport
SalesSuccess

Support-to-Expansion Goldmine Playbook 2026

Feature-request and limit-hit tickets from power users are pre-qualified expansion pipeline hiding in the support queue. This play catches the tagged ticket, qualifies it against engagement and plan data, routes the real opportunities to an AE as a PQL with the customer's own words attached, and measures support-sourced pipeline as its own number.

Starter
The playbook pack

Every playbook, one download

All 31 workflows as print-ready playbooks — diagrams included. Plus every new workflow as we publish it.

On-page playbooks stay ungated. Downloading subscribes you to new workflows from Accoil — unsubscribe anytime.