Sourcegraph · Strategy · Entry · 45 to 60 minutes

How should Cody's plan lineup change?

Sourcegraph builds tools that help developers search, understand, and work with code, including its Cody AI coding assistant. Answer this product management case and get it graded line by line against a weighted rubric.

strategy
segmentation
tradeoff analysis
written communication
go to market judgment

The situation

You are an associate PM on Cody at Sourcegraph. The GM and pricing lead have asked for a recommendation on whether the current Cody lineup still makes sense: Cody Free, Cody Pro, Cody Enterprise, and Cody access bundled into Enterprise Starter. Over the past few quarters, the team has heard mixed signals from users and internal teams. Some plans are easy to explain, while others create overlap, edge cases, or extra work across support, billing, documentation, and go to market motions. At the same time, any change could disrupt current users, create trust issues, and pull attention away from the enterprise customers Sourcegraph most needs to serve well. Leadership wants a short strategy memo before an upcoming packaging review, with a decision soon after. Your job is not to redesign Cody itself. Your job is to recommend how the plan lineup should evolve, which customer groups should be affected or protected, and how Sourcegraph should handle transition and communication if you propose changes. The hard part is balancing simplicity, continuity, and strategic focus.

What to produce

A 1 to 2 page strategy memo.

Your answer must

Describe the core problem with the current Cody plan lineup, using customer segments and business tradeoffs rather than feature ideas.
Present 2 to 3 credible packaging options for Cody Free, Cody Pro, Cody Enterprise, and Cody access in Enterprise Starter.
Make a clear recommendation, including what should stay, change, combine, or end, and why.
Identify which user groups would be affected, which should be protected from disruption, and what transition path each group would get.
Define 3 to 5 success metrics or leading indicators that would show whether the plan decision is working within the first few months.
Name the main risks of your recommendation, including user trust and revenue or adoption risk, and give a mitigation for each.

Constraints

Do not assume major new product features or a full pricing redesign in this cycle.
Your recommendation must cover only Cody plan packaging and transition, not broader Sourcegraph company strategy.
Existing enterprise customers must not face a service interruption because of your proposal.

Format

Use short sections: problem, options, recommendation, transition, metrics, risks.

How Sourcegraph actually played it

Sourcegraph announces it will retire Cody Free and Cody Pro and remove Cody from its Enterprise Starter plan on July 23, 2025, while keeping Cody Enterprise. It explains the reason as focusing on where developers see the most value as models move toward more autonomous work. A short example of sunsetting plans with a clear date and reasons.

Give a date, say who is affected, and say who is not.
Link a product-line simplification to a shift in how the product is actually used.
Protect the segment you are committed to, such as enterprise customers.
Point users to the successor product so the change is not just a removal.

Built from Changes to Cody Free, Pro, and Enterprise Starter plans by Kelvin Yap, Sourcegraph.