The Build / Hire / Automate Decision.
PH—011
Build, hire, or automate. The three lanes are not equivalent. Each has a cost curve, a timeline, and a failure mode. Here is how Cost Analysis models the trade on our installs, and the one thing every in-house spreadsheet leaves out.
I The Three Lanes
The recommender outputs a ranked prescription stack. Each prescription resolves to one of three lanes.
Build. The organization writes the code, assembles the system, and maintains it in-house. Highest long-run ownership. Highest short-run risk.
Hire. The organization adds a team with the domain expertise to own the capability. Slowest to stand up. Most durable when it works.
Automate. The organization installs a tool, an agent, or a service that performs the capability. Fastest to ship. Most vendor risk.
Every prescription gets a fourth classification as well: whether it is reversible. Build is usually irreversible within twenty-four months. Hire is reversible on sixty days. Automate is reversible on thirty.
II Cost Is Not the Deciding Factor
Every enterprise analysis of build-hire-automate eventually converges on cost. This is a mistake. Cost is rarely the binding constraint. Timeline is.
The question that matters: what does the organization need running in ninety days? If the answer is “a thing that moves the KPI,” automate almost always wins, because build and hire cannot meet the timeline. If the answer is “a capability that compounds for five years,” build or hire moves to the top, because automate rents capability rather than owning it.
Our Cost Analysis surface shows all three, side by side, with timelines. The number is not the headline. The timeline is.
III Timeline Compounding
Build compounds the fastest in capability but slowest in calendar. Month one of a build is zero value. Month twenty-four is full value. Hire compounds more evenly. The second hired engineer is worth more than the first. Automate is near-flat. Month one is close to month twenty-four on the value curve. The tool does not get smarter by sitting there.
The right answer is almost never a single lane. The right answer is a mix. Automate the urgent, hire the durable, build the strategic. Our Cost Analysis shows this as three overlaid curves. Leadership picks the lane mix in the same session.
IV The Spreadsheet Omission
Every in-house build-hire-automate spreadsheet we have been shown has left out the same line item: the cost of getting the lane wrong.
A build that fails to deliver is not a zero. It is a negative. The team is burnt out, the codebase has accumulated debt, and the organization is slower next year than it would have been without starting. A hire that doesn’t work is a multi-quarter hole, both in salary and in morale. An automate that leaves on renewal exposes the organization to a vendor transition it is not ready for.
The Cost Analysis surface shows the failure cost for each lane alongside the success cost. This is the one insight we have that the internal spreadsheet almost never includes. Once leadership sees it, the choice usually changes.