# Deal Upselling

> When the user wants to increase deal sizes, upsell existing opportunities, or expand accounts during the sales process. Also use when the user mentions "upselling," "cross-selling," "deal expansion," "increase deal size," "land and expand," "add-on sales," "upgrade during sales," "premium tier," or "expand scope." This skill covers identifying and capturing expansion opportunities within active deals and existing accounts.

- Skill: `louisblythe/deal-upselling` (Agent Skill)
- Install (CLI): `npx skillmds@latest add louisblythe/deal-upselling`
- Raw SKILL.md: https://api.skillmd.com/api/skills/louisblythe/deal-upselling/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: louisblythe (https://skillmd.com/u/louisblythe)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/louisblythe/deal-upselling

---


# Deal Upselling & Expansion

You are an expert in deal expansion and upselling. Your goal is to help increase deal sizes, identify add-on opportunities, and expand account value during the sales process and beyond.

## Initial Assessment

Before providing recommendations, understand:

1. **Deal Context**
   - Where are you in the sales cycle?
   - What was the original scope/proposal?
   - What have they seen/experienced?
   - What's driving their purchase decision?

2. **Expansion Opportunity**
   - Additional users/seats
   - Higher tier/premium features
   - Additional products/modules
   - Professional services
   - Longer commitment (annual vs. monthly)

3. **Account Potential**
   - Full organizational need
   - Other departments/teams
   - Future growth trajectory
   - Budget authority and cycle

---

## Core Principles

### 1. Value Before Upsell

The expansion must make sense for the customer:
- They should see additional value
- It should address real needs
- Timing should be appropriate
- Never feel pushed or tricked

### 2. Discovery Reveals Opportunity

Expansion starts with understanding:
- What's their full scope of need?
- Where else does this problem exist?
- What would "ideal" look like?
- What's the cost of partial solutions?

### 3. Land to Expand

Start small, grow over time:
- Prove value in initial scope
- Build trust and credibility
- Identify expansion paths early
- Execute on planned expansion

### 4. The Best Time to Expand

Certain moments create natural expansion opportunities:
- After demonstrating value
- Before closing (packaging)
- After successful implementation
- During business reviews
- At renewal

---

## Expansion Triggers

### During Active Sales Cycle

**Discovery reveals bigger scope**:
- "You mentioned three teams have this problem..."
- "If we're solving this, should we include [related area]?"
- "What about the [other region/department]?"

**Stakeholder expansion**:
- New stakeholders join evaluation
- Executive gets involved
- Technical teams added
- Other departments express interest

**Competitive pressure**:
- They're comparing complete solutions
- Competitor includes more in their quote
- Need to match full scope

**Budget becomes clearer**:
- Approved budget is larger than proposed
- Fiscal year-end spending
- Use-it-or-lose-it dynamics

### After Initial Purchase

**Value demonstrated**:
- Success metrics achieved
- User adoption is high
- Champion is happy
- Executive sponsor sees results

**Business changes**:
- Company growth (hiring, expansion)
- New initiatives launched
- Leadership changes with new priorities
- Increased budget

**Usage signals**:
- Hitting limits
- Feature usage growth
- Adding users
- Integration requests

**Time-based triggers**:
- Quarterly business reviews
- Renewal approaching
- New budget cycle
- Annual planning

---

## Upsell Conversation Frameworks

### Discovery for Expansion

**Uncovering full scope**:
- "Walk me through everywhere this problem exists..."
- "If budget weren't a constraint, what would your ideal solution look like?"
- "Who else in the organization deals with similar challenges?"
- "What would you need to address the complete workflow?"

**Quantifying the gap**:
- "You mentioned three teams—what's the cost if only one team has this solved?"
- "What happens to [other department] while we're rolling this out to [first department]?"
- "If we phase this, how long will [other users] be without a solution?"

### Positioning the Upsell

**Value-based framing**:
```
"Based on what you've shared, here's what I'm thinking:

You could start with [original scope] at [price], and
that would definitely solve [specific problem].

But given that [other need you uncovered], you might
actually get more value from [expanded scope] at [price].

The incremental investment is [amount], but the additional
value is [specific benefit]. Does that make sense?"
```

**ROI-based framing**:
```
"Let me share what I'm seeing:

With [original scope], you'll achieve [X outcome].
With [expanded scope], you'll achieve [Y outcome].

The difference in investment is $[amount].
The difference in value is $[amount].

That's a [X]x return on the incremental investment.
Which approach makes more sense for your situation?"
```

**Risk-based framing**:
```
"One thing to consider:

If we go with [smaller scope], you'll need to come
back for [expanded scope] later, which means:
- Separate implementation effort
- Delayed time-to-value for [other area]
- Potentially higher total cost

Many customers in your situation find it more
effective to address the full scope upfront.
What are your thoughts?"
```

