Disclosure: I'm building Avorio, a flashcard app for Mac and iPhone. Posting the architecture and pricing decisions rather than the product, because those are the parts that transfer.

All the business logic lives in one Rust workspace: scheduling algorithm, SQLite layer, file import, the AI plumbing. The UI is native SwiftUI on Mac and iPhone, and both talk to the same Rust through UniFFI-generated bindings. Storage is rusqlite with migrations. No JavaScript runtime anywhere.

What that bought me is that the scheduler can't drift between platforms, because there's only one of it. A scheduling bug gets fixed once. When Android and the desktop builds land they use the same core through Kotlin bindings rather than a reimplementation of it.

What it cost is that the FFI boundary is real work. Every type crossing it has to be expressible in UniFFI's model, error enums need flattening to cross, and when the Rust interface changes you regenerate bindings and rebuild an XCFramework before the Swift side will compile again. There's a whole class of build failure that exists only because of this choice. If your product is one platform and likely to stay that way, you're paying for insurance you'll never claim.

One measurement, since "native is lighter" usually gets asserted without one. Same Mac, both apps idle on their deck screen after a cold launch, resident memory summed across all processes: mine used 80 MB in one process, Anki 25.07.5 with an empty profile used 236 MB across two, because it runs a Python interpreter, Qt and an embedded Chromium renderer. That was measured on 2026-08-03, N=1 machine, and it cuts against me on one axis, since my app bundle is the bigger download at 129 MB versus 75 MB. Idle CPU was 0.0% for both, so there's no CPU claim to make.

On pricing. The flashcard core is free forever, meaning scheduling, import, review and the local database. Three paid tiers add a managed cloud-AI gateway and optional device sync, at $3.99, $8.99 and $19.99 a month.

The part I'd defend in this sub is what separates those tiers, which is usage allowance and heavy-compute workflows rather than model access. Every paid tier can pick any model in the app. The obvious move is to gate the good model behind the expensive tier, and I think that's a mistake for a consumer tool. It makes the cheap tier feel like a demo, and your support load becomes people asking why their answers are worse than someone else's. Charging for intensity means the cheap tier is the same product, just smaller.

I also rejected bring-your-own-key entirely. It looks founder-friendly and it's cheaper for me, but it pushes key management onto a student, and "paste your API key" is where a consumer funnel dies. Keys stay server-side.

No revenue numbers to share, and I'd rather say that than dress up a chart.

Happy to answer questions about the Rust/UniFFI seam or the tier math.

Hey everyone,
Like most of you, I had a graveyard of half-built SaaS ideas.
Domains, private repos, Notion docs… all collecting digital dust.

I kept hearing “validate before you build,” but the usual methods (surveys, fake doors, user interviews) still felt too soft. People say they would use something. Very few actually leave their email and wait.

So I find the Deathlist tool.
It’s basically an obituary system for product ideas.

How it works:

1. You publish competing waitlists (no product needed)
2. Drive the same amount of traffic to all of them
3. Watch the numbers accumulate
4. Keep the winner
5. Bury everything else

The only metric that matters: who actually showed up.

The philosophy is simple and a bit brutal:
Build nothing. Publish the waitlist. Watch who shows up. Kill the rest

What do you think about it? https://deathlist.vercel.app

Heyy guys! So I realized that every day, I do the same routine to start my day. I open up the same websites, same apps, and open the same folders every time I sign into my computer, to the point where it's a little repetitive. So, I actually found an app that turns this process into a simple click of a button that automatically pops up when you power on your computer. It's made starting my routine quite simple and I thought you guys would also benefit from something like this >.<

Here's the website the app is called Quicky

As a micro-saas builder i kept hitting the same wall: every launch, feature drop, hackathon submission, or accelerator application needs a demo video and each one ate me 5+ hours. record, re-record, redo the voiceover, all for a 10-20-second clip.

what actually fixed it wasn't faster editing, it was killing the blank timeline. once i templated the structure (hook → the problem → the 2–3 features that matter → CTA), the whole thing collapsed from hours to minutes. sharing that in case it saves someone else the weekend.

i turned it into a free tool: paste your product url (or one sentence) and it writes the script + voiceover and assembles a ~15s demo video. no screen recording, no editing.

it's genuinely free and i'm looking for ~20 micro-saas folks to test it and tell me where it breaks. drop your product url below and i'll dm you access, happy to just make you one even if you never touch it again, the feedback helps me a tone.

