wowprompt

Build, buy or partner decision memo for a new product capability

Compares building a capability in-house, buying a ready tool or API, and partnering with another company, across cost over three years, time to launch, control, risk and team effort, and ends with a recommendation and the conditions that would change it. Use it for features like payments, chat, search, video calls, KYC or analytics.

A decision memo with a three-option comparison table, a three-year cost view, risks for each path and a clear recommendation
The output this prompt produced, unedited.

The prompt

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

  1. | Factor | Build | Buy | Partner |
  2. A three-year cost table with totals.
  3. The main risk of each option and how to reduce it.
  4. Recommendation, with what would change it, such as volume doubling or a vendor raising prices.
  5. Next steps for the next two weeks.
build vs buybuild or buy decisionproduct strategy memovendor evaluationmake or buy analysisproduct decision

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity