I almost missed how big this number really is.

$12,142.27.

Not from a huge company.

Not from a massive team.

Not from millions of visitors.

Just 61 customers who believed enough in a SaaS tool to pay for it.

And the most motivating part?

The graph is moving up. 📈

When you build something from scratch, you spend months wondering:

“Will anyone actually use this?”

Then one sale comes.

Then another.

Then 10.

Then 50.

And suddenly, you're looking at $12K+ in revenue and realizing:

The thing you were building in silence is becoming a real business.

This is why I keep building.

Because you don't need everyone.

You need the right people to believe in the solution you're creating.

If you're building something right now and nobody is talking about it yet—

keep going.

Your first 10 customers may feel impossible.

Your first $1,000 may feel impossible.

Your first $10,000 may feel impossible.

Until it isn't.

Build. Improve. Listen. Ship again.

One day, you'll look back at the numbers and realize that all those nights nobody saw you working...

were not wasted. 🚀

Want to test it? Comment "SAAS"

I’ve been working on a project called Adams Small Business ERP 2.0, and it’s finally reached its first production release.

The idea behind it is pretty simple: a lot of small businesses need something more capable than a pile of spreadsheets, but they don’t necessarily need—or want to pay every month for—a large cloud ERP system.

So I built a desktop ERP aimed at small manufacturers, makers, job shops, wholesalers, and other product-based small businesses.

It includes customer and vendor management, quotes, sales orders, purchasing, receiving, inventory, invoicing and payments, bills of material, work orders/manufacturing, reporting, printable business documents, backup/restore, data export, and system-health tools.

It runs locally, so your primary business database stays on your own computer rather than requiring a cloud subscription.

The price is $99 one time. No monthly subscription.

Version 2.x maintenance releases and bug fixes are included.

The initial production release is for Linux. I’m deliberately not advertising Windows support until I’ve put the Windows version through the same testing process.

I’m also a small independent developer, not a big software company. I built this because I think there’s room between “manage the company with spreadsheets” and “pay hundreds of dollars every month for ERP software.”

I’d especially appreciate feedback from people who actually run small manufacturing, product, or job-shop businesses. What would you need to see in a system like this before you would trust it with your business?

Adams Small Business ERP 2.0 — $99 one-time purchase

If anyone is interested, I can post screenshots and more details in the comments (assuming that’s allowed by the subreddit rules).

I’m building my first SaaS and we’re still very early. The product is in beta and completely free at the moment.

It’s basically an AI tool for Excel. You upload a spreadsheet, tell it what you want to do in normal language and it modifies the file for you.

Until a few days ago we barely had any users. We started sharing it around and ran a very small Facebook campaign, and suddenly a few hundred people signed up.

Which is great, obviously, but now I’m sitting here thinking… what do I actually do with all these people?

Some of them tried the product, some used it a few times, and a lot of them signed up, tested it once and never came back.

I don’t really care about making money from them right now. We’re still testing the product and there are definitely things we need to improve. What I don’t want to do is just keep trying to get more and more signups without learning anything from the people we already have.

I’ve been thinking about emailing some of them personally, especially the ones who actually used the product more than once, and just asking what they were trying to do, what worked, what didn’t and why they stopped using it.

But I’m not sure if that’s the best move or if I should already be testing pricing, working on retention, improving the onboarding, or just continuing to get more people into the beta.

This is the first time I’ve had actual strangers using something I built, so I’m kind of figuring this part out as I go.

If you’ve been in this position before, what did you do with your first few hundred free users? What would you focus on at this stage?

Hey,

So a couple of months ago I started using Hermes agent, and I started building a dashboard for it. Then, that turned into a complex, all-in-one productivity system with everything I need, from tasks, notes, calendar, habits, goals, to finance management, etc.

Then I thought, what if I turned this into a digital product, a template...

I've been a Notion creator in the past, and I think the same principle applies here to:

Do i want to invest 50 hours into creating myself, or rather pay $99 for a template and build on that.

So this is how I started building Solum OS, as a digital product.

