I meet a version of this founder more often than you'd think: smart, capable, sitting on a genuinely good idea, still "just polishing a few things" before launch — for the second year running. Nothing's technically wrong. The logo isn't quite right yet. The website copy needs one more pass. The positioning will be finalized "once we've done a bit more research." Every individual delay sounds reasonable. Stacked together, they add up to a business that's been circling the runway for so long it's starting to forget why it wanted to fly in the first place.
I have a favorite cautionary tale for this exact pattern, and it's not from branding at all. It's from video games, and it might be the most expensive lesson in "waiting for perfect" that any industry has ever produced.
Fifteen years chasing a version that never arrived
Duke Nukem Forever was announced in 1997, on the strength of its predecessor's huge commercial and critical success. Expectations were sky-high, and the team had every reason to believe they were sitting on a guaranteed hit. Then the waiting began. The game switched engines multiple times as the team kept deciding the current version wasn't good enough yet. Release dates were announced and quietly abandoned, year after year. The original studio, 3D Realms, stayed small and self-funded, which meant nobody with real financial pressure was forcing a ship date — so the team kept chasing an ever-moving idea of "finished," restarting major chunks of work whenever a better version seemed possible.
By the time Duke Nukem Forever finally shipped in 2011 — fourteen years after it was announced, a length of development that earned it an actual Guinness World Record — the gaming landscape had moved on entirely. First-person shooters had evolved into more tactical, multiplayer-focused experiences. The humor and mechanics that would have felt fresh in the late '90s felt dated and out of step with what players now expected. The game that was supposed to be the definitive shooter of its generation released to largely negative reviews, and effectively ended the franchise it was meant to relaunch.
Here's the detail I think about most: nobody involved was lazy, or incompetent, or indifferent. By most accounts, the team kept chasing genuine improvements, real creative ambitions, better technology as it became available. The problem was never a lack of effort. It was that "not quite ready yet" became a permanent state instead of a temporary one, and the market didn't wait for them to feel ready.
Why "just a bit more polish" feels so reasonable in the moment
I understand the pull, because I've felt it myself. There's a real psychological comfort in "almost ready" — it lets you keep believing in the perfect version of the thing without ever having to find out how the real, imperfect version actually performs in the world. Launching is vulnerable. Waiting feels like diligence, even when it's functioning as avoidance.
I've come to believe, pretty firmly, that clarity comes from action, not from waiting for clarity to arrive first. You don't get the confidence to launch and then launch. You launch with what you actually have, and the confidence — along with the real information about what needs fixing — comes from what happens after. Waiting for the "right" moment, the fully resolved brand, the flawless version, is often just procrastination that's found a more respectable outfit to wear.
What actually gets lost while you wait
The cost of over-polishing isn't just time, though the fourteen years Duke Nukem Forever spent in development is a fairly dramatic illustration of that alone. It's relevance. Every year you spend perfecting a brand in private is a year the market keeps moving without you — competitors launch, categories shift, the exact cultural moment that would have made your original idea feel fresh quietly passes by while you're still adjusting a color palette nobody's seen yet.
A brand that launches at 80% and improves in public, in response to real feedback from real customers, will almost always outperform a brand that stays at 95% in private for years, waiting for a completeness that keeps redefining itself the closer you get. The market doesn't reward the most polished idea. It rewards the idea that showed up while it still mattered.
How to tell if you're actually polishing, or just avoiding
A few honest questions, if you recognize yourself in this at all:
Has your launch date moved more than once for reasons that weren't about the market, but about your own comfort with "not ready yet"? One legitimate delay is normal. A pattern of them is a tell.
Could you launch a genuinely useful, if imperfect, version today — and would that version actually embarrass you, or would it just not be the dream version yet? Those are very different problems. Only one of them is a real reason to wait.
If a strong competitor launched something similar next month, would your current pace get you there first, or would you still be "polishing" while they took the position you wanted? The market isn't waiting for your perfect version, the same way gaming didn't wait for Duke Nukem Forever's.
What I'd actually tell that founder
Ship the version that's genuinely useful now, even knowing it isn't finished — because it never fully will be, and the market's patience for "almost ready" is a lot shorter than yours. Fix the logo later. Refine the positioning with real customer feedback instead of more internal debate. The brand you build in public, adjusting as you go, will very likely end up stronger than the one you spent years perfecting in private, precisely because it got to exist in the real world long enough to actually learn something.
Fourteen years of waiting for "ready" produced a game the market had already moved past by the time it arrived. Don't let your brand do the same thing, one reasonable-sounding delay at a time.
If "almost ready" has quietly become your permanent state, let's fix that. Book a Brand Call → and get unstuck.