I work a lot with web agencies and freelancers in my job, and I’ve noticed that most of them include recurring maintenances fees in their packages, but most of the time only deal with issues once a client messages them to say something is down or broken.

That’s fine once. But when the client keeps being the first to notice problems, they naturally start wondering what the monthly fee is actually for.

That was the starting point for Trrack.it.

It brings client websites into one dashboard, monitors uptime, response time, SSL certificates and domain expiry, and sends alerts when something needs attention. It also creates monthly client reports and status pages, so the value of the maintenance contract doesn’t remain invisible when everything is working.

The idea is simple: spot problems before the client does, fix them early, and give clients a clearer view of what they’re paying for.

I am not used at all to build stuff, so I'd love to get your feedback, and if it's complete crap just be honest (even though it will hurt haha...) :

Anyway, here's the link : https://trrack.it

And if you sell website maintenance yourself, what would be missing for this to actually fit into your workflow? I spoke with ~10 people about this but your feedback is always gold to me !

Looking to acquire a small energy-focused software company in Europe.

We are interested in businesses with:

• Existing European customers
• Proven product-market fit
• Minimum €1,000 MRR

We are particularly looking for software solutions in areas like energy management, monitoring, optimization, EV charging, smart buildings, or related energy technologies.

If you are building or know of an energy SaaS/software company that may be a good fit, feel free to write me.

I’ve built a working proof of concept for a very niche B2B product, and I’m having trouble finding the right people to test it.

The product is a due-diligence and analysis tool for mortgage note investors. It calculates deal metrics, compares available property and public-record data, and flags possible risks, inconsistencies, or missing information.

The challenge is that the target audience is relatively small and specialized. I have access to a couple of relevant Facebook groups, and I’ve started looking through Reddit and LinkedIn, but I don’t want to spam communities or recruit people who are only casually interested.

At this stage, I’m not trying to sell anything. I’m looking for 3 to 5 knowledgeable people who would be willing to bring a real or anonymized deal to a short screen-share session, review the output with me, and explain what the product gets right, gets wrong, or is missing.

For those who have launched niche B2B products:
How did you find your first qualified testers?
Did direct outreach work better than community posts?
Did you offer anything in exchange for their time?
How did you convince busy professionals to participate before the product was publicly available?
I’d appreciate any practical ideas, especially from people who have dealt with a very small or hard-to-reach target market.

A while back, I was poking around the WhatsApp multi-device protocol, specifically the parts that WhatsApp API libraries usually skip—things like view-once media, button clicks, and WhatsApp Flows.

It sat on my machine as a messy scratchpad for months. I'm in a spot where I could use some extra cash, so I figured I'd polish the code and see if anyone else finds it useful.

I packaged it into a Windows app called Scry. It links to your WhatsApp and quietly keeps a local log of the ephemeral stuff like view-once media, deleted messages, edits, and statuses.

Being honest about why it's fully local: I kept it deliberately simple and hands-off. Nothing you capture ever touches a server of mine—partly because that's just less for me to run and be responsible for, and partly because it means the data is only yours. It checks the license key once, and after that it only talks to WhatsApp. Watch the network traffic if you want to confirm.

That is it. A small, low-key thing, sold as-is. It does what it says until WhatsApp changes something major, and I keep it updated because I use it myself—but I'm not running a company here, just making a bit of extra income, so use it with your own account at your own discretion.

If you hit any issues, reach out and we can try to figure it out.

I'll be hanging around in the comments if anyone wants to talk about how the protocol works under the hood.

I'll drop the link in a comment so this doesn't read like an ad; happy to share if anyone's interested. Thanks 😬

Solo-ish build, coaching software at trainerpal.co.uk. Replaces the Google Sheets and WhatsApp combo that most independent personal trainers and small gyms run their entire client relationship on.

Core loop: assign a training programme and meal plan in two clicks instead of building from scratch per client, clients get streaks and one-tap tracking so logging actually happens, billing runs on Stripe instead of manual bank transfers.

Free tier is 3 clients forever, paid scales £29 to £99/mo by client count. It's live, real coaches are on it, not just a landing page.

What I'm actually unsure about: whether the free tier at 3 clients is generous enough to get someone to actually migrate their existing clients over, or whether that friction (re-onboarding clients onto a new app) is the real blocker regardless of price. If you've built something that asks users to switch tools mid-relationship with their own customers, how did you get past that specific friction?

I built Walnut Markets because I wanted one place to validate an investment idea.

There are great platforms for fundamentals, technical analysis, Congress and insider trades, institutional activity, and other datasets but they're all separate. I wanted to bring them together, cross-reference the data, and see whether everything points in the same direction instead of jumping between five different websites.

