2
4 Comments

0 real signups in 29 days — killing FacelessFlow (the post-mortem)

I pre-committed to kill thresholds on Jul 21 so I couldn't move the goalposts: 50+ emails by Aug 9 → build the MVP, 15–49 → iterate, under 15 → kill it and publish the post-mortem.

Final count: 0 real signups. (1 email total, and it was my own test entry.)

So: kill it. Here's the post-mortem.

The idea: FacelessFlow — niche/format discovery + flat-fee rendering + official-API publishing for faceless-video creators. Landing page first, product second.

What I did:

  • An X post every 2 days (automated), each one a single insight from a research drop
  • Value-first posts in YouTube-growth subreddits (new account, so karma-building came first)
  • A real lead magnet: 10 video formats from small channels that beat their sub count 5:1+ and their own median views 3x+, screened against live YouTube data

What I got wrong:

  • Launching the page is not distribution. It sat untouched for the first week — the actual push didn't start until Jul 18, which left less than three weeks before the deadline. Not enough runway for any channel to compound.
  • I never got real signal on whether the pitch itself lands, because traffic was too thin to tell "bad pitch" from "no one saw it."

What's next: no MVP, no iteration on this pitch. If I come back to faceless-video tooling, distribution goes first next time, not last.

Page (up for now, may come down): https://facelessflow-self.vercel.app

Thanks to everyone who gave feedback on the original page-copy post — genuinely useful even though the numbers didn't move.

on August 9, 2026
  1. 1

    The thing I'd change next time is the shape of the threshold rather than the number. "50 emails by Aug 9" bundles reach and conversion into one figure, and those two fail for completely different reasons, so a zero can't tell you which one broke.

    A floor underneath it separates them. Something like: 300 unique visitors on the page, and 5% of them converting. Miss the traffic floor and the experiment simply didn't run, so the honest verdict is "distribution failed" rather than "the offer failed". Hit the floor with 1% converting and you've genuinely tested the pitch. Same discipline, but now both outcomes are decidable.

    The other thing worth instrumenting is the step before the page, because that's almost certainly where this one died. Impressions and outbound clicks counted per channel would have told you in week one that nothing was arriving, while there was still time to change something. Signups is a lagging measure of about five stacked things, so it's the one number you can't debug from.

    One detail in your write-up is quietly good news: the single email was your own test, which means the form and the delivery path both work. That rules out the most annoying class of silent failure and narrows this to reach.

  2. 2

    This is a hard post to write but an important one — thanks for sharing honestly.

    The demand validation step is where most of us skip too fast. I made a similar mistake before and learned to check HN, GitHub, and Reddit for real complaints before writing any code.

    What signals did you have that people actually wanted this before you built it?

  3. 1

    The part about not knowing whether the pitch was bad or simply unseen is probably the most useful takeaway here. Zero signups feels like a clear result, but with almost no traffic it really isn't enough evidence to diagnose the offer itself. The kill threshold still makes sense though — sometimes the disciplined decision is to stop before spending another month trying to manufacture signal.

  4. 1

    The pre-committed kill threshold is the most disciplined thing I've seen a founder do. Most people move the goalposts. The lesson about distribution going first is one most founders only learn after killing something — respect for publishing it honestly.

Trending on Indie Hackers
I Just Discovered My Analytics Numbers Are Mostly Fake. Here Is Why. User Avatar 99 comments Co-founders suck… User Avatar 82 comments I built an AI that finds the right product for your customers User Avatar 43 comments Solo-built Pistly for months. Launching on PH this week and I still don't know if the market wants it. User Avatar 35 comments I built a tool to find people already talking about problems your product solves User Avatar 34 comments The easiest version of generation history was probably the least useful one User Avatar 32 comments