How to get your first 100 users for a web app

You get your first 100 users by talking to people with the problem, shipping a simple onboarding that shows value fast, and stacking 3–4 low-cost channels: communities, launch sites, targeted outreach, and useful content. Do it in short loops (daily or weekly), measure only activation and retention, and keep the scripts and follow-ups simple.

Key takeaways

• Start with 15–20 problem interviews to confirm pains and words your audience actually uses; build your landing and messages from their phrases.
• Stack channels: 1–2 communities, 1 launch day, 20–30 targeted cold emails, and 3–5 SEO pages can reliably compound to 100 users.
• Design onboarding to produce one “aha” action in the first session; use a 3-step checklist and a single welcome email with a short video.
• Make direct asks: end every call and post with one clear next step (try link, book call, invite a friend); follow up 2–3 times.
• Track a tiny funnel: visits → signups → first value → 7-day return; ignore vanity metrics until you hit 100 users.

A 10-day sprint to your first 100

• Day 1: Define your ideal customer profile (ICP) and the job they hired your app to do. Draft a one-sentence promise.
• Day 2–3: Run 10 problem interviews; record phrases and must-haves. Write your landing headline from real user words.
• Day 4: Ship onboarding: one “aha” checklist, empty states with sample data, and a welcome email.
• Day 5: Soft launch in two niche communities with a value-first post and a short demo.
• Day 6: Create three SEO-backed pages: a comparison page, a template/use-case page, and a “how to” guide.
• Day 7–8: Send 25 targeted cold emails and 25 LinkedIn DMs using the scripts below; book 5 demos.
• Day 9: Submit to 5–10 relevant directories and launch sites. Prepare a pinned comment and FAQs.
• Day 10: Review funnel metrics. Double down on the two channels that produced activations; schedule a weekly loop.

Nail the problem: ICP and promise

• ICP quick pass: industry, role, team size, urgency, budget authority, tool stack. Write this in 5 lines—not a persona novel.
• Job-to-be-done: “When I’m [situation], I want to [motivation], so I can [expected outcome].”
• Promise line formula: “[Outcome] in [time] without [big hassle].” Keep it honest and specific.

Example: “Publish a client-ready roadmap in 15 minutes without spreadsheet wrangling.”

Problem interview guide (20–30 minutes)

• Opener: “Walk me through the last time you tried to [task]. What kicked it off?”
• Digging: “What took the most time? What did you try before? What almost worked?”
• Friction: “Where did you copy-paste or use a workaround? What did you wish existed?”
• Money/value: “If this vanished tomorrow, what breaks? How do you measure success?”
• Close: “Want early access? I’ll send a 2-minute demo. Okay to circle back in a week?”

Recording sheet:

• Trigger words users say
• Tools used today
• Steps that feel heavy
• Constraints (security, approvals)
• Must-have vs nice-to-have

Solution discussion (only after patterns emerge)

• “Based on what you said about X and Y, would a tool that [specific] help?”
• “Which part would you try first? Anything missing for day-one value?”
• “If we shipped just A and B, would you try it next week?”

Ship onboarding that creates the “aha” fast

Target: A new user should do one meaningful action in 2–3 minutes.

• In-app 3-step checklist: “1) Connect data, 2) See result, 3) Share/Export.”
• Empty states with sample data: a single “Try with sample” button.
• One welcome email (plain text): who it’s for, 1-minute demo link, reply-to for help.
• A 60–90s Loom-style walkthrough: only the happy path; caption it.
• Success state with a share link and nudge: “Invite a teammate to unlock templates.”

Welcome email template (plain text):

Subject: Quick way to [outcome] in 2 minutes

Hey [First],

You mentioned [pain]—here’s the fastest way I know to fix it today:

1. Open your workspace: [link]
2. Click “Try with sample” to see [result] instantly
3. If helpful, import your file or invite one teammate

I read every reply—if you get stuck, hit reply and I’ll fix it.

– [Your name]

Activation checklist inside product:

• Default you into a space with 1 pre-filled example
• Bright CTA shows “Next: [clear action] (30 sec)”
• Track only: reached example → ran first action → shared/exported

Communities: show value before the link

Pick one or two communities where your ICP already hangs out. Contribute twice before you post your thing.

Where to look:

• Niche Slack/Discord groups frequented by your role or industry
• Subreddits for specific workflows
• Founder-maker spaces for build logs and feedback

Posting framework (value-first):

• Hook: a specific pain you solved (“I spent 6 hours reconciling… here’s the 10-minute fix.”)
• Give: write the steps or share a small template pack
• Soft CTA: “If you’d rather not build it, I put my tool here [link]. Happy to answer Qs.”

Comment strategy:

• Thank every reply within an hour on launch day
• Offer 1:1 help: “DM me your file; I’ll set it up”
• Pin a short FAQ to reduce repeats

Related deep dives: Where to launch your app in 2026: 17 places, ranked, Product Hunt alternatives: 12 other places to launch, and Build in public: a practical guide for first-time makers.

Launch sites: prepare, then engage

A good launch day can easily yield your first 50–100 signups if your page is clear and you engage.

Assets checklist:

• A crisp tagline and a 20–30 word pitch
• 3–5 benefit bullets with user words
• 1 short video (no sound needed) + 3 annotated images
• Maker story: why you built it and for whom
• Replies to 10 common objections as pre-written comments

Launch-day rhythm:

• First 2 hours: respond to every comment quickly and personally
• Midday: share two user quotes or a mini case
• Afternoon: post a how-to tip thread; invite questions
• End of day: honest recap; thank moderators and supporters

Post-launch follow-up:

• DM 10 commenters who asked good questions; offer a setup call
• Share a “what we shipped after feedback” update a week later
• Turn the most common question into a help doc or a template

Targeted cold outreach that users welcome

The goal is conversations, not clicks. Keep it short, personal, and tied to a recent trigger.

Finding prospects ethically:

• Search for visible signals: job titles in your ICP, posts complaining about your problem, recent tool migrations
• Use conference speaker lists, meetup pages, or public directories that match your niche
• Build a simple spreadsheet CRM: name, company, trigger, email/URL, last touch, status

Cold email template (50–70 words):

Subject: Quick question about [specific task]

Hi [First], noticed your team ships [X]. When [situation], do you still [inefficient step]?

I built a 2-minute way to [outcome] without [hassle]. Here’s a 45s demo (no gate): [link].

Worth a try this week? If not relevant, I’ll close the loop.

– [You]

Follow-up cadence:

• +2 days: “Should I close this?” short nudge
• +5 days: send a one-sentence tip or template they can use without your tool
• Stop after 3 touches unless they engage

LinkedIn DM opener (if they post about the pain):

“Loved your post on [topic]. We saw the same snag at [context]—here’s the 3-step checklist we use. Happy to share the template; if you want it pre-filled, I can drop it into our tool for you.”

Call booking script:

“10-minute setup call to get you from [current pain] to [first result] live on the call. If we can’t do it in 10, I’ll write the steps for you instead.”

Content that pulls in your exact users

Make content that solves a job in 10 minutes, not thought pieces. Start with three page types that map to search intent.

Page 1: Comparison (vs. status quo or well-known alternative)

• Target: people deciding today
• Structure: intro (use-case fit), table of differences, who should pick which, switch steps
• CTA: “Try with sample” and “Import your [thing]”

Page 2: Template or recipe

• Target: operators who want a ready-to-use artifact
• Structure: quick intro, downloadable template, 5-minute setup video, free view-only example
• CTA: “Use this template in the app”

Page 3: How-to guide with screenshots

• Target: people stuck on a specific step
• Structure: problem, prerequisites, 1–2 short paths, gotchas, copy-paste snippets
• CTA: “Do steps 1–3 in our tool in 2 minutes”

SEO basics without going deep into theory:

• Put the exact problem phrase from interviews in the H1 and first 100 words
• Link between pages using plain-language anchors
• Include last-updated date and a short FAQ per page
• Add your pages to a simple sitemap and request indexing

Further reading: SEO for indie apps: a beginner's playbook and How to write a landing page that converts.

Directories and listings that still work

Directories bring warm traffic when they’re curated and topical. Aim for 5–10 relevant submissions in week one, and refresh later with updates.

Submission checklist:

• Clear category fit and tags your ICP would browse
• 30–50 word description with the user outcome first
• 3 screenshots that show the “after” state
• Link to a template or sample project to lower the barrier

Places to consider:

• Niche industry directories and community-run tool lists
• Launch platforms and roundups oriented to your role
• App catalogs where buyers compare options by use case

If you want to appear where builders and buyers actually browse, list your app on Zivvi—our catalog includes every major web app and launches from indie teams. You can submit your listing at Zivvi.

To discover where your audience already goes, browse Categories, check Trending, and scan Popular. Use Search to find adjacent tools your users likely know—those names power your comparison pages and outreach hooks.

Build referrals into the first session

Referrals work when they’re immediate, specific, and low-friction.

In-product prompt (after first success):

• “Invite 1 teammate to unlock [useful perk]”
• “Share this view-only link with a client; they don’t need an account”

Milestone rewards that feel fair:

• Unlock a premium template after 1 invite
• Priority setup help after 3 invites
• Feature vote or office hours after 5 invites

Referral email you can send users to forward:

Subject: Thought this could save you 10 minutes today

Hey [Name], I used [app] to [outcome] in a couple minutes. Here’s a sample you can copy: [link].

If it helps, you can try it without signup here: [link].

Support that creates loyal early users

Offer human help fast. Early users value speed and care over polish.

• Put a “Chat with the maker” button inside the app
• Offer 15-minute setup calls during your first 100 users window
• Keep a simple help center with 5–7 pages for the top questions
• Send a 7-day check-in: “Did you get [promised outcome]? If not, I’ll do it for you.”

Reactivation nudge (plain text):

Subject: Still want [outcome]?

Quick check—do you still need [outcome]? If yes, reply with your [file/context] and I’ll set it up manually so you can see if this is worth your time.

Keep score with a tiny funnel

Decide what “user” means for you: signup or activated user (completed the “aha” action). For the first 100, count activated users.

Metrics to track (weekly):

