In-app Onboarding

Candu

Native-feeling in-app content, built without engineers.

candu.ai →

How teams use it post-sale

Candu lets CS and growth teams ship in-product banners, checklists and empty-state content that looks native. Driven by engagement segments, the same surface can show a getting-started checklist to a stalled trial and an expansion prompt to a team bumping against its plan limits.

Swap it within In-app Onboarding

Any of these runs the same plays — Accoil pushes the same signal wherever the work happens.

Where Candu swaps in5

No published workflow names Candu yet — it’s here as a swap-in equivalent. Every play below runs on a in-app onboarding tool that Candu can stand in for; the signal and the steps stay the same.

YOUR EXISTING EVENT STREAMAPIYESLEAVE ALONEREADYSIGN-OFFPAIDSIGNAL · ACCOILWeekly check: one departmentwhere peers run twoDepartments on theproductPeers' departmentcountPlan & ARR vs peersSigns of a second teamSCORE · ACCOILCheck the records before callingit a gapSecond teamconfirmedAlready paid for?Champion & inviterBudget or org changesDECISIONIs there a move worth makingnow?DECISIONWhich move fits this account?ACTION · HUBSPOTDraft a champion-led rollout onthe HubSpot recordACTION · HUBSPOTDraft a sponsor conversationwith the evidenceACTION · HUBSPOTDraft a guided session to help thesecond team startACTION · HUBSPOTNo move: note why on the recordfor the next checkHUMAN STEPAE or CSM decides and runs themoveACTION · APPCUES Onboard the second team ontoits own use caseOUTCOMEEight weeks on: did the teamstart, did billing change?
SalesAccount Management

Second-Department Expansion Playbook 2026

Your best customers run the product in more than one department. This play checks every account against that benchmark each week, confirms the second team is real before anyone calls it a gap, and puts the right move on the account in your CRM: a champion-led rollout, a sponsor conversation, a guided session – or no move, with the reason noted.

Intermediate
YOUR EXISTING EVENT STREAMAPIYESLEAVE ALONESELF-SERVEHIGH-TOUCHSIGNAL · ACCOILWeekly check: one feature wherepeers use two or threeFeatures in regular usePeers' feature countNext feature peersaddedPlan & ARR vs peersSCORE · ACCOILCheck the records before callingit a gapPast onboarding?Peers who kept itIn their plan already?Renewal or orgchangesDECISIONIs there a move worth makingnow?DECISIONWhich move fits this account?ACTION · APPCUES Prompt the next feature wheretheir main task endsACTION · CUSTOMER.IO Send a story of a team like theirsadding itACTION · HUBSPOTDraft the second use case on theHubSpot recordHUMAN STEPCSM decides and brings it to thenext callACTION · HUBSPOTNo move: note why on the recordfor the next checkOUTCOMEEight weeks on: is the secondfeature in regular use?
SuccessGrowth

Second-Value Seeding Playbook 2026

Your best customers show you which feature comes after the first. This play checks every account against them each week, finds the feature customers like it added next and kept, and puts the move on the account in your CRM: an in-app prompt and a short story, the CSM on the next call – or no move, with the reason noted.

Starter
YOUR EXISTING EVENT STREAMAPIYESLEAVE ALONEOVER 90DINSIDE 90DRIGHT-SIZESIGNAL · ACCOILWeekly check: fewer seats in usethan peers your sizeActive vs paid seatsPeers' active-seat %Plan & ARR vs peersActivity per seatSCORE · ACCOILCheck the records before callingit a gapSustained, notseasonal?Quiet vs never startedDays to renewalCuts, champion &ticketsDECISIONIs there a move worth makingnow?DECISIONWhich move fits this account?ACTION · HUBSPOTDraft a seat review with bothpaths on the recordACTION · HUBSPOTDraft a reactivation plan for theunused seatsACTION · HUBSPOTDraft a right-size quote with theseat listACTION · HUBSPOTNo move: note why on the recordfor the next checkHUMAN STEPAM or CSM decides and runs themoveACTION · APPCUES Guide never-started seats to afirst result in-appACTION · STRIPEIssue the right-size quote at thestandard rateOUTCOMEEight weeks on: seats in use, or aright-size agreed?
Account ManagementRevOps

The Shelfware Confession Playbook 2026

Seats paid and seats in use drift apart. This play compares each account's seat use every week with customers its size that renewed at the same or higher revenue, checks the records before calling it a gap, and puts one move on the account in your CRM: a seat review with both paths, a reactivation plan, a right-size quote – or no move, with the reason noted.

Intermediate
YOUR EXISTING EVENT STREAMAPIYESNODROPPEDCALLTHE RESTSIGNAL · ACCOILWeekly check picks up thechange your team recordedAccounts it shouldtouchTheir usage beforeAgreed successmeasureHeld back from thelaunchACTION · BEAMERBTell the accounts it's for, noteveryoneACTION · APPCUES Guide first use to the result itexists forSCORE · ACCOILFour weeks on: told vs held back,by segmentMoved as expectedTried and droppedNo changeMoved the wrong wayDECISIONDid it land, or is there a reason towait?ACTION · HUBSPOTNo move: adopted, or a reason towaitDECISIONWhich move fits this account?ACTION · APPCUES Ask one question at the drop-offpointACTION · HUBSPOTDraft a CSM conversation on theHubSpot recordACTION · APPCUES Send the guide again, logged onthe recordHUMAN STEPPM and CS lead read the resulttogetherOUTCOMEEight weeks on: what did theearlier launch earn?
GrowthSuccess

What Changed After the Release Playbook 2026

Every release, price change and campaign is a change worth measuring. This play picks the accounts a change should touch before it ships, tells and guides only them, and four weeks on sorts each one: moved, tried and dropped, no change, or the wrong way. Accounts that moved are left alone; the rest get a move on the CRM record.

BIntermediate
YOUR EXISTING EVENT STREAMAPIYESLEAVE ALONEA FIXA NEW PLANSIGNAL · ACCOILAgreed check date, or your teamflags a relevant fixReason they leftUsage at exit vsbenchmarkARR when they leftWho made the callSCORE · ACCOILCheck the fit at exit and whetherthe reason still standsFit at exitFixed or repricedsince?Months since they leftDecision-maker stillthere?DECISIONIs a win-back worth making now?ACTION · HUBSPOTNo move: note why and whatwould change itDECISIONWhat answered why they left?ACTION · HUBSPOTDraft a 'we fixed it' note on theHubSpot recordACTION · HUBSPOTDraft a new-plan note on theHubSpot recordHUMAN STEPAE decides, sends it and answersany replyOUTCOMEEight weeks on: did they reply,did anyone come back?
GrowthSales

Churned-Account Win-Back Playbook 2026

Some former customers left over one reason your team has since fixed. This play checks them each quarter, and whenever a fix or new plan ships: did they look like your successful customers before they left, and does the reason still stand? The answer lands on the CRM record as a drafted note for the AE, or no move, with the reason and a recheck date.

BStarter

Browse the full library →

The playbook pack

Every playbook, one download

All 32 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.