37signals · Execution · Mid · 45 to 60 minutes
How independent should Know Your Company be?
37signals is a software company known for building web based tools for work, including Basecamp. Answer this product management case and get it graded line by line against a weighted rubric.
- Execution strategy
- Tradeoff analysis
- Prioritization
- Learning plan
- Cross functional planning
The situation
You are a PM at 37signals. Jason Fried has asked you for a recommendation on how to set up and launch a new product concept called Know Your Company. The company already has Basecamp and established ways of building, supporting, and operating software, so one path is to reuse as much of that foundation as possible. Another path is to treat this effort as more independent, with its own team, process, and customer rollout. Why this matters now: the product is moving from idea to first customers, and the choices made at the start could shape speed, learning, and long term fit. Reusing existing infrastructure could save time and reduce overhead, but it may also force the new product into decisions made for a different problem. Starting more independently could protect learning and focus, but it may duplicate work and slow the company down operationally. Assume leadership will support a small initial team and wants a plan for how to onboard early customers without overcommitting before the team learns what the product really needs.
What to produce
Write a 1 to 2 page execution memo.
Your answer must
- State a clear recommendation for how independent the product should be across team structure, infrastructure, and operations.
- Compare at least two credible options, including the main tradeoffs of each.
- Propose an initial customer rollout and onboarding approach for the first 6 to 8 weeks, including what the team should learn during that period.
- Define 3 to 5 early success signals or metrics that fit this stage of the product.
- Identify the top risks of your approach and the mitigation steps or decision triggers you would use.
Constraints
- Leadership wants a plan that can begin with a small initial team.
- Existing 37signals infrastructure and operating habits are available, but they were created for other products, especially Basecamp.
- You need an approach for very early customer onboarding, before there is enough evidence to optimize for scale.
Format
Use short sections: recommendation, options and tradeoffs, rollout plan, success signals, risks.
How 37signals actually played it
Jason Fried describes how 37signals approached its newest product, Know Your Company, as a separate small company inside the business rather than another product built on Basecamp's infrastructure. Fried looks back at how Basecamp was built in 2003 with four people and no inherited tools, and plans a small team and weekly onboarding of around five customers. A useful case for PMs deciding how independent a new product should be.
- Start a new product with a small separate team to avoid fitting it into old decisions.
- Look at how your first successful product was built for the process to copy.
- Roll out to a handful of customers each week to learn before scaling.
- Be wary of leaning on existing infrastructure when exploring a new problem.
Built from Building Know Your Company by Jason Fried, 37signals.
Related case studies
- How should 37signals price a new product?37signals · Strategy · Mid
- Should Basecamp Offer Free Access Again?37signals · Strategy · Mid
- Should Basecamp Revisit Its Pricing?37signals · Strategy · Entry
- How should 37signals price a new chat tool?37signals · Strategy · Entry
- How should Basecamp 5 launch to customers?37signals · Go-to-market · Senior
- A stuck HEY feature with a fixed time budget37signals · Product sense · Mid