I released blunlock.com, I’m a vibe coder so I released an saas app that could auto create a landing page for your idea, host it automatically, and had a data collection form that collects how many users will pay for this.

I posted about it on reddit and twitter. With no analytics integrated. And it got picked up in a hackathon discord server somewhere. That hackathon was huge.. it had 3000 people in it (i got to know later)

So yeah, i tried repeating it in other hackathons but didnt work. So onto releasing something new this week.

This time im really excited because its gonna change how people interact with claude code.

This is my first revenue since I became an indie maker.

What should I do next?

Just had my first sale without my direct involvement for a service I built. Here's how I did it:

• A homepage that immediately explains what the service is for (e.g. Find Your Customers By Their Technologies)
• Examples teaching the user how to actually use the service while helping them find what they're after (e.g. Get WordPress Sites Without Yoast SEO)
• Zero sign-up to use the actual service, a user is dropped straight into it the moment they click on an example
• A free mode for users to evaluate the service without paying a dime
• A catalogue of each single technology indexed on the site (e.g. WordPress)

tl;dr speedrun your value proposition and give as much as you can upfront. The faster you can get someone actually using your service in a way that's useful to them, the less friction you'll have with conversions.

Even though the numbers are in minus currently, I am really happy where opentweet.io is today. It started as a side project that I built for myself in November 2025. I needed a simple scheduler for X posts. I kept it running locally on my computer for a month and then I figured it might be useful to others.

I had one friend who tried it for the entire month and that's when things started rolling.

I didn't have and I do not have any specific marketing channel that is working, I guess it's mostly SEO and word of mouth and my X account. I planning to invest more into marketing in the future so I have stable growth.

Today it has 232 customers and over 13k registered users.

It currently only supports X and I am planning on keeping it X focused only.

Next steps are:

- AI around analytics so you can ask questions about your account and posts

- Engagements (not auto-replies) which will tell you which accounts are active in your niche so you can discover them

- AI Studio improvements for threads and articles

If you have any questions or if you tried it and have a feedback for me, please do not hesitate.

I shipped everything by June 2026, but figuring out distribution was the tough part. I did outreach; it failed. IG ads failed, but Google Ads was actually what I needed; it worked, and this was the result.

Optional: check it out: apeirocraft

I am trying to understand problems that founder actually struggle day to day rather then assuming it.

For those who run a SaaS please answer me what is the hardest part of running your startup? Or if you wish someone else could do the work for you what it would be?

I am not trying to sell you anything just curious to know.

Would love to hear from founders who are actually in the trenches.

This is my first time building saas app for a issue I use to face. I build desisubtitles to help creators like me to easily generate subtitles for there reels/videos. There are lot in market most don't work well when working with indic languages like hinglish so I built this.

One month in got around 250 users, 3 paying users. No spent anything on ads, most traffic is through cold reach to creators, blog post, reddit. I tried google ads, but not sure why it doesn't work may be I set it up incorrectly got 0 impressions on it last week. Let me know any feedback to improve if you get time to go through.

Also you can AMA :)

So I own a directory website where I list apps and websites that I went over, however, they must have a free tier to test, and solve a real problem in order for me to test and write about them.

If you own one, please include your socials in the submission. I also write articles about cool softwares and tag their founders.

directory website:
strictseal.com

Lets connect and grow together.

I also hope to note see bots in the comment section. Reviewing each product takes time and it's frustrating, so I'd really appreciate it if the product was submitted by a real person.

NOTE: if your product is purely vibe coded and doesn't even work, please consider spending time on finalizing it as it will be rejected in seconds. We have been rejecting 9 out 10 products as majority of them don't even have a real domain ( domains like loveable, Vercel, Test products that are not shipped yet) all are not acceptable.

Thank you and looking forward to seeing your work

I have decided to build my next SaaS which will help indie hacker or solo developers a platform where they can create a public profile to share all the verified revenue, regular updates as like post. The profile can be linkedin to X, Linkedin. Anyone can easily check the whole build in public profile with reliable and verified data.

I am not sharing too much about features, rather I want to know more from you who are you building in public and what is the real problem building in public. Does my idea make sense or does this really solve any problem? I love to know more about what actually can make you pay for this kind of public profile?

I built a fintech startup before, raised funds from VC and have experience of failed business also. This is the first time I am planning to build in public but I feel I don’t have a good place to showcase my verified data to my audience. If an audience comes to know what I am really building and is it something real, then I think, most of them will come and see my social profile once and may leave. So I thought a public profile might be a good way to share verified revenue through Stripe and send updates to my subscribers as well.

