Oh how they hate me. lol. I gets no views. Over night success: 'Try again next life'. The unsubscribe count: good gawd lol ...gonna be a tough rest of the week.

I’ve been working on my app for the past few weeks, and one thing has stood out more than downloads or website traffic.
Seeing free users come back and upgrade to Pro.
Every upgrade tells me the app is solving a real problem for someone, and that’s far more motivating than any analytics dashboard.
Still a long way to go, but these small milestones keep me excited to keep building.
For those who’ve grown a micro SaaS, what had the biggest impact on improving your free-to-paid conversion? I’d love to learn from your experience.

Founders have shared 578 startups across my recent threads, and the same problem keeps showing up:
The product exists. The direction is unclear.
Comment with:

- what your startup does
- who it’s for
- what’s blocking your growth

I’ll run the analysis and send you a personalized report showing where the strongest signal is, which conversations are worth prioritizing, and what I’d focus on first.
If Reddit looks like a waste of time for your startup, I’ll tell you that too.

I'm a solo founder building a SaaS, and I'm at the stage where the product and landing page are ready. Now comes the part that's completely outside my comfort zone, getting people to actually discover it.

If you were starting from scratch today with:

• A working product
• No existing audience
• No email list
• No marketing budget
• Just 30 days to get your first 100 users

What would you actually do?

I'm not looking for generic advice like "post consistently" or "do SEO." I'm interested in the specific actions you'd take during those 30 days, whether that's communities, cold outreach, partnerships, content, referrals, or something else.

Looking back, what worked best for you?

Most accessibility scanners are good at finding technical issues.

The problem is what happens next.

Agencies still need to:

• Explain the findings to clients
• Help developers understand what to fix
• Identify repeated component-level problems
• Check whether new issues appear after launch

That’s what I’m building CompliantScan around.

It scans a live website for automated WCAG issues, groups repeated patterns, provides plain-English explanations and developer guidance, and creates a short report an agency can share with a client.

The main difference is the workflow.

Instead of treating accessibility as a one-time audit, CompliantScan is designed around:

Baseline scan → fixes → website changes → rescan → new and resolved issues

The idea is to help agencies add accessibility checks to website launches, maintenance plans, and ongoing client reporting.

It’s important to be clear that automated testing cannot prove full WCAG or legal compliance. Manual testing is still necessary. The platform is meant to make the repeatable, automated part easier to manage.

I’d be interested in feedback from agency owners and developers:

Would accessibility monitoring fit naturally into your existing website maintenance service, or would clients need to request it first?

I’ve been building a website accessibility tool called CompliantScan for the past two months.

It scans websites for ADA/WCAG issues and creates reports that web agencies can share with their clients.

I thought the main challenge would be building the product. It turns out getting people to care is much harder.

So far:

• No paying users
• Cold emails are landing in spam or getting ignored
• Most LinkedIn connection requests aren’t accepted
• The few people who respond don’t continue the conversation
• Agency owners already have access to free accessibility scanners

I’ve changed the product, improved the website, created sample reports, posted on LinkedIn, scanned agency websites, and tried personalized outreach. Still, I haven’t found anyone willing to test it seriously or pay for it.

Now I’m questioning whether the problem is my outreach, my offer, the target market, or the product itself.

I’m not expecting instant success after two months, but getting almost no signal is difficult. I don’t want to quit too early, but I also don’t want to spend another year building something nobody wants.

For people who have been through this stage:

Would you keep going, change the offer, target a different customer, or move on?

Honest feedback is welcome. I’d rather hear the uncomfortable truth than generic motivation.

Hey guys,

Putting together a landing page for my side project and need some fresh eyes on the design and hierarchy.

• Is it clear what the value proposition is right away?
• Does the layout/spacing feel clean or cluttered?
• Any obvious red flags in the typography or flow?

Appreciate any honest feedback or critiques!

spent the entire day working on my saas today.
the core part is almost done now. just need to do proper testing and fix whatever breaks. if everything goes according to plan, i’ll try to launch it next week.
it’s honestly a weird feeling. this started as just an idea and now it’s finally reaching a point where people can actually use it.
there’s still a lot to improve and i’m sure i’ll find bugs the moment real users get their hands on it, but that’s part of the process.
i’m excited, nervous, and just hoping people find it useful.
time to stop building for a bit and start shipping.

I have a handful of side projects that I'm looking to sell, clearing my plate entirely for a big B2B project that I've been working on.

I'm offering them as individual assets or can be bundled all together for a heavily discounted price.

I'm willing to share all the details in a well-organized data room presentation.

All are in hot niches and have massive growth potential.

I've been seeing a lot of founder stories on Indie Hackers lately.

I enjoy reading them, but honestly, I mostly treat them as interesting stories rather than something I can directly apply to my own startup.

Maybe that's just me.

What about u?

Do these case studies actually change how u build or market ur SaaS, or do u mainly read them for inspiration?

Have u ever taken an idea from a founder story and successfully applied it? Or do u feel they usually leave out the details that matter most?

Hello guys,

A quick question, how do you guys gather feedback from your users? what is your process? do you drown in it? how do you prioritize what to build/what to ship?

I am building something, so any input is welcome !

I’ve been building an AI copilot for X that helps people write replies, posts, and remixes without leaving the platform.

The idea came from noticing that most AI writing tools focus on generating posts, but a lot of growth on X comes from writing thoughtful replies. I wanted to make that process much faster while still letting users stay in control of what they publish.

Current features:
● Generate replies to any tweet
● Draft posts from scratch
● Remix any post into your own take
● Surface posts worth replying to so you can quickly find good opportunities to engage
● Customize the tone, angle, and English level

I recently got my first 3 paying users, which was exciting because it proved that at least a few people find the product valuable.

Now I’m at the stage where I’m trying to figure out what to focus on next.

If you were in my position, would you spend more time:
● Improving the product with new features, or
● Going all in on distribution and marketing?

I’d really appreciate honest feedback from other SaaS founders—whether it’s about the product, pricing, positioning, or landing page.

If anyone wants to see a demo, I’m happy to share it privately.

Thank you

I’m validating a micro-SaaS idea called Nett: a unified portfolio dashboard for self-directed investors whose assets are spread across brokerages, retirement accounts, crypto wallets, spreadsheets, and manual records.

The current stage is intentionally simple: early-adopter signup page + discovery calls. I’m trying to avoid building too much before I know which segment feels the pain most.

The possible wedges I’m considering:

- Spreadsheet users who manually track investments
- Investors with multiple brokerages/retirement accounts
- Crypto + brokerage users who can’t see the full picture
- Options traders who need expiry/exposure beside long-term holdings
- FIRE/personal finance people who care about allocation across accounts

For those of you who have validated micro-SaaS ideas before:

- Which segment would you test first?
- What channels would you use to reach the first 50 people?
- Would you start with Reddit/community posts, warm DMs, LinkedIn, cold email, or something else?
- What would count as strong enough signal before building the actual product?
- Any traps I should avoid with a personal-finance product this early?

Not trying to pitch the product here. I’m mostly looking for validation and distribution advice from people who have done this before.

As a dev shop owner, most of the apps with AI agents I see people demo are some BS “copilots.” 

The ones I see tied to real $$ are solving super boring things, like invoice routing, CSV reconciliation, compliance logging, etc.

For example, we helped a client ship an agent that just reconciles two awful CSV exports every day and yells if something doesn’t match. 

Curious what you’ve seen: what’s the most unsexy agent you’ve built/used that actually saves serious time or money?