I'm going to give you the real numbers, not the polished version.
TextSight took about 14 months to go from 0 to 1,000 users. The first 100 took 3 months. The next 900 took 11 months. The growth curve wasn't a hockey stick — it was a slow acceleration that required a lot of patience and, honestly, more than a few weeks where I wasn't sure it would work.
This is not a "how I grew my SaaS to 10k MRR in 30 days" post. Those posts exist. I don't trust most of them.
This is a post-mortem on what actually worked, what didn't, and what I'd do differently if I were starting from scratch today.
What I Had at Launch (Almost Nothing)
No audience. No email list. No Twitter following worth mentioning — around 200 followers, mostly other indie hackers who'd seen me building in public. No press relationships. No budget for ads. I was building out of India, which meant the usual "just get on podcasts" advice didn't map cleanly to my situation.
What I did have: a working product, a genuine belief that the problem was real, and about 6 months of runway if I didn't pay myself.
I launched a quiet beta in early 2024. No Product Hunt. No Hacker News Show HN. I just posted a thread on Twitter explaining what I'd built and why, and shared a link in two subreddits where I thought the target user might be.
First week: 23 signups. Most of them were other builders watching my build-in-public thread. Not my actual user.
The Channel That Got Me to 100: Reddit
Specifically, three subreddits: r/college, r/studentlife, and r/AIDetection.
I didn't spam links. I answered questions. When someone posted "I got flagged for AI but I didn't use AI, what do I do," I wrote a detailed, helpful answer — and at the end mentioned that TextSight shows you the specific phrases that trigger flags, if they wanted to check their writing before resubmitting.
About 40% of my first 100 users came from Reddit comments I wrote over a 6-week period. I probably wrote 80 to 100 comments total. Maybe 30 of those drove signups.
The thing that worked: I was actually trying to help people, not trying to acquire them. The comments that got upvoted and clicked through were the ones where I explained the false positive problem, validated what the person was experiencing, and gave them practical information. The ones where I mentioned TextSight as an afterthought — not a pitch.
The thing that didn't work: any comment that felt like an ad. Even subtly. People on Reddit can smell self-promotion in the first sentence. You lose them immediately.
What I'd do differently: start this earlier, when I was building the product. The feedback from those early Reddit conversations would have shaped the product faster.
The Channel That Got Me to 300: SEO Content
I started writing blog posts in month 3. Not "content marketing" in the strategy-deck sense. Just: write genuinely useful answers to questions people are actually searching.
The first post that ranked was something like "can turnitin detect chatgpt in 2024." It was 1,800 words, genuinely answered the question, and started ranking on page 2 within 6 weeks. It didn't drive huge traffic, but it proved the model.
From there I kept writing. One post per week on average, some weeks two. The goal was always: what does someone type into Google when they're experiencing the problem TextSight solves?
By month 6, I had roughly 14 posts live. Two of them were driving 60% of the organic traffic. The others were low-traffic but collectively meaningful. By month 9, those long-tail posts had compounded — several of them started ranking for related terms I hadn't targeted intentionally.
The content that consistently performed:
- Comparison posts ("ZeroGPT vs X")
- "Is this detector reliable?" type queries
- Specific use-case questions (students, freelancers, HR teams)
- Answer-focused posts that led with the answer and then expanded
The content that didn't perform:
- Generic thought leadership ("The Future of AI Writing")
- Posts optimized for keywords but thin on actual information
- Anything that tried to be too clever or editorial without giving the reader something practical
Lesson: SEO content works when it's genuinely answering a real question someone asked. When it's optimized for clicks rather than for the reader, the ranking doesn't hold.
Month 4 to 8: Twitter/X and Build-in-Public
I started posting more consistently on Twitter — once a day, sometimes twice. The format that worked: short observations from building, specific numbers when I had them, honest updates that included the bad weeks.
"Three weeks with no new signups. I think the problem is the onboarding flow. Testing two changes this week."
That kind of post got more engagement than anything polished. The indie hacker community on Twitter responds to honesty. They've seen too many "I hit $1k MRR in 30 days" posts to trust them. A founder saying "here's what's not working" feels rare.
What this channel did well: built a small but loyal audience who followed the journey and shared the product when they found it useful. Got me on two small podcasts (each drove maybe 15 to 30 signups). Connected me with other SaaS founders who gave product feedback I couldn't have gotten otherwise.
What it didn't do: drive significant volume. I probably got 120 to 150 users directly from Twitter over the 14-month period. Important, but not the core growth driver.
The harsh truth about Twitter/X for distribution: unless you already have an audience or go viral (which is hard to manufacture), it's a slow build. Worth doing for community and learning. Not a growth channel at early stage without a large following.
The First 100 vs. The Next 900
The first 100 users were almost all students. Specifically: international students and ESL students who had been flagged unfairly and wanted to understand their own writing. They found TextSight through Reddit, through early blog posts, through occasional word of mouth in student Facebook groups and WhatsApp chains I had no visibility into.
They converted to paid at a rate of about 12%. Low, but understandable — students are price-sensitive and the free tier (5 scans/day) was enough for their immediate problem.
The next 900 were more diverse. Freelance writers came in around month 5 as the freelancer-facing blog content started ranking. HR professionals came in around month 7, often through comparison posts that HR-adjacent people were searching. Content agencies started appearing around month 10.
The conversion rate improved as the user base diversified. Students convert at 10–14%. Freelancers convert at roughly 22–28%. HR professionals and agency users convert at 35–40%. The product is the same. The willingness to pay is different because the cost of not having reliable detection is higher for a professional than for a student.
This changed how I thought about content priorities. I still write for students — they're a large segment and high-volume users of the free tier, which matters for word-of-mouth and SEO signals. But the content that drives revenue is the professional-use content.
The $7.49 Pricing Decision
I'll be honest: the pricing was partly strategic and partly guesswork.
The strategic part: most comparable tools charge $9.99 to $19.99/month. Positioning below that range — but above the "this isn't serious" threshold of $4 to $5 — seemed right. I didn't want to compete purely on price, but I needed to be accessible to students and early-career freelancers.
The guesswork part: I picked $7.49 because it felt specific. $7.99 is a common price. $8 is round. $7.49 reads as carefully considered rather than arbitrary. I have no rigorous data proving this improves conversion. It might not. But my conversion rate on the pricing page has been stable at 7 to 9% since launch, which I consider acceptable for this category.
What I'd test if I were starting fresh: a $12.99/month plan with more features for professionals, alongside $7.49. The users who really need detection at volume — agencies, HR teams — would probably pay more. I haven't done this yet because I haven't wanted to split attention. That's on the roadmap.
Channels That Didn't Work
Product Hunt: I launched twice. The first time, I got 180 upvotes and a good day of traffic. It drove about 45 signups over two weeks. Most of the traffic was other product builders, not users of AI detection tools. The problem with Product Hunt for this category is the mismatch: the audience is makers, not the people who need AI detection. If you're building a developer tool, PH is perfect. If you're building for students and freelancers, you're in the wrong room.
Facebook Groups: I tried posting in content marketing groups and student groups on Facebook. Most groups have strict self-promotion rules, and the posts that didn't get removed got almost no engagement. One exception: a group for international students at UK universities — that drove 30 to 40 signups over a month. Highly specific community, real problem, worked.
Cold email: I sent 200 cold emails to content agencies. Got 4 responses. 1 signed up for a free trial. This probably wasn't the right approach — the email was too long and the value proposition needed to be communicated through the product, not through outreach.
Influencer outreach: I reached out to 12 education YouTubers. Got 2 responses, 0 partnerships. This was a long shot and I knew it. Still worth mentioning because a lot of early-stage founders overweight influencer as a channel before they have social proof.
What the Playbook Actually Looks Like
For any SaaS founder trying to grow without paid acquisition, here's what I'd tell you:
Find the 3 places where your users are already talking about your problem. Not talking about you — talking about the problem. Go there and be genuinely helpful. Don't sell. Answer questions. Establish that you understand the problem better than anyone else in the thread.
Write content that ranks for the specific questions your users type into Google. Not keywords — questions. "Can Turnitin detect ChatGPT" is a question. "AI detection tools" is a keyword. The question-based content ranks better and converts better because the intent is precise.
Show the work publicly. The indie hacker build-in-public community is small but valuable. They'll share your product if they trust you, and they trust you if you're honest. Include the bad weeks.
Know your conversion rate by segment. Not overall — by user type. If you don't know this, you can't prioritize content or features correctly.
Be patient for 6 months before you draw any conclusions. SEO compounds slowly. Reddit builds slowly. Word of mouth is invisible until it isn't. Most of the signals I had at month 3 were too noisy to be meaningful. The signal became clear by month 6 to 8.
What's Next
1,000 users isn't a large SaaS. It's proof that the problem is real and people will pay to solve it. The next chapter is about depth — improving the product enough that the free-to-paid conversion rate climbs, retention improves, and word-of-mouth accelerates.
I'm not planning to run ads until organic growth plateaus. That hasn't happened yet.
If you're building something similar — bootstrapped, solo or small team, no audience at launch — this playbook is the honest version of what works. It's slower than you want. It compounds in ways you can't fully track. But it produces users who actually need the product and stay.
That's the kind of growth worth building.
Related reading: