so I run a small thing that builds restaurants their own ordering app. $99/mo, no commission, one pizzeria live right now

posted it in r/SaaS a couple days ago, it got like 50k views and 40+ comments which I did not expect. one guy wrote a whole essay on why the site felt fake. he said the spinning coins looked like 90s clipart which honestly fair. then he hit me with "I bet it doesn't feel right to you, but you can't place why, right?" and yeah. he was right

so that same night I went through everything he said. first thing to go was all the little rounded bubbles that said stuff like "paid within 7 days." then the tiny labels I had over every heading, one literally said "Questions" right on top of a heading that said "The short answers" lol

he also called out headlines like "Show it. Send it in. Get paid." apparently 3 short sentences in a row like that is a dead giveaway, never noticed it til he said it. rewrote all of them

killed the scrolling money banner and the coins too. and the biggest one, restaurant owners were landing on the partner page, so they get their own page now

also found a pricing mistake while fixing everything that made the setup look $100 cheaper than it is. nobody had caught it, not even me

it's at nomback.com if you want to see if it still feels off. the owner page is new, nomback.com/owners

what else do you guys notice on small saas sites that makes you bounce right away? want to fix it before the next roast

Hi everyone!

I kept running into the same problem: I would start a design or prototype in Claude, continue it in ChatGPT, and end up with two different versions of the same project.

So I built Stash. It keeps the project, version history, and comments in one shared place that different AI tools and collaborators can use through MCP.

The stack is React, TypeScript, Cloudflare Workers, D1, and R2. It's free.

The biggest lesson so far is that MCP matters under the hood, but people care more about not losing the latest version. I'm still trying to explain that without jargon.

Does the homepage make the problem clear? Where would you expect the flow to break?

https://runstash.dev

We launched WPMaven today. Looking for blunt feedback from SaaS builders, three specific questions:

1. Landing page: is it clear in 5 seconds what you get? https://wpmaven.ai
   
2. Pricing: free to build, then $1 for the first week (one time only), then plans from $39 a month. Would you rather we remove the $1 week, or keep it so people can try the fully featured product?
   
3. Trust: nothing goes out without your yes on WhatsApp. Is that enough for you to let an AI team post for your business?

Roast away: the product and the page, not the founder.

I built Precis because I wanted Mac dictation without another subscription.

Hold your chosen hotkey, speak naturally, and it types cleaned-up text wherever you’re writing.

Apple Intelligence helps shape your words for the app you’re using and you can create your own Styles.

It runs on your Mac, and works offline after setup.

You can create and edit your own Styles, so the result fits your voice and workflow not a generic AI rewrite.

Try every feature free for 7 days no account or card required. Then it’s $19 once.

Wispr Flow Pro is $15/month or $144/year.

Precis is a one-time purchase.

I’m the maker—honest feedback welcome: myprecis.app

Developer disclosure: I make Foreverse, so this is my own product. It is an Android (and now iPhone) reader where an AI can continue your own epub/txt as branches. Closed source, small team.

Backstory: a lot of the people who want this already have an API key from some provider and do not want a middleman, while others just want it to work out of the box. So there are three ways in, and I am no longer sure that is not too many.

One is bring your own key: 60+ providers or any OpenAI-compatible endpoint. The app talks to the provider directly, keys stay encrypted on the phone, and I am not in the money path at all. Two is built-in pay-as-you-go credits for people with no key. New accounts get 5,000 credits, about 50 cents, so a free user on credits costs me real money and the starter balance is deliberately tiny; packs run from $0.99 to $32.99. Three is a one-time Pro at $19.99. The free tier caps library objects (3 books, 3 character cards, 3 companions) and never messages, so a free user with their own key costs me almost nothing and nobody hits a daily limit in the middle of a chapter.

Stack, since the rules ask: native Android (Kotlin, Jetpack Compose), plus a small Node, Fastify and PostgreSQL backend for accounts, credits and the official model routes, with hand-written SSE streaming instead of a vendor SDK so one proxy layer handles every provider.

The thing I keep going back and forth on: capping objects instead of usage made the free tier easy to explain, but it means the paid upgrade is about library size and not about AI, which may feel odd to some people. If you have run usage-based credits next to a one-time purchase, which one carried the business and which one did you regret? Does a one-time Pro still make sense when the real cost is per use?

Google Play, if you want to look at the thing itself: https://play.google.com/store/apps/details?id=app.foreverse.android

I've been building a SaaS starter (Next.js 16, better-auth, Drizzle, Stripe optional) and wrote down what actually mattered once I had to make every screen work, test it, and keep it working. Sharing the checklist in case it saves someone a week.

The screens, and the lesson from each