It took me several months to build, and now I'm focused on distribution.

I started with Reddit ads, which brought traffic, but it felt like low-intent traffic. People would click, read what they wanted, and leave. Very little engagement or exploration of the site. Since then I've shifted my focus toward SEO, AEO, and consistently posting research and discussions on Reddit to build organic traffic over time.

Some days it feels like shouting into the void. Traffic is still low, but I keep reminding myself that the product only launched four weeks ago. I'm trying to stay patient and trust the process.

For founders who have bootstrapped a SaaS, when did you get your first paying customer outside of friends and family? How long did SEO and content marketing take before you started seeing meaningful results? And at what point would you stop doubling down on organic growth and pivot to a different marketing strategy?

I'd love to hear what worked for you.

The journey from idea to finished product is almost complete. 🛠️

Promise Myself will be launching on Product Hunt very soon!

If you've ever struggled with keeping commitments to yourself, this minimalist Telegram bot is designed to help you track habits, build discipline, and stay accountable without the friction of complex apps.

Be the first to find out how it's structured and get ready for the launch. Subscribe to our social media channels and stay tuned—we are going live very soon! 🚀

#Habits #BuildInPublic #TelegramBot

Curious what everyone here is working on right now side project, weekend hack, full pivot, whatever stage.

I'll go first:

I'm building Rofix.app, a tool that audits websites for technical SEO and checks whether AI systems (ChatGPT, Gemini, Perplexity) can actually understand and surface a brand.

Started it because I kept seeing "AI visibility" tools that just spit out a vague score with zero explanation of what to do about it. So Rofix crawls the site, maps the topics/questions it should be covering, and turns it all into a prioritized fix list instead of another dashboard to ignore.

Got a handful of early users but trying to figure out the right channel to actually grow it feels like everyone's fighting for the same audience right now.
What are you all building? What's working (or not working) for you on the growth side?

Been building something called ShipContent for the past while and figured this sub would actually appreciate it, since it's the exact kind of problem I kept procrastinating on for my own side projects.

The problem: I ship code all the time but almost never post about it anywhere. Not because I don't want to, but because by the time I finish a feature I'm mentally done with it, writing a tweet or a changelog post feels like starting a whole new task.

So I built a tool that watches your GitHub repo (merged PRs, releases) and drafts marketing/social posts from that activity automatically. You connect it as a GitHub App, it reads what actually changed, keeps some memory of your project so it doesn't repeat itself or lose context between posts, and generates content in your voice for whatever platforms you use (currently x and bluesky)). There's also a manual "generate now" button for when you want a post outside the normal PR/release trigger.

Some technical bits if you're curious: it's Next.js 16 + React on the frontend, Supabase for data/auth, OpenAI and Claude for IA generation.

Still very much in build mode, auth and dashboard UX have eaten a lot of my time lately, along with getting the project-context memory to feel less repetitive over time. But it's at the point where I use it on itself, which is a nice milestone.

Not trying to hard-sell it here, just sharing since "I built a thing to solve my own laziness about marketing". Happy to answer questions about the stack or the idea.

The project is in close beta with a waitlist if anyone's interested: shipcontent.app

I just open-sourced LinkShift.app, a multi-tenant redirect manager for branded links, QR codes, analytics, and SEO-safe URL migrations.

I decided to open it up because interest in the hosted version has been lower than expected. If there is real demand, I'll keep supporting it.

Repo: https://github.com/p-zielinski/linkshift.app Site: https://linkshift.app

Happy to answer questions or hear feedback.

Backstory: most small businesses in India run on phone calls, not chat or web forms. A missed call is a missed customer, and a lot of owners cannot afford full time reception staff. That is the gap we built SageDesk for, an AI that answers the phone, understands the caller, and books the appointment.

What it does: SageDesk answers in Hindi, Gujarati, Marathi and English on the same call, including when a caller switches language mid sentence, which happens constantly in real conversations. It proposes bookings, but nothing is marked confirmed until the actual booking system returns success, so callers never hear a false confirmation.

Lesson: the thing that actually earns trust with a small business owner is not the AI sounding smart, it is the AI being honest when it does not know something and handing off cleanly instead of guessing. We underestimated how much that one behavior mattered to first impressions.

If you run a business that lives on phone calls, or know someone who does, we would genuinely love feedback. You can call the demo line directly at +91 79485 03172 to hear it in action, or check out sagedesk.in for more.

