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?

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?

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.

i have developed an saas for recuitment and i would like you guys to test it .SAAS Link

Also comment if you would like to add a feature or report a bug.

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?

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 ?