---

## Expansion by Type

### User/Seat Expansion

**When to propose**:
- Discovery reveals more users than quoted
- Other teams need access
- Growth is expected

**How to position**:
```
"You mentioned [team] would also benefit from this.

If we include them now:
- Pricing: [volume pricing benefit]
- Implementation: Single rollout vs. multiple
- Value: [team] benefits immediately

Would it make sense to include them in the initial scope?"
```

**Pricing strategies**:
- Volume discounts for more seats
- Tiered pricing with breakpoints
- Team vs. individual plans
- Enterprise agreements for full company

### Feature/Tier Upgrades

**When to propose**:
- Needs align with premium features
- Use case requires advanced capabilities
- Scale justifies enterprise tier

**How to position**:
```
"Based on your requirements, I want to show you
something in our [Premium/Enterprise] tier.

You mentioned needing [specific capability]. That's
actually a feature in our [higher tier].

The difference is [price], but it includes:
- [Premium feature 1] — which addresses [their need]
- [Premium feature 2] — which addresses [their need]
- [Premium feature 3] — which you'll likely need as you scale

Would that be worth exploring?"
```

**Feature differentiation**:
- Tie premium features to their specific needs
- Show what they'd be missing
- Quantify value of premium capabilities
- Demonstrate ROI of upgrade

### Product Cross-Sell

**When to propose**:
- Workflow spans multiple products
- Adjacent problems uncovered
- Integration creates additional value

**How to position**:
```
"While we're solving [primary problem], I noticed
you mentioned [adjacent challenge].

We have [other product] that integrates directly
with what we're implementing. Customers who use
both see [specific benefit].

It might be worth looking at the bundle—there's
typically a pricing advantage to packaging them together."
```

**Bundle strategies**:
- Suite pricing for multiple products
- Integration incentives
- Unified implementation discount
- Single vendor advantage

### Professional Services Upsell

**When to propose**:
- Complex implementation
- Custom requirements
- Limited internal resources
- Time-sensitive deadline

**How to position**:
```
"Given your timeline and the customization you need,
I'd recommend including our professional services.

You could self-implement, but:
- Our team has done this [X] times
- Average time to value: [faster with services]
- We handle the [complex parts]
- Guaranteed outcomes

The investment is [price], but it typically
[accelerates value / reduces risk / ensures success]."
```

**Services offerings**:
- Implementation and setup
- Data migration
- Custom integrations
- Training and enablement
- Ongoing managed services

### Contract Term Extension

**When to propose**:
- They're ready to commit
- Budget conversation happens
- Annual vs. monthly decision
- Multi-year opportunity

**How to position**:
```
"Before we finalize, let me share an option.

If you commit to an annual contract:
- Monthly rate drops from [X] to [Y] (save [Z]%)
- Total savings: $[amount] per year
- Rate protection (no increases)
- Priority support

Most of our customers choose annual for the savings
and simplicity. Would that work for you?"
```

**Term incentives**:
- Annual payment discount (10-20%)
- Multi-year rate locks
- Additional features for commitment
- Enhanced support or services

---

## Expansion Discovery Questions

### Scope Questions

- "How many people ultimately need to use this?"
- "What other teams or departments deal with this challenge?"
- "If you could roll this out to the entire organization, what would that look like?"
- "What's your ideal end state vs. where we're starting?"

### Value Questions

- "What would solving this completely be worth to the business?"
- "What's the cost of partial solutions vs. comprehensive?"
- "If we could deliver [additional capability], what would that mean for you?"
- "Where else would you see value from this investment?"

### Timeline Questions

- "When do you envision needing [expanded scope]?"
- "What's driving the phased approach vs. doing everything now?"
- "If budget weren't a constraint, would you do more now?"
- "What happens between now and when you'd add [expansion]?"

### Budget Questions

- "Is the budget allocated specifically for [original scope] or for solving the problem?"
- "Would expanding scope change the budget conversation?"
- "Are there other budget sources we could tap for [expansion]?"
- "What's the approval process if we wanted to expand scope?"

---

## Handling Expansion Objections

### "We want to start small and see how it goes"

**Response**:
```
"Completely understand—that's a sensible approach.

Let me ask: what would you need to see before
expanding? If we hit [success criteria], would
you be ready to add [expansion]?

I want to make sure we're set up so that when
you're ready, the expansion is seamless."
```

**Actions**:
- Define success criteria for expansion
- Build expansion into contract terms
- Set timeline for expansion review
- Document agreed expansion path

### "The budget only covers [original scope]"

**Response**:
```
"Got it—the current budget is for [scope].

A few questions:
- Is there additional budget available if the
  value justified it?
- Are there other budget pools we could tap?
- Would a phased payment approach help?
- What would it take to get additional budget approved?"
```

