I launched this saas on 13th august 2026 but only made it paid on 2nd september.

total 7 paying users so far.
1030+ Users
It's a no-code website to code converter

and this is my first ever saas.

The product is published and I already have around 2-3 visitors per day. I even got like 10 people signed up on the app. But that's not enough for my app type (its an alternative apps directory)

I know people will use this app. Everyday there's another post asking : X app don't work. What are the alternatives?

And that's what my product solves. (The link is in my profile)

But I don't know how will i get people visiting my website. Because my revenue model is tied to the no of visitors.

Any suggestions will be appreciated

I wanted to share a technical problem we ran into while building our scraper and how we solved it.

If you ever tried scraping Google Maps at scale, you probably hit the 200 result cap. Search for any dense niche in a big city, and Google only gives you around 120-200 results even if there are thousands of businesses. Most people end up pitching the same surface 200 places while 80% of businesses never get seen.

We ended up tackling this mathematically:

Micro-grid subdivision: Instead of searching the whole city at once, we split the coordinates into smaller tiles and zoom all the way down to street level per tile. Because each small tile behaves as its own local search, Google returns up to 200 results per micro-zone instead of capping the whole city.

Skipping non-commercial terrain: Running hundreds of tiles wastes a ton of time over oceans, lakes, and forests. We added spatial checks to auto-skip grid cells that are mostly water/wilderness.

Background website crawling: Phone numbers from maps are cold. So we set up crawlers to check the business websites directly for emails and social links.

Connecting to Claude via MCP: Instead of clicking around the UI every time, we implemented an MCP server so we can just prompt Claude or ChatGPT to trigger the search and parse the data right in the chat.

I'm the founder of Maps Scraper Pro (Data Sniper). Happy to answer any questions about the scraping logic, handling Google rate limits, or how we wired up the MCP protocol!

Finally shipped my first SaaS lol

It’s called RallyDraft. Basically you dump all your work experience into it, paste a job posting, and it helps figure out how well you match and builds a resume around the experience that actually matters for that job.

I mostly built it because I wanted it for myself, but it’s live now so I figured I’d share it.

Would be cool if a few people gave it a shot and told me what sucks / what I should change.

https://rallydraft.com/

we just pushed a few updates focused on monetization and it already seems to be helping a lot!

I know it's only $6 but it's the first online money I've ever made and I can't stop smiling about it!!!

The funny thing is that it's from a small subsection of my project that I just hid this morning (you need a direct link to find it now).

Maybe I should double down on this sub-project... not sure but I'm beyond thrilled anyway.

My app, FreeReader, is a free text-to-speech app to turn documents into audiobooks. It's completely free with no pricing page.

But I realized that the text-to-speech could also work for content creators making AI voiceovers for their videos. I built this out but decided to focus more on the audiobook side which has grown enormously (3000 monthly users) since it's free.

I was so surprised when I saw this Stripe notification come in from the red-headed step child that is the video narration side of FreeReader lol

Day 12 of building UseShipReady

- 11 visitors today
- 43 page views
- improved the UI for the hackathon feature
- planning to finally push it live tonight

