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.
An account can find one use for your product and stop there, because nobody shows them the second.
Your best customers show you what comes next. Look at the ones who renewed or expanded: how many features they run each week, and which one they added second. An account living on one feature, where comparable customers run two or three, has a second value moment waiting – and those customers already tell you which feature it is.
This play works that gap weekly, one account at a time, inside the team already using the product. A new team starting is the second-department play; a paid add-on is the seat and add-on play; a bigger plan is the PQL handoff. Each check ends with a seed, or a note on why there isn't one.
Measure it on the share of accounts at benchmark breadth, the weeks from first to second feature, and renewal rate at benchmark breadth against one-feature accounts.
How it works10 steps
01SignalCompare every account with your broadest customers
Build the benchmark once, refresh it quarterly:
- Comparison customers: same segment (plan tier, size band), 12+ months as customers, renewed at the same or higher revenue. Aim for 20; with fewer, label it low confidence.
- What a feature is: the five to eight features that carry real work, each with one event that proves use – the report runs, the export sends, the integration syncs. Page views don't count.
- What regular use means: default, used in three of the last four weeks.
- The pattern: the median number of features in regular use, median ARR at that count, and – for each main feature – which feature those customers most often added next. Your CS lead approves it.
Each week, compare every account with it: fewer features in regular use than the benchmark median is a gap. Say an account pays $9,000 and lives in reporting, and similar customers run reporting, scheduled exports and alerts at $13,000: the $4,000 is a comparison, not a forecast. (The numbers are illustrative.)
Run it as a weekly saved query in PostHog, Amplitude or Mixpanel, or a spreadsheet. Under about a hundred accounts, do it by hand.
02ScoreCheck the records before calling it a gap
- Past onboarding? Default, 90 days in. Before that, one feature is normal.
- Peers who kept it: of comparable customers on the same main feature, how many added the next one and still use it 90 days later. Under one in four (default) is a weak fit.
- In their plan already? Check billing or the CRM. This play seeds what they already pay for; an add-on or a bigger plan goes to its own play.
- Renewal or org changes: 90 days of CRM notes and tickets, plus the renewal stage.
03DecisionDecide whether there's a move worth making now
Leave it alone if the account is still onboarding, the fit is weak, the next feature isn't in their plan (note which play picks it up), or the check found a cut, a departed champion or a renewal in procurement. Everything else picks a move.
04ActionLeave it alone, and write down why
Set Recommended move to No move, write the reason in one line, and set Review date to when it could change. A weak fit can mean a customer outside your core segment – no prompt fixes that, so give your CS lead a task to look at it. More in Leave It Alone.
05DecisionPick the move that matches how the account learns
- Self-serve: ARR under $10,000 (default) or no named CSM. The in-app prompt and story run on their own – a lane your team chose to automate.
- High-touch: everyone else. The seed goes on the record for the CSM's next call; if none is booked in 30 days (default), the task says book one.
06ActionPrompt the next feature where their main task ends
Show the prompt in Appcues at the moment the main task finishes – the report just ran, the export just landed – never on login. One sentence, prefilled with their work. Show it twice at most (default); a dismissal means not now.
07ActionSend a story of a team like theirs adding it
One Customer.io email, three days after the prompt (default): how a team of their size and main feature added the next one, and what changed. One link, landing inside the feature with the first step done. Suppress it the moment the feature shows up in their usage.
08ActionDraft the second use case on the HubSpot record
A task for the CSM with the evidence and the call note below. The CSM sets it due before the next call.
09Human stepThe CSM decides and brings it to the call
The CSM runs it as drafted, changes it, or passes. Before acting, record the success measure and the review date. Once these drafts have been right for a few weeks, your team may choose to automate more.
10OutcomeReview what changed, then sharpen the benchmark
On the review date, record three answers: is the second feature in regular use, did the account's measures move, and what else played a part? Sending a prompt is activity; the feature in regular use is progress; the renewal or expansion is the result. If nothing moved, change the move, stop it, or give it time. Each quarter, check which next features stuck for which accounts and update the benchmark.
Setup and templates
Data sources: feature events from your analytics tool or event table; plan and ARR from billing or the CRM; renewal stage and notes from the CRM. By hand: one row per account, one column per feature, marked when it meets the regular-use rule. Account-level numbers need your analytics tool's account add-on (group analytics in PostHog, Accounts in Amplitude, Group Analytics in Mixpanel) and a group call in your app. Save the query, then subscribe to it (in Amplitude, add it to a dashboard and subscribe to that) so the result lands in your inbox or Slack on the schedule you set.
Company properties in HubSpot (Starter or above; free HubSpot allows 10 custom properties in total), or your CRM's account object:
| Property | Type | Filled by |
|---|---|---|
| Features in regular use | Number | Weekly check |
| Benchmark features | Number | Weekly check |
| Next feature | Single-line text | Weekly check |
| Peers who kept it | Number (%) | Weekly check |
| Recommended move | Dropdown select: Self-serve seed · Next-call seed · No move | Weekly check |
| Move reason | Single-line text | Weekly check |
| Success measure | Single-line text | Account owner |
| Review date | Date picker | Weekly check, then account owner |
| Review result | Dropdown select: In regular use · Tried, not kept · Didn't try · Stopped | Account owner |
The automation here uses HubSpot workflows (any Professional hub). On Free or Starter, run the same saved view and create the tasks by hand.
The weekly list is a saved view: Recommended move is known and Review date is this week or overdue. In HubSpot that's two filter groups: Review date is This week, or Review date is before Today. Next-call seeds create a task for the CSM, "Second use case: [next feature]", with the call note in the body.
Self-serve seeds need no task: sync Recommended move and Next feature into Appcues through its HubSpot integration (it syncs every 30 minutes) and into Customer.io, and target Recommended move is Self-serve seed for each next feature. Send the task-finished event to Appcues and trigger the prompt on it, and set the flow to show at most twice. Send the feature's usage event to Customer.io and set it as the story's exit condition. If you use message limits, turn off auto-retry for this automation.
Log both sends on the HubSpot record. Customer.io writes each send with a webhook step that calls HubSpot's API; if the From address is a HubSpot user's, a BCC to your HubSpot logging address also works. Appcues logs each prompt on the contact's HubSpot timeline.
Apply these checks to marketing emails sent by hand or automatically: permission to send, accurate sender details, required address information, an easy unsubscribe and shared suppression checks. Keep required service notices separate from marketing.
In-app prompt (Self-serve):
[Action that finishes their main task] – want [next feature] to [result] every [time]? [Set it up]
Story email (Self-serve):
Subject: How [team like theirs] uses [next feature] with [main feature]
Hi [name] – [peer team] used [main feature] the way you do. They added [next feature] to [job], and [what changed]. It takes about [time] to set up: [link to the first step].
Call note (High-touch): what they use today · what comparable customers added next, and how many kept it · the one job it would take off their plate · the ask: "Who on your team owns [job]?" (a person's project outlasts the call) and a date to try it.
No move: "No move – [reason]. Recheck [date]."
How Accoil fits
Accoil is a customer-success consultancy with our own tooling, and this is a play we run with you, not for you. We build the benchmark with your team, and you approve it. Every week we check every account in the agreed segment, and the recommended move and its evidence land on the account record in your CRM – we recommend HubSpot – at a pace your team can actually run. Your team makes every call, including which moves run on their own. Nobody from Accoil contacts your customers. After the agreed window we review what changed together, and you keep the playbook, the benchmark and the analysis.
Running it yourself? Swap HubSpot for Salesforce or Pipedrive, Appcues for Candu (its HubSpot sync only reads, so note prompts by hand, and a developer triggers the prompt through Candu's JavaScript API), and Customer.io for Ortto. On Salesforce, the field writes need API access (Enterprise and up, or an add-on on Professional). On Pipedrive, automations and date triggers need the Growth plan. The play stays the same.
Thirty minutes with Kate, Simon or Peter on one example segment: what a successful customer looks like, where the gaps are, and whether there's work worth doing this quarter.
Talk to a founder →Keep reading
Community-Led Retention Loop Playbook 2026
Your advocates are already in your data: the accounts and people using the product well past what your successful customers do. This play takes them from the weekly check, looks for a reason to wait, and puts one ask on the account in your CRM: a community invite your team chose to automate, a CSM's personal ask – or no move, with the reason noted.
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.
Pricing Migration Without the Churn Spike 2026
New pricing is a chance to put every customer on the plan that fits how they already work. This play sorts each account by its usage against the new packaging and your successful customers, then runs the move on the CRM record: a wave notice, an upgrade case, a call first – or no move until renewal, with the reason noted.
Every playbook, one download
All 32 workflows as print-ready playbooks — diagrams included. Plus every new workflow as we publish it.