37signals · Go-to-market · Senior · 45 to 60 minutes

How should Basecamp 5 launch to customers?

37signals is a software company best known for Basecamp, a project management and team collaboration product. Answer this product management case and get it graded line by line against a weighted rubric.

Go-to-market strategy
Risk management
Stakeholder judgment
Customer empathy
Operational planning

The situation

You are a senior PM at 37signals, preparing a recommendation for Jason Fried and David Heinemeier Hansson. The team is close to launching a major new version of Basecamp, but this is not a net new product. Existing customers already run active work in the current version, so the launch plan will affect daily operations, customer trust, and support load from day one. Leadership needs a decision on two linked questions. First, how should the new version be introduced to the current customer base, phased in over time, offered as an option, or switched over on a single plan. Second, how firm should the launch date be, given that product readiness, app readiness, documentation, and support preparation all need to line up. The hard part is that each path creates a different kind of risk. A slower rollout may reduce immediate disruption, but it can leave the company supporting multiple experiences at once. A faster rollout can simplify the product story, but it raises the stakes if customers push back. You need to recommend a launch approach, date logic, and support plan.

What to produce

A 1 to 2 page launch recommendation memo.

Your answer must

State your recommended launch approach for existing customers and defend it against at least one credible alternative.
Describe how you would set the launch date, what could justify moving it, and who should make that call.
Identify the most important launch dependencies and risks across product, apps, customer communication, and support, and rank them.
Lay out a customer communication and support plan, including how to handle customers most likely to resist the change.
Define the first two weeks of launch monitoring, success signals, and actions you would take if adoption or support volume goes off track.

Constraints

Do not assume new features, price changes, or a separate migration product.
Do not assume extra headcount beyond the current product, engineering, design, and support teams.
Your plan must work for an existing paying customer base that depends on the product for daily work.

Format

Use sections for recommendation, launch date logic, dependencies and risks, customer communication and support, and launch monitoring.

How 37signals actually played it

After releasing Basecamp 5, the co-founders discuss the launch: setting and moving the date, why the mobile apps became a point of no return, the decision to move all customers to the new version at once, and how they handled customers who pushed back hardest. A full transcript is on the page. A rare first-hand account of launching a major version for an existing customer base.

Treat setting and moving a launch date as a real decision with trade-offs.
Migrating all customers at once removes a split product but raises the stakes for support.
Identify the point of no return (here the mobile apps) early.
Plan for the customers who resist change and have support ready.

Built from Launch details & decisions (REWORK podcast transcript) by Jason Fried and David Heinemeier Hansson, 37signals.