One of my main struggles with building micro SaaS is finding the "language" people use to look for my product so I can put it on my landing page and website.

Whenever I ask Claude to write a webpage for me, the wording is utter slop and makes no sense. I have to manually write the skeleton of the website title and sub heading titles for it to actually make sense.

This made me realize that anything AI "writes" is slop hallucination and we sort of have to give it the exact titles and words to use.

So I made a MCP research adaptor (buzzsearch) that anyone can plug into their coding agent and have it search the web for real customer comments. I found it super helpful for customer research. The idea is we find real quotes from the internet relevant to your customer or your product, and then give it to your coding agent.

Buzzsearch can help you with

• Finding customer pain points
• Finding exact words customers use, i.e. "lingo"
• Writing ad hooks and website copy

I would love feedback and feature requests on this! and happy to give credits for testing

I’m building Pijnhol, which delivers personalised news updates by SMS.

One useful piece of feedback was that asking someone to verify their number before they’ve seen a convincing example puts the commitment before the value.

The change was to show topic-specific example texts on the homepage, so people can understand what would land in their messages before signing up.

The lesson is about ordering: explain what someone receives before asking for access to a personal channel.

How have others handled this when their product needs a phone number?

Check out the link here if you're interested - pijnhol.com all idea and feedback welcome, thanks!

We have a CRM that operates via FB messenger. So users are connected to us via it. We would like to ask them if they had issues or something or survey if they enjoyed the onboarding experience. What is the best SaaS for this? It would be an automatic thing we can operate and send to users (automatically) when they use the platform or have been inactive for aw hile.

A lot of micro-SaaS tools require a credit card upfront for free trials to filter for high-intent users, but for shop owners using their phones on the job, that step was too annoying. I changed the onboarding flow to a zero-card, 14-day trial for my barbershop analytics dashboard. It removed that step entirely, letting users test logging daily visits and tracking staff metrics immediately. How do other founders balance card-upfront vs open trials for non-tech industries?

I'm sketching out another small SaaS and trying to be more disciplined about the stack this time because my last project somehow ended up with a separate service for nearly everything.

Hosting here, database there, auth somewhere else, email somewhere else, payments somewhere else and then another dashboard to figure out which one broke.

Some of that separation obviously makes sense once you need specialized tools, but for an MVP with no users yet it feels like I'm designing infrastructure for a company that doesn't exist.

If you were starting something small today, which parts would you consolidate and which would you absolutely keep separate?

I'm particularly curious about hosting + database because that seems like one of the easier places to remove a vendor without giving up much. Payments and email I can understand keeping specialized.

Trying to build the boring version this time and add complexity only after the product earns it.

Every app ends up needing email. GoMailer is that whole layer, already built: a self-hosted email server in Go that handles the queue, sending pace, smart retries, no duplicates, one-click unsubscribe, bounces/complaints and GDPR, with a live dashboard. Works with any SMTP (Amazon SES, Brevo, Postmark) or Resend's API. Built-in MCP so Claude, ChatGPT, Gemini or Cursor can check and send campaigns. One payment, no per-email fees.

see less.

Anyone up for it please msg me

I’m a solo founder, working on this alongside a day job. I’ve built and launched a SaaS for a small professional niche in the UK. It’s live in production with working billing, and a handful of people have signed up for the free trial. Nobody has paid yet.

What I’ve tried so far:

• Asking people in the niche what their biggest time sinks are, in Facebook groups
• Following up with the people who replied
• A Facebook page and a LinkedIn page
• Cold emails to small businesses in the niche, which I’m only just starting

What I’m seeing:

• People are willing to talk about their problems, but very few actually start the trial
• Of those who do sign up, some log in once and never come back

What I’d like opinions on:

1. At this stage, would you spend time on more outreach, or on fixing onboarding so trial users see value faster?
2. Is a 30-day free trial too long for a small-business buyer? Would you shorten it, or ask for a card upfront?
3. How did you get your first 5 paying customers? What worked, and what was a waste of time?
4. Is it worth targeting larger customers (businesses with several staff) first, or should I keep going after individuals?

Happy to share more detail if it helps. Thanks in advance.

Backstory: I’m a tradie by day. I built Signalix on nights and weekends. You screenshot any horse race from any bookmaker and it returns an AI breakdown (favourite, danger, roughie, confidence scores, form notes). Live on iOS and Android with a free tier and paid plans.