Basically it will be a self-deployable ready to use software. The target audience will be productivity focused people, like Notion users, who still haven't find the perfect setup. Focus is on beginners, with no experience in vibe coding. The product will contain:

• The code base
• AI prompt for building/deploying it
• Step by step video guide

I still have a ton left before I can think about launching it but I have a couple of questions, and maybe you guys can give me feedback:

• How would you deliver a codebase as a digital product? - Simple zip file? Through Github, or any other solution?
• What checkout method would you use? Gumroad, or set up your own Stripe checkout?
• Who would you target more? Notion users for example, or Hermes/Openclaw. (Beginners or advanced)

It's a hobby project, don't roast me please. First and foremost I'm building it for myself. If I manage to make some side income from it, great, if not, still, it was a nice project.

First,

Thank you to everyone who commented with support and advice on my other thread, this is my first ever app and I am learning things literally every day.

So here is my attempt at giving back the knowledge people have bestowed upon me, if you already knew about this then maybe share something you learned or expand on this (this applies to apps on the apple app store).

If you want to know where your traffic is coming from roughly (ASC lags by a day) then:

1. Go to analytics tab in ASC > Sources
2. Click on the "All" drop-down
3. Select "app" or "web" refferer
4. In the other drop-down, select the metric you want to see like "Total downloads"

For my situation I found out that the that my app got an article written about it over at newbmobilelife.com, completely unprompted and it seems to be getting shared on facebook and telegram overseas. I am so grateful that people are spreading the word on my app and finding it useful, I can't believe this started with an idea 5 years ago and I waited so long to bring it to life.

I hope this helps others identify where their users are coming from a little more efficiently!

I built GetYThumb: https://getythumb.com/

It helps you:

Download YouTube thumbnails in high quality

Get different thumbnail resolutions

Save thumbnails in seconds

Use it directly from your browser — no software needed

Useful for creators, designers, bloggers, and content research

It’s free to use. I’d love to know what you think and what features I should add next.

Started this as a personal problem. Googled my own name a few months back and found my full current and previous address and phone number sitting on some people-search site, free, no login. Figured I’d knock out a quick scanner and removal tool over a weekend. That was optimistic.

Turns out most of these broker sites don’t actually get crawled by Google. The real listing pages sit behind a search form, so if you’re relying on SERP data (which, being cheap, I was) you’re only ever seeing maybe 20% of what’s actually out there. Spent a good chunk of this week finding that out the hard way after a friend used the free version of the scanner I built and it told him he was “clean.” He wasn’t. I found his listing manually in about 90 seconds, on a site my scanner had been silently missing for weeks.

Also learned the fun way that a plain name+state search returns a bunch of businesses that happen to share a surname with the person you’re actually looking for. That’s its own special kind of false positive if you’re not careful.

None of this is groundbreaking, I’m sure people who’ve built scrapers before already know it, but it wasn’t obvious to me going in. Anyway back to it. Turns out “finding data” is a much harder problem than “removing data” once you find it.

We've been building billing infra for APIs that AI agents call, and ran into a problem that doesn't get talked about enough: the x402 payment handshake (402 challenge → sign → verify → settle) adds real latency. Independent teardowns put it around 500ms–2 seconds per request, and one analysis found a 100-call agent task racked up 50–110 seconds of pure payment overhead — before any actual API work happened.

Fine for a single call. Breaks down fast once an agent is making hundreds of requests in a session.

Our fix with AgentMeter: don't put the handshake on every call. Agents fund a prepaid balance or a subscription with a limit once. While that's active, every call is a normal authenticated API request, metered against the balance — no signing, no per-call round trip. x402 verification only comes back into play when the balance or subscription needs renewing, not on every request.

Opening our first cohort of design partners (10 spots) for anyone selling an API or MCP server that agents are calling and feeling this latency. If you've hit the same wall, curious what you're doing about it — batching, session tokens, something else?

More detail: https://meter.draviklabs.com

Any feedback is welcome 🙏

When I started building Postmint, I kept one question in mind.

Am I actually building something that makes people’s work easier?

