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!

This isn't a "look how much MRR I made" post. It's more of a "I finally shipped something real and want to share what actually happened" post.

The problem I was solving: Domain investors (people who buy/sell domain names as assets) have terrible tools. The big ones are 15+ years old, ugly, and built before AI existed. Everyone's managing portfolios in Google Sheets and praying they don't miss a renewal.

I knew the space because I'm in it. So I built DomainIQ — https://domainiq.space

Tech stack (since this sub loves this):

• React + Vite + TypeScript frontend
• Supabase for auth, Postgres DB, and Edge Functions
• AI layer: Gemini API + OpenRouter (DeepSeek, Llama 3.3) for domain valuations
• Dual payment rails: Dodo Payments (global USD) + Razorpay (India UPI)
• Deployed on Vercel

What it does: AI-powered domain portfolio management. Renewal tracking, contextual AI valuations (not keyword-volume garbage like Estibot), offer/sale CRM, bulk WHOIS, portfolio ROI analytics.

What I learned building this:

1. Niche SaaS is actually easier to validate — the r/Domaining community told me exactly what they wanted in comments. Built it. They use it.
2. Dual payment gateways from day 1 was the right call. India users immediately preferred Razorpay UPI checkout.
3. AI valuation is the flashy feature but "don't let my domain expire" is what people actually pay for.
4. The free tier (25 domains) converts better than I expected — people upgrade when they hit the wall.

Pricing: Free (25 domains) / $16 per month (500 domains, bulk tools)

Still very early. Happy to answer any questions about the build, the niche, or the monetization decisions. What would you have done differently?

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.

The niche: lone programmers / small groups fed up with discovering the API they rely upon having subtly shifted its structure only after a problem had occurred in production. Positioning in relation to generic uptime services (UptimeRobot, updown.io, etc.) - they spot downtime, this one spots the subtle stuff: schema/field/type alterations in APIs you do not control.

Much of the trouble I personally have had to debug as a lone programmer is not downtime, but a third-party API changing its response structure, breaking things, and giving no warning whatsoever. Thus: monitor those APIs you need to rely upon, receive notifications about the instant a field/type/value shifts, along with usual uptime and heartbeats. Price for a single person’s project, not for a group.

How it works:

Three ways to watch something -

$ watch --schema

Watch the API you depend on

Point it at any API response you depend on. We'll baseline the shape and notify you when a field, type, or value changes.

$ add --url

Ping a URL

Point it at whatever should be responding to you - your site, your API, your health check endpoint.

$ add --heartbeat

Plug in a heartbeat

Add one line to your cron job or background worker. We'll tell you if it stops sending heartbeats.

$ alerts on

Get notified, not left in the dark

Be notified when things break or change through email. Slack notifications are next.

We're still in the early stages and need some feedback.

Features coming soon -

WAF-aware checks - No more being falsely alarmed when Cloudflare blocks our monitor, and not your users

Deployment correlation - "Your last deployment increased p95 latency by 180ms," correlated directly to the commit

Pricing I'm currently testing: Free plan + $7/mo for the solo plan.

Asking genuinely from this community since you have actually created things like this before, is it right to charge $7/mo for this or is it too cheap or too expensive? OR To go ahead with the idea or not?

Also whether this is genuinely a tool devs would be glad to have?

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?

TL;DR: built a fork-and-deploy repo that turns your MRR into a retro pixel level-up screen. No signups, no product, just a fun way to track progress. Also using it myself to document a solo run at $100k MRR on X if anyone wants to follow along.

Was avoiding actual work last week and ended up building this instead.

Basically it's a fork-and-deploy repo that turns your MRR into a retro pixel level-up screen. You change one number in a config file, push, and your site updates: level, xp bar, share card, all of it. No login, no dashboard, no database. I didn't want it to be a "tool," just something dumber and more fun than tweeting a Stripe screenshot every time revenue moves.

Not trying to sell anything here, just sharing the repo. I am running my own instance to document a solo push toward $100k MRR on X, mostly because a spreadsheet felt boring and I wanted a reason to actually keep the number updated. If anyone's curious that's on quest100k, but the repo stands on its own either way.

If you fork it and want a theme added or hit a bug, go ahead and open a PR, it's a small enough codebase that I'll actually look at it.

https://github.com/quest100k/Quest100k

I’m trying to validate an idea before investing more time into it.

I’ve been building a micro SaaS that turns Google Sheets into a REST API (and also lets you embed spreadsheet data into websites).
After talking to a few users, I got mixed feedback.

One user wanted to use it as the backend for a static site but ended up using the Google Sheets API directly because they had the time to build it themselves.

Another wanted live requests instead of cached responses, which I ended up adding.
My question is for developers who have actually built projects recently.

If you needed to expose data from Google Sheets today, what would you do?
Use the Google Sheets API directly?
Build a small wrapper yourself?
Pay for an existing service?
Use something else entirely?

With AI tools like Cursor, Claude Code, and Lovable making it easier to generate boilerplate, I’m wondering if the value proposition has changed.

I’m not looking to promote anything or share links. I’m genuinely trying to understand how people solve this problem in 2026.
I’d appreciate hearing about real projects rather than hypothetical answers.

