User Expansion: The Motion Play That Turns Unused Seats Into Revenue

User Expansion: The Motion Play That Turns Unused Seats Into Revenue

You see 150 seats on contract. Only 80 are active. The instinct is automatic: "Get those 70 people signed up and we hit our expansion number."

That instinct will cost you deals.

At a Glance

When to Run This Play

Run user expansion when:

• Saturation gap exists: Seats on contract exceed active users by 25% or more
• Health is solid: NPS is above 40, usage trend is flat or up, no churn risk flags
• Product fit is proven: The customer has renewed or is on track to renew
• Trigger event occurs: New user onboarding cohort completes, product release adds capability, customer department grows

Do not run this play if:

• The account is at churn risk or negotiating renewal
• User saturation is dropping due to macro headwinds (RIF, right-sizing)
• Product-market fit is unproven at the account level

The Context You Need First

Three things change how you run user expansion in 2024–2026:

1. AI-driven workforce restructuring is real.

Block, Databricks, and others have announced significant layoffs, replacing human roles with AI agents. If your customer is in a restructuring cycle, their unused seats might stay empty for 6–12 months. The play shifts from “how do we activate these people” to “how do we solve for a smaller, different team.”

2. Net Revenue Retention is the scoreboard.

SaaS companies in the top quartile maintain NRR of 120% or higher; the median sits around 105–110%. User expansion is the primary driver for product-led companies. Every seat you activate feeds NRR. But you only get there if you play it right.

3. Every empty seat is a human decision, not a software problem.

The person who didn’t get invited to use the platform is a person. They have a job, a learning curve, competing priorities. If they weren’t activated on day one, there’s a reason. Find it.

The Motion Play: User Expansion Campaign (6–12 Weeks)

Phase 1: Audit & Understanding (Weeks 1–2)

Goal: Map the user landscape and understand why seats are empty.

Actions:

1. Pull the data. Get your customer’s actual adoption curve from your platform. Who’s active? Who hasn’t logged in in 30+ days? What’s the trend?
2. Interview the account executive and customer success manager. Ask:
   • “Why do you think those 70 seats are empty?”
   • “Have they asked for user access before?”
   • “What would change if they were using the platform?”
3. Map the buying stakeholders. Who approved the original seat count? Why did they estimate high? Are they still at the account?
4. Assess the macro context. Is the customer in a hiring cycle or right-sizing cycle? Are team structures changing?

Output: A one-page “user expansion opportunity map” that lists empty seats, reasons for non-adoption (product gap, process gap, training gap, macro headwind), and the human owner on the customer side.

Phase 2: Product & Pricing Diagnosis (Weeks 2–3)

Goal: Determine if your standard offer solves for the unused seats or if you need flexibility.

Actions:

1. Ask the hard question: “What license tier or product configuration would these people actually use?”

   Not everyone on your platform needs the same tier. A support team might use basic workflows. A data analyst might need advanced reporting. An operations coordinator might need limited view-only access.

2. Audit your pricing model. Can you tier down? Can you offer a read-only license? A workflow-limited license? If your product can adapt, do it. If it can’t, that’s a product problem, not a sales problem.
3. Test the hypothesis with your CSM. Share the idea: “What if we offered a $200/month tier for users who just need X?” Does the customer’s eyes light up, or do they push back?
4. Prepare 2–3 options. Standard seats at the original price, tiered seats at a lower price, or a bundle that adds a small group of seats at a discount to the total contract value.

Output: A pricing and product recommendation, approved by your product and finance teams.

Phase 3: Champion Building (Weeks 3–4)

Goal: Build the relationship before you pitch the expansion.

Champions aren’t found. They’re built. And they’re built before the ask.

Actions:

1. Identify the internal champion. This is usually the user who has the most to gain from expansion. If you’re expanding into the support team, find the support director. If it’s operations, find the ops lead.
2. Have a value conversation, not a sales conversation. Meet with them (or their CSM does, depending on relationship). Ask:
   • “What would it look like if your team had access to this?”
   • “What would you be able to do differently?”
   • “What’s the friction that keeps them from using it today?”
