The Eight-Week Review Playbook 2026
Eight weeks after a move, this play brings the account back up and asks what changed. It keeps activity, progress and business result apart, checks what else played a part, and puts the verdict on the CRM record: it worked, change it, stop it, or give it more time – with the reason noted. Each quarter, what worked goes back into the benchmark.
Your team runs moves every week. Each one is a chance to learn what works for which accounts – if someone looks back against a result agreed before the move.
Don't stop at "We sent 40 emails." Track what happened next, and don't let a before-and-after chart give the play credit for what a pricing change did. This play is the look back, on a date agreed before the move, with the verdict on the account record.
Measure it on the share of moves reviewed on their date, the share that reached a business result, and revenue credited under one agreed rule.
How it works11 steps
01SignalAgree the result and the date before the move
The review starts before the move does. When the account owner takes a move from the weekly check, they fill in two fields:
- Success measure: a milestone from the benchmark – what comparable customers who renewed at the same or higher revenue reached – plus the business result it should lead to, and when. "Second team active: 3+ users in 3 of the last 4 weeks. Paid expansion by the renewal." No benchmark yet? Build it first.
- Review date: eight weeks out by default.
Under about a hundred accounts, run the review by hand: one spreadsheet row per move.
02ScoreKeep activity, progress and business result apart
Sending a message is activity. A customer reaching an agreed milestone is progress. A renewal or a paid expansion is a business result. Record the highest level reached.
Then ask what else played a part: a release, a pricing change, a campaign, a new champion. Credit revenue with the one rule your team agreed (template below), and where you can't tell, record Can't tell.
Say a guided session ran for a new team in week two, with three follow-up emails. Eight weeks on, six of their people are active in three of the last four weeks, and billing hasn't changed. That's progress; the business result isn't due until the renewal. (The numbers are illustrative.)
03DecisionApply the rule: did it reach the agreed result?
Yes if every part of the success measure is met. Anything else is Not yet – including a milestone met with the business result still to come, and a result that arrived but isn't the one you agreed.
04ActionWorked: record the result and how it's credited
Set Review result and Credit, add Revenue credited if the rule allows it, and clear Recommended move and Review date. The account goes back into the weekly check.
05DecisionNot yet: change it, stop it, or give it time
Defaults; tune them. Apply them in this order:
- Stop: the customer said no, the reason for the move went away (a budget cut, the champion left), or this is the second miss in a row.
- More time: the milestone is met and the business result is due later, or the measure is at least halfway to target and still rising. One extension only.
- Change: everything else. Change one thing – who it went to, when, or the move itself – and say which.
If the move never ran, record No activity and choose Change (rerun it) or Stop.
06ActionDraft the changed move on the record
Set Recommended move to Change the move, with the change note, a new success measure and a new review date. The changed move uses the original play's templates.
07ActionStop the move and note why
Set Recommended move to Stop, write the stop note in Move reason, and clear the review date.
08ActionMore time: no move, with the reason and one more date
This is the play's leave-alone lane. Set Recommended move to No move, write the evidence that it's still moving, and set one more Review date – the renewal, in the example above. Don't add a second move on top; you'd lose the read on the first. Leave it alone covers holds in full.
09Human stepThe CS lead and account owner review it together
Once a week, go through everything due. The owner knows what the records don't and runs any next conversation with the customer. The lead applies the rules the same way across the team. If your team chose to automate a move, this is where you check it still earns its place.
10ActionEach quarter, feed what changed back into the benchmark
Read the quarterly roll-up: which moves reached a business result, for which accounts. Where practical, randomize move timing across equally eligible accounts. Otherwise, compare against similar accounts that hit the same trigger in the same window, and label the result observational. Retire moves that stayed at activity for two quarters (default). Adjust the benchmark where a milestone didn't lead to revenue, or where accounts below it renewed anyway. Your CS lead approves each change.
11OutcomeNext quarter: is the playbook sharper than the last?
Compare the quarters: more moves reviewed on their date, a higher share reaching a business result, fewer Can't tell. If nothing improved, check the success measures first – vague ones make every review a guess.
Setup and templates
Data sources: CRM activity on the record (what the team did); a saved query in PostHog, Amplitude or Mixpanel for the success measure; billing from Stripe or your CRM deals; release notes, pricing-change dates and campaign lists for what else played a part. 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. By hand: one spreadsheet row per move, filled on the review date.
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 |
|---|---|---|
| Play | Dropdown select: your plays | Account owner, at the move |
| What the team did | Single-line text | Account owner |
| Success measure | Single-line text | Account owner, before the move |
| Review date | Date picker | Account owner, before the move |
| Reviewed on | Date picker | CS lead, at the review |
| Review result | Dropdown select: Business result · Progress · Activity only · No activity | CS lead, at the review |
| Credit | Dropdown select: This move · Shared · Other cause · Can't tell | CS lead, at the review |
| Revenue credited | Number (currency) | CS lead, under the attribution rule |
| Recommended move | Dropdown select: Change the move · Stop · No move | CS lead and account owner |
| Move reason | Multi-line text | CS lead and 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: 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. A HubSpot workflow on Review date creates the owner's task, "Eight-week review: [account] – [move]", due that day, with the review note in the body. The same workflow sends the CS lead a notification.
Quarterly roll-up: a HubSpot report (Professional), shown as a pivot table, on companies with Reviewed on this quarter, grouped by Play and your segment property, showing counts by Review result and Credit and the sum of Revenue credited. By hand: filter the spreadsheet the same way.
Review note (logged on the record):
Eight-week review, [date]. Move: [what the team did, with dates]. Agreed: [success measure] by [review date]. Progress: [milestone reached? with the number]. Business result: [renewal or paid expansion? with the amount]. What else played a part: [release, pricing, campaign, people]. Credit: [This move / Shared / Other cause / Can't tell]. Next: [Worked / Change / Stop / More time, and why].
Change note: "Changed – [who / when / the move] because [evidence]. New measure: [milestone] by [date]."
Stop note: "Stopped – [customer said no / reason gone: what / second miss]. Back to the weekly check."
Attribution rule (agree it once, before the first review):
A before-and-after change alone doesn't show our move caused it, and credit is a rule we agree for the books, not proof. We credit revenue to a move when the success measure was met within [window], the move ran as recorded, and no [release, pricing change or campaign] touched the same measure for this account in that window. If one did, the credit is Shared. If we can't tell, we record Can't tell. Campaigns and releases are credited by this same rule. We record revenue after the move separately from revenue credited to it. Where it's practical, we stagger move timing across similar accounts, or compare with similar accounts that didn't get the move in the same window, and label that comparison observational.
No move (More time): "No move – still moving: [measure, now vs target]. Review [date]. One extension."
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. We agree the success measure and window for each move with you before it runs, and one rule for crediting revenue. Each week we bring up the moves due for review in the agreed segment, and the evidence and a recommended verdict land on the account record in your CRM – we recommend HubSpot – at a pace your team can run. Your team makes every call. Nobody from Accoil contacts your customers. After the agreed window, we review what worked together. We also revisit the benchmark, more frequently in the first 90 days, less so after that. You keep the playbook, the benchmark and the analysis.
Running it yourself? Swap HubSpot for Salesforce or Pipedrive (on Pipedrive, Premium or higher for the roll-up report, or keep it in the spreadsheet). The play stays the same. 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.
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
Build the Benchmark from Your Best Customers Playbook 2026
Every other play compares accounts with a benchmark. This is how to build it: pull the customers who renewed flat or up, shrank or left, strike the unfair matches, compare usage and revenue by customer type and stage, label thin segments low confidence, and have your CS lead approve what good looks like – then check it every quarter.
Expansion Signal to PQL Handoff Playbook 2026
Your customers who upgraded showed you what ready looks like before they asked. This play checks every account against them each week, confirms the records before anyone calls it ready, and puts the move on the account in your CRM: an upgrade conversation for your AE, an in-app prompt your team chose to automate – or no move, with the reason noted.
Renewal-Risk Radar Playbook 2026
Renewals go best when the account already looks like your customers who renewed. From 90 days out, this play compares every renewing account with them each week – usage and revenue – checks the records, and puts one move on the account in your CRM: an expansion look, a value review, a save plan with the CSM – or no move, 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.