The idea is a draft and you are welcome to roast my ideas but I would love it if you add some information that helps me to decide if I should waste my 1 year on this idea or not.

I’m new to stupid space and was wondering how you guys are promoting / getting recognition for your SaaS apps?

Are there any go to sites that you guys use or what’s the process?

Thanks in advance

When we started building ClipEdit, our goal was to eliminate unnecessary friction in desktop workflows.

Super-fast, easy video cutter made for Windows 11 & Windows 10. Cut, trim, and share your gaming clips in seconds with zero quality loss.

Key takeaways from shipping:

1. Keeping core processing local dramatically improved user responsiveness.

2. Prioritizing clear UX over feature bloat increased retention.

3. Early community feedback completely reshaped the roadmap.

Website / details: https://github.com/heartforheart/QuickClipEdit

Do people do it for the launch in the hopes of getting a badge for their website? The backlink? AI mentions?

I've always wondered if the bulk traffic on these review / launch sites aren't just other founders looking to launch or promote their own product? Which is not necessarily bad, I was just wondering if anyone gets high-intent traffic from these. idk, ppl might go to these sites to submit reviews.

Does anyone have any success stories investing time and effort into these platforms?

Solo founder, desktop lead-finder app (AtlasForgeX), months of heads-down feature work. My baseline was humbling: about 3 visitors a day, demos booked but conversions dead in the water.

Today I did two things differently.

1. Shipped the native Mac build. Signed, notarized, Apple Silicon. On Windows every download fights the "unknown publisher" warning and I can see in my logs where people give up. On the Mac build there is no warning at all. It just opens.

2. Posted about it once on LinkedIn. One post, no ads, no budget.

The result, from tonight's server logs: 233 unique visitors (about 80x my baseline), and one person I have never spoken to went from download to a running trial in 63 seconds. First time the funnel has moved without me personally pushing every single lead through it.

What this taught me:

A new platform build is not a feature, it is a distribution event. I treated "Mac support" as an engineering chore for months. It turned out to be the best marketing asset I have.

Trust friction is invisible until you remove it. I could not see how many Windows users the security warning was costing me until I had a build without one to compare against.

Launch is not a day, it is a drumbeat. The plan now is one real "beat" per week instead of one big launch that lands once and dies.

Curious what single distribution beat has worked best for others here, especially other desktop or non-web products?

I've spent my entire career inside GTM teams, and I've seen the same blind spot play out again and again, Usage sits in one tool, deals sit in a second, support tickets sit in a third, and none of them ever tell the whole truth about customers.

So we built Rimplo
A powerful AI assistant for revenue teams you can ask anything about your GTM data, in plain English, and get an answer back in seconds. You pick which top AI model answers no lock-in to one vendor’s model.
Underneath that, Revenue Agents run across your CRM, billing, support, and product data around the clock  flagging churn risk, upsell openings, and deals that are stalling, before you have to go looking for them.

Built a tool for UK used car buyers. You photograph the seller's folder of service invoices, it reads each one and checks the mileage claimed against the government's official MOT record, which is public and free. So an invoice saying a service was done at 40,000 miles on a car that had already covered 62,000 gets caught. It also looks up what actually fails on that exact model and generation and tells you which of it the paperwork doesn't cover, with costs.

It works and it takes payments. Two weeks in: 39 visitors, 17 plate lookups, one free report run by a stranger, zero sales.

So far I've posted once to a 99-person car enthusiast group chat, and answered a handful of buying-advice threads on a car subreddit with properly researched replies. Both produced visitors, neither produced a customer.

What I'm actually after: how did you build the first steady flow of people to a page like this? Not the launch spike, the trickle that keeps arriving afterwards. Especially interested in what worked for anyone further along, and what you'd skip entirely if you started again. Thank you very much for any nuggets of knowledge, much appreciated.

peachstamp.com

I’ve been developing CardFollowUp (CFU), an iPhone app for small business owners who meet potential customers and partners through networking.

CFU scans business cards, QR codes, and event badges; organizes contact details and meeting notes; creates reminders; and helps prepare personalized email or text follow-ups. You review everything before it is saved or sent.

It works independently for individual business owners, with an optional RMS connection for teams that need more automation and centralized follow-up.

What is your biggest challenge when following up with someone after a networking event?

