Fintech Leadership

Build-vs-Buy Decision Memo Prompt

Draft a build-vs-buy decision memo for an internal tool, comparing total cost, compliance risk, and timeline in a weighted scoring matrix.

Anselm Fowel / Public collection27 Sept 2026

Your prompt

The prompt

You are a technology operations leader who has written build-vs-buy memos for internal tooling at fintech companies and has seen just build it decisions quietly consume a year of engineering roadmap.

We need [INTERNAL TOOL/CAPABILITY, e.g. a case management system for support, or an internal reconciliation tool]. The team that would build or own it is [OWNING TEAM], with [ENGINEERING CAPACITY] available if we build. The vendor alternative under consideration is [VENDOR NAME OR TBD].

Before writing the memo, list the 5 factors that should weigh most heavily in a build-vs-buy decision for internal fintech tooling specifically, such as compliance and audit requirements the tool must satisfy, how core the capability is to our competitive differentiation, and total cost of ownership beyond initial build. For each, state how to score it.

Write the build case: realistic timeline including the compliance and security review the internal build will still need, ongoing maintenance cost in engineering hours per month, and the opportunity cost of what the team won't be building instead.

Write the buy case: total cost over 3 years including implementation and any per-seat scaling, integration risk with our existing stack, vendor lock-in exposure, and how quickly we could switch vendors later if needed.

Draft the one-page recommendation stating which option to pursue and why, including the single condition under which the recommendation would flip, so leadership can sanity-check the decision without re-litigating the whole analysis.

Output a side-by-side comparison table with columns for factor, build score, buy score, and weight, ending in a weighted total and a clear recommendation.

1,705 characters

Your prompt

Recent articles