Month 2, No Audience, 0 Users: Find Your First SaaS Prospects

When every startup post says “build in public" and “talk to users", it sounds useful - until you’re staring at month two with no audience, no users, and, as one founder put it, “14 things on fire". The advice isn’t wrong. It’s just incomplete. Because it skips the part you actually need: where the first conversations come from when nobody knows you exist.

One early-stage builder summed up the gap perfectly: “Most SaaS growth advice is technically correct" but it’s “just written for someone slightly ahead of you". That’s the problem with generic playbooks: they assume you already have distribution, or at least a trickle of users to interview.

This article is about a different starting point: finding people who are already describing the problem your SaaS solves - today - on Reddit, X, and LinkedIn - then using those conversations to get your first prospects, your first demos, and your first “oh wow, I need this" moments.

Why “build in public" feels useless in month 2

The internet’s standard advice cluster shows up in almost every thread:

• build in public
• talk to your users
• nail your ICP

It’s so common that one founder repeated it verbatim - “build in public"; “talk to your users"; “nail your ICP" - and then followed with the part that matters: “All true. all useless on month 2 with no audience and 14 things on fire". (From a lead conversation surfaced in the context you provided.)

What’s happening here isn’t laziness. It’s math.

If you have:

• 0 followers
• 0 customers
• 0 inbound

…then “build in public" is a long-horizon strategy. It might work over 6–12 months. But you need signal this week.

And “talk to your users" breaks entirely when you have none.

So the month-two job becomes:

1. Find strangers who already have the pain
2. Talk to them without sounding like a vendor
3. Use what you learn to tighten ICP + messaging
4. Repeat until the product and the pitch click

The fastest path to your first prospects: start from pain conversations

Early traction usually doesn’t come from “going viral". It comes from being present in the right place at the right time.

A different founder described the opposite experience - doing all the “right" research, then hitting the wall anyway: “I looked at the market, read Reddit feedback, stared at my dashboard: 0 users". They added: “I just gave up on my first app". (Another lead conversation in your context.)

That’s the failure mode when your research stays academic.

Reading Reddit feedback is not the same as:

• finding current threads where someone is asking for help
• seeing what they’ve already tried
• understanding what they refuse to do (objections)
• engaging with a response that fits the tone of that community

Your first prospects are rarely “out there searching for your product name". They’re searching for a way out of a problem.

That’s why social platforms are disproportionately powerful early:

• People describe their problems in their own words.
• They mention what they’ve tried.
• They name competitors.
• They reveal buying triggers (cost, time, team constraints).

The trick is not “search more". It’s search better.

A practical 7-day plan for finding your first SaaS prospects

If you’re in month 2 and you need traction fast, here’s a plan that forces contact with reality.

Day 1: Write a one-sentence “problem you fix" statement

Not features. Not “AI-powered". Just the before/after.

Bad: “Automated workflows for modern teams".

Good: “Turns messy customer requests into a prioritized queue so you stop missing follow-ups".

You need this sentence because it becomes your filter for what counts as a real lead conversation.

Day 2: Define 2–3 “pain phrases" people would actually say

Your buyers won’t say “need a workflow tool". They’ll say things like:

• “I keep losing track of…"
• “Is there a tool that…"
• “What’s the best way to…"
• “I tried X and it didn’t…"

Pull phrases from:

• competitor reviews
• Reddit posts in adjacent subreddits
• your own past experiences

Day 3: Find 20 conversations across Reddit, X, and LinkedIn

Do this manually once so you learn what you’re looking for.

Reddit: search within relevant subreddits using pain phrases and “alternatives" queries.

X: search for complaints + “anyone know" + “recommendations".

LinkedIn: look for “rants" and “lessons learned" posts from your target role.

Your goal is not volume. It’s a shortlist of conversations where:

• the problem is explicit
• the person is experiencing it now
• there’s enough context to respond meaningfully

Day 4: Craft two non-spammy response templates

Objection you’ll feel immediately: “If I reply, I’ll sound promotional". That’s valid - especially in Reddit.

Use a structure like:

1) Mirror their situation (prove you read it)
2) Ask one clarifying question
3) Offer a small tactical tip
4) Only then mention your tool as optional

Example:

• “It sounds like the issue isn’t X, it’s that Y happens after Z. When you tried [thing], what broke first?"
• “One quick workaround: [tactic]. If you want, I’m building [product] for exactly this - happy to share a 2-min loom".

You’re not closing on the spot. You’re opening a door.

Day 5: Do 10 engagements + 10 DMs (only where appropriate)

Rules:

• On Reddit, comment first. Don’t jump to DMs unless invited.
• On X, you can reply publicly, then ask if they’re open to a DM.
• On LinkedIn, you can comment thoughtfully, then connect with a short note.

