avoid-bonehead-customers — quality + safety report

---
name: avoid-bonehead-customers
description: Force a direct-to-consumer reality check whenever a user is debating GTM, distribution, or partnership strategy for a product whose technology is genuinely strong. Use this skill aggressively when the user says "should we partner with X", "we need a strategic partner", "the legacy player has the customers", "they'll handle sales/distribution/integration", "we'll license it to BigCo", "we don't have a sales team so let's partner", "the enterprise will roll it out", or "we'll sell through the distributor". Also fires on debates over OEM vs DTC, white-label vs branded, channel sales vs direct, founder ceding board seats or voting control to a customer-investor, or any moment a startup with great tech is about to hand its distribution to a slower, dumber incumbent who will not deploy it properly. The lesson is Zip2: great software routed through media companies who refused to use it. Trigger eagerly even when the user does not name Musk or the framework.
---

# Avoid Bonehead Customers

> "If you've got great technology, go directly to the end consumer. Don't sell it to some bonehead legacy company that doesn't understand how to use it."
> — Elon Musk, *The Book of Elon* (Chapter: Starting Zip2)

## What this skill captures

When you have genuinely strong technology, the binding constraint on its impact is not the tech — it is whoever stands between the tech and the end user. Musk learned this the expensive way at Zip2: "We built the best technology, but it wasn't being deployed properly." Knight Ridder, the New York Times Company, and Hearst owned the board seats and voting control, "kept trying to push the company in directions that made no sense," and routed great software through organizations that would not fully use it. The F-22 metaphor is the whole skill in one image: building fighter jets and selling them to people who roll them down the hill at each other.

The value this skill gives the user: a brutal pre-mortem on any GTM decision that hands distribution, deployment, or control to a slower incumbent. It forces the question "will this customer actually deploy what we built, at full performance?" before you sign the deal, take the board seat, or build the channel.

## When to use this skill

- A founder is debating partnership vs direct-to-consumer for a product that is technically ahead of the market.
- A startup is offered an OEM, white-label, or reseller deal by a large incumbent who "has the customers."
- A customer-investor wants board seats, voting rights, or strategic control in exchange for a distribution deal.
- A team is justifying a partnership because they "don't have a sales team" or "can't reach end users."
- Leadership is celebrating a logo (Knight Ridder, NYT, Hearst-shaped) without asking whether the partner will actually ship the product to users.
- You are post-mortem-ing a stalled launch and the symptom is "great tech, no adoption" — check whether you sold it to a bonehead.

## The how-to

1. Name the end consumer explicitly, and ask whether your distribution path actually reaches them at full power.
   > "That's when I realized you want to sell your products straight to the end consumer."
   > — *The Book of Elon*
   If the partner sits between you and the user, every feature, every release, and every UX decision will be filtered through their incentives. Most of the time, the filter destroys the product.

2. Audit the partner's competence and willingness to deploy the tech properly — not just their distribution footprint.
   > "We built the best technology, but it wasn't being deployed properly."
   > — *The Book of Elon*
   A large incumbent with millions of customers is worthless to you if they will not actually ship your tech at the performance it is capable of. "Access" to users you cannot reach at full fidelity is not access.

3. Refuse board control, voting control, and "strategic direction" in exchange for distribution.
   > "The challenge was too much control by the existing media companies. They had too many board seats and too much voting control over Zip2. They kept trying to push the company in directions that made no sense."
   > — *The Book of Elon*
   The deal sheet matters more than the press release. If a customer-investor gets governance, they will steer the company toward what is convenient for them, not toward what the tech can do.

4. Run the F-22 test on every channel/partnership decision.
   > "It's a bit like building F-22 fighter jets and selling them to people who roll them down the hill at each other. Not the way to use the technology!"
   > — *The Book of Elon*
   Ask: if we ship our best work to this partner, what is the probability they roll it down a hill? If non-trivial, the partner is the wrong customer regardless of their size, brand, or check size.

5. If you are already trapped, plan the exit and reuse the lesson on the next bet.
   > "I felt like we had our wings clipped somewhat with Zip2. I wanted to avoid being constrained by our customers like that, and go direct-to-consumer. That's what motivated me to start PayPal."
   > — *The Book of Elon*
   Sell, spin out, or rebuild direct. The lesson is portable: at the next company, structure distribution so no incumbent can clip your wings.

6. Pick the next product specifically because direct-to-consumer is structurally possible.
   > "I wanted to build another internet company to show technology can be extremely effective when used properly."
   > — *The Book of Elon*
   Constrain your product choices to ones you can ship to end users yourself. Bandwidth, regulation, atoms, and incumbents are all reasons a market forces you through a middleman — weight that heavily in the idea-selection step, not after you have built.

## Common failure modes

- "We don't have a sales team, so we have to partner." Hiring a sales team is a solvable problem; ceding distribution to a bonehead is not.
- Treating a logo customer as validation. Knight Ridder, NYT, and Hearst all became investors and customers — and still would not deploy the tech properly.
- Accepting board seats or voting control from a customer-investor in exchange for distribution. Musk's exact warning: "They kept trying to push the company in directions that made no sense."
- Confusing "access to users" with "deployment to users." A partner who reaches millions but ships a degraded version of your product is a worse channel than reaching thousands directly at full power.
- Choosing a product whose distribution structurally requires legacy incumbents (regulators, OEMs, carriers) without first asking whether you can route around them.

## When NOT to use this skill

- The "partner" is genuinely the end consumer (e.g., you sell developer infra and the dev at BigCo is the user). Then BigCo is not a bonehead middleman — they are the consumer.
- Your technology is not actually great yet. If the tech is mid, distribution leverage from an incumbent may be the right trade; the F-22 metaphor only bites when you actually have an F-22.
- The market is structurally gated (regulated industries, defense, utilities) and no direct path exists. Use the skill to minimize incumbent control, not to pretend a direct path exists.
- You are deliberately using a partner as a short-term cash bridge with a planned exit (Musk did exactly this with the Compaq sale), and the partnership terms do not surrender governance.

## Source

The Book of Elon by Eric Jorgenson (2026, Scribe Media). Chapter: "Starting Zip2" (in "Becoming a Founder").