4
19 Comments

Healthy Signups, Zero Activation

A Product-Market Fit lesson for SaaS founders

I recently reviewed a SaaS product that looked healthier than it really was.

Traffic was coming in.

People were signing up.

The category had real market interest.

On the surface, that feels like progress. If you are an early-stage founder, it is easy to look at those numbers and think: "The market wants this. We just need to improve the onboarding."

But there was one problem:

Almost nobody was reaching the first meaningful value moment inside the product.

That changed the diagnosis completely.

Traffic validated awareness.

Signups validated interest.

Activation was supposed to validate value.

And activation was effectively zero.

The first assumption was onboarding

Near-zero activation naturally points to onboarding.

That was my first instinct too.

When we looked closer, the onboarding flow had obvious friction:

  • too many steps before first value
  • too many concepts introduced too early
  • one onboarding path for every user type
  • no segmentation based on skill level or intent
  • no fast path for users with a clear automation goal
  • no simple route from signup to first meaningful outcome

So yes, onboarding needed work.

But the deeper issue was not just screen-level friction.

The real question became:

Was the product attracting users who could realistically reach value through the current product path?

That is a different question from "is onboarding confusing?"

Support tickets were more useful than the funnel

The analytics showed where users stopped.

Session recordings showed hesitation.

But support tickets explained why.

The pattern was clear: many users wanted automation outcomes. They wanted speed, clarity, and execution.

But the product required setup, strategy creation, and product-specific learning before the payoff happened.

That created an expectation gap.

The promise sounded fast.

The product path felt slow.

The users were not all failing for the same reason either. Two segments were getting mixed together.

The product was serving two different ICPs

The first segment was beginners.

They represented a larger market, but they needed a lot before they could succeed:

  • education before usage
  • guided setup
  • examples and templates
  • concept explanations
  • decision support
  • confidence-building moments

The second segment was automation seekers.

They were narrower, but the path to value looked simpler:

  • clearer intent
  • lower education requirement
  • faster setup need
  • more obvious success criteria
  • shorter time-to-value

That led to the key product-market fit lesson:

The best first ICP is not always the largest possible market.

Sometimes the best first ICP is the segment with the shortest credible path to value.

The recommendation was not "fix onboarding"

A cleaner onboarding flow would help.

Better copy would help.

Fewer steps would help.

But if the wrong segments keep entering the same product path, onboarding improvements can only do so much.

The recommendation became an ICP narrowing experiment.

Not a permanent pivot.

Not abandoning the larger market.

Just a cleaner experiment:

  1. Pick the segment with the fastest path to value.
  2. Rewrite the promise for that segment.
  3. Simplify onboarding around one first-value action.
  4. Remove concepts that do not matter before activation.
  5. Measure whether more signups reach the value moment.

Narrowing the ICP reduces variables.

Messaging gets sharper.

Onboarding gets simpler.

Support content gets more focused.

Product priorities get clearer.

Activation data becomes easier to interpret.

The lesson I took from this

A signup is not product-market fit.

A signup means the promise was interesting enough to create action.

But it does not prove that the user understands the product.

It does not prove that the user can reach value.

It does not prove that the product can create repeatable success.

For this product, healthy signup volume created optimism.

Zero activation created clarity.

The strongest takeaway:

Low activation can expose a product-market fit problem hiding behind what looks like an onboarding problem.

So before buying more traffic, rewriting the landing page, or polishing onboarding screens, I would ask:

  • What is the first meaningful value moment?
  • Are signups reaching it?
  • Which segment reaches it fastest?
  • Which segment needs too much education before value?
  • What do support tickets reveal about expectations?
  • Would a narrower ICP make the product easier to activate?

Strong interest creates momentum.

First value creates evidence.

Without activation, product-market fit is still a hypothesis.

Question to all founders

For founders who have seen healthy signups but weak activation:

Did you fix it by improving onboarding, narrowing the ICP, changing the product promise, or something else?