3. Share a success story. Tell them about a similar team at a similar company that activated. Keep it real: “Similar company, similar role, they started with five people on the team, now they have nine. Here’s what changed.”
4. Give them a small win first. If possible, activate one or two users for free or at a trial rate for 30 days. Let them feel the value before the official pitch.

Output: A champion who understands the value and is bought in to an expansion conversation.

Phase 4: The Expansion Pitch (Weeks 4–5)

Goal: Present the offer in context of their macro situation and needs.

Framing:

Do not pitch this as “buy more seats because you bought more seats.”

Pitch this as: “We’ve been working with your team, and we see an opportunity. Your support team is doing X, but they’re not using the platform for Y. Here’s a configuration that fits their workflow, at a price point that makes sense. We think this will help you hit [goal: faster response times, fewer escalations, better data on common issues].”

The ask: Expansion seats at the agreed tier/price, usually on a 12-month term to match their renewal.

The sweetener: If you’re discounting, make it time-limited (first 12 months at 20% off, renews at full price). Build in a review: “Let’s check in at 90 days. If adoption is above X%, we lock in the price. If it’s below, we adjust.”

Output: A signed expansion order or a committed-to timeline for expansion seats at the next renewal.

Phase 5: Activation & Accountability (Weeks 5–12)

Goal: Ensure the new users actually activate and stay active.

Actions:

1. Run a targeted onboarding for the new cohort. Not a generic webinar. Specific training for their role and workflow.
2. Assign a CSM touch point. Every week for the first month, someone checks in: “How are you using the platform? What’s working? What’s friction?”
3. Monitor adoption metrics. By day 30, you should see:
   • 70%+ of new users have logged in
   • 50%+ are performing a key action (submitting a request, viewing a report, creating a workflow)
   • Engagement is trending up, not flat
4. Troubleshoot fast. If adoption is lagging by week 3, you know it. Figure out why (training gap? Product gap? Wrong tier? Wrong people?) and fix it.
5. Connect to their outcome. At day 90, share the result: “Your support team is now handling 12% more tickets per person using the platform for workflow routing. Here’s the impact on SLA compliance.”

Output: 70%+ adoption of new seats by day 90; engagement that justifies the expansion at renewal.

What Success Looks Like

At 90 days:

• 70%+ of newly activated users are active (logged in within 7 days)
• 50%+ have performed a key action related to their role
• NPS for the new cohort is within 5 points of the overall account NPS
• Churn risk has not increased
• CSM has documented the outcome and impact

At renewal:

• User adoption remains 70%+ for the expanded group
• Expansion ARR from new seats is locked in at the agreed price
• Customer advocates for broader expansion in adjacent teams
• You have a repeatable playbook you can run every 6 months

Longer-term signal:

• NRR contribution from user expansion exceeds 8–12% year-over-year
• Expansion revenue has lower churn than new logo revenue
• Your best expansion plays come from existing customers, not hunting for new logos

Handling Resistance

“We don’t need those seats.”

This is the most common pushback, and it’s often true. Don’t argue. Instead: “I hear you. But let’s run a small pilot. Activate three people on the team for 30 days at no cost. If they don’t find value, we move on. If they do, we’ll have your buy-in.”

“We just went through a reduction in force.”

Acknowledge it directly: “I know you’re in restructuring mode. The seats we’re talking about aren’t about headcount increase; they’re about using your existing team more effectively with less manual work. Makes sense to revisit in Q3?”

“The price doesn’t make sense for us.”

Go back to Phase 2. You have room to tier down, package differently, or discount for a limited time. But don’t leave money on the table by accident. Ask: “If the price was X, would it work?” and close the gap.

“We’re happy with what we have.”

This is the hardest one because they might be right. Play it straight: “That’s great. The reason I’m bringing this up is that we see teams like yours using the platform for A, B, and C, and getting 15–20% productivity lift. I don’t want you to leave that on the table. Want to revisit this in 90 days?” Set a calendar reminder. If nothing has changed, let it go.

Adapt to Your Buyer

Mid-market (100–500 employees):

User expansion works best when tied to a department initiative (faster support resolution, better analytics, compliance reporting). Pair the CSM with the department head. Get executive air cover from your sponsor.

Enterprise (500+ employees):

