Most early-stage devtools founders think the hard part is getting to 100 signups. The hard part is getting to 100 paying users with retention curves that don't bleed. The first metric is a vanity number; the second is the entire business.
This is the week-by-week playbook for getting from zero to 100 paying users in 90 days. It works for products in the $50-$500/month range (which is where most early devtools land). It assumes you have a product that's at least functional, positioning that's at least defensible, and a founder who can write technical content. If any of those is missing, you're not in the 100-paying-users phase yet; you're in the get-to-the-starting-line phase.
Weeks -3 to -1: pre-launch
The three weeks before launch determine whether the launch is a moment or a sequence. Skipping this phase is the most common error.
Week -3. Lock positioning. Run the six-box canvas with your team in a 90-minute session. Rewrite the homepage in the new positioning. Have it reviewed by three senior engineers who aren't in your company. Update by Friday.
Week -2. Ship the quickstart. Five-minute path from landing page to first successful API call or command. Test it cold on three friends. Fix anything that takes longer than 30 seconds at any step. Write the FAQ for the top 10 questions the testers asked. Ship by Friday.
Week -1. Seed the channels. Identify the three channels you'll lean on at launch — typically one community (a subreddit, niche Slack, Lobsters), one large-audience moment (Hacker News, IndieHackers Show), one owned (your newsletter, your Twitter). For the community, you should already have 4-6 weeks of contributing activity behind you. If not, your launch will land harder elsewhere. For Hacker News, prep the 48-hour pre-launch checklist. For owned, draft the launch email/post.
Week 0: launch week
Launch on a Tuesday. The week is not "launch day + 4 quiet days." It's a sequence:
Monday. Soft launch. Email 30-50 people personally — friends, peers, past customers, anyone who's been waiting. The email is short and asks one thing: "I'm shipping Tuesday. If it's useful, would you reply with feedback?" These 30-50 people are your conversion engine for Tuesday's launch traffic — they'll show up, share, and seed the social proof.
Tuesday. Show HN at 6-9am PT. Owned-channel post (newsletter, LinkedIn) at 9am PT. Twitter/X thread at 10am PT. The order matters; HN first, owned second, social third. Each channel reinforces the others.
Wednesday. Engagement day. Reply to every comment everywhere. Answer every DM. Update the Show HN thread with a status comment ("48 hours in: X signups, Y feature requests, here's what's next"). The momentum compounds.
Thursday. Ship a small visible improvement based on launch feedback. Bug fix, feature, doc update — something. Post about it in the channels. This second wave produces nearly as much signup volume as launch day in many cases.
Friday. Personal follow-ups to the 30-50 you emailed Monday. Thank them for any signals (signups, comments, shares). Ask one specific question to each: what would they want this to do that it doesn't?
Expected signups for a competent week-zero launch: 200-2,000, depending on channel hits. Expected paying conversions in week 0: 0-15. Conversion follows activation, which follows usage, which takes time. Don't measure paid conversion in week 0; measure activation rate.
Weeks 1-4: activation
The first month after launch is about converting signups into activated users. "Activated" means: the user reached a first-success moment in the product. For your product, define this explicitly — first API call, first dashboard created, first command run. Track it.
The activation rate determines everything downstream. A 60%+ activation rate on signups is healthy. 40-60% is fixable. Under 40% is a quickstart problem, and you should pause everything and rewrite the onboarding.
Specific moves for weeks 1-4:
- Customer interviews. 5-10 calls with people who signed up but didn't activate. Ask what stopped them. The patterns will be brutal and useful. Fix the top 2-3 in product or docs.
- Activation email sequence. Three emails. Day 1: "welcome, here's the quickstart" with one specific call to action. Day 3: "stuck? Here are three things others get stuck on." Day 7: "still trying? Here's a 5-min Loom" or "Reply if you'd like to hop on a call."
- 1:1 community presence. If you have a Discord or Slack, the founder personally answers every question for the first 4 weeks. The relationships built here are your first 30 customers.
- Content cadence. One post per week, written by founder or CTO. Tied to specific things you learned from week-zero traffic. The content is what brings back traffic in weeks 4-12, when the launch spike has faded.
Weeks 5-8: conversion
By week 5 you should have activated users — people using the product successfully. Now the question is: which of them are willing to pay, at what tier, for what value?
The single highest-leverage move: personal upgrade conversations. For activated users on the free tier, the founder personally reaches out. Not a marketing email. A real DM or email: "Saw you've been using [Product] for two weeks — what's the use case? Anything I can help unblock?" This conversation, repeated 30-40 times, surfaces the actual reasons people would or wouldn't upgrade.
You'll hear three patterns:
- "It's working great for my side project but I haven't justified moving the team yet." → You need a champion's kit and a stronger Pro tier.
- "I'd pay but I need [feature X]." → If feature X comes up 4+ times, ship it. The feedback is the roadmap.
- "It works but I'm using it for free." → Either your free tier is too generous, or this user isn't your ICP. Either way, useful signal.
Expected paid conversions by end of week 8: 15-40. If you're under 10, you have an activation or value problem and you should slow down, fix it, and not push for more signups until conversion improves.
Weeks 9-12: scaling what works
By month 3, you should have data on which acquisition channel produces the best-converting customers. Almost always, it's not the channel that produced the most volume.
The exercise: for every paying customer, write down how they found you. Group by source. Calculate two things per group: total signups → paid (conversion rate), and average revenue per paying customer. The channel with the best combined score is what you double down on for the next quarter.
Patterns I've seen:
- HN drives huge volume, average conversion, mid-revenue customers. Good for awareness; not the long-term engine.
- Technical content (your own blog posts) drives slower volume, higher conversion, higher-revenue customers. Best long-term engine for most devtools.
- Founder personal outreach drives lowest volume, highest conversion, highest-revenue customers. Use it for enterprise and design partners.
- Reddit and niche communities drive moderate volume, very high retention. The long-term moat.
Build for the channel that wins your specific calculation, not the one your pattern-matching brain expects.
The 90-day red line
At day 90, ask one question: are paying customers still using the product daily? Not "did they pay" but "are they engaged, today, this week, after the initial enthusiasm wore off?"
If the answer is yes for >70% of paying customers — you have product-market fit. Spend the next quarter on growth.
If the answer is between 40-70% — you have something that works for some customers and not others. Spend the next quarter on customer interviews to figure out what segments retain, double down on that ICP, narrow your positioning.
If the answer is under 40% — you don't have PMF yet. Don't scale acquisition. The leakier the bucket, the more expensive each additional gallon you pour in. Spend the next quarter on product, not marketing.
This is the most important decision point in the first year. Founders consistently misread it because the launch metrics look great. Signups, MRR added, social mentions all look healthy. But if the people who paid you in week 4 aren't using the product in week 13, you don't have a business — you have an attention spike with a credit card form attached.
What 100 looks like
The companies that hit 100 paying users in 90 days usually share five things:
- A founder who's personally in every customer conversation for the first three months.
- A quickstart under five minutes, tested cold on real engineers.
- Three deeply-worked channels (one community, one launch, one owned), not eight shallow ones.
- A pricing structure that signals "this is a real tool for real teams," not a hobby SaaS.
- Weekly technical content from someone who can write code.
None of these is magic. All of them are work. The companies that ship them get to 100. The companies that don't, don't — and they tend to plateau at 20-40, then decay.
You can do all five. The question is whether you'll spend the three months doing them consistently, or whether you'll get distracted by tactics that feel like growth but aren't.
Open a doc. Write today's date. Below it, write the next 13 weeks as a calendar. For each, write one specific outcome (e.g., "Week -2: quickstart shipped, tested on 3 cold engineers"). Put it in front of your team. The plan exists or it doesn't, and the absence of a plan is the absence of a result.
The full launch checklist, week by week.
The 0-to-100 Paying Users Launch Checklist chapter ships the complete week-by-week plan from -3 weeks pre-launch through month 3 — with the activation funnel design, the upgrade conversation scripts, the channel scoring rubric, and the 90-day red line decision tree.
Get the toolkit → $97Ten years of developer marketing — Vaticle, MinIO, Pusher, Pluralsight. I write about GTM for devtools founders who run it themselves. Want me to run this on your company for a week?