Back to Blog

Content Ideas for SaaS Companies: Score, Don't Brainstorm

Stop collecting content ideas for SaaS companies and start scoring them. Map ideas to pipeline stages and rank your backlog in 15 minutes.

Anatolii Kharchuk
Anatolii KharchukCofounder, CPO · November 21, 2026

Key takeaways

  • Match every content idea to the pipeline stage you're actually in: invisible, aware, evaluating, or converting.
  • Score each idea 1-5 on stage fit, reach, effort, and proof; ship anything over 16 and park anything under 12.
  • Build-in-public posts, teardowns, and migration guides beat generic listicles for pre-revenue SaaS with zero traffic.
  • Mine your own build log, fresh community threads, and competitor gaps for ideas competitors can't copy.
  • Run a 90-minute weekly block to source, score, and start one idea per weak pipeline stage, and skip the week if nothing is shipped.

Stop collecting lists of content ideas for SaaS companies and start scoring them. Map every idea to the pipeline stage it serves, from invisible to converting, then rank your backlog with a simple rubric covering reach, effort, stage fit, and proof. You'll know what to write this week in about 15 minutes.

Why Do Most Content Ideas for SaaS Companies Waste Your Time?

You ship on Lovable, launch, then google "content ideas for SaaS companies" and get a list of 50 generic prompts. None of them ask the only question that matters: what does a stranger need to see before they trust a product with zero users and zero reviews?

The brainstorm trap: 50 ideas, no pipeline

Idea lists treat content as a volume game. But your funnel is invisible-to-aware, not aware-to-evaluating, so comparison posts and feature roundups are wasted effort. Threads on r/SaaS and r/Entrepreneur about getting the first 100 users without paid ads keep landing on the same point: early content works when it matches the reader's stage, not the writer's mood (r/SaaS).

Why stage fit beats topic volume pre-revenue

Search volume tells you what established SaaS brands can rank for, not what moves your first 100 paying users. One stage-matched post that answers an actual objection beats ten high-volume listicles, and it costs less to produce — a tradeoff we break down in what content publishing really costs and when to skip it.

What Pipeline Stage Is Your SaaS Actually In?

Most "content ideas for saas companies" lists fail because they ignore stage. A launch post can't help you if nobody knows your product exists, and a comparison page is wasted if you have zero traffic to convert. Match the idea to the stage or don't write it.

StageWhat it meansFastest signal
InvisibleNobody knows you existUnder ~100 monthly visitors, no branded search
AwarePeople recognize the problem and your nameRepeat visitors, Reddit replies, newsletter signups
EvaluatingPeople compare you to alternativesPricing page views, "vs" searches, demo-adjacent questions
ConvertingReady buyers hit frictionTraffic but no signups, abandoned checkouts

Signals you're still invisible

You launched on Lovable or Replit, posted once, and heard nothing. Zero branded searches, zero mentions anywhere. Content here means showing up where your users already hang out, not publishing into the void. The revenue-first approach in content ideation for solo founders starts here for a reason.

Signals you have awareness but no evaluation

People reply to your build-in-public posts and a few visit your site, but nobody compares you to anything. They know the problem, not your product. This stage needs content that connects your name to the problem: teardown posts, honest changelogs, niche case examples.

Signals you're close but not converting

You get pricing page views and "how does this compare" questions, but signups stall. Write objection-handling content: migration notes, honest limitations, "who this is not for" pages. Fixing stage mismatch beats writing more content every time.

Which Content Ideas Work at Each Pipeline Stage?

Invisible stage: build in public, launch logs, problem rants