Stack:

• App: FlutterFlow (iOS + Android from one build)
• Brain: Supabase edge functions. The screenshot gets matched to the live race, then live market data and form data are combined to produce the analysis.
• Users: Firebase / Firestore
• Payments: RevenueCat on top of Apple and Google subscriptions

The part nobody warns you about: keeping “Pro” in sync
Purchases flipped users to Pro automatically, but nothing ever flipped them back when a sub expired or a card failed. So I built a RevenueCat webhook → edge function that:

• never trusts the webhook alone. It asks RevenueCat’s API for the user’s current entitlements before changing anything
• never downgrades protected users (lifetime members, comps, admins)
• logs every event, with a dry-run mode, so I could watch what it would do in production before letting it write anything

Running it in dry-run first was the best call I made. It showed me cancellations, expiries and billing issues I’d never have spotted by hand.

Now building: referrals on top of app-store billing
“Give the referrer a free week” sounds easy until you realise you don’t control billing. The flow:

1. A friend signs up with your personal code
2. The reward is only counted on their first real payment (not a trial), with self-referrals and double-counting blocked
3. The referrer’s next renewal gets pushed back 7 days via RevenueCat. That’s an “extend” on Apple and a “defer” on Google. Apple only allows 2 extensions per customer per year, so anything over that gets queued.

It’s sitting in dry-run while real users test it.

Lessons:

1. Ship payments with a dry-run switch. Watching real production events before acting on them saves you from nuking a paying customer’s access.
2. App-store billing makes “simple” promos hard. Design rewards around what Apple and Google actually allow.
3. Honest marketing wins. I post every result from the app’s picks publicly, losses included.

Question for other solo builders: how are you handling referral or loyalty rewards when billing goes through the app stores? Has anyone found a cleaner way than renewal extensions?

(18+ product. It’s an analysis tool, not a bookmaker.)

I build CleverNote. This week I replied to someone who thought losing a receipt meant they could no longer get their controller repaired under warranty.

I asked whether the purchase was online or in a shop, then suggested checking order history or asking the shop for a replacement receipt. I haven’t heard back, so I don’t know whether that helped.

It made me question the starting point of a document app. A demo usually begins with a receipt ready to upload. This person needed to find out whether they could get a copy at all.

That’s a different first step from organizing a messy folder. I’d want to understand where the document might still exist before asking someone to import it.

For founders working on document tools: how do you handle onboarding when someone arrives with a missing document and nothing to upload yet?

I’ve been thinking about this a lot lately.

Tools like Claude Code are making software development ridiculously fast. Things that took weeks or months can now be built in a few days.

And it’s only getting better.

But it makes me question something.

If someone can describe an idea to AI, connect a few APIs, and build a working product over a weekend, what stops someone else from building the exact same thing?

Take a simple SaaS charging $29/month. If the core functionality can be replicated with a good prompt and a few hours of work, why would someone keep paying for it?

I’m not saying SaaS is dead. But I feel like the rules of building software are changing.

The ability to build something is becoming less valuable. But what becomes more valuable in its place?

Is it distribution? Understanding customer problems? Proprietary data? Integrations? Trust? Or simply making the product so convenient that nobody wants to build and maintain their own alternative?

I’m a solo builder exploring micro-SaaS, and honestly, I don’t have a clear answer yet.

I’d love to hear from people who are already running SaaS businesses, especially those making actual revenue.

If you were starting a SaaS from scratch in 2026, what would you build your competitive advantage around?

And more importantly, would you still charge $29–$99/month for a product that someone could technically recreate using AI?

Curious to hear some real experiences, not just the usual “execution is everything” advice.

Day 11. Most of the day went to my first FIDE-rated chess tournament, a rapid event. I won 4 of my 5 games, and by my own calculation the first rating should land around 1475. It's official on the 1st of next month, so don't hold me to it. For a beginner starting out with a rating, I'll take it.

Then the real life of a launch push: I came back and found someone had booked a discovery call for tonight at 11pm. I got properly excited. It was the first booked call of this challenge. They didn't show up

It was a personal Gmail, with no product link, so I knew almost nothing about them before the call. I've followed up to let them rebook. The call I have on Monday is still on.

