u/Background-Pay5729

I noticed something about myself recently.

Whenever a project feels uncertain, I start “organizing” instead of building.

New roadmap.
New notes.
New task board.
New positioning doc.
New list of things to research.

It feels productive, but a lot of the time it’s just procrastination with better formatting.

The projects where I make the most progress usually have a much simpler loop:

Build one thing.
Show someone.
Fix the obvious problem.
Repeat.

No huge plan. No perfect system. Just shorter cycles.

Wondering if anyone else does this.

How do you tell the difference between useful planning and just avoiding the uncomfortable part?

[ Removed by Reddit on account of violating the content policy. ]

[ Removed by Reddit on account of violating the content policy. ]

[ Removed by Reddit on account of violating the content policy. ]

https://preview.redd.it/onjemyf0ix1h1.png?width=800&format=png&auto=webp&s=68e0e97c61fd470da273f54dbcd26fedd42df145

I launched my app about a month ago, and it just crossed 56 customers. (proof)

The surprising part is that the biggest growth lever so far was not a new feature.

It was distribution.

For the first few weeks, I kept doing the classic builder thing:

• improve the landing page
• tweak onboarding
• add one more feature
• rewrite the headline
• polish screenshots
• wait until it felt “ready”

Some of that helped, but none of it mattered much while nobody was seeing the product.

The first real jump came when I started posting publicly with actual numbers and screenshots. Not polished launch announcements. Just honest updates about what was happening, what changed, and what I was learning.

A few things that seemed to work:

1. Specific numbers beat vague traction claims
“Got 9 customers in one day” performed much better than “getting early traction.”

2. Screenshots made it believable
People are skeptical of startup posts. A simple graph did more than a polished paragraph.

3. The story came before the product
The posts that worked were about the journey first. Product mention at the end.

4. Clear positioning mattered
Every confused comment became copy feedback. I kept tightening the explanation until people understood the product faster.

5. Distribution had to become part of the build loop
Post, get comments, see what people ask, update copy/onboarding, repeat.

56 customers is not some huge company, but it changed how I think about launching. I used to treat marketing as something you do after the app is ready. Now I think it has to happen while the product is still being shaped.

This is my app btw.

[ Removed by Reddit on account of violating the content policy. ]

One thing I’m noticing with vibe-coded SaaS is that people are getting way faster at building, but not necessarily better at getting discovered.

You can now ship a decent MVP in a weekend.

Landing page, auth, database, Stripe, dashboard, onboarding. All doable way faster than before.

But then the launch happens, a few Reddit posts get some traffic, maybe a Product Hunt spike, maybe some X posts, and then everything gets quiet.

That’s the part I think a lot of builders underestimate.

The bottleneck is moving from “I built something” to “people keep finding this without me manually posting every day.”

That’s what pushed me into building BeVisible.app.

Not because I think every SaaS needs 500 AI blog posts. I actually think that’s usually the wrong way to look at it.

The better question is:

What would someone search when they are already feeling the pain your product solves?

For most small SaaS products, that means building content around:

• alternatives to the tool they already use
• comparison pages
• use-case pages
• integration pages
• “how to solve X” guides
• problem-aware posts
• industry-specific landing pages

That stuff is boring compared to building features, but it compounds.

The issue is that doing it manually is a grind.

You have to research keywords, write the page, make it specific, add internal links, create visuals, publish it, track what moves, then come back later and update the pages that are getting impressions but no clicks.

Most founders don’t fail at SEO because they don’t understand it.

They fail because the workflow is too easy to ignore.

So the product I’m building is basically an attempt to turn that into a system: research, content, internal links, images, publishing, and tracking in one loop.

The main lesson so far:

Vibe coding makes product creation cheaper.
But distribution still has to be earned.

And if you don’t build some kind of discovery engine after launch, you just end up with a working product nobody consistently finds.

This is gonna sound boring compared to all the AI video/avatar stuff, but I’ve been messing with AI for SEO content and it’s honestly been one of the more useful workflows for my solo SaaS.

The basic problem was simple: I knew I should be publishing more content, but actually doing it every week was annoying.

It wasn’t just writing. It was finding keywords, checking what people were searching for, making the article not sound like AI garbage, adding internal links, finding or making images, formatting everything, publishing it, then checking later if anything moved in Google Search Console.

When you’re solo, that turns into a lot of tiny tasks that never feel urgent, so they just don’t get done.

What I started building is basically a daily SEO content system. Full disclosure, it’s my own product: BeVisible.app.

The idea is pretty straightforward:

• research content opportunities
• generate SEO articles
• add internal links
• create featured images
• publish to WordPress/Webflow/Ghost/Notion/custom CMS
• track results over time

