Second-Department Expansion Playbook 2026

Watch for a usage cluster that doesn't belong to the original department: users on a new email-domain pattern (marketing@ where engineering@ landed), a newly created workspace, or a burst of invites from one team to people the account has never seen before. Accoil's traits and segments make the "home department" explicit, so the outlier cluster is a query, not a hunch.

• The signal carries the fields the whole play runs on: new-team user count, the inviter's identity, the new cohort's feature mix vs the home team's, and its growth rate.
• Three or more users from the new group within two weeks is a cluster; one curious visitor is noise. Don't fire on the first stray login.
• Capture the inviter at detection time — it's the single most valuable field in this play, and it's unrecoverable later.

An invite burst proves curiosity; retention proves a use case. Score the new cohort on whether its usage is sticking — week-2 retention of the new users is the cleanest single test. Out of this step come the fields the routing decision reads:

• New-cohort retention — what share of the new team's users came back in week two. Above roughly half, you have a beachhead; below, you have a demo that happened to spread.
• Seats on current plan — how much room the account has before the commercial conversation is forced anyway.
• Account health — never run an expansion motion on a shaky account; a struggling home team plus a new department equals two churn risks, not one opportunity.

And read the feature mix carefully — it's the classifier. If the new team uses the same features as the old one, this is seat growth: price it that way and route it to the seat-upsell play. If the mix diverges, it's a new use case — scope it like a new deal, because it is one.

One rule: week-2 retention above the bar and account health solid → the expansion motion starts. Anything less → watch, don't pounce. The expensive mistake is jumping on day 3 with a sales call about usage the new team barely remembers trying — you get one credible "we noticed your marketing team started using us" moment per account, so spend it when the data says the use case is real.

Post to #expansion and tag the account's AE (or CSM, wherever expansion lives). The message is a cluster map, not a task: how many new users, which team they look like, what they're doing differently from the home team, how fast they're growing — and, in bold, who invited them. The AE should read it and know the next move without opening a dashboard.

The inviter is the key datum in this entire play. The person who invited the new team is your internal seller — they already pitched the product to a neighboring department and won. Your job is not to sell; it's to formalize what the champion started.

• Ask the champion, not the new team: "I noticed a few folks from marketing joined — sounds like that's your doing. Could you intro me to whoever runs that team?" Warm beats cold by an order of magnitude inside an account.
• Arm the champion: a one-paragraph summary of what the new team has done so far makes their intro effortless to write.
• Cold-emailing the new department's lead while a willing champion sits in the org chart is the anti-pattern. It wastes the warmest intro you'll ever get.

The new department has a different job to be done — the original team's onboarding will bounce them. A marketing team dropped into an engineering-flavored setup flow concludes "this tool isn't for us" in one session. Build a department-specific flow in Appcues keyed to the new cohort's actual feature mix: their first-value action, their templates, their vocabulary. Target it on the cohort's traits so home-team users never see it. This is the step that turns a beachhead into a department — the intro opens the door, the onboarding decides whether they stay.

Open the opportunity in Salesforce with its own type: second-department expansion, tracked separately from seat upsell. The distinction isn't bookkeeping vanity — a new department is a new use case, a new budget line, and usually a new economic buyer, so it forecasts, prices and closes differently than adding seats to an existing team. Attach the evidence: the cluster date, the cohort's retention, the champion who made the intro. When the pattern repeats across accounts, you have a repeatable second-department motion instead of a lucky quarter.

If the new cohort's retention is below the bar, do nothing loud. Keep the cohort tagged, let the department-agnostic product experience work, and recheck retention in 30 days. Some beachheads need a second invite wave to reach critical mass. The one quiet move worth making: tell the champion you noticed their colleagues trying it, and ask if there's anything that would help — that's support, not sales, and champions remember the difference.

The outcome is an account that's multi-threaded and multi-budget: a second department running its own use case, with its own stakeholders and its own reason to renew. Track the multi-department percentage of your book over time — it's one of the strongest churn-resistance numbers in post-sale. One-department accounts are one reorg away from gone; two-department accounts have to be cancelled twice.