sheet III · strategy 2 / 80

Completeness

Полнота

Accumulation Holds Depth 2 · Excavator

all-in-one, one-stop shop

Moats it grows into

  • #5 Switching costs 2 · Excavator

    Every module the customer adopts adds a migration to the bill for leaving; ten adequate tools bound together cost more to replace than one great tool.

  • #27 Bundling and reach 2 · Excavator

    A new piece ships to the existing customers through the login they already have; the reach is paid for once, and every addition rides on it.

Summary

A strategy of covering every adjacent need in one place, so the customer stops looking elsewhere. Each added piece raises the price of leaving, because leaving means replacing all of them at once. It holds, but shallowly: both moats it digs are excavator depth, and both are losing ground as software becomes cheap to assemble.

How it works

The mechanism is the end of comparison. A customer with ten needs and one supplier stops shopping; the eleventh need goes to whoever already serves the other ten. Two things compound. First, breadth: a rival must match the whole set before the customer will even look, and matching the whole set costs more than any one customer will pay for it. Second, entanglement: data, workflows and habits spread across the pieces, so the bill for leaving is ten migrations, not one.

No single part has to be the best. No blade on a Swiss army knife is the best knife; the edge is that all of them are in one pocket. Walmart's supercenter is one parking lot, one cart, one checkout for groceries, tyres and a prescription. A customer who starts comparing the parts is already leaving; the strategy works only while they weigh the whole.

Why it holds — or only takes

Holds, because breadth is something a rival must build rather than a position it can declare, and the building digs two moats directly. Switching costs grow with every piece the customer adopts: each one is another migration on the bill for leaving. Bundling and reach grows because the same login, the same contract and the same sales call carry every new module — its distribution is paid for once, and a point-solution rival must buy that reach one customer at a time. Both are depth 2. A rival with a modular stack and a few years fills them, and cheap assembled software is shortening the years.

Do you have it

  • Customers ask you to add a category instead of buying it from a specialist.
  • A rival beats you on one feature and still loses the deal, because the buyer would need three vendors instead of one.
  • Churn happens only at full re-platforming, never over a single feature complaint.
  • Each new module sells faster than the last, because the buyer already signed the master contract.
  • Customers describe you by the number of tools you replaced.

How to dig it

  • List the customer's adjacent jobs and add the one they now do in a spreadsheet or under a second login.
  • Share one data model across the pieces, so each addition deepens the entanglement instead of sitting beside it.
  • Price so the second module is nearly free and the fifth is unthinkable to unbundle.
  • Ship the missing pieces at adequate, not excellent; the value is the closed gap.
  • Keep one login, one bill, one support queue — the bill is where the customer feels completeness.

How it erodes

  • A best-of-breed rival with a clean importer wins the one job that matters, and the rest follow it out.
  • Open APIs and integration platforms let the customer assemble their own bundle from specialists.
  • Each mediocre module turns into a reason to leave once migration becomes cheap.
  • Generated software lowers the price of breadth; a rival matches your ten modules in a season.
  • The largest accounts outgrow your weakest piece, and the unbundling starts at the top.

Solo, without capital

A solo builder can be complete for one narrow customer: every job of a wedding photographer, a dental practice, a one-truck mover. Switching costs are fully within solo reach; bundling and reach only partly, because reach across a mass market needs a sales force. Breadth is a headcount problem: every module needs maintenance, and ten half-finished tools ship more bugs than one finished tool. Neither moat can be rented, and both sit low on the ruler, where a rival fills them in a few years.

What the matrix says of its moats

In nature, in business

Nature
—
Business
Swiss army knife, Walmart

Cases

  • Microsoft Office — Sold Word, Excel and PowerPoint as one suite, so a rival had to match all three before a company would move.
  • Zoho — Put dozens of business applications — mail, CRM, books, HR — under one login and one subscription for small companies.
  • Walmart — Built the supercenter format: groceries, general merchandise, a pharmacy and tyres under one roof with one checkout.

Combines with

  • Bundling — The next piece arrives free with the piece they already pay for, so breadth never has to be sold twice.
  • Low-friction — One login and one bill make the breadth feel like one product instead of ten.
  • Versatility — A maker competent across many tasks is the only one who can keep ten modules alive at once.

This strategy on the map → Map this combination →

Fights with

  • Specialization — Depth in one job and coverage of all of them draw on the same hours; the complete product is adequate everywhere.
  • Simplicity — Every added piece is another surface to break; completeness multiplies the points of failure simplicity removes.

Map this tension →

Strategy taxonomy © kepano (Steph Ango), paraphrased with attribution. Role and moat mapping © Moat Atlas. Many ways to win ↗