CommandBar · Go-to-market · Senior · 45 to 60 minutes

How should CommandBar price Copilot?

CommandBar is a B2B software company that helps other software products guide, support, and assist users inside the app. Answer this product management case and get it graded line by line against a weighted rubric.

The situation

You are a senior PM at CommandBar, and leadership is preparing to launch Copilot, a new AI offering, more broadly. The CEO, head of sales, and finance lead want a pricing and packaging recommendation before the go to market plan is finalized. The team sees strong customer interest, but there is disagreement about how to charge. A pure usage based model may better align price to value and cost, especially if AI usage varies a lot by customer. But sales worries that uncertain monthly spend will trigger finance review, slow approvals, and make enterprise buyers hesitant. On the other hand, a simple flat price or very generous unlimited plan could be easy to buy, yet it could become painful if customer usage grows faster than expected. Assume Copilot has meaningful variable cost tied to usage, buyers include mid market and enterprise software companies, and the launch team needs one initial pricing approach rather than a long menu of options. Your job is to recommend a defensible starting model, explain the tradeoffs, and show how CommandBar should learn and adjust after launch.

What to produce

Write a 1 to 2 page pricing recommendation memo.

Your answer must

Constraints

Format

Use sections for recommendation, rationale, alternatives, risks, and post launch learning.

How CommandBar actually played it

A first-person account of how CommandBar priced its AI product Copilot, with the American Airlines lifetime pass as a warning about pricing mistakes and discussion of usage-based pricing tradeoffs with finance approvals.

  • Avoid pricing that can hurt you as usage grows
  • Uncertain spend slows purchases
  • Learn from past pricing mistakes

Built from How we priced our AI SaaS product (and the mistakes we avoided) by User Obsession.

Related case studies

Keep practising