1
3 Comments

Most users don’t churn — they just never finish

I might be wrong here, but…

I’ve been thinking about this a lot recently, and I’m not fully sure I’ve got it right yet…

But I think a lot of what we call “retention problems” are actually something else.

Completion problems.

Most products today are really good at:

getting users in
giving them access
showing them what to do

But not necessarily getting them to finish.

And when users don’t finish, everything downstream looks like:

churn
low retention
weak engagement

But those are just outputs.

The real question is:

Did the user actually complete the thing that creates the result?

I started noticing this more with workbooks and course material.

People download PDFs.
They open them once.
Maybe they start…

But very few actually complete them.

And as a creator, you don’t really see that happening.

You just assume:

maybe they weren’t motivated
maybe the content wasn’t strong enough

But I’m starting to think the issue is more structural than that.

The experience itself creates friction.

The biggest drop-off seems to happen between:

download → done

That gap is where everything breaks.

I’ve been building something around this idea called Formely.

Formely turns static PDFs into hosted, fillable workbooks and tracks completion so you can see where users drop off.

Not just:
“did they open it?”

But:

how far did they get
where did they stop
what actually got completed

What’s been interesting is how much this changes how you think about content.

Instead of asking:
“Was this good?”

You start asking:
“Did they finish it?”

I’m starting to think we’re missing a layer in most products.

Something closer to:

completion tracking
behavioural visibility
outcome-based feedback loops

Almost like an infrastructure layer, not just a feature.

Curious if anyone else has been thinking about this?

Or if you’ve seen similar drop-off patterns in your own products.

Feels like there’s something here, but still figuring out how far it goes.

on March 25, 2026
  1. 1

    Most users don’t churn.

    They fade out before the product becomes true for them.

    Access → exposure
    Completion → belief
    Belief → return

    If the first outcome never gets completed, “retention” is often just the metric-name we give to a broken crossing.

  2. 1

    This hits close to home, I'm building a travel app
    and the hardest thing isn't getting people to sign up,
    it's getting them to try the core feature (camera scan)
    even once.

    What I've found is that users who try the main feature in the
    first session almost always come back. Users who don't
    try it in the first session almost never do.

    The whole onboarding question for me became, how do I
    get someone to point their camera at something Japanese
    within the first 2 minutes? Everything else is secondary.

    Still figuring it out but your framing of "never finish"
    vs "churn" is exactly the right way to think about it.

  3. 1

    The more I dig into this, the more it feels like we’ve optimised everything around access…

    but not around follow-through.

    And that gap compounds over time.

Trending on Indie Hackers
I shipped 3 features this weekend based entirely on community feedback. Here's what I built and why. User Avatar 119 comments $36K in 7 days: Why distribution beats product (early on) User Avatar 117 comments I've been reading 50 indie builder posts a day for the past month. Here's the pattern nobody talks about. User Avatar 112 comments Finally reached 100 users in just 12 days 🚀 User Avatar 107 comments We made Android 10x faster. Now, we’re doing it for the Web. 🚀 User Avatar 71 comments I realized showing problems isn’t enough — so I built this User Avatar 32 comments