Nobody knows you exist yet, so the goal is being seen in places your future users already read. Build-in-public threads, launch logs from your Lovable or Cursor build, and plain problem rants about the pain your tool fixes all work here because they read like a person, not a pitch. This is also where AI search visibility starts: referral traffic from chatbots is growing fast enough that publishers now track it separately from Google, and tools get cited by ChatGPT mostly because they show up in real discussions and detailed sources across the web, not because they publish more pages (Ahrefs' study on AI search referral traffic). The compounding move is picking one stage-matched idea type and shipping it weekly instead of rotating through six formats: a solo founder who posts one honest build-in-public update every week for three months has 12 artifacts working for them, while the founder who writes one launch post and one "top 10 tools" listicle has two. The first founder also gets quoted in threads; the second gets ignored. Every idea below follows the same rule: match the format to what the reader can do at that stage, then repeat it (content ideas chosen for revenue, not rankings).

Aware stage: comparison and teardown content, niche how-tos

They know the problem and are searching for approaches. Teardowns ("why your Bolt app's onboarding leaks signups") and narrow how-tos ("setting up AutoMod-safe Reddit posts") get found and shared.

Evaluating stage: migration guides, honest limitations posts

They're comparing tools, including yours. A "moving from spreadsheets to X" guide or a post listing what your product handles badly converts skeptics better than another feature page.

Converting stage: onboarding and use-case content

They signed up. Short use-case walkthroughs ("using X to answer your first 20 support tickets") reduce time-to-value and churn.

How Do You Score Content Ideas Before Writing Them?

Brainstorms produce lists. Rubrics produce priorities. Score every idea on four factors before you write a word.

The 4-factor scoring rubric

Rate each 1–5:

  • Stage fit: does this serve the stage you're actually in? A zero-user SaaS is in "invisible," so ideas that reach strangers beat ideas that convert readers you don't have yet.
  • Reach: how many of your target users will this plausibly hit? A Reddit answer in the exact subreddit they haunt outranks a generic listicle.
  • Effort: hours to ship, including research. Lower is better when you're solo.
  • Proof available: can you show a real build, number, or screenshot? Proof is what makes content convert instead of just exist.

Add the four scores. Anything under 12 waits; anything over 16 ships this week.

Worked example: scoring three ideas for a zero-user SaaS

Say you shipped an AI meeting-notes tool on Lovable. Score three ideas:

  1. "10 AI meeting tools compared" — stage fit 2 (you're invisible, comparison content needs an audience), reach 2, effort 4, proof 2. Total 10. Skip.
  2. "I built a meeting-notes app in a weekend with Lovable — here's the prompt chain" — stage fit 5, reach 4, effort 3, proof 5. Total 17. Ship now.
  3. "How I got my first 10 users from niche subreddits, week by week" — stage fit 5, reach 4, effort 2, proof 4. Total 15. Ship second.

The build-in-public post wins because it's the only one with proof you already own. More signal sources like these live in 7 content ideation signals hiding in your ship cycle.

When a 6/10 idea beats a 9/10 idea

A high total doesn't mean write it today. A 17-point idea that takes two weeks of research loses to a 14-point idea you can ship tonight, because volume and iteration beat polish at zero users. Weight effort heavier the more pre-revenue you are, and re-score old ideas after each launch: your proof factor changes every time you ship.

Where Do You Find Ideas That Aren't Already Saturated?

Keyword tools show you what everyone already wrote. Your best ideas come from three places competitors can't copy.

Mining your own build log

Your ship cycle is content. The bug that ate your weekend, the feature you cut, the Lovable prompt that finally worked. "I rebuilt onboarding three times before anyone signed up" beats another "10 SaaS growth tips" listicle. Write the post while the frustration is fresh.

Community threads as idea sources

Search Reddit for your exact problem phrasing: "first 100 users without paid ads," "launched on Lovable, now what." Sort by new, not top. New posts show what people are asking right now that no post answers yet. If you see the same question twice in a week, that's your next article. HeyCatch surfaces these threads automatically so you're not spending 3 hours a day scrolling, and content optimization signals for solo founders help you check whether your draft actually answers the question.

Competitor gaps as idea sources

Read the last ten posts from tools like Postiz or Predis.ai. Note what they skip: pricing breakdowns, honest failure posts, stage-specific advice. Their blank spots are your angles.

How Do You Turn One Idea Into a Stage-Matched Series?

The 1-to-3 expansion pattern

Take one core insight from your scoring rubric and split it into three pieces, one per pipeline stage. Say you learned that AutoMod-safe Reddit comments drive your first 100 users. The invisible-stage piece is a build-in-public post sharing that raw lesson. The aware-stage piece is a comparison of manual browsing versus a tool workflow. The evaluating-stage piece is a teardown of your actual comment-to-signup numbers.

What to keep evergreen vs. stage-specific

Keep the underlying insight evergreen: the lesson about where your users hang out does not expire. Keep the framing stage-specific, because a vibe coder who has never heard of you needs a story, while someone comparing tools needs specifics. Rewrite the stage-specific wrappers as your numbers change, and leave the core insight alone. One idea, three assets, one rewrite cycle per quarter.

How Do Solo Tools Like HeyCatch, Oetzi AI, and AutoTraction Fit This System?

Criteria applied equally to every tool including HeyCatch

Score each tool on the three things the system demands: does it map ideas to pipeline stages, does it score ideas before you write, and does it help execute?

HeyCatch covers planning and execution across channels, including Reddit, and guides which ideas to ship when. It will not do your positioning for you; if your stage mapping is wrong, it amplifies the wrong content faster.

Oetzi AI and AutoTraction are direct competitors focused on Reddit-led growth. Check Oetzi AI and AutoTraction directly for current features, since both are early products and scope shifts. Postiz and Predis.ai are adjacent: scheduling and social content creation, useful once you have ideas, but neither scores ideas against a pipeline stage.

Where manual + spreadsheet still wins

If you have under ten ideas and one channel, a spreadsheet with your scoring rubric beats any tool. Adopt software when the rubric runs weekly and execution time, not judgment, becomes the bottleneck.

What Does a Weekly Idea-to-Publish Routine Look Like?

The 90-minute block

Block one calendar hour a week, same slot, and split it: 30 minutes sourcing (mine Reddit threads, your support DMs, and your build-in-public replies for real questions), 20 minutes scoring everything from the last section's rubric, 10 minutes picking exactly one idea per pipeline stage you're weak in. The remaining 30 minutes go to drafting or briefing, not polishing. Publishing happens on other days; this block only decides and starts.

When to skip a week

Skip if you have an unshipped idea still in draft or a launch, fix, or customer call that week. One idea shipped beats four scored. If you miss two weeks running, cut the sourcing step and just publish your best backlogged score instead.

FAQ

How many content ideas should a pre-revenue SaaS have in its backlog?

Keep it small: 10 to 15 scored ideas is plenty. A long unscored backlog creates decision fatigue, not output. Score each idea on reach, effort, stage fit, and proof, then pick one per weak pipeline stage each week. If your backlog exceeds 15, prune the bottom half rather than writing faster.

Is build in public still worth it in 2025 for getting first users?

Yes, because it matches the invisible stage: nobody knows you exist, so content that reads like a person beats content that reads like a pitch. Weekly build-in-public posts compound, giving you 12 artifacts after three months and citations in community threads. One launch post plus a listicle gives you two artifacts and silence.

Should I write for Google or for ChatGPT citations when I have zero traffic?

Neither purely. With no traffic, show up where users already hang out and in detailed sources AI tools cite. ChatGPT citations come from being mentioned in real discussions across the web, not from publishing more pages. Write stage-matched content for humans first; AI visibility follows the same discussions.

What's the 90/10 rule for content vs. building?

Spend 90% of your time building and talking to users, 10% publishing. Content at the invisible stage amplifies a product people can find, not a substitute for one. If writing starts eating build time, cut back to one shipped idea per week. One idea shipped beats four scored.

You shipped a product.

Let's get it earning.

Get started