Build less, own more of the outcome: what fails first

A purchased platform still needs an owner on-call for failure modes, data handling, and process fit.

I will stay on this thesis — no adjacent manifesto, no tour of every neighboring discipline.

When pressure rises, teams drop the unowned practice first. Put Build less, own more of the outcome in the path of work — templates, checklists, review norms — or admit it was optional applause.

On Build less, own more of the outcome, start from ownership of the failure mode and the exit path. Purchase price is the down payment; integration debt is the mortgage.

How it actually works

Install the smallest set of mechanisms that make success and failure legible. Skip the program name.

Build the harness, buy the commodity: keep eval suites, policy, and audit logs in systems you control even if inference is purchased.

Evaluating vendors like critical-path systems includes asking how you pause them. No pause path means no operational maturity.

Start from ownership. If nobody on your team can operate the failure mode, you did not buy a capability — you rented a demo with a support email.

Integration debt belongs on the same board as features until retired. Otherwise procurement wins the quarter and on-call pays the year.

Platforms you buy still need owners — for identity integration, data retention, incident comms, and process translation. Procurement does not create ownership.

When a vendor becomes your process, document the process in your words. Otherwise a price hike or outage becomes an identity crisis.

If nobody on your team can operate the failure mode, you did not buy a capability — you rented a demo with a support email.

Where this shows up

A team builds a custom agent platform because it feels strategic. Six months later they maintain auth, quotas, and UI chrome instead of product differentiation. Commodity inference plus an in-house harness would have been enough.

No exit plan. Price increases. Suddenly “switching costs” are discovered during budget season. A tabletop unwind once a year is cheaper than surprise.

Build the harness, buy the commodity works until someone rebuilds the commodity “for flexibility.” Flexibility without differentiated ownership is usually nostalgia.

Tradeoffs

Building custom feels like control and often buys maintenance. Buying feels like speed and often buys integration debt. Name the debt either way.

Vendor features arrive fast. Your process still needs translation into owned runbooks.

Keeping harnesses in-house costs engineering time and preserves exit. Worth it for anything on the critical path.

Measure what you claim to care about. If Build less, own more of the outcome only appears in kickoff slides and never in review, incident, or planning artifacts, it is branding. Put a verification signal where people already look.

Write one page while the decision is still warm — context, options, choice, owner, revisit date. Verbal alignment on Build less, own more of the outcome evaporates under ordinary calendar pressure, and Slack archaeology is a poor substitute for a decision record.

Failure modes

Each of these is a missing control, not a personality problem:

• No exit plan; switching costs discovered during an outage or a price hike.
• Building because pride, buying because fear — neither from ownership analysis.
• Vendor success metrics replacing your product metrics.
• Shadow purchases by teams that skip security and data review.

What to do this month

• Annual: run a tabletop exit for one critical vendor.
• Require eval and audit ownership to stay in-house for AI tooling.
• Track integration debt items on the same board as features until retired.

Make-or-buy with agents in the mix still requires you to define tool allow-lists and human override. Buying the runtime does not buy judgment.

Evaluate AI vendors like critical-path systems: SLOs, incident communication, subprocessors, kill switches, and data boundaries.

Build less, own more of the outcome: prefer thin custom layers over reimplementing commodity models. Copilots make greenfield look cheap until on-call inherits it.

Price integration debt explicitly: connectors, identity, logging, eval wiring, and the people who will babysit them. Purchase price is the down payment.

Exit drills are cheap insurance. Export a sample, revoke a key, and time how long a degraded mode lasts before you need the vendor again.

Write exit strategies for bought AI tooling before procurement: data export, prompt/eval portability, and a 90-day unwind drill. Soft lock-in is still lock-in.

The new cost of custom is maintenance, not typing. AI makes that easy to forget until the second quarter of on-call.

Keep eval suites and audit logs in systems you control even when inference is purchased. That is how you keep judgment portable.

Integration debt after purchase: five half-connected identity paths and no single owner for authz bugs. Procurement celebrated; on-call paid.

A price hike arrives and nobody can list what data is trapped where. The exit sketch should have been written at purchase, not at panic.

A vendor’s success metrics replace product metrics in leadership reviews. That is lock-in of attention. Keep your north-star metrics in-house.

One more practice worth installing: Every build: name the commodity you refused to buy and why ownership differs.

Ambiguity is expensive. Spell out what “good” looks like for Build less, own more of the outcome in one paragraph a new teammate can reuse.

Close

Harnesses outlive vendors. Invest accordingly.

Carry the claim as a habit, not a brand: Build less, own more of the outcome either compounds ownership or it was applause.