I’m not pretending this replaces strategy or guarantees rankings. SEO still takes months and bad AI content is everywhere. But the useful part is removing the repetitive publishing work so content actually goes live instead of sitting in a doc forever.

The biggest thing I’ve learned is that AI is way more useful when it handles boring operations, not when it tries to be “creative.”

Curious if anyone here is using AI for organic traffic.

I’m doing a small experiment for B2B SaaS founders.

Send me your product and I’ll turn it into a search-focused article that explains:

who it’s for, what problem it solves, what category it belongs in, and why someone would pick it over the usual alternatives.

The goal is simple:

When a buyer searches Google or asks ChatGPT/Gemini/Claude for tools in your space, your SaaS has a clearer shot at being understood and recommended.

No pitch deck needed. Just drop:

Startup:
Website:
What it does:
Who it’s for:
Main competitor or category:

I’ll do the first 20.

First come, first serve.

I think a lot of no-code builders are running into the same trap.

We can build the product way faster now.

Bubble, Webflow, Framer, Softr, Airtable, Supabase, Make, n8n, Lovable, Cursor, Replit, whatever your stack is. You can get from idea to working product insanely fast compared to a few years ago.

But then the hard part shows up.

Nobody cares.

Not because the product is bad.

Because nobody can find it.

I’ve seen this happen a bunch:

• founder builds a nice tool in 3 weeks
• posts it on Product Hunt
• shares it on Reddit
• gets a small spike
• maybe gets 20 signups
• then traffic goes flat
• then they start adding more features
• then they rebuild the landing page
• then they wonder if the idea is dead

But the issue is usually not the builder or the app.

The issue is that the internet has no idea what the thing is.

Most no-code products launch with:

• one homepage
• one pricing page
• maybe a changelog
• maybe a few tweets
• no comparison pages
• no use-case pages
• no integration pages
• no “how to solve this specific problem” pages
• no content that explains the category
• no pages answering the questions people ask before buying

That is fine if you already have an audience.

It is brutal if you don’t.

No-code removed a lot of the friction from building software, but it did not remove the friction from earning trust.

People still need to understand:

• What does this replace?
• Who is it for?
• What problem does it solve?
• Why not just use Google Sheets?
• Why not use Zapier?
• Why not use Airtable?
• How is it different from the bigger tool?
• Does it work with my current stack?
• What happens after I sign up?
• Is this serious enough to rely on?

Those questions should be pages.

Not just answers you give one by one in DMs.

The best thing I’ve changed in my own workflow is treating every repeated question as a distribution asset.

If someone asks “Does this work with Webflow?” that becomes a page.

If someone asks “How is this different from Zapier?” that becomes a page.

If someone asks “Can I use this for agencies?” that becomes a page.

If someone asks “Is this good for local businesses?” that becomes a page.

If someone asks “What should I do if I already use Airtable?” that becomes a page.

This is boring, but it compounds.

A no-code builder with 30 useful pages can look more trustworthy than a technically better product with one vague homepage.

My current simple playbook:

1. Write down the last 25 questions people asked about your product.
2. Group them into themes.
3. Turn each theme into one clear page.
4. Add internal links between related pages.
5. Make sure your homepage links to the most important ones.
6. Keep doing it every week.

The point is not “start a blog” in the generic sense.

The point is to make your product easier to understand by humans, Google, and now AI answer engines too.

I’m building in this area, so I’m biased. I made BeVisible to help turn these product questions into SEO/AI visibility pages and publish them consistently.

But you can do the manual version in Notion or Google Docs today.

Before building the next feature, write the page that explains the feature you already built.

A lot of no-code products don’t need more product yet.

They need more surface area for people to discover and trust what already exists.

I used to think SaaS content meant “write helpful blog posts.”

Now I think that’s only half right.

The problem is that most SaaS blogs are helpful in the wrong direction.

They publish stuff like:

• 10 productivity tips for remote teams
• What is workflow automation?
• The ultimate guide to customer success
• 7 ways to improve collaboration

None of this is evil. It’s just too far away from the buying moment.

A founder does not wake up thinking:

“I need a thought leadership article.”

They wake up thinking:

• “Why is my onboarding conversion dropping?”
• “Is there a cheaper alternative to [competitor]?”
• “Can this integrate with HubSpot?”
• “How long does migration take?”
• “Will this work for a 12-person team?”
• “What happens if I cancel?”
• “Why does every tool in this category look the same?”
• “Do I need software for this or can I do it in Sheets?”

Those are buying questions.

And weirdly, most SaaS sites barely answer them.