You’ll often have multiple user expansion plays happening in parallel (IT, sales, support, operations). Coordinate through a single expansion owner at your company. Run a quarterly business review where you show total expansion ARR and impact by department. Enterprise expansion takes longer but is more sticky.

SMB (10–100 employees):

Expansion is often about removing friction, not selling. The owner or manager has limited bandwidth for training. Onboarding needs to be 15 minutes, not 2 hours. Tier down aggressively. Pricing flexibility matters more than features.

How AI Changes This Play

AI changes the macro context, not the play itself.

The shift: Customers are right-sizing after over-hiring. That means fewer people, more powerful tools, and higher expectations for what those tools can do. A team of five is replacing a team of fifteen. Those five need the platform more than ever, but they need it configured differently.

The tactic: In Phase 1, ask about AI adoption and automation roadmaps. Is the customer deploying AI agents? If yes, the expansion play might not be about more people, but about different people (analysts, prompt engineers, AI ops roles you didn’t think about). The seats you’re expanding into are different seats.

The opportunity: AI is eliminating low-skill work. The remaining roles are higher-skill, higher-value work. Those people are more likely to adopt your platform because it directly impacts their ability to do their job. Expansion revenue becomes more predictable, not less.

AI Expansion Prompt for Your Team:

Run a user expansion motion for [account]. The customer has [X] seats on
contract, [Y] active. Before we pitch expansion, I need:

1. Their org chart today and projected org chart in 6 months (hiring,
   layoff, restructuring?)

2. AI/automation roadmaps they’ve shared (we need to know if the empty
   seats are staying empty)

3. A tiered pricing option that fits three scenarios: (a) they hire,
   (b) they stay flat, (c) they reduce further

4. A champion interview summary: why aren’t the other seats being used?

5. A success metric tied to their goal, not our goal (faster resolution,
   more revenue per employee, compliance, etc.)

Once I have that, I’ll pitch. Not before.

Related Plays

• Land-and-Expand Strategy – the macro framework that positions user expansion as a core revenue lever
• Cross-Sell Targeting – when expansion isn’t about more users, but different product lines
• Customer Health Score – the diagnostic tool you use to decide which accounts are expansion-ready
• Renewal Negotiation Play – how to lock in expansion seats at renewal without giving away margin
• Persona Expansion – when you’re expanding into a different buyer type within the same account
• Pilot-to-Production Conversion – how to move an expansion pilot from trial to committed ARR

The Accountability Pattern

You earned the expansion, or you didn’t.

If your product provided value, if your CSM delivered on the promise, if the customer hit their goal in phase one, expansion is not a campaign. It’s organic. It’s the customer asking for more.

If you have to pitch hard, if adoption is slow, if you’re discounting to close, then you didn’t earn it yet. Go back to phases 1–3. Build more relationship. Prove more value. Then the ask becomes easy.

That’s the motion play. That’s how you turn unused seats into real, sticky, predictable revenue.

Frequently Asked Questions

How do I know which accounts to run this play on?

Start with accounts that have 30%+ user saturation gap (seats on contract vs. active users), solid health (NPS 40+, flat or positive usage trend), and renewal coming in the next six months. Those are your highest-probability targets.

What if the customer says the seats are for future hires?

Push back gently: “I understand. Future hires will need training and onboarding anyway. But we see most teams benefit from having 1–2 power users first, who can then train the next wave. Want to start with two seats and add more when the hires land?” You’re solving for actual adoption, not seat count.

How aggressive should the discount be?

Only discount if you have to. Most successful expansion plays don’t need heavy discounts because the value is clear. If you’re discounting more than 15–20%, go back to phases 1–2. The gap isn’t price; it’s value clarity or product fit.

What’s the minimum expansion ARR to make this worth running?

Probably around $15K–20K annual seat value. Below that, the effort doesn’t pay off. Above that, every point of adoption percentage multiplies quickly.

How do I handle it if a user activates but then goes dormant?

This is normal. At 90 days, segment your new users into active and dormant. For dormant: one last CSM touch (a call, not an email) to understand friction. If there’s a real issue, fix it. If adoption just wasn’t going to happen, accept it and focus on the cohort that did activate.

Part of the It’s Just Revenue Sales Plays Library — practical frameworks for revenue teams who want to stop the theater and start closing.