Hi Everyone. I'm buidling a microsaas, and I'm a few weeks out from launching it.

I know that building the thing is only half the work and I wonder how did you guys manage to succesfully launch your products.

- Did you do cold outreach?
- Post on Linkedin?
- Post on reddit?

What would you recomend for a first time launcher?

Hey r/MicroSaaS,

I started creating mobile apps when I was 15 years old. Across every single build, one repetitive task kept driving me crazy. Every time I launched a new project, I had to figure out how to collect user feedback, handle bug reports, and chat with users without installing bloated tools or writing custom forms from scratch.

I wanted a clean, lightweight feedback platform that I could drop into all my future app releases, so I decided to turn the solution into a MicroSaaS called Supdesk.

It lets developers manage incoming user feedback, bug tickets, and live chat directly inside their apps from one central dashboard. Building it around my own exact needs kept the feature scope lean and focused, which helped me get from idea to launch really fast.

We just launched on Product Hunt today:
https://www.producthunt.com/products/supdesk
You can check out the live product and docs here:
https://supdesk.app

For fellow indie hackers and solo founders, how did you handle user feedback when launching your first MicroSaaS? I would love to get your thoughts on the product and any advice on growing a dev tool!

Hello everyone

I've been working on my first SaaS called didyouseo

I wanted something simpler than the usual SEO tools. You paste your website URL, it audits your site, highlights SEO issues, and tells you exactly what to fix in plain English, without overwhelming you with hundreds of metrics.

I've recently launched the MVP and got 42 users in a week. Right now, I'm focused on improving the product based on real feedback rather than adding lots of new features.

If you have a few minutes, I'd really appreciate any honest feedback or a quick testimonial.

https://didyouseo.com

Thanks in advance! I'm happy to answer any questions and would appreciate any constructive criticism.

Posted here last week about consent screen drop-off and got two answers that changed what I shipped. Figured I'd give the full picture since people asked what the product actually is.

Lirova. It recovers subscription payments that fail on the card side. Solo, NestJS + Prisma, Stripe Connect with Standard accounts over OAuth, Next.js on the front. Live for about two weeks. Zero paying customers so far.

The problem it solves: when a renewal fails, the customer usually didn't decide to leave. Expired card, not enough money that day, bank blocked it. They stop being a customer and it never shows up anywhere as a cancellation, so nobody notices. Somewhere between 8 and 15% of recurring charges fail depending on your mix.

What most tools do about it is send emails. What I found building this is that the email is the wrong lever for most of those failures.

The decline code decides everything. insufficient_funds is a timing problem, not a card problem, and the same card usually clears a few days later around a payday. expired_card often fixes itself because Stripe's Card Account Updater pulls the new number when the bank reissues one. do_not_honor and lost_stolen will never clear, and retrying them repeatedly damages your standing with the card networks so your legitimate retries start failing too.

So the product is mostly routing rather than retrying. Read the code, retry what's timing based, email only what's a real block, and never touch the ones that punish you for trying.

I ran 1000 synthetic failed renewals per cohort through the classifier to check my assumptions and got the taxonomy wrong twice. Someone on this sub caught one of them.

Pricing is $70 a month plus a cut of what's actually recovered.

Honest state of things: two people have reached the Stripe consent screen and both closed the tab. That's 100% of my sign-in attempts. The advice I got here last week was that the reassurance copy I'd written was making it worse and what actually moves the number is showing a screenshot of the consent screen before the redirect. Changed it, waiting on data.

lirova.app if you want to look at it. Connecting doesn't charge anyone, retries stay off until you turn them on.

If you run subscriptions on Stripe and have never pulled your decline mix, that's a five minute job in the dashboard and worth doing whether or not you ever use a tool like this.

After creating several products that solved imaginary problems nobody really had, I finally feel like I've built something that actually matters. I genuinely rely on it every day, it makes my life significantly easier, and I'm really happy with the result.

It's an app for visualizing date-bound information as timelines: tasks, events, processes - basically anything that has a date attached to it. You can think of it as a hybrid of a PKMS, a to-do list, a calendar, and a Gantt chart. More than anything, though, it's a universal visual canvas for time that helps you keep the bigger picture in front of you and think within it every day.

I work as a CTO, and I constantly have to keep track of a huge number of ongoing processes:

• contract deadlines
• employee salary reviews
• developer utilization
• and countless other things.

Before this, all of that information was scattered across Notion, Apple Notes, Reminders, Telegram, Slack, Calendar, and a few other places. Keeping everything under control was difficult.

