2
4 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 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.

  2. 1

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

  3. 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.

  4. 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.

Trending on Indie Hackers
Priorities for launching a SaaS solo, with no budget User Avatar 225 comments I built a tool directory that doesn't pretend every founder has the same needs User Avatar 51 comments AI helped me ship faster. Then I forgot what my product actually does. User Avatar 29 comments I built a browser-based photo geotagging tool. What should I lead with? User Avatar 7 comments How I Run a 1.7M Product Search Engine at 66ms on a $0 Hosting Budget User Avatar 6 comments AI Overviews: The Threat to Blogs and Reference Websites User Avatar 6 comments