on June 24, 2026
  1. 1

    The frame of 'shortest credible path to value' is the cleanest way I've seen this kind of trap renamed — most founders genuinely do read flat activation as 'we need better onboarding copy' and never get around to asking whether the people walking in were ever the right walkers. The piece I'd love to hear you push on: when you narrow ICP for an experiment like this, you implicitly throw away whatever early signal the other segments were giving — including segments that might activate fine with a slightly different product. How do you decide that cost is worth paying, especially early on when the dataset on any one segment is tiny? Is there a way you've found to keep the narrowing reversible without diluting the experiment itself?

  2. 1

    The 'shortest credible path to value' frame is the right one. But finding that segment is harder than it sounds.

    When we did this, the highest-intent segment wasn't who we expected. We assumed power users would activate fastest. Actually it was the beginners who had ONE specific job they wanted done — not the ones who wanted to learn the whole system.

    Support tickets told us more than analytics ever did. Users would say 'I just want to do X' but our onboarding taught them about Y, Z, and A first.

    The shortest path to value often means ignoring 80% of what your product can do and getting someone to ONE outcome as fast as possible. Everything else comes after activation.

  3. 1

    Same problem here. What worked for me was sending a single email 10 minutes after signup with one concrete action: "run this curl command and see live data." The people who did that converted. The ones who didn't, churned. Onboarding is really just getting someone to their first "aha" as fast as possible.

  4. 1

    This really resonated with where I'm at.

    I recently had around 27 visitors to Ashive, but almost all of them bounced before reaching what I'd consider the first meaningful value.

    My first instinct was to keep improving the onboarding, but I'm starting to wonder if I don't even have enough signal yet to know whether it's an onboarding problem, an ICP problem, or simply not enough conversations with real founders.

    Still trying to figure out how to get enough honest users before optimizing the wrong thing.

  5. 1

    The useful distinction here is “screen activation” vs “workflow activation”.

    A user can finish onboarding and still not reach value if the product has not helped them complete the job they came for.

    I like the ICP narrowing idea because it forces one sharper question: which segment can reach the first real outcome with the least explanation?

    That makes activation data cleaner. Otherwise every onboarding test mixes together product friction, wrong audience, weak intent, and expectation mismatch.

  6. 1

    This feels like one of the most common SaaS problems.

    Did you eventually figure out whether it was an onboarding issue, an expectation mismatch, or something else entirely?

    1. 1

      Actually, it was more of an ICP issue; however the onboarding is still the issue and needs to be fixed asap. :)

      1. 1

        That's actually encouraging to hear.
        I think a lot of founders jump straight into rebuilding the product when the real issue is simply getting the right people through the door first. If the ICP isn't right, it's almost impossible to know whether onboarding is actually broken or just being tested by the wrong audience.Now that you've narrowed the ICP, I'm curious whether the onboarding issues look different than they did before, or if they've stayed pretty much the same.

  7. 1

    The expectation gap feels like the key here. If the promise attracts users looking for a fast automation outcome, but the product first asks them to learn strategy and setup, even a cleaner onboarding flow may not fix activation.

    I like the idea of narrowing the ICP as a diagnostic tool, not a permanent positioning decision. It reduces enough variables to show whether the real issue is friction, audience fit, or the product path itself.

    1. 1

      Correct. I decided to go that path to really reduce the risk and validate the newly focused ICPs.

  8. 1

    This is exactly my situation too. Signups but
    no activation. Have you tried onboarding
    emails or in-app guides?

    1. 1

      I have ton of user support requests to know for sure that there are other issues than just onboarding flow. Breaking the flow into 2 parts is a simple yet effective solution for my client.

      1. 1

        I am open to discussion if you need to brainstorm ideas. It can be icp, messaging as well.

  9. 1

    One thing that helped me think about this: define the activation event as the first real workflow completed, not the first screen completed. For a consumer app I’d also split “curious signup” from “came here with a job to do” before touching onboarding, because those two users need totally different first sessions.

    1. 1

      Usually activation events should be picked after looking at correlation between retention and the action that gives the highest level of retention aka best use case. In my case, I have to push users to activate first before I can view retention data. It is usually more than one factors. I use my framework to really diagnose the situation: https://product-led-growth.com/saas-growth-diagnosis

  10. 1

    Interesting writeup.

    The part that always trips me up is that onboarding fixes and ICP fixes can produce the exact same result.

    Activation goes up either way.

    Figuring out which one actually caused the improvement is where things get interesting.

    1. 1

      To be honest , as an advisor I start by looking at fundamentals like ICP, key use case ( North Star ) . It can be onboarding that contributes the growth bottleneck; however I do start by looking from bottom to top.
      What you are describing is true for products with product market fit. Onboarding will help only if you are attracting the right audience. Without that, onboarding will yield no results. I am open to discussion. Looking forward.

      1. 1

        That's exactly why I commented.

        The same activation improvement can justify very different conclusions depending on what you believe caused it.

        Happy to share the fuller thought if it's useful.

        What's the best email to reach you on?

        1. 1

          would you mind sending me a request here ? I am interested in knowing how you approach this as well. We will be able to learn from each other. https://product-led-growth.com/contact-product-led-growth-consulting-services

Trending on Indie Hackers
Priorities for launching a SaaS solo, with no budget User Avatar 237 comments I built a tool directory that doesn't pretend every founder has the same needs User Avatar 57 comments AI helped me ship faster. Then I forgot what my product actually does. User Avatar 34 comments Most early-stage SaaS companies miss churn signals — here’s how to catch them early User Avatar 22 comments I thought picking a voice for my app would take a day. It rebuilt everything. User Avatar 16 comments Drop your landing page URL. I'll use Ferguson to tell you why visitors might be leaving User Avatar 13 comments