They hide the useful stuff in sales calls, onboarding docs, Slack threads, demo scripts, support tickets, and founder DMs.

Then they wonder why their blog does not convert.

The best content ideas are usually already inside the company:

1. Sales objections
2. Every objection should probably be a page.
3. Competitor mentions
4. If prospects keep asking how you compare to X, that is not awkward. That is content demand.
5. Support tickets
6. If customers keep asking the same setup question, write the page.
7. Churn reasons
8. If someone left because they misunderstood the product, your website probably failed earlier.
9. Demo call questions
10. Your best SEO topics are often sitting in Gong, Zoom notes, or your founder’s inbox.
11. Integration requests
12. Every “Do you work with X?” can become a search landing page.
13. Use cases
14. Features are how you describe the product. Use cases are how customers describe their lives.
15. “Not for” explanations
16. A page that says who should not use your product builds more trust than another generic benefits page.

The mistake is treating content like a traffic channel only.

It is also a sales asset.

A good page should make the next sales call shorter.

If someone reads 5 pages on your site and still needs you to explain the basics, the content failed.

My current test for SaaS content:

Would I send this to a confused prospect?

If the answer is no, I probably should not publish it.

That one filter kills about 80% of generic blog ideas.

I’m building in this space, so I’ve been thinking about this a lot. The tool I’m working on helps turn these questions into SEO/AI visibility pages and publish them consistently.

But honestly, you can do the first version manually:

• Export your last 50 sales/support questions
• Group repeated questions
• Turn each cluster into one clear page
• Link those pages from your homepage, pricing page, and docs
• Watch which ones prospects actually mention on calls

Forget “content calendar” for a minute.

Build a question-answering machine for buyers.

I’ve been looking into why some SaaS products show up in ChatGPT / Claude / Google AI answers and others basically don’t exist.

The pattern is less exciting than people want it to be.

Most SaaS sites are not “bad at AI SEO.”

They are just hard to understand.

A lot of them have:

• a beautiful homepage
• vague feature blurbs
• no comparison pages
• no use-case pages
• no “how it works” pages
• no pricing explanation beyond a table
• no docs or support content that answers buyer questions
• no pages that clearly say who the product is for and who it is not for

Then the founder asks: “Why does ChatGPT recommend my competitor?”

Because your competitor gave the internet more useful context.

Here are the boring pages I now think most SaaS companies should publish before worrying about any advanced AI visibility tactic:

1. “[Product] alternatives” page
2. Not a fake comparison table. A real page explaining who should pick you, who should not, and how you differ from the obvious options.
3. “[Competitor] vs [Your Product]” pages
4. People hate these because they feel aggressive, but buyers search this way. AI answer engines also need contrast to understand positioning.
5. “Best [category] tools for [specific audience]”
6. Not “best CRM software.” More like “best CRM software for commercial real estate brokers.” Specific beats broad.
7. Use-case pages
8. Most SaaS sites describe features. Buyers describe jobs. “Automated reporting” is a feature. “Send weekly client reports without opening a spreadsheet” is a use case.
9. Problem pages
10. Write about the painful situation before pitching the product. A lot of traffic comes from people who do not know the category name yet.
11. Integration pages
12. If your product works with WordPress, Shopify, HubSpot, Slack, Stripe, whatever, every integration is a discovery surface.
13. Migration pages
14. People rarely wake up wanting software. They wake up wanting to leave software that annoys them.
15. “How we think about X” pages
16. This is underrated. AI systems seem to understand brands better when the site has clear, opinionated explanations of the category.
17. Support-style content
18. Docs, FAQs, troubleshooting, setup guides. This stuff feels unsexy, but it gives crawlers and answer engines concrete language.
19. Internal links between all of the above
20. A pile of disconnected pages is weaker than a topical map. Your pages should explain each other.

The mistake I see is founders jumping straight to “How do I rank in AI?” before their site can answer basic questions:

• What do you do?
• Who is it for?
• What problem do you solve?
• What are you replacing?
• What are you not good for?
• What proof do you have?
• What should someone read next?

My current workflow is:

1. List 20 buyer questions people would ask before buying.
2. Search those questions in Google, ChatGPT, Perplexity, and Reddit.
3. Note which brands keep showing up.
4. Compare the pages those brands have that we don’t.
5. Publish the missing pages.
6. Add internal links so the site becomes easier to understand.
7. Repeat monthly.

It is not glamorous, but it compounds.

Disclosure: I’m building in this space. I made BeVisible.app because I got tired of doing this workflow manually for SEO and AI visibility. But the main point is not “use my thing.” The main point is that most SaaS teams do not need a secret AI trick yet.

They need to make their product legible.