Building & Strategy
Stop Over‑Showing Your Product
Osborne Computer talked up better machines before it could ship them, and buyers simply stopped ordering the one it could.
2026-09-181 min read
Showing prospects everything you plan to build feels like selling ambition. What it actually does is move the buyer's attention from the product in front of them to a better one that does not exist yet. Two things follow. Buyers who like the future version wait for it, and buyers who sign expect the demo rather than the shipping product, so every missing screen reads as a broken promise.
The textbook case is Osborne Computer. Its Osborne 1, launched in 1981, was one of the first commercially successful portable computers. When Adam Osborne began promoting more advanced successor models well before they were ready, dealers and customers held off on the current machine, sales fell while the new ones were still unfinished, and the company filed for bankruptcy in 1983. Historians still argue about how much of the collapse that announcement caused, since cheaper rivals such as Kaypro and the company's own cash troubles also mattered. The pattern earned a name anyway: the Osborne effect.
Software startups rebuild the same trap in miniature. A demo walks a prospect through analytics, integrations, and an assistant that are still on the roadmap, the prospect signs expecting all of it, and the account team spends the next year apologizing for dates. The durable version of the pitch shows what ships today, names one next capability, and lets the product earn the rest.
Key insights
Promoting a better future product can freeze sales of the current one, a pattern named after Osborne Computer.
Customers anchor on what the demo showed, so unshipped features become broken promises rather than exciting upgrades.
Show what ships today plus one clearly labeled next step.
Why it matters
A roadmap shown too early can stall today's revenue, because interested buyers rationally wait for the version you described.
Features demoed but not shipped turn into obligations that pull engineering toward what sales promised instead of what customers actually use.
Use this tomorrow
1Open your current demo or pitch deck, mark every screen showing something not yet generally available, and remove all but one of them.
2Ask your two most recent new customers which feature they expected at signing that they still do not have, and add each answer to the next sales-team meeting agenda.
Go deeper
The Osborne effect is now standard vocabulary in hardware and product strategy, and it is a big part of why many companies keep successors quiet until they are close to shipping. The risk is highest when the new version is an obvious upgrade and the purchase is easy to postpone. It is weaker when the current product solves an urgent problem, because the cost of waiting outweighs the appeal of the better model. That makes urgency, not secrecy alone, the real protection.
There is a legitimate counter-case: enterprise buyers often want roadmap visibility before committing to a platform they will depend on for years. The distinction that matters is between direction and promises. Describing the problems you are investing in builds confidence, while demoing specific unshipped screens creates commitments your team may not meet on the implied timeline. Many companies handle this with a clearly labeled roadmap conversation kept separate from the product demo.
