What to outsource and what to keep in-house: the Own vs. Rent rule

Every operating leader ends up sorting the same list. Here is everything the company needs done, and here is the question that comes with it: which of this should live inside the company, and which of it should we pay someone else to do? Most teams sort that list by instinct, under pressure, one vendor decision at a time. That is how a company ends up renting the work its operating rhythm depends on while carrying full-time weight for work that happens once.

Chapter 8 of Operational Alpha offers a cleaner rule, and it fits in a sentence.

The rule: own what recurs, rent what spikes

The Own vs. Rent rule says to own what is recurring and tied to your operating rhythm, and to rent what is spiky, one-time, or perspective-based. Recurring work rewards ownership because every repetition makes the next one better. Standards tighten, definitions of “done” accumulate, and the people doing the work get faster and more precise. Spiky work offers none of that. It happens once, or once every few years, and some of it is valuable precisely because it comes from outside your walls.

The rule sounds obvious written down. Almost nobody runs their vendor list through it.

The own-list: work that should compound inside your company

The book's own-side list is deliberately unglamorous:

• Reporting packs and scorecards
• Pipeline hygiene and follow-up engines
• Onboarding coordination
• Vendor follow-ups that prevent delays
• Traffic control for projects and decisions
• Collections workflows and close prep

None of these will ever headline a board deck. But these are the streams that, when broken, create fog and waiting inside the company. Reports arrive late and get rebuilt by hand. Follow-ups slip and the pipeline goes quiet. Decisions sit in limbo because nobody owns the tracker. The book calls that fog the fuel of the Survival Loop, and it is the reason your most senior people keep absorbing work three levels beneath them.

Owning these streams pays in a specific sequence. The first designed seat brings relief: less chasing, fewer dark zones where work disappears until it is late. Relief that survives a vacation or a bad week becomes continuity. And continuity becomes compounding, because each additional seat is easier to add than the last. Definitions of “done” exist. Examples of great work exist. Review loops exist. The book calls the payoff the Memory Dividend. When the system remembers, capability stops resetting to square one every time a person changes. That compounding, built deliberately, is the whole logic behind the Mini-GCC model.

The rent-list, and why renting is the right call

The rent-side list from the same chapter: a rebrand, a one-time website overhaul, niche legal work, a diligence sprint. Nothing on it recurs. A rebrand that happens once in a leadership tenure builds no rhythm worth housing. Niche legal work calls for depth you will use rarely. A diligence sprint is over in a matter of weeks. And perspective-based work is often better rented on purpose, because the outside eye is the point of buying it.

Renting this work is good judgment. The rule exists for the other direction.

The trap: renting core forever

The trap is renting core forever, paying repeatedly for the same capability because nothing was compounded. It happens quietly. The reporting pack goes to an outside firm because the team is stretched this quarter. The collections follow-ups go to a service because it feels temporary. Two years later the invoices are still arriving, and every engagement starts from zero because the learning left with the vendor. You have paid for the same ramp-up over and over and own none of it.

Owned capability compounds. Rented capacity resets. The expensive mistake is renting the work your operating rhythm depends on, year after year, because nothing ever accumulates.

The tell is the renewal. When an invoice for the same recurring stream renews for the third time, the arrangement has quietly become a lease on core capability, with all of the cost and none of the equity.

How to run the sort on your own operation

List every stream of work you currently buy as a service, and add every recurring stream your senior people absorb personally because there was nowhere else to put it. Then ask two questions of each. Does it recur, weekly or monthly, as part of how the company actually runs? And when it breaks, does the breakage create fog and waiting inside your walls? Two yeses put the stream on the own side. Everything else can stay rented with a clear conscience.

Two adjacent decisions follow the sort. The first is sequencing: of everything on the own side, which stream of work goes to a first seat. The second is the vehicle: embedded versus outsourced teams, which decides whether the capability compounds for you or for the provider.

This is where Kayana engagements sit. At enterprise scale, companies build the own side as a Global Capability Center. At middle-market scale, the vehicle is an embedded team: seats designed around the recurring streams above, run inside your cadence and your tools, so the capability compounds in your company. Grown seat by seat, that layer is how mid-market companies build a Mini-GCC. You define the work and what “done” means. We design and run the environment around it, which is the part that makes the compounding hold.

Quick answers

The Own vs. Rent rule is one page of a larger argument about building capability that stays. The full playbook is the book — Operational Alpha →.