That Friend Who Was Going to Win Over the VCs
You know the one. Pitch deck half built two years ago, still mentions it at parties, swears the VCs just haven’t heard about it yet. Here’s what’s actually been happening to his project this whole time, in five acts: his expectations, his nerve, his allergy to manual work, his need for applause, and the slow leaks nobody noticed until the boat was gone.
Act 1: He Wanted It Paid Off Yesterday
He priced his own time the way a loan shark prices debt: interest due immediately, in full, with a bonus for showing up early. He had, after all, deigned to spend his evenings on this, and a sacrifice of that magnitude surely deserved a prompt and generous return. Anything less felt less like a slow start and more like an insult.
1. He wanted the payoff before the thing had even finished loading
Durable things tend to take years, which is inconvenient information for someone who budgeted a few months. He gave it a reasonable runway, watched the number stay unreasonably flat, and concluded the years were simply never coming. That conclusion said far more about his deadline than about the idea underneath it.
2. One bad month and he called it a verdict
Revenue dipped one month, and he heard, quite clearly, a verdict: this doesn’t work, close the laptop, move on. In fact it was a snapshot of one month, nothing more, but he reached for the first available explanation and sprinted off with it before anyone could suggest a second look.
3. He kept comparing it to the easier win next door
Every time he weighed an hour on the project against an hour on something with a faster, clearer return, the project lost, because that comparison is rigged against anything patient by design. He ran the comparison more than he ran the project, and eventually there was no project left to compare anything to.
4. He never let it just be a hobby
Business or bust was the only setting on the dial, with nothing in between, no small reliable pleasure allowed to just be a small reliable pleasure. So when it quietly declined to become a business, he filed the whole thing under bust, when a more honest filing cabinet would have had a drawer marked simply: good way to spend a Tuesday evening.
Act 2: He Flinched at Small Audiences
He sized the whole thing for a stadium tour when what he actually had on his hands was a very good living-room act, the kind that plays beautifully to forty people who genuinely wanted to be there.
5. He dodged the niche because “not enough customers”
A superniche audience is small by construction, and smallness reads as danger to anyone running the numbers in advance, so he avoided it the way people avoid a dog they have not yet met. What he was avoiding was not actually a shortage of customers, which he never properly tested, but the fear of one, which he tested constantly and at great length.
6. He wouldn’t move without a guarantee
He would not lift a finger unless he was already fairly sure the finger-lifting led directly to a result, which ruled out almost everything worth trying, since very little that matters comes pre-certified. Certainty, as a rule, arrives after the work, not before it, and he kept waiting at the wrong end of that sequence.
7. He kept auditioning for an audience he didn’t need
He counted on maximum engagement and paying clients arriving almost immediately, because in his head the only legitimate outcome was broad, fast, obvious traction, measured against a market he never needed to win over in the first place. By that standard the project was always going to look like it was failing, because he was grading a quiet dinner party on the attendance of a stadium concert.
8. Not knowing yet felt like failing
Not knowing yet felt, to him, uncomfortably close to failing, so he kept demanding the answer before the next step rather than letting the next step produce the answer. A perfectly good project got shelved for the high crime of being honestly uncertain, which, it turns out, almost everything worth building is, right up until it suddenly isn’t.
Act 3: He Wanted It to Run Itself
He built it, admired it, and then tried to quietly leave the room, on the theory that a good project should run on autopilot the moment it is launched. The room, as it turned out, had been expecting him to stay.
Get Grandomastery’s stories in your inbox
Join Medium for free to get updates from this writer.
9. He wanted to matter less, not more, after launch
He wanted the project to need less and less of him once it launched, ideally approaching zero, which is a perfectly natural thing to want and a fairly reliable way to lose the one thing that made it good: him, actually showing up for it. Make yourself optional and, somewhat poetically, the payoff becomes optional along with you.
10. He handed the creative part to a tool anyone else could copy
A whole wave of AI-powered tools launched on precisely this theory, that delegation would let the founder step away for good, and a whole wave of them have since quietly shut down. Not because the underlying idea was foolish, but because whatever a model can generate, the next model generates too, at which point there is no moat, no founder in the loop, and nothing left to actually defend.
11. He treated his own hands-on work as a design flaw
Manual input had, in his mind, become faintly ridiculous, a sign of a process that should have been automated three steps ago. But when he himself was the product, as he often was, automating himself out of the workflow amounted to automating the product out of existence, a trade he never quite meant to make.
Act 4: He Kept Checking the Crowd
Things were going fine, genuinely fine, right up until someone at a party asked a single question, and in the time it took him to answer, fine quietly stopped being true.
12. “So when are the VCs signing?”
So, when are you going to actually make money off this, you’ve been doing it for years now, the asker said, with the easy confidence of someone who has never once had to build anything slowly. There was only ever one acceptable answer in the asker’s head, he did not have it on hand, and somewhere in the awkward pause he began to believe he never would.
13. The project’s bad month became his bad month
He fused his own worth to the project’s metrics somewhere along the way, without noticing the splice, so a slow week stopped reading as a slow week and started reading as a referendum on him personally, which is a much heavier thing to carry up a flight of stairs.
14. One skeptic outweighed years of his own conviction
One raised eyebrow from one respected person, and years of his own quiet conviction evaporated on the spot, as if the eyebrow had more evidence behind it than he did. His project, it turned out, was only ever as stable as the most doubtful person he happened to be listening to that particular week, which is a fragile foundation for anything meant to last.
15. A louder neighbor made him feel like he was losing
Someone else’s growth chart, posted somewhere he happened to be scrolling, was never actually his growth chart, and the two of them had never even been playing the same game by the same rules. None of that stopped it from stinging on a quiet Tuesday night, in the particular way that other people’s good news always manages to.
Act 5: The Slow Leaks
No single villain shows up for this part. Just five small, undramatic ways the thing went quietly flat while he was busy looking somewhere else.
16. He mistook the quiet part for the dead part
Good ideas tend to go quiet for a while before they go loud, which looks, from the inside, almost exactly like nothing happening at all. He quit right in the middle of the quiet part, which was, with excellent comic timing, the precise stretch where the next real development was already forming.
17. He widened it until the niche disappeared
He kept adding features, kept widening the scope, kept making it a little more like everything else, one reasonable addition at a time, until the thing that once had a specific identity looked suspiciously like a competitor to itself, which is an unusual way to lose, but a way to lose nonetheless.
18. He did it all alone and it wore him out
He carried the whole thing alone, with no one around to share the cognitive weight of it, and solitary burnout turned out to be a far more efficient killer than any downturn in the market ever managed to be.
19. He polished it until nobody ever saw it
He kept polishing it past the point of usefulness, delaying the one thing that would have actually told him what to fix, namely someone else’s unimpressed eyes on an unfinished version.
20. He’s still grading it on day-one goals
The goals he was still grading himself against were speculative guesses from year one, written by a version of him who knew considerably less, and he never once sat down to rewrite them. The project, by any reasonable current standard, was doing fine, and it kept failing a test that nobody had bothered to update in years.
