Build, Buy, or Hire

Every capability gap in your business can be closed three ways:

• •Build: Your team creates it. You convert engineering hours into a system or process - a Capital Investment in Labor.
• •Buy: You purchase it from a vendor - SaaS Subscription Pricing, a one-time license, or a managed service. The vendor already solved the problem and you pay for their solution. (Note: acquiring a company to obtain a capability involves Capital Structure, M&A due diligence, and integration risk - a fundamentally different decision class from purchasing a vendor tool.)
• •Hire: You bring in a person who has the capability, adding to your Labor line and importing Knowledge Capital that did not exist inside your organization.

The decision is not "which is cheapest." It is "which generates the most ROI given my Time Horizon, risk appetite, and strategic needs."

Each path hits your P&L differently, and the wrong choice compounds:

Build front-loads cost. If the build succeeds, you own an Asset that can become a competitive moat. If it fails, you burned Cash Flow and time with nothing to show.

Buy creates ongoing Fixed Obligations. A SaaS tool at $2K/month is predictable, but it is a permanent line item. Over a 3-year Time Horizon, that is $72K - possibly more than building it. And you do not own the Asset. The vendor controls the roadmap, the Pricing, and part of your Cost Structure.

Hire adds permanent overhead to your Operating Statement. A $150K hire might cost $195K once you include benefits and overhead. That is a Fixed Obligation regardless of output. But a strong hire brings Throughput that a tool cannot - judgment, adaptation, and the ability to solve problems you have not identified yet.

Operators who default to one path without running the comparison destroy value. Builders default to build. Finance people default to buy. Neither is thinking about Capital Allocation.

Evaluate each option on four dimensions:

1. Time to Value

How fast does each path deliver a working capability?

• •Build: Weeks to months. You carry Execution Risk - it might take longer than estimated, and it usually does.
• •Buy: Days to weeks. The vendor's product already works. Your Time to Value is mostly integration and configuration.
• •Hire: Weeks to months. Factor in Time-to-Fill plus the weeks before the new person reaches full Throughput.

2. Expected Total Cost Over Your Time Horizon

Do not compare upfront costs. Compare the Expected Total Cost over the period you need the capability. When computing costs that include people, always use the full annual cost: salary plus benefits plus overhead (payroll taxes, equipment, office space). This is the real number your Operating Statement reflects.

• •Build: Implementation Cost (engineering hours at their full annual rate) + ongoing maintenance (typically 20-30% of build cost per year). Use Amortized Cost to spread the build over its useful life.
• •Buy: Monthly or annual fee multiplied by duration. Watch for annual vendor rate increases - some vendors raise Pricing 10-15% per year once you depend on them.
• •Hire: Annual cost (salary + benefits + overhead) multiplied by duration. Include recruiting costs (Full-Cycle Recruiting is not free) and the risk of Tribal Knowledge concentration - if this person leaves, does the capability leave with them?

3. Differentiation vs Commodity

This is the most important dimension.

• •If the capability is a Commodity (payroll, email delivery, cloud hosting) - buy it. Your custom version will never be better than a vendor who does only this.
• •If the capability drives differentiation (your pricing algorithm, your matching engine, your proprietary workflow) - build it. Using a Commodity solution for your core competitive moat hands your advantage to everyone using the same vendor.
• •Hire when the capability requires ongoing human judgment that cannot be systematized yet.

4. Opportunity Cost

What else could those resources be doing? If your engineering team is at capacity and the Bottleneck is shipping Revenue features, pulling engineers off to build an internal tool has a measurable cost: the features they would have shipped, the Revenue those features would have generated, and the Time to Value delay on everything else in the Pipeline. Each engineering hour has a Shadow Price equal to the best alternative use of that capacity.

Run this analysis every time you identify a capability gap. The decision tree:

1. 1)Is this a Commodity or differentiation? If Commodity, default to Buy unless the vendor market is broken (overpriced, unreliable, or nonexistent).
2. 2)What is the Time Horizon? If you need it for 6 months, Buy. If you need it for 5 years, the math often favors Build. Use the break-even calculation from the worked examples below.
3. 3)What is the opportunity cost? If your team has spare capacity, Build is cheaper than it looks. If they are at the Bottleneck, Build is more expensive than it looks.
4. 4)Does it require ongoing judgment? Systems handle known patterns. People handle unknown ones. That is a Hire signal.
5. 5)What risk can you manage? Build carries Execution Risk. Buy carries vendor risk (they raise prices, discontinue the product, get acquired). Hire carries retention risk (Tribal Knowledge walks out the door).

Staging: Buy Now, Build Later

You do not always have to pick one path. When a capability is a source of differentiation but you need it immediately, Buy to close the gap, then Build or Hire for long-term ownership. This is investment sequencing applied to capabilities: the vendor bridges the gap while you invest in the permanent solution. Set Exit Criteria upfront - define when the custom solution must be ready and what triggers the switch. The best Operators treat Build, Buy, and Hire as stages in a sequence, not a single choice.

Build, Buy, or Hire is where opportunity cost becomes an operational decision. Every dollar and every hour allocated to one path cannot work somewhere else - this is the Capital Allocation tradeoff applied to capabilities. The decision depends on Time to Value: when Revenue is at stake, speed often dominates cost. Downstream, it feeds into Capital Budgeting (how you evaluate and approve these investments), NPV analysis (comparing the present value of each option's costs and benefits), and Payback Period (how quickly each option recoups its investment). It shapes your Cost Structure: Build can produce Capital Assets (engineering costs may be capitalized on your Balance Sheet under applicable accounting rules, though many companies expense them), Buy creates recurring expenses on your Operating Statement, and Hire adds to your Labor line as a Fixed Obligation.