Framework: The Tech-Finance Decision Matrix
- Description: This is your primary tool for capital allocation. It moves the Build vs Buy debate from a technical preference to a financial and strategic decision, helping you decide where to invest proprietary engineering effort versus where to use off-the-shelf efficiency.
- Origin & Attribution: Rooted in McKinsey’s Three Horizons of Growth and popularised by Geoffrey Moore’s Core vs Context model.
- Context & Heritage: This evolved from traditional manufacturing Make or Buy analyses used to optimise supply chains. In the tech world, it has been adapted to account for the unique costs of technical debt and the high speed of SaaS innovation.
The Framework
- Core (The Build Zone): This is your competitive moat. If the technology directly creates your unique value proposition or intellectual property (IP), you build it. You want full control over the roadmap and zero dependency on a third party for your secret sauce.
- Context (The Buy Zone): These are necessary but non-differentiating functions like payroll, CRM, or email servers. If a specialised vendor can do it 80% as well as a custom solution for 20% of the cost, you buy it to keep your engineers focused on the Core.
- Innovation (The Experiment Zone): Use the Three Horizons to allocate budget. Spend roughly 70% on Horizon 1 (Core stability), 20% on Horizon 2 (Emerging adjacencies), and 10% on Horizon 3 (Disruptive, high-risk R&D).
- The Partner Bridge: For complex tech that is Core adjacent but requires expertise you lack (e.g. specialised AI models), you partner or borrow capabilities to move faster without the full overhead of an in-house build.
Metrics & Success Indicators
- Quantitative Metrics:
- Total Cost of Ownership (TCO): Comparing the 3-year cost of building (dev salaries + maintenance + infra) vs. buying (licences + integration + vendor fees).
- Opportunity Cost: Revenue lost by diverting five engineers for six months to build a commodity tool instead of a core feature.
- Qualitative Success Indicators:
- Strategic Focus: Your top engineering talent is working on the most valuable 20% of your code that generates 80% of your revenue.
- Agility: The ability to swap out bought tools as better market alternatives emerge, rather than being locked-in to a legacy custom-built monster.
Prerequisites & Dependencies
- Clear Business Strategy: You cannot decide what is Core if the business hasn't defined its primary competitive advantage.
- Financial Visibility: Access to accurate data on developer fully-loaded costs (salary + benefits + overhead) to make a fair TCO comparison.
Customisation (How to Fork)
- For Startups: Lean heavily into Buy for everything except your MVP. Speed-to-market is your only real currency.
- For Enterprise: Look for Buy and Blend strategies—purchasing a platform but building custom extensions on top to get the best of both worlds.
The Translation Layer (Communication)
- To the Board: I am treating our engineering capacity as capital. We are only building where it creates a proprietary asset that increases company valuation.
- To the Engineers: I am not outsourcing your work; I am clearing away the boring commodity tasks so you can solve the truly hard, unique problems that define our company.
Similar Frameworks & Tools
- Other Options: Wardley Mapping (vividly plotting what is a commodity vs. what is unique); Gartner’s Pace-Layered Strategy (Systems of Record vs. Innovation).
- Good Tools: TCO Calculators; Spreadsheet-based weighted scoring matrices.
Recommended Reading
- The Alchemy of Growth (Baghai et al.): The origin of the Three Horizons.
- Dealing with Darwin (Geoffrey Moore): The definitive guide on Core vs Context.
Summary (TL;DR)
Don't build what you can buy, and don't buy what makes you unique. Use this matrix to ensure your expensive engineering resources are always pointed at your company’s unfair advantage.
Action Plan
- Immediate Step: Inventory your top 10 engineering projects. Tag each as Core, Context, or Innovation.
- Information Gathering: Run a TCO analysis on the next major Build request. Does it actually save money or create value over three years?
- Core Focus: Be ruthless about Context. If it doesn't help you win in your market, find a vendor who does it better.