Build vs Buy Decisions

Build, buy or partner calls made on evidence: a decision register, total cost of ownership models, vendor shortlists and proofs of concept, renewal and exit plans, and reviews that check whether past choices still hold.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Build vs Buy Decisions, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

201

Starter tasks

🧩 Product Management

Build vs Buy Decisions

Deciding whether to build a capability in-house, buy a tool or partner, weighing cost, time, differentiation and long-term maintenance.

  1. Build vs buy decision register
  2. Core versus context capability map
  3. Decision rights for sourcing calls
  4. Shared scoring criteria for build, buy or partner
  5. Three-year total cost of ownership model
  6. Fully loaded engineering cost rate
  7. Retrospective on past sourcing decisions
  8. Requirements brief before any vendor contact
  9. Opportunity cost of using roadmap capacity
  10. Monthly vendor scorecard review
  11. Renewal calendar and notice periods
  12. Quarterly sourcing portfolio review
  13. Maintenance hours for in-house components
  14. Vendor release and roadmap watch
  15. Weekly triage of new sourcing requests
  16. Vendor viability and health check
  17. Seat and usage true-up against licences
  18. Sourcing assumptions tracker
  19. Reading software contracts as a product manager
  20. Estimating build effort without optimism
  21. Open source licence basics for product use
  22. Running scripted vendor demos
  23. Technical due diligence on a vendor API
  24. Wardley mapping for sourcing choices
  25. Negotiating with software vendors
  26. Vendor shortlist from longlist to three
  27. Time-boxed proof of concept
  28. Scoping the build option with engineering
  29. Partner, white-label or revenue share option
  30. Buy the core, build the edge
  31. Exit plan and lock-in assessment
  32. Security and privacy review of a shortlisted vendor
  33. Sourcing recommendation memo for leadership
  34. Contract signature and procurement handover
  35. First 90 days with a new vendor
  36. Migrating from an in-house component to a vendor
  37. Bringing a bought capability in-house
  38. Major renewal negotiation
  39. Responding to a vendor acquisition or end of life notice
  40. Founder default of buying before product-market fit
  41. Scale-up review when bought tools start to strain
  42. Inherited homegrown system decision
  43. When engineers want to build it themselves
  44. Sourcing under a fixed launch date
  45. Tool consolidation after a merger or reorganisation
  46. Explaining build vs buy choices to the board
  47. Sourcing choices for AI model capabilities
  48. Staged decisions with trigger thresholds
  49. Written sourcing principles for the product organisation
  50. Annual audit of sourcing decision quality

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Build vs buy decision register

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Most teams cannot say when they chose to build their own billing, buy their search engine or partner for payments, or who agreed it and why.

First tasks

  • Create the register with columns for options, choice, owner, reasons and review date
  • List the bought tools and in-house components the product depends on today
  • Ask the longest-serving engineer why the three biggest components were built in-house
  • Check the register for decisions that have reached their review date @recurring(monthly:8)

Core versus context capability map

Every product depends on dozens of capabilities, from login and email delivery to the recommendation logic customers actually choose you for, and only a few of them deserve your own engineers. Mapping each capability as differentiating, important but standard, or commodity gives a default answer for most sourcing questions before anyone opens a vendor website.

First tasks

  • List every capability the product relies on in one sheet
  • Mark each one differentiating, standard or commodity with a one-line reason
  • Check the differentiating list against the reasons customers give for choosing you
  • Walk the engineering lead through the map and record where you disagree
  • Refresh the map after the annual strategy review @recurring(yearly)

Decision rights for sourcing calls

Without agreed decision rights, a product manager can sign a tool on a credit card while a six-month platform build sails through on one engineer's enthusiasm. Setting thresholds for who recommends, who decides and who must be consulted, by annual cost and engineering effort, means small calls move fast and large ones get proper scrutiny.

First tasks

  • Draft three thresholds by annual cost and engineering weeks
  • Name who recommends, decides, is consulted and is informed at each threshold
  • Ask finance and security where they need to be consulted
  • Publish the agreed page next to the decision register

Make it yours.

Install Build vs Buy Decisions, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.