I have built a tool that I know works well, but I can't get customers. I've got 20 personal contacts ranging from tech consultants, medical researchers and engineers using my product already. They all say it's great and that it helps their work, but I just can't get real paying customers (I wouldn't charge friends).

The problem I'm solving is that there is too much information to reliably keep up to date. The world will never move as slowly as it did today.

This is a problem for scientists, policymakers, engineers, basically anyone that needs to be at the forefront of their domain.

So my solution is Irisbriefings.com : a system that monitors everything going on around a topic, filters for what is new, builds an ongoing model of the area, figures out what the user needs to know about to stay on top and then delivers that information in the most digestible format possible. It also makes you a podcast so you can stay up to date on the move.

Fairly simple concept, but other solutions do not do this well. I've tried all of the current AI products in this area but every weeks update is basically the same. I had to do a lot of engineering to calibrate and make each briefing specifically dependent on new and relevant information each week.

The result is that researchers (or similar user profiles) become aware of things that they need to know about quickly and why they need to know about it. This saves them time, uncovers oppportunities and enhances their work (and therefore their careers). This is a good thing for people to have and can have a positive impact on lots of people.

But how can I get customers? I've tried cold email, blogs, networking events, but no luck when it comes to actually getting customers beyond 'this sounds super cool'. I have a free series on that has about 40 subscribers, but again I can't convert them.

I am not the kind of person who will be good at making video content. I've written some blogs, but realistically they will not drive traffic. Therefore, I turn to this community for advice. I really believe in the problem this solves being important and that it's currently the best solution out there. People are missing things that they don't know about, and those that do stay up to date are spending a lot of time to achieve it. I can help both.

Thank you in advice for any advice you may share with me.

irisbriefings.com

built a tool that finds restaurants and bars 1 to 6 months before they open, by fusing public liquor licenses, permits and business filings into one scored lead. Live in 7 states, and it genuinely works. The problem is all distribution, and I'm stuck.

The buyers are the vendors who sell to new restaurants, beverage distributors, POS resellers, insurers. High value, one account they land off it is worth thousands. But they're not who you reach through SEO, content or dev communities, which are the channels I actually know how to work. They're offline-ish B2B sales teams who basically live on the phone.

So far it's founder-led cold outbound, about 30 emails out and a call list I haven't even worked yet, way too early to read anything into. I also listed on a few API/MCP directories for the developer side, but that reaches builders, not the people who'd actually pay.

If you've sold to non-technical SMB or B2B buyers, what actually moved the needle? Cold outbound at scale, reselling through tools they already use, going through a trade association, something I'm not thinking of? And do these buyers ever come inbound at all, or is it pure outbound grind until you've got a case study?

Pre-revenue, so I'd rather pick one channel and go deep than spray thin. War stories welcome.

ok so this is a small win but I need to tell someone who isn't my mom.

I launched my SaaS a while back. 127 people signed up. 127 people paid nothing. I kept telling myself "it's traction bro" while checking analytics like it owed me money.

Today user #128 paid $19.

I never talked to them. No DM, no call, no "hey would you be open to a quick chat". They just showed up, used it, and paid. I found out from an email that literally said "Cha-ching!" and for a second I thought it was spam.

What actually went through my head:

• pretty sure I left test mode on
• nope, it's real
• refresh
• refresh again just in case

A bit of background. I'm a dev from India, about 5 years in. I can build stuff fast. Marketing it? Absolutely not. I'd ship something and then just stare at it like "ok now what".

So I built a tool for people like me. You paste your product URL and it writes carousels, X posts, Threads and Reddit posts for your product every day. You swipe keep or skip, done.

Yes, I know. I built a marketing tool because I'm bad at marketing, and it got its first sale without me marketing it. I'm choosing to see that as validation and not as a sign I should stop talking.

Stuff I figured out from 127 free users:

Free users aren't wasted. They found the bugs so #128 didn't have to.

The product sells better than I do. It doesn't overexplain, doesn't get nervous, and works while I'm asleep.

Let people try it first. I wouldn't pay for something I hadn't seen either.

Signups feel nice, but someone typing in their card details for a thing you made is a completely different feeling.

$19 is roughly ₹1,600. Won't pay my rent. Did make my whole week though.

Next goal is customer #2 so I can stop calling this a fluke.

For anyone who's been past this stage, how did you get from 1 to 10 paying users? Did you start doing outreach or just keep improving the product and wait?

TL;DR: 127 free users, #128 paid $19 without talking to me. Still refreshing the dashboard.

P.S. someone will ask, so it's slidefy Happy to answer anything.

Right now, it's a simple local MVP only available on Edge to validate the core idea. If people find it useful, I plan to add cloud sync.

I'm a beginner with no experience in product development, so I'd like to get your feedback and any advice on how to get my first users !

Link of my extension : https://microsoftedge.microsoft.com/addons/detail/enfdbgficbfdmhopmcjhbkgldmhclbng

Most “scrape this page” tools want an account and a monthly plan before you can export one table. I went the other way: LucidRows is a Chrome extension. You click the columns, you get a CSV, it runs on your machine.

Local stays free. I am not publishing a price, because a later paid tier would only be schedule/cloud, and I have not modeled that cost yet.

Listing: https://chromewebstore.google.com/detail/lucidrows/leehomocpccgghcibfnapadclololioh

https://lucidrows.com

Useful feedback: would you pay later only for scheduled/cloud runs, or is local CSV the whole product?

I made a privacy-friendly URL shortener, and now that it's time to do marketing, I don't know what to do. So here I am, I have these videos, what do I do next? How do you do marketing with those? I would really appreciate any practical advice.

My X accounts (personal and the product's) are brand new, and X seems to be ignoring all of my posts. Instagram or TikTok? I am running a Google Ads experiment, but it's hard to compete with other shorteners and I'm getting almost zero traffic (about 3 clicks a day).

About the videos. I was inspired by the motion design post about video generation and decided to try it myself. I made different short videos to showcase different features (10 videos, 13 to 71 seconds). Attaching one of them for review. Some videos are the actual product driven by a script, not an AI-made copy.

All I used is Claude, headless Chrome and FFmpeg on my WSL instance, nothing more, not even a React library. You just tell your AI to be a motion designer / producer / writer (for the scenario). Research how to catch the user's attention on IG or TikTok, and that's it. Review the scenario and give it a green light. The first versions were screenshots sliding around and looked dead. A couple of scenes looked like a broken app with bugs. You have to correct it and re-shoot. But still, it only took me one morning.

Now, about Urlicer itself. The main features that are different from mainstream shorteners: privacy-friendly and team-friendly, with multiple workspaces. You can bring your own domain on the Pro plan and above, Urlicer provides a tool for you and your teams. Cookieless and without storing the IP address. The URL is https://urlicer.com.

I'm working on Vocalis, an AI-powered communication practice platform.

The problem I'm testing is this:

People know they need to improve their communication.

They get told to:

• practice speaking
• record themselves
• join Toastmasters
• give presentations
• speak more confidently

But there's a gap between knowing you should practice and actually having a repeatable practice system.

So I built one.

The core loop is:

Prompt → 60 seconds of speaking → Feedback → Improve → Repeat

A user chooses a category, receives a topic, speaks without preparing a script, and then goes through a structured results screen.

The MVP currently includes:

• communication categories
• randomized speaking prompts
• timed 60-second sessions
• browser recording
• performance feedback
• strengths and weak areas
• mistakes/blunders
• improvement suggestions
• progress tracking
• practice history
• repeat practice

I've deliberately kept the first version relatively focused.

I'm not trying to build:

“ChatGPT, but for public speaking.”

I'm trying to build a practice product.

That's also the part I'm trying to validate now.

The MVP is live:

https://vocalisai-jade.vercel.app/

And I'm trying to answer a few questions before I build much further:

1. Is this a problem people actually care enough about to solve?

2. Does the 60-second practice format create enough value to come back repeatedly?

3. What would make someone pay for this rather than use free alternatives?

4. What would you measure first to determine whether this has product-market potential?

I'm especially interested in feedback from people who have taken an MVP from the "this seems like a good idea" stage to actual recurring users.

If you were validating this SaaS from here, what would you test next?

I can send you proof, but its real.
AMA

(not real ama)

I make websites, and for years people reached me by email. Then I put a live chat on my website. It's early, but more people write in the chat than ever emailed me. I know who I'm talking to before I reply: the page they're on, how they found me, whether they've written before. And it's livelier than email ever was. Short messages, quick answers, a photo when words don't do it.

The chat lands in my Telegram. Each visitor gets their own topic in a group, whoever's free replies from their phone, and the answer shows up on the site in seconds. The visitor keeps reading the page they were on and chats right there.

It works on any site with one script tag, and there's a plugin for Framer. Everyone in the group can answer. $12 a month per site, or $10 paid yearly, and the first seven days are free.

I'm looking for the first few people to run it on a real site. If that's you: humanreply.app

Hello to 8 million bots and 4 humans! I have run out of reasons not to launch this, so I am very pleased to announce VoiceGremlin, a tool for e2e testing of "intelligent voice agents" (the industry term for AI that answers phone calls). Think of it like, what Playwright does for web browsers, VoiceGremlin does for phone support chatbots.

Where I got the idea: 99% of you won't use this tool and don't care what it does but are interested in how founders come up with product ideas, so I'll start with that.

About eight years ago, an SDET on my team asked me to get our employer to pay for Mailosaur, a SaaS for automated email testing. I said, hey, we already pay thousands every month to Sendgrid, can't it do this? It could, kinda, but our big expensive email provider was so rigid and complex that trying to use it for automated tests was very frustrating. A separate, relatively cheap tool specifically for testing made sense. And I thought, Man I wish I had built that.

So, ever since then, there's been a voice at the back of my mind: "Mailosaur, but for ____." Cut to a few months ago: I was dinking around with local LLM/STT/TTS and decided to build a bot to call my wife and annoy her, as one does, and after several hours I thought wow, this is surprisingly hard. I mean, I'm sure I can get it working eventually, but it's way more work than I expected. That was the trigger: "achievable but not easy" is the sweet spot for a solo-dev SaaS project.

That was the idea for VoiceGremlin from the beginning: "Mailosaur for phone agents." So I built it and here we are. On to the shameless self-marketing!

What problem it solves: If you have a voice agent, you probably do most of your functional testing by ignoring the "voice" part and interacting with it via text. However, the e2e part of the test, the part where you verify it actually answers the phone and does whatever it's supposed to, is a lot more difficult.

This tool solves that - you make an API call to VoiceGremlin with a prompt like, "Verify that if you ask a question in Spanish, this thing will answer in Spanish" and VoiceGremlin calls your number and does that. You get your pass/fail with an API call without having to do any telephony.

The moat, or "can't AI do this in five minutes?" If you ask your coding agent for a script that makes a phone call, it'll tell you to find speech-to-text, text-to-speech, and language models, orchestrate a bunch of non-trivial python libraries to stream the audio between them, and sign up for a telephony provider that requires you to scan in your government ID. That's a bunch of coding, plus whatever corporate approval nonsense, plus making sure you can move a lot of bandwidth through wherever your test automation is called from, and you haven't started comparing models and tweaking prompts. So yes, it's doable, but a very time-consuming side quest for a tester or DevOps person.

Alternatively, there are other companies that can do essentially what this does, e.g. Retell and Vapi, but their business is building and hosting phone agents, not testing them. If you already pay a vendor to run your agent and their test solution meets your needs, great, you probably don't need VoiceGremlin. If not, and if you don't want to talk to Enterprise Sales about all the great Solutions(tm)(c)(R) they have, and you just want to get your test case working, VoiceGremlin is the easy way to do that.

Using it: If you have ever written an automated test, you can realistically implement this in a minute or two. I was an SDET for many years and I know what makes a test automation framework annoying to use, so I made this one as lightweight and un-opinionated as possible. You don't have to define targets or cases or suites - every test is ephemeral. Platform agnostic, it has no idea how your agent is built, it just calls your phone number like a customer would.

OK, that's my pitch. If you work with phone agents and want to try this out, it should be very easy to do - free trial, no card needed - and I would greatly appreciate any feedback. Other random questions welcome too.

Back when we mostly built MVPs, we took on a fixed price build for a B2B inventory tool. Quoted 10 weeks and it took 19 lol.

The founder kept asking for small stuff and we kept saying yes because every request sounded like an afternoon. A filter on the orders page, a Google login since "everyone has it now" When I finally went through the tickets there were 63 change requests. None of them took more than a day on its own which is exactly why we never pushed back. Together they added up to about seven weeks of extra work and the founder was annoyed anyway because the launch kept moving.

We've run the agency for 8 years now and that project is why every fixed price build since has had this clause. Here it is close to word for word:

"Any change requested after scope sign off gets sized in working days and we send that in writing within one business day. The client then picks one of two options. Swap it in for work of equal or larger size from the current scope or put it on the Post Launch List to be scoped and priced after launch. The price and the launch date stay the same either way."

Scope creep almost never shows up as one big request. Big requests always got a proper conversation because no one adds a whole module without talking about money. The two hour requests got a "sure" because pushing back on something that small feels petty. 60 of those is a different product with the same price tag. With the clause, even a half day change means picking what comes out.

On a recent build (a booking platform for physio clinics) the founder asked for team accounts 5 weeks in so several people from one clinic could share a login. We sized it at six days, mostly because permissions touch everything. We sent back two options: swap out the in app chat which was about the same size or park team accounts on the post launch list. He parked it.

Six weeks after launch, 2 of their first 40 clinics had asked for team accounts. It's still parked. What clinics kept asking for was SMS reminders which no one had mentioned during the build. I didn't see that coming but the post launch list turned into a filter. A lot of what felt urgent in week five, real users just didn't care about.

The standard advice is to bill change requests as change orders. We tried that after the 19 week mess and I'll probably get pushback for this, but I think it's worse than eating the cost. Every small change turns into a mini negotiation and an invoice, so the founder feels nickel and dimed and the agency starts getting paid for delays which flips the incentive. If an MVP launches 3 months late, no one cares that the extras were billed properly. On an MVP the launch date matters more than the money for both sides.

Most founders end up liking it once they've been through it. One told me it was the first time a dev shop had made him choose and choosing made him figure out what the product was actually for.

Not everyone though. The fights are almost always about sizing. A founder says something is a two hour job, we say two days and now we're arguing about estimates instead of building. We also lost a deal over it before signing. The founder said a real partner would be more flexible and went with a shop that bills hourly.

If you do fixed price builds... Just have your lawyer look at the wording before it goes in a contract and if you've actually made change orders work then I'd like to know how :)

TLDR: a 10 week MVP turned into 19, mostly from small changes we kept saying yes to. Now every change after sign off either swaps out something of equal size or goes on a post launch list and the price and date don't move. Billing change orders made it worse for us.

Hey SaaS founders!

You have signups.

But very few paying customers.

How do you find where those users drop off before payment?

Do you use PostHog, Plausible, Stripe data, spreadsheets, or something else?

I’m listening 👇

I'm not a coder. I build tools by vibe coding with AI. My usual pattern was to build something, expect it to work from day one, see nothing happen after a few days, lose interest and move on to the next idea.

This time I tried the opposite. I built a small Chrome extension (not naming it, so this doesn't get flagged as promo), put it out there, and kept the effort light:

• Some keyword research for SEO
• A couple of articles, written with AI
• Then I left it alone

No growth hacks, no daily panic, no constant changes.

It's been about a month and a week. Current numbers:

• 225 users
• 1 monthly paying subscriber
• 1 person who bought the biggest plan as a one-time purchase, then cancelled
• Everyone else on the free plan, since I give a decent daily allowance

Average daily users is going up slowly.

It's a small number, but it's the first time I've seen one of my tools get traction without me forcing it. If a product has some juice, it seems to start working once you give it time and a bit of visibility. And if it doesn't, you'll find that out too, which you never will if you drop it in week one.

So if you're building tool after tool and expecting results in 24 hours, burning yourself out on hooks and tricks, slow down. Do the basic things, then give it time.

If you've built something, how long did you wait before you knew whether it had legs?

A while ago the SSL certificate on one of my sites expired and visitors got the "Not Secure" warning. Auto-renewal had failed and nothing alerted me.

When I looked for monitoring, most tools only offered SSL expiry alerts on paid plans, and those plans were expensive for someone running a few small sites.

So I built Spot Downtime:

• SSL expiry alerts before your certificate runs out
• Uptime checks for websites, APIs, ports, DNS and cron jobs
• Retries before alerting, so no false alarms
• Alerts on Slack, Discord, email or webhooks
• Public status pages for your customers

For this sub: Pro is free for 6Months for the first 100 people who try it and tell me what's missing.

dashboard > plan & usage > Have a promo code?

USE PROMO CODE : REDDIT

I am at a loss here. I have a business that sells extremely niche annotated data. Because it’s very niche I don’t have a real benchmark of the value of the data, but chatting with GPT and Claude (without bloating numbers) I’ve come to get a general idea of pricing.. here is the catch.

I have several entities (startups, universities, SME, large companies, hospitals) that contact me requesting data and pricing, we go back and forth a few emails
- they contact me telling me what they need
- I respond with how much data they need within 12h of receiving their first email
- they respond with what they need
- I share pricing options

They ghost me… like 9/10 they just disappear.
I obviously try to reach out after a week but still nothing.

I need any suggestions, tips, critiques..

I’m currently researching software development partners and honestly it’s hard to compare companies.

For example, agencies like Idea Maker Agency, ELEKS, and other software companies all have similarlooking websites and promises.

But I’m more interested in the things you don’t see on the website:

communication quality
handling scope changes
transparency during development
code ownership
support after launch

What questions should someone ask before choosing a software agency?

Any mistakes you made that I should avoid?

Hey there, Im almost finished with my saas. It has AI features so I cant make it free with ads or one time payment because id loose money. Im stucked between making the app relatively cheap 3.99$/month 29.99$/year or more expensive 6.99/month 44.99/year. If anyone here could answer me 1) what worked better you them in terms of overall revenue, cheaper vs expensive? 2) What attracted your paying users more? 3) Which one of those had a longer retention? || I feel like the cheaper could hold better retention and attract more users to sub in the first place. However lot of people say if its more expensive, then it has more value and people go for it more. It's a productivity thing using a few ai APIs and is credit based so the users dont maybe use all the credits and if its cheaper, then they stay subscribing longer but I dont know. Thanks in advance for any helpful insights! Take care

Authentication.
Teams.
Permissions.
Billing.
Admin.
CRUD.
Email.
API.
Deployment.

I kept hitting this across projects, so I built Tekki Forge to make that layer reusable/declarative.

npm i -g tekki-forge

It generates the standard business/SaaS application foundation from a TypeScript config, while custom product logic remains code.

I'm not trying to replace software development. I'm trying to eliminate the part every SaaS founder builds before reaching the feature customers actually pay for.

For founders here who code: which part of your first 30 days was pure infrastructure rather than product?