How Many Packages Should You Offer?

Stop offering three options when the buyer needs one clear recommendation. Here's why the menu approach backfires.

The Short Answer

Offer one package. Not three. Not a menu. One clear recommendation based on what they told you they need.

The buyer came to you for guidance. When you give them options, you're asking them to do your job. They don't know which package to choose—that's why they're talking to you. So tell them. Recommend the solution that fits their problem, and let them push back if it doesn't work.

Why We Offer Multiple Options

Most people think offering three packages makes them look flexible. They think: "I'll give them options so they can choose what fits their budget." They think it shows they're accommodating, that they're meeting the buyer where they are.

Here's what's actually happening: you're avoiding making a recommendation because you're afraid of being wrong. You don't want to suggest the $10K package if they were thinking $5K. So you offer both—plus a $15K option for good measure—and let them decide.

But that's not helpful. That's you making the buyer do the analysis you should have done during discovery. You're not being flexible—you're being indecisive. And the buyer feels it.

What the Menu Sounds Like

Here's the pattern most people follow when they offer multiple packages:

  • "We have three options: Basic at $3K, Standard at $6K, and Premium at $10K."
  • "I can do this at different levels depending on your budget."
  • "Here are your choices—let me know which feels right."
  • "We could go light, medium, or full-service, depending on what you need."

Every one of these statements puts the decision back on the buyer. You've just handed them a restaurant menu and said "pick something." That's not guidance. That's abdication.

What the Buyer Hears

When you offer three options, the buyer doesn't hear flexibility. They hear: I don't know what you need. They hear: I didn't listen closely enough to tell you which one is right. They hear: You're on your own.

Now they have to do math, compare features, weigh trade-offs—work they expected you to do for them. And because you didn't make a recommendation, they have no confidence that any of these packages will actually solve their problem.

Worse: they're now anchored on the cheapest option. You showed them $3K exists, so why would they choose $10K? You've taught them to pick the lowest price, not the best fit.

Before / After: The Menu vs. The Recommendation

Before (The Menu)

You: "So we have three packages: Basic is $3K and covers the core implementation. Standard is $6K and adds the training and support. Premium is $10K and includes everything plus ongoing optimization. Which feels right to you?"

Them: "Hmm. Let me think about which one makes sense and get back to you."

*(They ghost because they don't know what to choose.)*

After (The Recommendation)

You: "Based on what you told me—especially that you need this running by Q4 and your team doesn't have the bandwidth—I'd recommend the $10K package. That gets you the full implementation, training for your team, and the ongoing support you'll need to hit that timeline. Does that work?"

Them: "Yes. Let's do it."

Same situation. The recommendation closed because you did your job—you told them what they need instead of making them figure it out.

What If They Can't Afford Your Recommendation?

If you recommend the $10K package and they say "that's more than I have," that's when you address it. Not by offering three packages up front, but by understanding the gap.

Try this:

  • "What's your budget for this?"
  • "If we did $6K instead, we'd need to cut the ongoing support. Would that still solve your problem?"
  • "Help me understand—what would need to be different?"

Now you're having a real conversation about trade-offs. You're not presenting a menu—you're solving a problem together. And most of the time, when you make a strong recommendation, the buyer trusts it enough to say yes even if it's more than they planned to spend.

When Multiple Packages Actually Make Sense

There are times when offering tiers is strategic: self-service products with clear pricing pages, or when you're selling to different buyer segments with fundamentally different needs (small business vs. enterprise).

But in a live sales conversation where someone came to you for advice? You should already know enough about their situation to recommend one path. If you don't, that's a discovery problem—go back and ask better questions.

The menu works when the buyer is self-educating on a website. It fails when they're on a call expecting you to tell them what to do.

The Fix: Make One Clear Recommendation

1. During discovery, listen for their constraints

What's their budget? Timeline? Internal capacity? What outcome do they need? Don't just gather information—interpret it.

2. Use what they told you to make a recommendation

"Based on what you said about [constraint], here's what I recommend: [package]. That solves [problem] and gets you [outcome]."

3. State it as a recommendation, not the only option

You're not forcing them—you're guiding them. "Here's what I'd recommend" leaves room for them to push back if it's off.

4. Let them respond before offering alternatives

Don't preempt objections. If they say "that's too much," then you talk about adjusting scope. But don't offer the menu first.

5. Trust your recommendation

If you did good discovery, you know what they need. Don't second-guess yourself by hedging with options.

Do you offer menus when you should make recommendations?

Take the 2-minute quiz to find which of five self-sabotage patterns shows up in your sales conversations.

Take the Quiz

Related Articles