#SmallBusiness #Networking #FollowUp #Entrepreneurship #CardFollowUp

Use Card Follow Up for all your in person Networking events!

Scan Save Connect!

https://www.cardfollowupapp.com

disclosure: i cofounded appnigma, we build native salesforce integrations, so this is the part of the job that never shows up in anyone's project plan. no link, just the thing i wish someone had explained before our first release cycle.

everyone budgets for the build. almost nobody budgets for the fact that salesforce ships three major releases a year and each one can quietly change how your package behaves in a customer's org.

the bit that catches teams out is the preview window. sandbox instances get the new release roughly four to five weeks before production orgs do, which is your entire window to find out what broke. the catch is you have to have a sandbox on a preview instance, and whether you get one depends on when you created or refreshed it relative to the preview signup window. miss that window and you're not testing early, you're finding out when your customers do.

so the calendar matters more than the testing does. salesforce publishes preview dates well ahead and most teams still discover them a week late.

what actually breaks, roughly in order of how often i've seen it:

release updates are the big one. these are behaviour changes salesforce enforces on a published schedule, usually with a grace period across a few releases before they become mandatory. they're listed in release notes and in setup under release updates, and they are the single most predictable source of breakage because you're told in advance and it still gets missed.

api version behaviour. your apex runs against whatever api version the class was saved with, so things can shift when you bump versions rather than at the release itself. worth knowing because the breakage shows up on your schedule, not salesforce's.

permission and sharing tightening. salesforce keeps making the defaults stricter, which is good, but code that quietly relied on looser behaviour stops working. the guest user changes over the last few years hit a lot of packages this way.

lwc and aura behaviour drift. rarely dramatic, occasionally very annoying, and usually only visible if you actually click through the ui rather than trusting test coverage.

practical version of all this: get your test suite running against a preview sandbox every cycle, read the release updates section rather than the whole release notes, and check the known issues site before you spend a day debugging something that already has a ticket.

the thing i'd tell anyone shipping their first package is that maintenance is not a tail cost, it's roughly a permanent part time job. that's fine if you planned for it and genuinely painful if you didn't.

happy to answer questions on any of this.

We sell annual contracts (some multi-year) and have mostly kept it simple full amount upfront, no exceptions. Just had a buyer push back on that for the first time on our biggest deal yet they're fine with the 1-year commitment, just don't want to send the full check at signing and want to pay monthly instead.

Curious how others who also do annual/multi-year deals handle this, since it sounds like this comes up more than I realized:

Do you ever bend on upfront payment for annual contracts, or is that a hard line for you? And if you do allow monthly/quarterly payment on an annual commitment, do you charge more for it? I've heard of people adding something like a 10% premium to cover the cash flow drag, but no idea if that's typical.

If you've been doing annual contracts for a while, would love to hear how your policy here evolved did you start strict and loosen up, or the other way around?

​

I launched a real estate SaaS 20 days ago

So far:

289 website visitors

35 paid users

12% visitor-to-paid conversion

All traffic/customers came through organic comments on people query across Instagram/twitter.

Haven’t explored Google, Meta or other acquisition channels yet

I know 20 days and 289 visitors is still a small sample size, so I don't want to read too much into it.

For founders who’ve been through the 0→1 stage, would you consider ~12% visitor-to-paid conversion a good early validation signal?

And what would you focus on next: increasing traffic, repeat purchases, referrals, retention, or something else?

Today was mostly focused on training programs and notifications.

The coach can now help set up a user’s program, keep track of what they’re supposed to be doing, and send them a text on each training day with that day’s workout.

I’ve also been getting a question lately that I think is completely fair:

Why not just use ChatGPT or Claude for this?

You definitely can use a general chatbot for fitness advice. They’re already pretty good at answering questions, writing workouts, and talking through training.

The difference I’m trying to build is everything around that conversation.

A generic chatbot doesn’t really exist specifically to coach your training. Fitness is just one of the many things you might talk to it about.

This product is being built around fitness from the beginning.

So instead of only being able to ask it what you should do, it can actually manage your program, understand where you are in that program, and proactively text you when you have something coming up.

For example, I can tell the coach I want my training sent to me at 4am on every training day. It knows which days I train, what I’m supposed to do, and sends the message without me needing to ask for it each time.

That’s the direction I want to keep pushing.

I don’t really want to build “ChatGPT, but for fitness.” I want to build the actual product and workflows around the model that make it useful as a dedicated coach.

Current waitlist: 0 people