Constraints first
- Every cost is shown for year one, two and three, with the working.
- Team time is counted in people and months, at the cost given below.
- Use only vendor prices pasted; mark anything missing as [price needed].
- Name what the business gives up with each option, not only what it gains.
- The recommendation fits in three sentences.
Inputs
- Capability needed: [e.g. in-app video consultations for a clinic booking app]
- Why it matters to customers and the business: [describe]
- Team available and monthly cost per engineer: [e.g. 3 engineers at Rs 1.8 lakh a month]
- Vendor or API options with prices and limits: [paste]
- Possible partners and what they offer: [paste, or none]
- Deadline and must-have requirements: [e.g. live by March, data stored in India]
Compare on
Cost over three years, time to launch, control over the experience, data and compliance, lock-in and exit cost, upkeep effort, and whether it is core to what makes the product different.
Output format
- | Factor | Build | Buy | Partner |
- A three-year cost table with totals.
- The main risk of each option and how to reduce it.
- Recommendation, with what would change it, such as volume doubling or a vendor raising prices.
- Next steps for the next two weeks.






