Scan time: 2-3 minutes / Read time: 3-5 minutes
Howdy rebel ideapreneurs 🦸♂️🦸♀️
🛗 The man who had his own rope cut
Elisha Otis, an inventor, stood on a platform in an open elevator shaft above a watching crowd.
He told a man with an axe to cut the rope holding him there.
This was 1854, at the Crystal Palace exhibition in New York.
The problem he was solving wasn't lifting.
Hoists already existed.
Everybody knew a rope could raise a platform.
What nobody would accept was a rope raising a person.
Ropes break, and a broken rope drops whoever is standing on the platform.
So people didn't trust elevators carrying a human, because they were scared the rope would break and they would fall.
Elisha had built a brake that gripped the guide rails on either side of the platform the instant the rope went slack.
The rope's job was to lift the platform, and that part already worked, every time.
The brake's job was to catch the platform on the one day the rope breaks, and nobody had ever seen that part actually happen.
He could have explained it.
He could have shown the drawings.
A drawing or an explanation only proves he understood the idea.
The only thing that would prove the brake actually worked was watching it stop a real fall.
So he rode the platform up in an open shaft, in front of a crowd, and had the rope cut.
The brake held.
He didn't fall.
Before that demonstration, elevators carried only goods, because nobody trusted a rope with a person's life.
That demonstration is why elevators started carrying people, and buildings could finally go taller than anyone could climb.
He didn't tell the crowd the brake would hold.
He had the rope cut while standing on the platform.
The crowd watched him drop a few inches, then watched the brake catch him.
⛳️ The problem
Elisha had the rope cut in front of a live crowd, instead of just telling people the brake worked.
But right now, we are four months into building our online course, and nobody outside our house has seen a minute of it.
We could show a rough version, but showing an unfinished thing feels like showing a lie.
So we keep building in private, until it is real.
Then we launch, and find out whether anybody wanted it, which is the moment we wish we had asked four months ago.
Elisha did not build a hundred elevators and hope, he let one crowd watch one platform fall and stop, and let them decide.
There is a three-minute trick that shows your future customers the finished experience before you build it.
Their reaction decides whether you build at all.
A founder did it with a three-minute video of software that did not exist yet.
His waiting list went from 5,000 to 75,000 overnight, so meet Drew.
📦 The product that was a video first
Drew Houston was building Dropbox, a software that didn't exist yet, and he made a three-minute video of it anyway.
The problem was hard to explain and harder to demo: Dropbox syncs files between machines.
Say that out loud and it sounds like nothing.
Worse, to show it working you need two computers, an internet connection, and someone patient enough to watch files appear.
The product also wasn't finished.
So he made the video instead.
A screencast showing what using Dropbox would feel like, with a file dropped in one computer and appearing in another.
He posted the video to Hacker News, a tech-industry forum.
Get this — the waiting list went from 5,000 to 75,000 overnight.
Not one of those people had used the product, because there wasn't much of a product to use.
Turns out 70,000 people signing up after watching a video was Drew's answer.
He didn't need a working product to find out whether anyone wanted Dropbox — he just needed people to see how it worked.
Dropbox got built.
Drew is now worth over $2 billion.
🔥 The recipe
➡️ The Preview
Elisha rode the platform up and had the rope cut in front of a crowd, and convinced them elevators were safe.
Drew made a video of Dropbox before Dropbox was built, and convinced 75,000 people to sign up.
What they both did has a name: The Preview.
Neither Elisha nor Drew was faking the demonstration.
Elisha's brake really worked, and Drew really did build Dropbox afterwards.
What was missing was proof — proof the brake would hold,
proof people wanted what Drew was building —
and watching is what created the proof
So you find out whether anybody wants your newsletter, course, or product while it's still cheap to change your mind.
Seventy-five thousand people joined the waiting list before Drew finished building it.
Let them watch the rope get cut.
That's it, my fellow outliers!
Yours 'helping you build profitable businesses 12x faster' Vijay Peduru 🦸♂️
🏄♀️ The prompt
The prompt below designs the preview of the thing you have not built, and the exact signal that means build it.
Save this prompt as a Skill or add to Project in your favorite AI tool — build once, use often.
Run it as is. Your AI sidekick will use your own files if it can see them, and the example values if it cannot.
CONTEXT:
- Use my own material first. If you can see my course outline, my lesson drafts, or my sales page, pull the real details from there instead of the examples below.
- If my Voice Profile exists, write in that voice. Otherwise, write in a clear, warm, no-jargon voice — first-person, plain words, no startup-speak.
- If my ICP / Audience doc exists, target that reader. Otherwise assume regulatory affairs specialists at small device companies.
- Anything I leave as an example, treat as real. Anything I delete, fill in from what you already know about me, and mark it as your assumption.
- The preview must be honest. It shows what the finished thing will do, and it never claims the thing already exists.
=============== INPUTS — edit these, or just run as is ===============
What I am planning to build, and how long it would take me to build properly:
{e.g. a paid course on writing regulatory documents for medical devices, three months of evenings, realistically five}
The single moment where somebody would think that is useful, and what I could show in ten minutes without building any of it:
{e.g. a rejected submission rewritten side by side until it passes, which I could show on one real example in a short video}
Where the people who would care already are:
{e.g. two LinkedIn groups and a regulatory affairs newsletter}
======================== END OF INPUTS ========================
Outputs:
1. The moment — the single thing to show, chosen because it carries the whole promise on its own.
2. The preview — exactly what to make this week, in the cheapest honest form, described shot by shot or line by line.
3. What I say — the words that go with it, making clear this does not exist yet and asking for the one signal I need.
4. The signal — the specific number or response that means build it, decided BEFORE I show anybody, so I cannot move the line afterwards.
5. What a no looks like — the response that means do not build it, and what I do instead.
Then tell me the day to publish the preview, and where.