Bill Gates

The pattern they actually represent

In November 1980 Microsoft signed a contract to supply the operating system for IBM's new personal computer. Microsoft did not have an operating system.

In December 1980 the company licensed one that already existed — 86-DOS, written by Tim Paterson at Seattle Computer Products — for a flat fee of $25,000. Then, in the Computer History Museum's account, "by the next summer they recognized the importance of owning it and being able to license it to other companies making IBM-PC clones, so they purchased all rights for an additional $50,000." Seventy-five thousand dollars, in two parts, for code it had not written. The second part is what mattered: "Microsoft retained the rights to the operating system and licensed it to other computer manufacturers, calling it MS-DOS."

The building was outsourced without ceremony. The owning was not outsourced at all.

The layer was there to take because the company assembling the machine did not want it. The IBM PC used industry standard commercial parts, and by the museum's reading that attitude extended to the software. Everyone treated the operating system as a component. One party treated it as a position.

IBM charged $240 a copy for CP/M and $40 for DOS. DOS stayed the bedrock under thousands of application programs for fifteen years, and in 1999 a federal court measured what that was worth: a share of the world-wide market for Intel-compatible PC operating systems above ninety per cent every year for a decade.

The 1995 memo that told his staff to reorganise around the Internet argues from the PC as its worked example, and it is candid: "The PC wasn't perfect. Aspects of the PC were arbitrary or even poor." The winning layer, said the man who owned it, was not the well-made one.

The blockage it speaks to

Read this if there is a component inside your product that you are writing yourself while a purchasable version has existed for years.

Your own billing. Your own admin panel. Your own scheduler, sign-in, editor, email sender. Each has a justification and it is usually true: the off-the-shelf version does not quite fit, the pricing gets annoying at volume, the integration is ugly. What it hides is the ranking. Your best weeks are going into a layer where quality changes nothing about who wins.

Meanwhile the layer that would compound is handled casually. The customer relationship sits inside somebody else's marketplace. The audience lives on a platform account you do not control. The rights to what you make are settled in one paragraph of a contract you read once, quickly, because the money was the part you were negotiating.

None of that is a discipline failure. Building is legible: it produces commits and something to demo. Buying produces an invoice and the sense of having skipped the real work.

Gates is the study for that exact stuckness because he made both calls inside eight months, and the cheap one is what everybody remembers. Licensing the code was easy. Paying again for the rights to something already working held for fifteen years.

Three moves you can steal

Write down the one layer you would refuse to rent. List everything your product stands on: payments, hosting, the customer list, the distribution channel, the content, the brand. Mark exactly one as the thing you have to own outright. Everything else becomes a purchase decision instead of a question about who you are.

Buy the working version and ship on top of it. Not the best version. The one that runs. Microsoft licensed an operating system that already ran instead of commissioning a better one, and the machine shipped with it in August 1981. In the same memo Gates tells his executive staff to study what the competition has already built: "I think SUN, Netscape and Lotus do some things very well." Somebody has solved your non-leverage layer and will hand it over today for money.

Read the ownership terms before you read the price. The $25,000 licence and the $50,000 purchase covered the same code; only the second one bought the position. In your own agreements, find the paragraph that says who may resell, who keeps the customer, and what you hold when the deal ends. It is worth more than the number you have been arguing about, and it is usually the one nobody redlines.

Where the pattern breaks

A layer position has a bill and it is paid in calendar. The ninety per cent figure exists because a court was measuring it: the United States filed an antitrust complaint on 18 May 1998 and the finding was entered in 1999. On 28 June 2001 the appeals court, sitting en banc, affirmed in part and reversed in part the holding that the company had unlawfully maintained its operating-system monopoly, reversed the attempted-monopolization holding, sent the tying claim back, and vacated the order to split the company in two. Owning a layer works until it works, and then someone with subpoena power holds your schedule for years. Before you take a position, name who gains standing over you the moment it pays.

What to do this week

Open whatever you are building and find the part of it that is not the reason anyone buys. There is one. There are usually three. Pick the largest, and spend an hour finding what it would cost to have that part outright this week — a service, a licence, a contractor, a library that already works. Write that number next to the number of weeks you were about to spend.

Then do the half that counts. Name the layer you are keeping and write one sentence: this is the thing I intend to still own in five years. Then go and check whether you own it now. Open the contract, the account settings, the export button, the renewal term. If the honest answer is no, that is the work, and it outranks the feature you had planned.