Should we build our own AI feature or buy a vendor product?
AI product management · Intermediate 2
Short answer
Buy when the need is common and not what makes you different, such as meeting notes or a generic support bot, and a vendor meets your security and data rules. Build when the feature is core to your product, needs your own data, or vendors cannot meet your quality, cost or compliance needs.
Deeper answer
Compare total cost over two or three years: licences or API spend, engineering time, maintenance, evals and support. Check lock-in: can you export data and switch? Run both through the same eval on your real cases before deciding.
Most teams today 'buy' the model through an API and 'build' the product around it: prompts, retrieval over their data, workflows and UX.
What a strong answer covers
- Buy for common, non-differentiating needs
- Build for core features using your data
- Checks security, data and compliance
- Compares total cost over time
- Evaluates both on real cases; considers lock-in
Answer it out loud in the mock interview about 1.5 min
Follow-ups to expect
- How would you compare a vendor's quality claims with your needs?
- What lock-in risks would you check?
Common mistakes
- Deciding on gut feel
- Ignoring maintenance cost of building
Learn it
Feasibility and build versus buy
- What does a good data strategy for an AI product look like?
- Your AI feature launched, usage is high, but customer satisfaction dropped. What do you do?
- How would you measure the success of an AI feature?
- How do you design a product experience when the AI is sometimes wrong?
- You launched an AI tool internally and nobody uses it. What do you do?
- How do you decide whether a problem is a good fit for AI?
- As a PM, how do you work with engineers on evals?
- How would you price an AI feature whose cost grows with usage?
- When should a product keep a human in the loop?