Recommend Build vs Buy for Restaurants
Company: Capital One
Role: Product Manager
Category: Product / Decision Making
Difficulty: medium
Interview Round: Onsite
You are the Product Manager for a low-code or no-code website builder for restaurants. The product helps restaurant owners create websites quickly and add plugins.
Answer:
1. Define major restaurant customer segments and identify the best target segment.
2. Propose a monetization model and key cost drivers.
3. Calculate per-customer profitability given a $200 onboarding fee, $20 monthly subscription fee, $300 one-time onboarding cost, and $100 annual service upkeep.
4. Decide whether to integrate with an external reservation provider or build booking in-house.
5. Identify factors missing from a pure cost comparison.
6. If external integration grows the customer base by 5% and in-house build grows it by 3%, starting from 100,000 customers, recommend a path.
### Constraints & Assumptions
- Use a 2-year evaluation horizon for the build-versus-buy decision.
- External integration: 2 engineers for 2 months, $120,000 annual salary per engineer, $100,000 one-time onboarding cost, and $15,000 monthly vendor subscription.
- In-house build: 4 engineers for 6 months, $120,000 annual salary per engineer, and $5,000 monthly upkeep after launch.
- Revenue starts only after the feature ships.
- State whether you are using base product profit, incremental customers, or feature-specific revenue.
### Clarifying Questions to Ask
- Is the goal profit, speed to market, strategic control, retention, or customer growth?
- What customer segments have the highest reservation demand?
- Are vendor fees fixed or usage-based?
- Does the reservation feature reduce churn or increase pricing power?
- How credible are the 5% and 3% growth estimates?
### What a Strong Answer Covers
- Segment selection and target rationale.
- Monetization model and cost drivers.
- Correct 1-year and 2-year per-customer profitability.
- Build-versus-buy cost calculation.
- Adoption-adjusted recommendation.
- Missing strategic factors such as vendor risk, data ownership, reliability, differentiation, roadmap control, and time to learning.
### Follow-up Questions
- How would your answer change if vendor fees scale with bookings?
- What if reservation capability is strategically differentiating?
- How would you validate the growth assumptions before committing?
- What metrics would you track after launch?
Quick Answer: Solve a build-versus-buy PM case for a restaurant website builder. Covers segmentation, monetization, per-customer profitability, external reservation integration versus in-house build, adoption-adjusted profit, and strategic tradeoffs.