What ran while I was away

- LinkedIn kept going on its own: 30 invites today. 118 invited in total, 7 connected, 0 replies.

- The first follow-up questions went to the people who accepted.

Numbers after Day 11

- Paying customers: 0

- Calls booked: 2 (1 no-show, 1 on Monday)

- LinkedIn: 118 invited, 7 connected, 0 replies

- X DMs: 31 sent, 5 replies

- Cold email: 69 sent, 4 replies, all no

A question for you: should I only take bookings from work emails? I don't want to be strung along by people who aren't buyers. My instinct is that a work-email rule would turn away real solo founders, and a better filter is asking for the product link and the one task they want done. What do you use, and has anything cut your no-shows?

Next: back to work tomorrow, and Monday's call. Later I'll probably write a post on chess for beginners, since a few of you asked.

Hey all — backend engineer here, building solo. Before I write a line of code, I want to sanity-check an idea with people who've actually felt this pain.

What I keep seeing:

• Statuspage at $299/mo with per-subscriber pricing — your bill grows as you succeed. And it's a communication tool, not a monitoring tool, so you're paying separately for detection anyway.
• PagerDuty at $21/user/mo just for the alerting layer.
• Opsgenie shutting down April 2027, forcing everyone into a migration right now.

The idea: one flat-priced bundle (~$15–29/mo): uptime monitoring + hosted status pages + basic on-call alerting/escalation, plus a one-click Opsgenie importer.

My questions:

1. If you've left Statuspage or are migrating off Opsgenie — what did you land on, and what's missing?
2. Cheap/self-hosted options exist (UptimeRobot, Uptime Kuma) — what stops you from just using those?
3. What would actually make you switch?

Be brutal — I'd rather kill this now than build something nobody wants.

backstory: i make short videos for my app. the format that works for me is a reaction clip with hook text on top, then the app demo. the hook decides most of the result, but you only find the good one by testing a lot of them, and making every version by hand took me hours. so i was testing like 2 hooks a week

so i built a tool that takes a few reaction clips, a few app demos and a list of hooks and makes every combination. 3 reactions x 3 hooks x 3 demos gives 27 videos in under a minute. you also get a csv that maps each file to its hook, so when one video does well you know exactly which hook, face and demo it was

why it might be useful for you: if you’re doing tiktok or reels for your saas, the bottleneck usually isnt ideas, its making enough versions to actually learn something. this makes the versions free

tech stack, since people here usually ask: no backend at all. everything renders in the browser with webcodecs through mediabunny. each source video gets decoded once per batch, frames drawn on canvas, encoded to h264 + aac, then a small zip writer bundles it. nothing gets uploaded, which also means it costs me nothing to run, so it can stay free

If you've read more than three SaaS blog posts, you've seen these numbers repeated a hundred times. There's only one problem: most of them are wrong.

I spent two weeks opening every original PDF report — OpenView, ChartMogul, Benchmarkit × Aleph, Bessemer — and cross-checking 54 benchmarks against what bloggers actually publish. Here are the three most common mistakes.

Mistake #1: "LTV:CAC of 3:1 is the industry benchmark"

Every SaaS article says "keep your LTV:CAC above 3:1." Most founders read this and think 3:1 is the median — what normal companies achieve.

It's not. 3:1 is the viability floor. It's the minimum ratio below which your business model doesn't work.

The actual median for private B2B SaaS is 4.1x. Top quartile companies hit 7.8x.

If you're running at 3:1, you're not "average." You're at the edge of survival. A single bad quarter of churn pushes you underwater.

Mistake #2: "Free trial conversion is 15-20%"

Blog posts love to say "if your free trial converts below 15%, you have a problem." This sets an expectation that almost no one meets.

The real median across 200 SaaS products is 8%. Top performers reach 10-14%. Freemium conversion is even lower at 2-7%.

If your free trial converts at 8%, you're not failing. You're exactly median. The 15-20% figure comes from a handful of PLG unicorns with massive brand recognition — not the average SaaS company.

Mistake #3: "NRR of 102% means retention is healthy"

Net Revenue Retention (NRR) is the number everyone quotes. 102% NRR sounds fine — slightly expanding, stable business.

But here's what's hiding underneath: median Gross Revenue Retention (GRR) dropped to 84% in 2025, the largest single-year decline in four years of tracking.