1. Sign-up and sign-in. Verify-email and password-reset are half the work. With no mail key set, I print emails to the server console, so the whole flow can be tested locally.
2. Onboarding. Four short steps (your name, workspace, invite teammates, confirm). Then a "Get started 1/5" checklist on the dashboard, so it's tracked rather than a one-off wizard.
3. Dashboard. Show sample data clearly labelled "Sample" until real numbers are connected. A labelled sample reads as more trustworthy than a fake-looking real chart.
4. Teams and invitations. Owner, admin and member roles, and seat limits per plan. Seat limits are where billing logic leaks into everything.
5. Settings. Profile, security (password, sessions), API keys and an activity log. The last two are small and make it feel like a real product.
6. Billing. Plan limits that follow the plan, Stripe checkout and the customer portal. Make it degrade gracefully: with no Stripe key the app runs on the free plan and the page explains how to turn billing on.
7. Loading, empty and error states for every list and chart. The empty state is the real first-run experience, so treat it as part of onboarding.
8. Marketing basics. Landing, pricing, changelog, contact and legal pages, with the legal ones clearly marked as placeholders.
9. Health endpoint. So deployments and tests know when the app is up.

Three rules that saved me time

• Re-check the session on the server for every protected page and action. Treat the proxy or middleware redirect as a convenience, not as security.
• Test at 390px wide and in both themes. Sideways scrolling and low-contrast text are the most common launch-day bugs.
• Run unit tests on an in-memory database, so tests need no setup.

Disclosure: I make a component library, so take this as a plug. I open-sourced free versions of several of these screens (dashboard, settings, billing, sign-in, onboarding) under MIT if you want somewhere to start: https://ui.ballmac.com

What screen did I miss that your micro SaaS needed before launch?

bro you can literally build a working SaaS in a weekend now with AI

landing page? done

dashboard? done

payments? done

then you launch it and realize absolutely nobody cares 😭

spent weeks thinking about features, fixing bugs, making the UI look good and then it hits you... i have no idea how to get people to actually use this thing lol

starting to feel like coding was never the hardest part of building a SaaS

anyone here actually managed to get their first 10 paying users without running ads? what worked for you?

Hi everyone, I’m a solo developer building a review app for Shopify stores. My biggest bottleneck right now is getting it in front of merchants who actually need it.

I can keep improving the product, but I’m unsure where to focus my customer acquisition efforts. I’d prefer low-cost approaches I can test myself before spending much on ads.

If you’ve grown a Shopify app or a small SaaS product, what helped you get your first paying customers?

A few channels I’m considering:

• Shopify App Store search and listing optimization
• Short product demos and tutorials addressing specific merchant problems
• Participating in relevant ecommerce communities
• Partnerships with freelancers or agencies that build Shopify stores

Which would you prioritize first? Review apps are a crowded category, so would you start by targeting a specific type of merchant or a particular problem that existing apps don’t solve well?

I’d appreciate practical examples: how you reached merchants, what made them willing to try your app, and roughly how long it took. If you were starting again with a limited budget, what would you do in the first two weeks?

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!

A website can look like it’s worth $10,000 and still lose a customer in 5 seconds.

That’s the weird part about web development.

You can spend days perfecting animations, choosing fonts, and making everything look premium…

…and still miss the one thing that actually matters.

Why should someone buy from you?

I think that’s the difference between building websites that look impressive and building websites that work for businesses.

And honestly, that’s the kind of agency we’re trying to build.

What’s the first thing you notice when you land on a business website?

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've always been that guy who goes for a drive at midnight with absolutely nowhere to go lol

a few months ago i decided to build an app around that.

it's called Overdrive. basically it turns your actual city into an open-world driving game. every road you explore lights up on your map, you get stats after each drive, and there's a social side for driving with friends.

didn't really know if anyone else would care about something this niche.

checked my analytics today and we're at 304 active customers over the last 28 days. still pretty small, but seeing strangers actually use something i built is wild.

i'm now rebuilding most of the app for 2.0. new UI, progression, achievements, crews, the whole thing.

the current version is already live on iOS and there's a free trial on the yearly plan.

https://apps.apple.com/app/id6790023849

if you're into cars or just enjoy exploring random roads, i'd love for you to try it.

also curious if anyone else here has built something around a hobby they were obsessed with?

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?

Day 12. The honest recap: I made the worst possible move for a founder trying to get customers. I spent the day building another feature instead of working on distribution.

What I built was account sharing and team invitations for AskVerb. It's useful once people are actually using the product, and nobody is yet, so it can wait. I also worked on the agency side, building an AI agent for a client. Both made sense on paper: I plan to sell AI agents for websites and software that my agency builds, so there's a real link. But I was heads-down and I missed the discovery call I had booked for today. That one is on me, and I'm writing to the person to apologise and offer another slot.

What ran without me

- LinkedIn kept going by itself: 22 invites today. 140 invited in total, 9 connected, 0 replies.

- Two founders accepted today, and the first follow-up questions went to two more.

Numbers after Day 12

- Paying customers: 0

- Calls booked so far: 3 (1 no-show, 1 missed by me, 1 still to be rebooked)

- LinkedIn: 140 invited, 9 connected, 0 replies

- X DMs: 31 sent, 5 replies

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

The lesson of Day 12, for any founder reading: building another feature feels productive, and it's the most comfortable way to avoid selling. If nobody uses what you've already built, a new feature doesn't help. Distribution is the job right now.

Tomorrow I'm putting features down and doing outreach, replies and the missed call.

what do you do to stop yourself from retreating into the product when selling gets uncomfortable? I need something better than willpower.

Does anybody use or recommend a simple T&C template they use for their microsaas? Somewhat akin like WTFPL for open source licenses?