• Visitors → signups → first action → share/export → 7-day return
• Activation rate = first action / signups
• Retention proxy = 7-day return / activated users

Channel view (just enough detail):

• Communities: posts, visits, signups, activations
• Launch: comments, visits, signups, activations
• Outreach: emails sent, replies, calls, activations
• Content: pages published, visits, signups, activations

Experiment log:

• Hypothesis, change, channel, metric moved, keep/kill decision
• One change per channel at a time for clean reads

Putting it together: three simple funnels

Option A: Community-led

• Two posts in targeted communities + steady replies
• Add a free template pack people can copy in 1 click
• Invite DM help; turn DMs into setup calls

Option B: Launch-led

• Prepare a punchy page and answers to top objections
• Engage live for a day; schedule 10 follow-up DMs
• Publish a “what we changed from feedback” post to reignite interest

Option C: Outreach + SEO

• Ship three pages (compare, template, how-to) using user words
• Send 50 personalized emails/DMs tied to visible triggers
• Use replies to refine pages; add FAQs and examples

Any two of these, executed for two weeks, can compound to 100 activated users when your onboarding is tight.

Scripts you can copy and adapt

Community post (value-first):

Title: The 10-minute way I stopped [pain]

I kept [undesired task]. Here’s the 3-step fix that got me to [result] fast:

1. [Step]
2. [Step]
3. [Step]

If you want a ready-made version, I wrapped it into a tiny tool. Free sample here: [link]. Happy to answer Qs or set it up for you.

Comment reply:

Thanks! If you share your [file/context], I can show the exact steps with your data. Takes ~5 minutes and no commitment.

Demo call opener (first 60 seconds):

“Goal for this call: get you from [problem] to [first result] before we hang up. I’ll screen-share for 3 minutes, then we’ll do it in your account. Sound good?”

Churn save (when a user stalls):

“Looks like you didn’t reach [first value] yet. Want me to do it for you and send a video? If it’s not useful, no need to keep the account.”

Checklists to keep you moving

Daily (30–60 minutes):

• Reply to every user message or comment
• Ship a micro-improvement to onboarding or a help doc
• Do 5 touches: one community value post/comment, one outreach follow-up, one DM help offer, one bug fix note, one gratitude note to a user

Weekly:

• 3 short customer calls or screen-share setups
• Publish one helpful page (compare/template/how-to)
• Submit/refresh one listing
• Review funnel metrics; pick one bottleneck to fix next week

Pre-launch page checklist:

• Promise line uses user words
• 3 benefits with proof or a screenshot
• Social proof (a quote or a tiny case)
• CTA for “Try with sample” and a book-a-setup link
• FAQ covering security, pricing label, import/export

Tooling that’s enough (and no more)

• Spreadsheet CRM for outreach and user notes
• Simple analytics that show first action and 7-day return
• Basic email tool with plain-text sequences for welcome and reactivation
• Video recorder for 60–90s explainers

You can get fancy later. For your first 100, speed of iteration beats tooling depth.

Methodology

Zivvi tracks a catalog of 2,300 web apps across categories, with each app’s worldwide traffic rank sourced from the Tranco list—a research-driven ranking that blends multiple traffic signals. When we reference rank movements, the 30-day change compares an app’s position roughly 30 days earlier to the latest snapshot. Ranks are worldwide traffic ranks (Tranco list) as of November 6, 2026. Zivvi does not accept paid placements in rankings or roundups; editorial picks are based on usefulness, clarity of value, and demonstrated traction signals.

Frequently asked questions

How long does it take to get the first 100 users?

If you stack two channels and run tight onboarding, many indie apps reach 100 activated users in 1–3 weeks. Your timeline depends on problem urgency and your ability to secure conversations quickly. Focus on activation over signups to avoid counting unengaged users.

What counts as a “user” for an early-stage app?

Count an activated user: someone who completes the core action that delivers value (your “aha” moment). Signups without activation can mislead your roadmap and morale. Define activation in one sentence and instrument it before you push for traffic.

Should I launch before doing customer interviews?

Talk to at least 10 people with the problem before a big launch. Early interviews give you the words, objections, and must-haves that make your landing and onboarding convert. You can still soft-launch in a community while you learn—as long as you lead with value and keep listening.

Do I need paid ads to get the first 100 users?

You don’t. Communities, launch sites, targeted outreach, and three high-intent content pages are usually enough. Paid ads can amplify later, but they’re expensive feedback if your onboarding and message aren’t dialed in yet.

What should my onboarding include for better activation?

Keep it to a 3-step checklist that produces one clear result in minutes. Use sample data, a short welcome email with a 1-minute video, and a visible success state that invites a teammate. Remove anything that doesn’t help a new user reach value on the first visit.

How do I avoid being spammy with cold outreach?

Tie every message to a visible trigger and a specific pain, keep it short, and offer value even if they don’t try your tool. Stop after 2–3 touches without response. If you wouldn’t send it to a friend in that role, rewrite it.

---

Ready to find your first users? Browse adjacent tools and categories your audience already trusts via Categories, see what’s Trending, or list your own app on Zivvi in minutes at Submit.