Most Stage 6 businesses meet expansion the same way. The first product is mature, with a customer base of 200-500+. The second product has been launched and validated against cold buyers — that's the workstream that defined Stage 5→6 graduation. Some existing customers have bought the second product through ad-hoc cross-sell, usually facilitated by the founder, an account manager, or a customer success lead who happened to spot the opportunity. The motion exists in some accounts. It's not running in every account.
The instinct is usually to layer 'expansion playbooks' over the customer success team. The Stage 6 team treats this as a service-extension exercise: better customer success scripts, more frequent QBRs, a renewals process that mentions the second product. Sometimes that produces a small lift. More often, it produces process overhead without a meaningful expansion-revenue uplift, and the founder remains the actual expansion engine for the largest accounts.
Why Stage 6 expansion is structurally different from Stage 5 first-cross-sell
Stage 5→6 graduation is about building the first cross-sell motion at all — the playbook for how the second product gets sold to existing customers, the first time. That work ships in Build the Product Stack and is genuinely a build, because the motion doesn't exist yet. Some customers buy through it; the playbook gets validated; the team learns what works.
Stage 6→7 graduation is different. The motion exists. The playbook has been validated in 20-30 accounts. The cross-sell happens — for some accounts. The graduation work is making it scale across every account, with the structural layers that turn ad-hoc expansion into systematic expansion.
Different shape. Different deliverables. Different metric of success. Stage 5 expansion success is 'first 20 cross-sells closed.' Stage 6 expansion success is 'every existing account has a planned expansion path, 30-40% of new revenue is expansion, founder is no longer in account expansion conversations.'
The four pieces of an expansion motion that scales
1. Cross-sell motion built across both products with a trigger map. The trigger map is the part most teams skip. What behaviour signals readiness for cross-sell? Specific signals — usage thresholds (the customer is hitting limits on product 1), role changes inside the account (a new VP joined who's already familiar with product 2), scope expansion in delivery (the project they hired you for is expanding into a domain product 2 covers), renewal milestones (the renewal conversation is the natural moment for the cross-sell pitch). Each trigger has a defined motion: who acts (account manager, customer success, sales rep), what they do (initiate the conversation, send the comparison, book the demo), what the success criterion is (cross-sell qualified opportunity within 14 days). Without the trigger map, expansion happens to customers who self-volunteer. With it, expansion happens to every account on a planned timeline.
2. Upsell motion built with a price-tier graduation map. Most Stage 6 businesses have multiple price tiers (basic / pro / enterprise, or starter / business / scale). The graduation map defines, for each customer, which tier they should be on now and which tier they're on a path toward. The conversation isn't about pushing customers to a tier they don't need — it's about making sure every customer is on the tier the value-they-receive justifies, and that the customer success rhythm surfaces the graduation conversation at the right cadence (typically annual or at significant usage milestones). The price-tier graduation map is built once, applied across the customer base, and tracked weekly.
3. Expansion target per account installed. Every customer has a planned expansion path. Not 'we hope they expand.' A documented path: this account is on tier X today, expected to graduate to tier Y by Month 12, with cross-sell of product 2 expected by Month 9. The path lives in the CRM, owned by the account manager, reviewed in weekly account reviews. The path isn't aspirational — it's the operating plan. When an account isn't on track to its planned expansion, the conversation happens proactively, not at renewal.
4. Comp tied to expansion revenue across the pod structure. This is the structural piece that makes the motion durable. If comp still pays only on new-logo close, account managers will keep prioritising new logos and expansion will stall regardless of how good the trigger map is. Comp restructured to pay on expansion revenue (cross-sell, upsell, price-tier graduation, continuity-rate signings) — at meaningful weighting — makes the team prioritise the motion. Pod-level comp visibility (how is each pod performing on expansion revenue this month) creates healthy competition and surfaces structural issues early.
Why the trigger map is the durability lever
Without the trigger map, expansion happens to the customers who self-volunteer. The customer who emails to ask about product 2. The customer who's already hit usage limits and is escalating internally. The customer whose renewal conversation surfaces a scope expansion. These customers buy because they were already going to. The motion didn't generate the expansion — it just took the order.
The trigger map flips this. Specific behavioural signals inside the customer base get monitored, and the motion fires when the signal hits. The customer who's hit 80% of usage on product 1 gets the cross-sell conversation triggered automatically. The customer whose primary contact has changed gets the introduction-to-product-2 conversation triggered. The customer whose project scope has expanded gets the price-tier graduation conversation triggered. Each motion is defined; each trigger has a defined response; each response has a documented owner.
The result is a motion that reaches customers who wouldn't have self-volunteered. These are the accounts where the expansion lift is largest, because the customer was ready but not actively asking. The motion captures the latent demand that ad-hoc expansion misses entirely.
What expansion-aligned comp actually looks like
The comp restructure has to be specific or the team will revert to the old behaviour. A typical Stage 6 expansion comp plan splits the comp pool across:
- New-logo close: 30-40% (down from 70-80% under old plan)
- Cross-sell of product 2 to existing customers: 25-30%
- Price-tier graduation (upsell): 15-20%
- Continuity-rate signings (recurring revenue stickiness): 10-15%
- Retention rebuy / renewal: 5-10%
The split signals what the business values. Account managers comp'd on this mix prioritise the expansion motion because the comp maths rewards it. Account managers comp'd on the old new-logo-heavy plan keep chasing new logos because that's where the comp is. The behaviour follows the maths every time.
Pod-level visibility on the new comp mix (every pod's performance against each comp dimension, weekly) surfaces structural issues early. If one pod is hitting new-logo targets but missing cross-sell, that's a coaching signal. If another pod is hitting cross-sell but missing upsell, that's a different coaching signal. The pod-lead structure (Workflow #14) is what absorbs these signals into daily and weekly coaching.
What this looks like working
The early signal is operational. Within 6 weeks of the motion launching, every existing account has a documented expansion path in the CRM. Account managers can answer the question 'what's the expansion plan for account X' without thinking. The trigger map is firing — first cross-sell conversations are happening with customers who hadn't self-volunteered. Comp visibility is live; pods can see their expansion-revenue performance weekly.
The mid signal is the lift. Within 16-20 weeks, expansion revenue starts showing up materially in the headline. New-logo revenue holds (the team isn't deprioritising new logos — they're adding expansion on top), and expansion revenue layers in at 15-20% of total new revenue.
The late signal is the compound. Within 12 months, expansion revenue is 30-40% of total new revenue. Revenue per customer is up 30-50% across the existing book. The founder is no longer in account expansion conversations because the pod structure runs them. The motion is durable because the comp aligns the team and the trigger map captures the latent demand the team would have missed.
Why this is distinct from BPS Existing Customers Buy More
The BPS Stage 5-6 workflow (Existing Customers Buy More) builds the first cross-sell motion at all. The team is learning what works. The first 20 cross-sells get closed; the playbook gets validated; the team builds the muscle. That's the right work for Stage 5→6.
GPG The Account That Grows Itself is structurally different. The motion exists; the playbook is validated; the team has muscle in the motion. The work is making it scale across every account at multi-pod scale, with comp restructure and expansion targets per account. Different scope, different deliverables, different timeline. Folding this into 'Existing Customers Buy More' would hide the scaling work in scope bullets where buyers can't see it. Stage 6 buyers need to see the scaling motion as a discrete workstream because that's what their business actually requires.
What this looks like in real businesses
A SaaS business we worked with had two products, a customer base of 350, and an existing cross-sell motion that had closed about 40 second-product deals over two years. The motion was working — when it was used. The problem: it wasn't being used in 60% of accounts. The expansion motion installed in our engagement: trigger map built (5 specific behavioural triggers per account), price-tier graduation map shipped (every customer mapped to current tier and expected next tier), expansion target installed per account, comp restructured 35% / 25% / 20% / 10% / 10% across the five comp dimensions. Within 6 months, expansion revenue rose from 8% of new revenue to 32% of new revenue. Revenue per customer was up 41% across the existing book. The founder dropped from being in 70% of expansion conversations to being in 10% of them. The pod-lead structure absorbed the rest.
Why founders resist this
The most common resistance is the comp restructure aversion. Comp changes are visible to the team and react fast. The fix is sequencing — design the new plan, walk the team through it, give 30 days notice, then ship. Done well, comp restructure produces a better team within a quarter. Done badly, it produces a quarter of pipeline disruption.
The second resistance is the trigger-map effort. Building the trigger map requires actual customer-base analysis — usage data, account history, role-change tracking, scope-expansion patterns. It's not a script you write in a week. The discipline is that the analysis produces the durable motion; without it, the motion is ad-hoc forever, and the founder stays in expansion conversations forever.
The third resistance is the worry that pushing expansion will damage relationships. Most Stage 6 customers welcome expansion conversations when they're triggered correctly — at the right moment, by the right person, with the right framing. The customer who's hit 80% of usage on product 1 isn't surprised when their account manager raises product 2; they were already thinking about it. The trigger map is what makes the conversation feel timely rather than pushy.
The bottom line
Stage 6 expansion is different from Stage 5 first-cross-sell. The motion already exists; the gap is making it scale. The fix is four pieces — cross-sell trigger map, upsell price-tier graduation, expansion target per account, comp aligned across the pod structure — and the lever lifts revenue per customer 30-50% without acquiring a single new logo.
By Week 20 every customer has a planned expansion path. Expansion revenue per pod tracked weekly, comp aligned, motion running without you in every account review. That's the lever Stage 6 founders skip and then wonder why revenue per customer plateaus while new-logo CAC keeps creeping up. The answer was always in the customer base. The motion is what surfaces it.
Frequently Asked Questions
How is this different from BPS Existing Customers Buy More?
BPS Existing Customers Buy More builds the first cross-sell motion at Stage 5-6 — the team is learning what works, validating the playbook, closing the first 20 cross-sells. GPG The Account That Grows Itself scales an existing motion across every account at multi-pod scale, with comp restructure and expansion targets per account. Different stage, different scope, different deliverables.
What goes on the trigger map?
Specific behavioural signals inside the customer base. Common triggers: usage thresholds (customer hits 80% of capacity), role changes (new VP joins the account), scope expansion in delivery (project broadens into a domain product 2 covers), renewal milestones, account-health-score shifts, support-ticket pattern changes. Each trigger has a defined motion (who acts, what they do, success criterion within X days).
Won't customers feel pushed if we install expansion targets per account?
Most don't, when the motion is triggered correctly. The customer who's hit 80% of usage on product 1 is already thinking about expansion; the conversation is timely, not pushy. The customer who's mid-renewal is already evaluating the relationship; the price-tier graduation conversation is timely, not pushy. The trigger map is what makes the difference between 'pushy outreach' and 'right-moment conversation'.
How does comp restructure work without disrupting the team?
Sequencing matters more than design. Walk the team through the new plan in detail before it ships. Give 30 days notice. Run a 30-day overlap where account managers see what they would have earned under both plans. Ship the new plan with full transparency. Done this way, the disruption is small and the right behaviour follows the maths within a quarter.
How does this fit into the wider Get Profitable Growth engagement?
Workflow #15 The Account That Grows Itself ships Weeks 13-20, after Workflow #13 Sales Calls That Score (Weeks 7-12) and Workflow #14 The Sales Team That Runs Itself (Weeks 11-18) have installed the call-level and structural sales discipline the expansion motion runs on top of. Together these three workflows are full Six Cs at multi-pod scale, with expansion as the primary revenue motion at Stage 6→7.