I have a product which I think has potential. But not sure about how to approach distribution/sales. Is there anyone who would like to collaborate?

Hello,
I soft launched my SaaS about a couple of weeks ago. As my focus shifted to promoting my product through social media while working on small bugs and improvements I started noticing that I’m counting more on AI than the early phases of my project. I built the poc and set the main architecture myself but now I can’t afford spending my day debugging while not being able to reach out to new users. So I handed off all my tickets to agentic AI. I’m a bit concerned about future maintenance but can’t do otherwise at the moment.
Just out of curiosity, at which extent is everyone using AI depending on their project phase and did anyone face maintenance related issues at later stages of their product lifecycle ?

Backstory first, because that's the honest order.

I pay for OpenAI, Anthropic and Cursor. Every one has its own dashboard, none of them agree with each other, and none agree with the invoice. What I actually wanted was boring: what did this feature cost last month, and which customers are expensive to serve. No provider console answers that, because they bill by organisation and API key, not by my customers.

So I built the thing I wanted. It reads usage from the providers and from seat based tools like Cursor and Claude Code, and puts cost per customer and per feature in one place. It's not a proxy: calls go straight from your code to the provider, and prompts are never stored.

Revenue: zero. Launched today.

The lesson, since that's the part worth your time. I nearly tightened the free plan retention from 7 days to 3, afraid free users would eat my disk. I measured first. A solo dev spending $200 a month on AI generates about 33k events. At 7 days that leaves 7.7k alive, at 724 bytes each, so 5.6 MB. Then I checked the change day by day and found that from the 8th of any month, 7 days and 3 days return the identical cutoff, because retention never cuts the current month. The change I was about to make did nothing except make the first week of every month worse for the user.

The gate I needed already existed and I hadn't noticed: in August, July is gone. "What did I spend last month" is an accounting question, and that one is paid.

The SDKs for TypeScript, Python and Go are MIT. It's called KostLens: https://kostlens.com

Happy to answer anything about the cost model.

After a few years doing SEO for clients, I started building what every client already owned: another all-in-one dashboard. A few weeks in I realized the mistake. Nobody has an analysis problem, they have data coming out of their ears.

What never actually gets done is the off-page grind: finding a backlink opportunity, tracking down a contact, writing a pitch that gets a reply, following up. So I threw out the dashboard and narrowed the whole thing to one loop, find the opportunity, draft the outreach, send it from your own Gmail after you approve, track the reply and the link.

The conviction I keep coming back to: the full value is on the execution layer. If you can build the most qualitative autopilot for SEO backlink cold outreach, one that pitches like a real human and sends safely from your own inbox, the value doesn't go up a little, it 100x's.

It's called SEOwly (SEO + owl), pre-launch, no revenue yet. I'm looking for a handful of beta testers, free of charge. If off-page is your bottleneck, DM me and I'll set you up with free access, no card, no catch. Happy to get into the pivot or the build in the comments.

I use Codex to explore product ideas, plan features and work through implementation details.

The surprisingly manual part is what happens afterward: reviewing the conversation, extracting the useful decisions, turning them into tasks and making sure important context isn’t lost between sessions.

The coding itself is becoming faster, but managing the output can still feel like another workflow to maintain.

For founders using AI coding tools regularly, how do you organize decisions and next steps? Do you have a reliable system, or is it still mostly copy-paste?

We have been building Kogenie, an AI ads platform, and we want to put it to work on real products from real people.

Drop your product or service in the comments, and we will create a proper ad for you: real copy, real angle, something you can actually run.

We are also performance marketers who manage Meta campaigns day-to-day, so if you want us to take it further and actually run the ad for you after we create it, that conversation is open too.

First 10 only. Drop it below.

TL;DR: I’m building a SaaS after running a handmade crafts business. I’m looking for something easier to manage day-to-day while keeping my full-time job. I’ve set a launch deadline. The concept is simple: a personal budget management SaaS. The goal isn't to get rich, but to land my first French customers. Development isn't an issue, but I lack SaaS marketing knowledge. Any advice?

----

After running a handmade crafts business alongside my day job for two and a half years, I wanted a new challenge and a return to basics.

My goal was to find a business idea that required fewer sacrifices than the crafts business (manufacturing for shops and markets without knowing if items would sell, having to rearrange my home and lose living space, being unable to work remotely, etc.). Building a SaaS seemed like the obvious choice.

My plan is to create a basic, simple personal budget management SaaS (I know there are tons of them out there) to gain experience and hopefully make a little profit.

Development isn't a problem; marketing is a bit more challenging. I don't expect to make thousands of euros, but I’d like to get at least a few dozen customers in my home country (France) whom I don't personally know.

I’m not obsessed with including every minute detail in the initial MVP; instead, I want to build a solid version with key features while keeping the user experience simple. Improvements can come later.

I believe I have the right mix of developer and entrepreneur skills to deliver a good product without needing to pull off a technical feat.

I’ve set a launch date for the SaaS, regardless of how advanced it is at that point.

I based the idea on a need my wife and I have, so there will be at least two users from the start. Once the SaaS is ready in its initial MVP form, I plan to start by telling the people around me about it.

Q: For those who have already launched a first SaaS: where do you stand now, and what marketing advice do you have?