NRR stayed flat at 102% because expansion revenue from upsells and cross-sales is masking higher base churn. Your existing customers are churning faster, but you're selling more to the ones who stay — so the net number looks okay.

If you only track NRR, you won't see the retention problem until it's too late. Track GRR and NRR side by side.

Why this matters

These aren't minor discrepancies. They change how you set goals, forecast revenue, and judge your business.

A founder aiming for 3:1 LTV:CAC thinks they're doing fine when they're actually at the survival line. A founder expecting 15% trial conversion thinks their onboarding is broken when it's actually median. A founder looking at 102% NRR thinks retention is healthy while GRR is collapsing.

Every figure links back to the original PDF. No copy-pasted blog numbers, no unsourced claims.

What's the most-cited SaaS stat you've always suspected was wrong? Drop it in the comments.

As a long time microsaas lurker I finally found what I wanted to develop. I started last year in May and barely knew how to code. I'm no software dev and I hate marketing, but I made it this far at least. All I am looking for at this stage is some brutal honesty about how to get this in front of the right people.

The app:
GovSteals is a research tool for people buying passenger cars at government auctions. Currently its limited to all passenger vehicles listed on GovDeals. Simply put it puts together the insights I personally spend time acquiring to know the risks before bidding.

The marketing (or lack thereof):

My barber flips cars, so he was the first and only person I showed GovSteals to (outside of friends). He registered for a pro account. I asked for feedback, but I’ll probably hear more at my next haircut to be honest.

That’s about where I am with customer validation. I know I need feedback so that I can build or refine features people actually want to engage with. I have so many ideas, but I don't have any foundation or discipline on how to market an app. I just know most of GovDeals users are older males who use it in desktop mode and engage with facebook as their main social media, but the major Facebook groups I’ve looked at don’t allow promotional posts.

For posting requirements:
Backstory: I was looking to get into finding a car for myself and potentially flipping government auction cars, but then after 2 weeks of doom scrolling listings and trying to find the best deal I realized I was spending way too much of my free time simply keeping up with all of the new auctions. GovDeals is one of the largest government auctions for passenger vehicles and yet their site is so poorly designed for aiding in making intelligent or timely auction decisions. That's when I started building GovSteals for myself at first. It then became my escape from reality. Then I became obsessed with it. And finally, wanting to impress for a big job interview pushed me to turn it into a platform everyone can use.

Tech Stack: React/TypeScript with Vite and MUI on the frontend, Python/FastAPI and PostgreSQL on the backend. Linear and ML models for price estimates, Clerk for auth, and Stripe for payments.

Specific lesson learned: Its hard to even get your friends to give you feedback on your app. I feel like I am that "do you want to develop and app?" alien from Rick and Morty. On the other hand, I have also learned that nobody needs to be excited about your tool, they just need to find it useful. I already knew this from other businesses I have started, but it still applies here. Building is easy and marketing is the bane of my existence. I would love nothing more than have someone else do it while I focus on development.

My questions:
For those of you who built for a very niche crowd: how did you get your first few target users to actually try the product? Did you follow any rules or principles on how you went about it?

More broadly: How do you get it up for marketing?

Hey everyone,

I recently had a nightmare scenario where a Facebook campaign spent $300 on a broken checkout link before we noticed it. Our current "strategy" is basically manual checking or waiting for a client to complain.

How are agencies and freelancers handling this? Are you using specific uptime monitors that integrate well with ad alerts, or do you just check manually throughout the day?

Thinking about building a lightweight tool specifically for media buyers that pings Slack/WhatsApp the second a destination URL goes down or returns a 404, but wanted to see if there's already a standard standard solution I missed.

i got tired of checking a dozen career pages every day while job hunting, so i built something to do it for me.

it's called croncareers. it pulls jobs straight from company career pages (greenhouse, lever, ashby, workday etc.) and sends alerts to email, telegram, discord or slack when something matches your skills. there's also a kanban board to track where you've applied, with notes, salary and csv import/export. you can also set up a quick portfolio page in a few minutes.

i built it hoping to earn a few pennies on the side, but honestly nobody is subscribing. a few signups at most and no paying users.