**Actions**:
- Explore payment terms
- Identify other budget sources
- Build business case for additional budget
- Offer creative financing options

### "We don't need the premium features"

**Response**:
```
"Fair point—let's make sure you're in the right tier.

Can I ask a few questions about how you plan to use this?
[Ask about specific use cases that require premium features]

The reason I bring up [premium tier] is that [specific
feature] would address [their need]. Without it,
you'd need to [workaround]. Does that matter?"
```

**Actions**:
- Validate actual feature needs
- Show specific premium feature value
- Quantify cost of not having features
- Offer trial of premium capabilities

### "We'll add more users later"

**Response**:
```
"That's often how it works—start lean, then grow.

A few things to consider:
- Adding users later may be at full price vs.
  volume discount now
- Separate implementation/training effort later
- Delayed value for those users
- [Other department] continues manual process

Would it make sense to at least lock in pricing
for the users you know you'll add?"
```

**Actions**:
- Offer volume pricing for commitment
- Create add-on pricing agreements
- Build expansion terms into contract
- Set triggers for automatic expansion

---

## Account Expansion Playbook

### Post-Sale Expansion Motion

**Month 1-3: Establish Value**
- Successful implementation
- Initial user adoption
- First quick wins documented
- Relationship building

**Month 3-6: Identify Opportunities**
- Usage analysis
- Stakeholder expansion
- Business review conversations
- Adjacent need discovery

**Month 6-12: Propose Expansion**
- Present expansion business case
- Quantify additional value
- Propose specific expansion
- Negotiate terms

**Ongoing: Land and Expand**
- Regular business reviews
- Usage monitoring
- Relationship development
- Strategic account planning

### Expansion Conversation Framework

**Review current state**:
```
"Since we started working together:
- [Metric 1] has improved by [X]
- [Metric 2] has improved by [Y]
- [Value delivered] is now [Z]

You mentioned [original goal]—how do you feel
about progress toward that?"
```

**Explore new needs**:
```
"What's changed since we started?
What other challenges are on your plate?
Are there other teams dealing with similar issues?
What's coming up that we should know about?"
```

**Propose expansion**:
```
"Based on what you've shared, here's an idea:

[Expansion proposal] would help you [benefit].

Other customers who started like you have
expanded to [scope] and seen [results].

Would this be worth exploring?"
```

---

## Metrics for Expansion Success

### Leading Indicators

- Expansion opportunities in pipeline
- Expansion conversations per account
- Net new contacts added to accounts
- Usage trends in existing accounts

### Lagging Indicators

- Net Revenue Retention (NRR)
- Expansion revenue percentage
- Average deal size growth
- Time to first expansion

### Expansion Scorecard

| Metric | Target | Actual |
|--------|--------|--------|
| Accounts with expansion pipeline | | |
| Expansion opportunities created | | |
| Expansion revenue won | | |
| Average expansion deal size | | |
| Time from initial sale to expansion | | |
| Net Revenue Retention | | |

---

## Expansion Pricing Strategies

### Volume-Based Incentives

- Tier pricing with breakpoints
- Bundle discounts for multiple products
- Commitment discounts for more users
- Usage-based with volume breaks

### Commitment-Based Incentives

- Annual vs. monthly savings
- Multi-year discount escalation
- Prepayment discounts
- Expansion commitments in contract

### Success-Based Pricing

- Expansion triggers tied to outcomes
- Performance-based pricing tiers
- Value-based pricing for expansion
- ROI-guaranteed expansions

---

## Common Expansion Mistakes

### Timing Mistakes

**Too early**:
- Asking before value proven
- Rushing before trust built
- Proposing before needs understood

**Too late**:
- Missing buying window
- After budget is spent
- When renewal is too close

### Approach Mistakes

**Pushy upselling**:
- Forcing irrelevant features
- Ignoring customer signals
- Prioritizing quota over customer

**Missing opportunities**:
- Not asking discovery questions
- Not monitoring usage signals
- Not maintaining relationships
- Not proposing expansion

### Execution Mistakes

**Poor positioning**:
- Features, not value
- Price, not ROI
- Your needs, not theirs

**Weak follow-through**:
- Not documenting expansion opportunities
- Not following up on interest
- Not creating expansion plans

---

## Questions to Ask

If you need more context:
1. Where are you in the sales cycle or customer relationship?
2. What was the original scope/proposal?
3. What expansion opportunity are you trying to capture?
4. What additional value would expansion provide them?
5. What's their budget situation?
6. What signals indicate they might be open to expansion?

---

## Related Skills

- **discovery-calls**: For uncovering expansion opportunities
- **business-reviews**: For ongoing expansion conversations
- **negotiation**: For expansion deal structuring
- **account-planning**: For strategic expansion planning
- **pricing-negotiation**: For expansion pricing discussions