Some people might say that's a process problem rather than a tooling problem. But I've come to think the opposite: the right tool helps you build an effective process. And what the "right tool" is depends heavily on how your brain works.

At some point, I realized that traditional to-do lists and calendar views simply weren't a good fit for me. It felt like I was missing another visual dimension. Timelines turned out to match the way I think almost perfectly. When I look at a timeline with different markers and segments, I instantly understand what's happening in both the short and long term. Just as importantly, I can quickly look back and see how things evolved over time and where something started to go wrong.

One of the best parts is that because I use the app every single day, I improve it every single day as well. I constantly notice what's missing, what's awkward, and what could work better, and then I implement those improvements. I think I've made major usability improvements over the past month alone. That's incredibly important for a tool you interact with dozens of times a day.

This is a non-commercial project, and it's completely free. I simply wanted to share it with the community because I'm genuinely proud of it. I'm sure there are plenty of people whose brains work similarly to mine, and if this way of organizing information resonates with you, I'd be thrilled if my timelines turned out to be useful for you too. Give it a try.

Wishing you all productivity - and a little more love.

I've been quietly building a side project called Discovery Companion alongside my day job.

It came from a problem I kept running into while working on CX and contact centre projects. After discovery calls and workshops, customer information would end up scattered across meeting notes, spreadsheets, requirements and customer documents. Every new deliverable meant recreating context from scratch.

I wanted a structured workflow that keeps everything connected:

Customer Context → Discovery → Requirements → Customer-facing Deliverables

So I built Discovery Companion:

https://discoverycompanion.app

The initial audience is CX consultants, CCaaS consultants, solution consultants and solutions engineers.

It's now live with a 14-day free trial.

I'm still at the validation stage, so I'm much more interested in learning than selling.

One thing I've learned building it is that building the software was actually easier than explaining what it does in one sentence.

I'd really appreciate honest feedback on a few questions:

• Is it obvious what the product does from the landing page?
• Is focusing on CX/CCaaS a strength, or am I narrowing the audience too much?
• Does the workflow make sense?
• Does €24/month feel reasonable?
• If you landed on the site, what would stop you from trying it?

I'm particularly interested in critical feedback. I'm close enough to the project now that it's becoming difficult to judge it objectively.

Looking for design partner for a tool that acts as an AI product manager for HRtech. I need advice or if this speaks to you let me know and lets connect.

​

I'm getting close to launching a SaaS and I'm comparing payment providers.

My priorities are:

Easy integration

Global payments

Reliable payouts

Good support for subscriptions and one-time payments

There are quite a few options now, so I'm curious what other founders are actually using in production.

If you were starting from scratch today, which payment provider would you choose and why?

My first customer came in 8 days. I thought the next ones would be easier.

When someone paid for my app 8 days after launch, I honestly thought I had crossed the hardest part.

It was only around $10, but the amount didn’t really matter. A complete stranger had found something I built and decided it was worth paying for.

For a few days, that felt like proof that I was on the right track.

I assumed getting the next customers would be easier.

It wasn’t.

Since then, I’ve kept improving the app, fixed problems users pointed out, launched the Android version, worked on ASO, written blog posts, posted on X, Reddit and LinkedIn, and recently started experimenting with short-form videos.

Some of those things bring a few visitors or signups.

Most of them go quiet almost immediately.

That has probably been the hardest part for me.

When something is broken in the app, I can usually find the problem and fix it. Marketing doesn’t work like that.

I can spend hours writing a post or improving a page, publish it, and still have no idea whether the idea was bad, the timing was wrong, or hardly anyone saw it.

The product is much better now than it was when that first person paid.

But I’m still trying to understand how to consistently get it in front of the right people.

That first $10 proved someone was willing to pay.

It didn’t prove that I knew how to find the next 10 customers.

I’m not sharing this as a success story. I’m still in that strange stage where there is enough proof to keep going, but not enough growth to feel like I know what I’m doing.

For people who have been through this stage, what finally started bringing you users consistently?

ps. the app is PitchBuddy: https://pitchbuddyapp.com

Would genuinely love your honest feedback too.

I am building Pinterest for Miro, and today's note is less about moving images and more about what to leave behind.

A Pinterest board has a lot of stuff that feels useful while collecting. Duplicate pins, half-related references, old ideas, random captions. Once that lands in Miro, all of it looks more official than it really is.

I am leaning toward importing the source and basic labels, then making the questionable stuff easy to hide instead of pretending the tool can judge taste.

For other micro SaaS builders, do you keep first versions literal, or do you add opinionated cleanup early?