Original Equipment Manufacturer

The term comes from the moment the company that builds something stopped being the company that sells it. One side is good at making the thing but nobody has heard of it. The other side has a name everyone knows and no capacity to build. Pairing them works for both, and for a long time there was no word for that pairing.

So the contracts came out vague. They said one party would build for the other, without settling whether this was supply, contract manufacturing, or sales on someone's behalf. The questions that mattered went unwritten: whose name goes on the box, and who does the customer call when it breaks. Months later, when complaints landed on the builder's desk, one side said it had only built the thing and the other said whoever built it owns the problem.

Original equipment manufacturer (OEM) nails that distinction down in a name. It splits the party that builds from the party that brands, and it settles that the product reaches the market as the branding party's own. The phrase hardened in manufacturing, but the structure carried into software unchanged.

The two sides bring different things. The supplier brings the product and responsibility for its quality. The brand owner brings the name, the sales channel, and the customer relationship. Customers believe they bought the brand owner's product, and most of them never learn another company is behind it.

Five things get settled in the contract.

1. Scope and specification — what gets built and how far it goes. If the brand owner wants a feature the product doesn't have, this is where the two sides decide who pays to build it.
2. Volume and unit price — how much the brand owner takes and at what rate. A product that lists at $90 per seat might go out at $30 per seat on a commitment of 5,000 seats a year, which is a steep drop from the direct price.
3. Branding rules — by default the builder's name appears nowhere on screen or in the documentation. Whether even one line can stay in a corner is a routine sticking point.
4. Incident responsibility and response times — customers contact the brand owner, who passes the problem to the supplier. The contract fixes how many hours until a reply and how many days until a fix.
5. Term and exclusivity — a clause barring supply to other companies in the same industry is common. Exclusivity gets traded against a longer term and a higher unit price.

Money and customers flow one way. What the customer pays goes to the brand owner, and only the agreed unit price comes back to the supplier. The customer list and the usage records stay with the brand owner too, so the supplier sees how its own product is used only to the extent the other side passes that information along.

In software the word overlaps almost completely with white label, which means shipping a product under the customer company's brand. For a software as a service (SaaS) product — software you subscribe to rather than install — swapping the logo and the colors is most of the work, which makes these deals easier to strike than in manufacturing, where a separate production run is involved.

Three situations come up often. A large company puts document editing inside its own office suite under its own name. A bank or a telecom drops an extra service into its own app. A foreign company entering a new market sells through a local company's brand first. In all three, the side lending the name already holds a large base of customers.

The case for doing it is specific: the product is finished but there is no time or money to build a name, while the other side has the customers and no time to build the product. A deal like this brings in thousands of users without hiring a single salesperson, and the revenue buys time to build the next thing.

There are places to avoid it. When the product sells on its own name. When knowing how customers use it is the raw material for the next release. And when one partner grows past half of total revenue. That last one causes the most damage. If the partner declines to renew, revenue halves the following quarter, and by then not a single line of the supplier's own reputation has accumulated in the market. Investors tend to raise the same point first when half the revenue sits inside one contract.

"This one ships without our logo, under their name. It's an OEM deal."

We build it, but the market sees it as the other company's product.

"The OEM price is a third of list, and it still beats selling direct."

Margin per deal drops, but the sales cost and time saved make the total better.

"OEM is 40 percent of revenue and that contract ends next June."

The whole company is riding on one partner, so start preparing now.

At Pagedeck, a large enterprise once got in touch about adding document editing to its own collaboration suite. The condition was that the Pagedeck name appear nowhere. Sofia brought in a three-year volume and price, and Grace immediately pointed out that the figure was more than half of what Pagedeck currently sells directly.

The discussion moved off whether to lend the name and onto what would be left afterward. Mia asked whether Pagedeck would be able to see which features those customers used and how often. If the answer was no, she said, that meant three years without the evidence the team uses to decide what to fix.

The most common reading is that OEM is just subcontracting. No name, a cut price — it looks like the lower seat at the table. But leverage comes from replaceability, not from branding. If only a handful of companies can build the feature, the supplier sets the terms; if similar products are everywhere, the supplier gets pushed around whether its name is on the product or not. Walking in assuming the weaker position means giving up terms that were actually winnable, like exclusivity limits or access to usage data.

The other one is that swapping a name is light work. The mental picture is replacing a logo at the top of a screen, so it looks cheap. In practice the product has to fit the partner's account system, its billing, and its permission structure, and the supplier has to hold to a promise about responding to incidents within hours. Price the deal on the logo-swap assumption and it turns into a contract where every additional sale loses money for its full term. Listing the partner's requirements line by line and counting the engineering days before signing is the safer route.