2
7 Comments

Three people signed up for my SaaS... and none uploaded a document.

Over the last few weeks, I noticed an interesting pattern while building DocMetrics.

Three different people signed up. Two were from the same company. None uploaded a document.

It's tempting to conclude my onboarding is broken, but I realized I don't actually know why they stopped.

They may have been evaluating the product, got distracted, didn't have a document ready, or hit onboarding friction.

Instead of guessing, I'm treating this as a hypothesis and planning to talk to more users before changing the product.

For those of you building B2B SaaS:

Have you seen users sign up but never complete the first meaningful action?

What turned out to be the real reason?

on July 24, 2026
  1. 1

    Machine Arena team here. Our equivalent of your upload is a spectator making a first prediction on a match, and the mistake that kept biting us in our own numbers was counting lookers as failed doers. Most people who arrive at a product this early never came to do the thing; treating all of them as onboarding casualties makes every funnel number look broken and points you at fixes for a problem you may not have.

    So beyond the interviews, which are right at n=3, one cheap structural move: label intent at the door. One harmless question at signup, roughly "do you have a document you want analyzed today, or just looking around", turns the next ten silent signups from anecdotes into labeled anecdotes. Lookers who then do nothing are behaving exactly as promised and tell you nothing about onboarding. An intender who stalls is a real signal, and that interview is worth ten cold ones because you already know what they came to do.

    It also compounds with the sample-document idea above, but for funnel reasons, not just trust ones: whoever still signs up after seeing the output on a sample is far more likely to be an intender, so the same drop-off number suddenly means something.

    And plus one on the two-from-one-company read: joint evaluation is its own cohort, and it usually resolves on the evaluators' timeline, not your onboarding's.

  2. 1

    the "two from one company" part might be signal, not just a footnote on the sample size. that reads like someone pulling a colleague in to eval together before either commits real data, a joint-decision pattern rather than a stuck-on-onboarding one. worth watching if that pairing shows up again in future signups

  3. 1

    Right call not to optimise off this yet, and worth being blunt about why: at three signups (two from one company, so really two accounts) there's no drop-off rate to read. Each of those is a case study, not a data point. Talk to them, like you said.

    The one structural thing I'd flag for a document tool specifically: making the first meaningful action "upload your document" is a trust chicken-and-egg. If the file is anything sensitive, people won't hand it over before they've seen the thing do something useful, and "sign up, now give us your real data" is a big ask on faith. That's why the sample-document path someone mentioned isn't just a diagnostic, it's probably the fix: let them see the output on your data before they risk theirs.

    When you do talk to them, the question that splits the causes cleanly is "did you actually have a document you were willing to upload right then" versus "you weren't sure what to do." Very different problems.

  4. 1

    Yes, I have seen this exact thing. The fastest diagnostic is to give them a sample document path on the first screen: “try it with our sample” next to “upload yours.” If people use the sample but not their own file, the issue is trust or readiness. If they ignore both, the issue is probably positioning before onboarding.

  5. 1

    I like that you're resisting the urge to optimize around a conclusion you haven't earned yet.

    What kind of evidence would actually convince you the problem is onboarding rather than something earlier in the decision to sign up?

    1. 1

      That's a great question.

      For me, it would take more than just seeing people drop off after signing up. I'd want evidence from conversations with users.

      If I consistently hear things like, "I wasn't sure what to do next," "I didn't understand what to upload," or "I expected to try it without uploading a document," I'd feel much more confident that it's an onboarding problem.

      On the other hand, if people tell me they were simply curious, didn't have a proposal ready, or were just evaluating tools, then the issue is probably earlier in the journey—or not really a product problem at all.

      At this stage, I'm trying to avoid optimizing based on assumptions and instead let user conversations point me to the real bottleneck.

      1. 1

        Appreciate the context.

        Would be good to continue the conversation as you learn more from those user conversations.

        What's the best email to reach you on?

Trending on Indie Hackers
I built an AI that turns an idea into a live business in under 10 minutes. Here’s what 1,000 launches taught me User Avatar 88 comments Building a startup costs $0. Your tooling budget costs $500K. Here's why. User Avatar 35 comments Building Noodle, a keyboard-first REST client for the terminal User Avatar 33 comments "Looks Good to Me" Is Quietly Killing Your Feedback Loop User Avatar 31 comments 787 tools for developers. 5 for nurses. Two weeks of tracking 14,000 indie launches. User Avatar 23 comments I didn't want to build another AI chatbot User Avatar 16 comments