Track outcomes in a simple sheet:

• conversation link
• pain phrase
• role
• response sent
• reply? (Y/N)
• follow-up date

Day 6: Run 5 “problem interviews" (even without users)

These are not product demos.

Script:

• “What are you trying to achieve?"
• “What’s the current workaround?"
• “What’s frustrating about it?"
• “What would a ‘good’ solution look like?"
• “What would stop you from switching?"

This last question is where pricing, trust, and switching-cost objections appear.

Day 7: Tighten your ICP and redo your homepage hero

After 5 interviews, you’ll have:

• exact phrases to put on your page
• a clearer “for who"
• competitor names and why people chose them
• objections you can proactively answer

Then repeat the loop weekly.

The real bottleneck: finding those conversations consistently

Doing the manual version once is important. But doing it every day is where founders burn out.

Scrolling Reddit, X, and LinkedIn for hours becomes its own unpaid job. And it comes with noise:

• bots and spam
• “growth advice" threads with no buying intent
• AI-generated fluff

This is where a tool like Achiv.com fits naturally into an early-stage motion - without replacing your voice.

Achiv.com’s promise is simple: Wake up to a curated list of people who need what you sell - daily, from Reddit, X, and LinkedIn.

Instead of setting up fragile keyword alerts that catch everything (including junk), you paste your URL and Achiv.com reads your positioning, builds an ICP, and monitors all three platforms. Each morning you get a curated kanban board of conversations that look like real demand.

The helpful part for month-two founders isn’t just “more leads". It’s reducing two kinds of waste:

1) Time waste: doom-scrolling for one good thread
2) Context waste: finding a thread but not knowing what to say

Achiv.com includes extracted pain points, detected objections, and competitor context with each lead - so you can respond like a human who understands the situation, not a vendor blasting a template.

“Do I really need a lead tool this early?" (A valid objection)

A common objection in founder circles is: “I shouldn’t buy tools; I should just do manual outreach or content".

That skepticism is healthy. In the customer insights you provided, many people simply don’t feel “in-market" for lead tools, or they prefer manual/content-led methods.

Here’s a grounded way to decide:

• If you can reliably find 10 relevant conversations per day in under 30 minutes, stay manual.
• If you can’t - and you keep ending days with “I posted, nothing happened" - you don’t have a content problem. You have a conversation-sourcing problem.

The goal of Achiv.com isn’t to automate your relationships or send DMs for you (it doesn’t). It’s to make sure you’re not guessing where demand is.

How to turn a “pain conversation" into a first call (without being cringe)

You don’t need a big audience to get your first calls. You need:

• the right thread
• the right timing
• the right tone

Use “micro-commitments", not asks for a demo

Instead of “Want to hop on a call?" try:

• “If I sent a 2-minute loom showing how I’d handle this, would that be useful?"
• “I can share the checklist we use - want it?"

Once they say yes, you have permission to go one step deeper.

Keep your product mention to one line

Your credibility comes from understanding their problem.

The product mention is just a breadcrumb:

• “I’m building X for this exact issue".

If they bite, continue. If not, you still earned visibility and trust.

Follow up once, with new value

A second message is fine if it adds something:

• a resource
• a template
• a quick analysis of their situation

Don’t “just bump".

What to measure in month 2 (so you don’t spiral)

When you have 0 users, traditional SaaS metrics won’t help.

Track these instead:

• Qualified conversations found/week (threads where pain is explicit)
• Replies/week (from comments + DMs)
• Problem interviews/week
• Repeatable pain phrase count (how often you hear the same wording)
• Competitors mentioned (and why)

If these are trending up, you’re building traction even before sign-ups.

And if you’re stuck at “0 qualified conversations", your next move is not “ship more features". It’s fixing discovery.

Achiv.com is useful here precisely because it’s built to surface those conversations daily across Reddit, X, and LinkedIn - without you living inside search bars.

Closing takeaway: month 2 is about contact with reality, not content volume

The founders who get through the “0 users" phase aren’t magically better at marketing. They’re better at creating feedback loops.

When someone says “I looked at the market, read Reddit feedback… 0 users", the missing piece is not more reading. It’s more talking - starting from real, live pain.

And when someone says “All true. all useless on month 2 with no audience and 14 things on fire", that’s not cynicism. It’s a signal that they need a more direct path to conversations.

Build the weekly loop:

• find pain conversations → respond like a peer → earn micro-yeses → run interviews → update ICP/messaging → repeat

If the “find" step is what keeps breaking, automate only that part. Achiv.com exists for exactly that: a daily, curated shortlist of real humans describing problems you can solve - so you can spend your limited founder hours on the part that can’t be automated: showing up helpfully and learning fast.