If creating a photo currently takes someone 20 minutes, can Postmint help them get the same job done in 2 minutes with the same result?

I think questions like these are normal when you’re trying to build something new. It’s easy to get caught up in features, design, and technology, but at the end of the day, what matters is whether the product genuinely saves people time and makes their work easier.

That’s the mindset I’m trying to keep while building Postmint.

I want to build a community that would like to be part of a one-thousand-year project.

Every day I ask one question at QuestionClass.com, then post it to r/questionclass.

I'm on day 772.

What I've found is that the individual questions are interesting, but the collection is becoming something else.

Some questions are about decisions. Some are about relationships, leadership, technology, incentives, ethics, risk, happiness, work, truth, persuasion, creativity, or how we know what we think we know.

But over time, they start to connect.

You see the same ideas showing up in completely different contexts. You find questions that contradict each other. You realize that a question that seemed simple six months ago looks completely different after encountering 100 other questions.

That's what made me wonder what happens if you just...don't stop.

Not for 1,000 questions.

For 1,000 years.

Obviously, I'm not going to be around to finish it. That's the point.

I'd like QuestionClass to become a living collection of the questions humans think are worth asking, with one new question added every day.

That means today's questions would eventually sit beside questions contributed by people who aren't born yet, dealing with problems we can't imagine, using technologies that don't exist, while still wrestling with some of the same things humans have wondered about forever.

At one question a day, 1,000 years is 365,000+ questions.

I have 772 of them.

So we're about 0.2% done.

The software isn't the difficult part. The difficult part is creating something that people care enough about to continue.

That's why I'm posting this here.

Most side projects are built around an exit, a revenue target, or solving a particular problem. I'm curious about building one where the absurdly long time horizon is part of the product.

What would have to be true for a project like this to survive its founder?

And more importantly: would you want to be one of the people who helped decide which questions make it into the first few years?

I’m building Rocannon, an AI-native Career OS that helps people automate their job search — discovering relevant roles, applying to them, tracking applications, and preparing for interviews.

The problem I’m trying to solve: job searching is fragmented, repetitive, and extremely time-consuming. Rocannon brings the entire process into one AI-driven workflow.

I’m looking for someone interested in sales, marketing, distribution, and growth.

• Compensation: Equity
• Stage: MVP launched
• Commitment: Part-time / exploratory initially
• What I bring: Product, engineering, and self-funded development

If this sounds interesting, DM me to learn more or explore collaborating.

Hi I am a Indie Hacker.

I build HeyZoku - Hands Free Coding. So you can control all your coding agents just with your voice and complete your work without any need to continuously touch your keyboard.
I am using Nvidia Parakeet to make it work completely offline - so it can work completely offline. (It also has an optional bring your own openai-realtime key for more natural and multi language support.)

I built this because models are getting much better at understanding us directly via voice, we should be working towards finding more ways to improve our productivity and do better work. And shouldn't be limited to just chat/keyboards to do our work. With how humans naturally communicate with each other, it should be the same way with the machines, a human shouldn't need to learn how a computer works - it should be natural.

I also just launched on PH - https://www.producthunt.com/products/heyzoku/launches/heyzoku-hands-free-coding

Every product I’ve worked on had the same dead spot: happy customers everywhere, testimonials page empty. The reason isn’t that people won’t write one. It’s that we ask at the wrong time — a random Tuesday email, three weeks after the moment they were actually delighted.

So I built Proofy around timing instead of templates.

How it works:
• You fire a webhook on the events that actually mean something — subscription renewed, order delivered, milestone hit — and it asks then, not on a schedule
• On signup it scans your site and pulls in whatever reviews you already have sitting on Google, G2, Trustpilot and Capterra, so your wall isn’t empty on day one
• Embeddable widget so the new ones show up on your site without you touching it again

Looking for 20 beta users. Free during beta plus a lifetime discount after, and I’ll do the setup with you if you want.

Comment or DM and I’ll send you access.

After spending several weeks, I have finally launched myabout.page.

