Second-Department Expansion Playbook 2026

Build the benchmark once, refresh it quarterly:

1. 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.
2. What a department is: a team property on users, a workspace per team, or job titles on CRM contacts. Email aliases are the fallback.
3. What active means: default, three or more users active in three of the last four weeks.
4. The pattern: the median number of active departments, and median ARR at that count. Your CS lead approves it.

Each week, compare every account with it: active departments, ARR against peers, and signs of a second team (new users outside the first department, a new workspace, a support thread about work done by hand). Say an account pays $12,000 and similar customers with both departments pay $18,000: the $6,000 is a comparison, not a forecast. (Inspired by a real business; the numbers are rounded and 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.

• Second team confirmed: it meets the active rule. Less is interest.
• Already paid for? Check the contract in billing or the CRM. If it's covered, the job is adoption, not new revenue.
• Champion & inviter: who invited the new team (your invite events), or the first department's most active user. Record it now.
• Budget or org changes: 90 days of CRM notes and tickets, plus the renewal stage.

If the new team does the same job as the first, it's seat growth – use your seat-upsell play instead.

Leave it alone if the second team isn't confirmed, or the check found a cut, a departed champion or a renewal in procurement. Everything else picks a move.

Set Recommended move to No move, write the reason in one line, and set Review date to when it could change. Send a "we noticed your team started using us" note only after you've confirmed the new team is real.

• Ready: confirmed team, known champion, not in the contract. Rollout.
• Sign-off: same, but budget or cross-department approval is the blocker. Sponsor conversation.
• Paid: the contract covers them; they haven't started. Guided session.

A task for the account owner with the evidence and the champion note below. The person who won the first department is your best way into the second.

The sponsor brief below: the work the team does by hand today, what comparable customers run, and a rollout plan with a start date.

Don't sell them what they own. Offer thirty minutes on how their own work runs in the product. No new revenue this quarter – but whether they start decides the renewal.

The AE or CSM reads the evidence and runs it as drafted, changes it, or passes. They own every customer conversation. Before acting, record the success measure and the review date: the team active in four weeks is progress; a paid expansion within a quarter is the result. Once a lane's drafts have been right for a few weeks, automate it. The guided-session invite is a good first candidate.

A department-specific flow in Appcues, targeted on the department field: their first win, their templates, their vocabulary. Book the deal as a second-department expansion, not a seat upsell, so the forecast and the renewal both see the new team.

On the review date, record three answers: did the team start, did billing change, and what else played a part? If nothing moved, change the move, stop it, or give it time. Each quarter, check which moves worked for which accounts and update the benchmark. A second department is a second reason to renew.