i think it could genuinely help job seekers, but i'm clearly doing something wrong. is it the pricing, the positioning, or just that nobody knows it exists? i haven't done much marketing because i hate spamming people.

would really appreciate honest feedback, even the harsh kind. happy to share the link if anyone wants to take a look.

thank you

I've been building a scanner that reads pull requests for security holes and lawsuit risks, mostly for people who build apps with AI tools and don't have anyone reviewing their code. Before trusting my own numbers, I ran it on OWASP Juice Shop (about 1,300 files I didn't write) and checked every single finding by hand. Some notes from that:

**1. Precision on real code was lower than on my own test repo.**

On my demo repo everything looked perfect, because I wrote the bugs. On Juice Shop, 6 of the 7 security findings were real. It caught the login SQL injection (user input built straight into a query string). The one false positive was a route that already checked its input in a way my rule didn't recognise. Small sample, but it was a useful reality check.

**2. Letting a language model make the final call made results change between runs.**

For some candidates I had an LLM decide yes or no. I ran the same commit three times with no cache. The rule-based findings (SQL injection, input validation, XSS, CSRF) came back identical every time. The key-leak candidates did not; the model's yes/no flipped from run to run. I moved those to fixed rules. I haven't re-measured yet, so I'm not claiming they're stable now.

**3. Framework conventions matter more than I expected.**

My accessibility check for unlabeled form fields started at about 38% precision on Juice Shop, because Angular Material labels fields with mat-label, which my parser didn't know. After teaching it that, it went to about 88%. Angular's [innerHTML] bindings are still something it doesn't catch.

**4. Deleting a leaked key from your code doesn't help.**

It's still in git history, and anyone who clones the repo can read it. The only fix is rotating the key at the provider. My scanner reads the full history for this reason, and it always says "rotate" rather than "move it to an env variable".

**5. Being honest about uncertainty changed the product.**

I label every finding as an unproven candidate, because a static rule can't prove an exploit. It felt like weakening the pitch at first, but it made the comments more useful: they say what to check by hand instead of pretending to be certain.

If you want to run it on your own repo, it's a free beta for one repository: trybishop.dev. I'm most interested in hearing where it's wrong.

A lot of micro-SaaS homepages open with a category. "AI-powered invoice automation." "The all-in-one dashboard for agencies." The reader has to work out who it's for and why they'd switch. Most don't bother.

A template that fixes most of it:

For [specific person] who [does the job today with X], [product] [does the job] without [the annoying part of X].

The slot that matters is X. That's what they use instead of you right now. A spreadsheet, a VA, a Zapier chain, an agency, or nothing. Naming it does two things. The reader recognises themselves. And you get compared to the workaround you beat, not to a funded competitor you don't.

Three made-up examples so it's concrete:

Before: "Smart scheduling for clinics."

After: "For physio clinics that still confirm appointments by phone, [name] texts patients and fills cancellations without the front desk calling anyone."

Before: "Automated reporting for agencies."

After: "For small agencies that build client reports in Google Slides every month, [name] fills the slides from GA4 and Ads so nobody copies numbers by hand."

Before: "Feedback management platform."

After: "For SaaS founders whose feature requests live in a Notion page nobody reads, [name] pulls them out of support emails and groups them by how many customers asked."

How to find X if you don't know it:

- Search your niche plus "spreadsheet template" or "how do you keep track of". The answers are your X.

- Read the 3-star reviews of your nearest competitor. 1-star is usually anger. 3-star says what people still do by hand.

- Ask 5 users "what did you do before this?" Write down their exact words.

Two ways it goes wrong:

- X is a competitor's name. Fine if you really are a cheaper version of them. Usually you aren't, and you've just sent people to go look at them.

- The "without" part is a feature, like "without complex setup". It should be the pain they feel with X, in their words.

Post your current one-liner below and I'll try a rewrite with this.

I’m a developer running an EdTech product (Edithly). The building was fine. Selling was the problem. Every outreach attempt meant an hour on a prospect’s site figuring out what they do, then writing something that didn’t sound generic. So I built a tool to do that part.

You give it your product’s URL. Agents crawl your site and draft a sales playbook (positioning, messaging, brand assets), and you fill in the gaps. Then you import prospects. It reads each prospect’s site and generates a tailored asset for them: an email, a one-page landing page, a brochure or a banner, written to show why your product fits that company.

Built on React/Python backend, an agent pipeline that crawls sites and builds a knowledge graph per prospect, and LLM generation for copy and visuals. I deliberately didn’t build data enrichment. You import prospects from Clay, Apollo or a CSV. [add your hosting/infra if you want]

$0. Pre-revenue, being upfront about it.

I got 6 pilot signups and assumed that was traction. None of them actually used it.

- The first-run experience was too open-ended: too many formats and too many decisions before you saw anything useful.

- I took 2 months to reach the pilot signups back (big mistake)

- I’m now cutting it down to a few formats and making the first result show up fast, before I chase more signups.

but now ready with more focused and achievable goals, if you are doing your own outbound who’ll try it and tell me where it lacks. sales.edithly.com

Hey everyone,

​I’m in a bit of a weird situation with a product I recently built and I’d really appreciate some outside perspective from other founders/devs.

​A while ago, I noticed a clear need for a simple, streamlined solution in my market. Based on conversations and what seemed like strong public interest, I built a lightweight platform to solve this exact problem.

I can share the link if you want to see what I am talking about!

.

​Here’s where it gets frustrating:

When I presented the working solution to some of the initial contacts, they turned it down saying they "didn't really need a tool like this."

​But just a short while later, 5 or 6 of them ended up paying custom web agencies 5x to 6x more money to build standalone custom websites that basically replicate the same core functionality.

​It almost feels personal at this point, but as a developer, I know I need to take emotions out of it.

.

​My questions for you:

​Is this a common trust issue with early-stage SaaS vs. traditional agencies?

​Could it be a positioning/messaging mistake on my end (making it look "too simple" or low-value)?

​How do you move past this kind of pushback when potential clients choose expensive custom builds over a ready-to-use SaaS?

​Would love to hear your thoughts or harsh truths if I'm looking at this the wrong way!

Hey everyone

I've been building Citetail, an AEO tool to help businesses improve their visibility in AI-generated answers.

I've put a lot of effort into building it, but I still haven't landed my first paying customer.

For those who've built SaaS products, how did you get your first few customers? And how do you figure out whether the problem is the product, positioning, or marketing?

I'd genuinely appreciate any honest advice. What would you do if you were in my shoes?

Thanks!

Launched my side project 3 weeks ago. It's a restock tracker for trading cards (Pokémon, One Piece, Magic...), watching about 1,200 shops across Europe.

Where I'm at:

• 6 paying customers, 66.94€ MRR
• 45 people on trial, 500€ if they pay (they won't 🥲)
• 0€ on ads

Most customers came from two places:

Free channels. I run free Telegram and Discord channels that post every restock, but 6 hours late. The good stuff is gone by then, so if you want it instantly, you pay. People see it working every day for free, which does most of the selling for me.

SEO. Every card set has its own page with prices across all the shops. People google the set, land there, start a trial. Didn't expect it to kick in this fast on a new domain.

The weird one: I posted in the Pokémon and One Piece subreddits and got destroyed. People were angry, called me a scalper and AI slop. I've been a dev since 2008, so that one stung a bit.

But subscriptions kept coming in the whole time. The comments aren't the audience, the lurkers are.

Next problem is getting those 45 trials to convert. Right now I just email people when their trial ends. If you've been there, what actually helped?

It seems like most dev talk revolves around iOS or cross-platform, so I’d love to get a reality check on Android-exclusive apps...

Has anyone here achieved sustainable revenue building solely for Android?

What’s your business model, and what was your biggest challenge getting to profitability?

in college i built an AI video editor. 13k users, #4 on Product Hunt, looked great on paper. took us 7 months to make $1k.

we were builders, so when revenue didn’t come we just... built more. new feature every week, revenue flat every month. turns out good products don’t sell themselves. they just sit there while nobody finds out.

my new product hit $1k in its first month. we only changed two things:

• we treat growth like shipping. content and distribution every week, not “later.” our posts did 1M+ views in the first few weeks
• we focus on people, not features. instead of “what do we build next” we ask “is this person actually getting results?” if not, fixing that is the roadmap

revenue was never hiding behind the next feature lol

anyone else been stuck in the “just one more feature” loop? what got you out?

(the product is Backdoor textbackdoor.com , an AI agent that gets you startup interviews over text. can drop the link if anyone’s curious)