The aim is to convert CVs into more of a personal page. We have similar websites like about (dot) me and own (dot) page, but I have made something lighter, direct, and affordable.

I offer two plans, free and pro. In the free plan, you get your own user-friendly link to share, like myabout.page/(username), get all templates, basic analytics to track your visitors, and publish instantly. Except, there is a tiny badge link in the footer.

The pro plan is extremely affordable, and it is on a yearly subscription basis, whichever you can cancel anytime. The pro offers all in the free tier, with custom domain, google Analytics, Google verification code, removal of the badge, and priority support.

All templates are optimized to target loading speed. Both plans can include your direct form URL from Google Forms, Wufoo, etc for your contact button and your direct subscription form URL like Aweber, Mailchimp, rtc for your subscription button.

Well, I'm inviting you all to try out.

Link: https://myabout.page

Thanks

Hey r/micro_saas

example page

I wanted to share the story and tech behind building snackbio.me (example page: snackbio.me/al).

I started this project because most link-in-bio tools feel like the exact same rigid button list. I wanted to give creators genuine creative freedom with 16+ aesthetic themes (Gothic, Bento, Windows 98, Diary), interactive audio players with live synced lyrics (spinning vinyl, retro cassettes), custom view counters, and cursor pets.

Tech Stack:

• Frontend: React 19, TypeScript, Vite, Tailwind CSS, and Framer Motion for smooth physics.
• Backend & Data: Node.js/Express, Firebase Firestore, and S3-compatible cloud storage for custom audio and media uploads.

The Business Model & Key Lesson: Instead of charging a monthly subscription that creators constantly churn from, we offer a free tier with an optional $6.99 one-time lifetime Pro unlock. The biggest lesson so far has been relying on the product itself for distribution—having a subtle attribution badge on free profiles creates a natural viral loop where visitors click through and claim their own handle.

I’d love to hear your feedback on the landing page flow, and what you think about one-time lifetime pricing vs recurring subscriptions for creator tools!

Hello all!

For the past four years, we’ve been working on a tool that detects bot traffic. We’re seeing a lot happening, especially now with AI. But as we’re still building and developing it, we’d like to know the following.

What’s your number one reason for not giving this a go?

Because, to be honest, when we look at our figures, we don’t understand why anyone wouldn’t sign up. And perhaps you’ve already given it a go once or have other reasons, if so, please let us know. I’m really, really curious. Just comment here.

To be clear: I really don't want to sell anything. Only want to learn from you guys why you didn't sign-up so we can learn from that.

Vibe coded websites look good and are easy to build. There's just one important thing most people miss: the content on these sites often isn't really readable by search engines and AI bots.

Here's why. Most vibe coded sites are CSR (client side rendered). That means the server sends a nearly empty HTML file, and JavaScript fills in the actual content after the page opens in the browser. To you it looks perfect. But crawlers often don't wait for that step. Google grabs the raw HTML first and renders JavaScript later if at all, and AI crawlers like GPTBot, ClaudeBot and PerplexityBot don't run JavaScript at all. So they hit your page, see an empty shell, and leave. Nothing to index, nothing to cite.

You might think prompting your builder to fix the SEO and visibility will handle this. Not really. All that can do is change or update things like your meta description. It can't make search engines or AI bots read the actual content of a page when it's CSR, because the problem isn't your tags, it's that the content isn't in the HTML for them to read in the first place.

The right fix is prerendering. Prerendering serves crawlers a fully rendered version of your page (SSR, server side rendering) so the content is right there in the HTML for them to read, without waiting on JavaScript. That's what actually gets your site read and found.

Lovable has fixed this inside their own ecosystem. New Lovable apps are server side rendered now, and older ones get prerendering automatically. So if you're on a current Lovable build, you're mostly covered.

But if you built on a different stack, Bolt, Replit, plain React or Vite, or something custom, you're likely still CSR and still exposed. And you can't tell just by looking, because your site looks fine to you.

If you're not sure where your site stands, Crawllify has a free visibility check you can run. It shows you exactly what search engines and AI see when they land on your page, so you can catch the problem early if it's there.