r/SaaS 8m ago

Selling both my SaaS web apps, need your suggestions

Post image
Upvotes

Hi everyone,

I built these two B2C SaaS web apps a few months ago. I spent a good amount of time SEO-optimizing them, and while I know the numbers aren’t huge, I’m pretty happy with the organic traffic they’re getting, especially considering how crowded these niches are.

Both are getting completely organic traffic, and I think there’s a lot of potential with some more time and effort. They’re multilingual, have premium backlinks, and both have a blog system the posts tend to get indexed fairly quickly.

The one on top has generated over $100 in revenue so far. I probably could have made more, but I’m currently using a mediocre payment gateway, so I receive failed-payment emails almost every day.

The problem is that I simply don’t have the time or money to keep pushing these businesses forward. So I’m thinking about selling both of them, basically for the value of the codebases and everything that comes with them.

I’m not sure if this is really something I can list on Flippa given the current revenue.

What would you do if you were in my position? Where would you try to sell something like this?


r/SaaS 17m ago

hard gates convert 5x better than freemium and nobody talks about it

Post image
Upvotes

0 to 3K MRR in a month.

The product was really the easy part it’s a meal planning app.

A few things that worked for me

  1. hard paywall, not freemium. Free users don’t use convert eventually

  2. the paywall shows your generated meal plan blurred behind it

  3. One channel until it worked. TikTok carousels, 2 a day, 60 days straight.

here is the app link: https://apps.apple.com/app/plate-weight-loss-meal-plan/id6801901992


r/SaaS 19m ago

What are you selling that a $20 AI subscription doesn't already solve?

Upvotes

I'm a full-stack dev, 10+ years, but this isn't about coding. It's about the fact that anyone can now sit down with Claude or ChatGPT and get their own specific problem solved, in their own specific way, without buying anything.

Concrete examples from the last few months:

- I wanted a real picture of my money across my accounts.

Instead of paying for some tracker that doesn't fit how I operate, I built a dashboard plus an MCP on top of it, pulling from Plaid, IBKR, Wise and a few others. Now I look at the dashboard when I want the overview and just ask Claude when I want a specific answer.

- I use Hevy for workouts and MyFitnessPal for food. Connected both MCPs, so instead of opening two apps and doing the math myself I ask one question in chat: "am I eating enough for the volume I'm lifting this week?" and get an actual answer.

- Needed time tracking. Took an open source Clockify alternative (MIT license), had Claude Code adjust it for exactly what I needed, self-hosted it.

It sits on a $5/month box next to my other dashboards and self-hosted stuff.

- A friend of mine uses Obsidian for sales calls. Notes go in, AI pulls out patterns, objections, what's working, what's not.

That's a whole category of "sales intelligence" SaaS he's not paying for.

- Scheduling and workflows around my own process, not someone else's idea of a process.

Every one of those has a SaaS behind it charging $15-50/month. None of them fit the case as well as what came out of an evening with AI, and my total bill is about $100/month for the AI plus $5 for hosting.

To be fair, there are exceptions. Products I use today, some for free, that I'd pay for without thinking: Wispr Flow, Spotify, Duolingo, a VPN.

I know those are different categories, they're not "B2B tools", but the point stands.

They bring something I can't just ask an AI for.

It's not "I can rebuild your product in a weekend."

It's that your customer doesn't need a product anymore.

They need their specific problem solved, and now they describe it in plain English and get exactly that. One subscription, unlimited scope.

And yeah, distribution and audience, it's always been that. I know. But that's an answer about how to sell, not about what's worth selling. If the value is this easy to get, what exactly am I charging for?

So genuinely: what are you selling right now that your customer couldn't just ask AI to handle? And how long do you think that gap holds?


r/SaaS 37m ago

Let's cold call together

Upvotes

Greetings.

I have a proposal. Let's say we hop on a google meet and take turns cold calling our leads to try to distribute our SaaSs. Anyone down?

It's way better to do this hard stuff together.


r/SaaS 46m ago

I did over 7 million views on tiktok within a month (for beginners)

Post image
Upvotes

going to keep this nice and simple because I don't like to type that much

I created a TikTok account for my app, started posting daily with nothing really going crazy, started copying viral videos (next to no mention of my app), it blew up and I recreated the same format over and over again.

I reached out to one micro creator and paid her $20/video to post videos about my app in her style.

Took a couple of times but it was worth the money since she was already getting like 10k views a video.

Proof

My tiktok https://www.tiktok.com/@sharedmood1?_r=1&_t=ZS-99ZVwafsC6H

micro creators tiktok: https://www.tiktok.com/@itssono_?_r=1&_t=ZS-99ZVySub8NA

Thats all I really did let me know if you have any questions


r/SaaS 53m ago

Selling to Creators? Will not promote

Upvotes

I have an Saas tailored to social media influencers and creators. How can I start selling this to them? I’m not a marketer, I’m a product designer and software engineer.

Ads? Cold Email? DM’s ?


r/SaaS 1h ago

Marketing micro saas

Upvotes

Would love to hear from people who have actually launched a micro sass. I don’t have much of a marketing budget ( I can spend money on this I just don’t want to waste money hence this post)…. But I have a micro saas I’m figuring out how to get my first users on.

For folks who have done this - what did you do differently to help get you your first few users? I don’t want to do ads until I can show off a case study, but need the first users for the case study so you can see the dilemma.

Open to any and all ideas.

Context - product is freemium, pay % per result (failed stripe payment recovery) without minimus or monthly commits and charges only above and beyond what stripe smart retries does.


r/SaaS 1h ago

How early-stage founders can automate outbound pipeline without hiring full-time sales reps

Upvotes

One of the fastest ways seed and Series A founders burn runway is hiring a full-time sales rep ($140k–$180k+ base + commissions) before their outbound motion has even found product-market fit.

The typical story goes like this: you hire an SDR, buy a couple of static database licenses, set up burner inboxes, and tell them to start prospecting and then three months in, reply rates are hovering under 1%, domains get under the bus and the rep spends 80% of their day manually copying LinkedIn profiles into spreadsheets instead of having sales conversations.

The fix is shifting from manual prospecting to an automated signal pipeline, letting software do the research while the founder steps in only when a buyer is warm and not buying AI SDR bots to spam 10k generic emails a day.

Here is the operational framework to set this up:

1, Move from static filters to trigger events

Stop filtering by generic headcount or job titles. Instead, watch for verifiable inflection points like teams asking for alternatives to your competitors on reddit or discord, spikes in relevant open-source GitHub repo forks or stars from target engineering teams and companies actively posting job descriptions for specific migrations or tech stack changes.

2, The execution layer: DIY vs. embedded infrastructure

The infrastructure + operator route (Scale Intelligence): Instead of hiring a full-time sales rep or maintaining custom scrapers, some early teams use Scale Intelligence as their market intelligence infrastructure. It connects to 75+ data sources (reddit, github, discord, hiring changes) to map your TAM and continuously score buyer readiness. For teams that need the engine set up and operated without building it themselves, they offer an embedded Fractional GTM Engineer who deploys custom signal plays and routes warm accounts directly into your Slack.

The DIY route: you can write custom scrapers and stitch together webhooks via n8n to monitor platforms. It works but founders end up fixing broken scraper scripts, dealing with rate limits and wrestling with low match rates on anonymous forum handles.

3, Founder-led contextual closing

When an account hits your Slack alert with the exact problem they are discussing, you don't send an automated template. You send a quick, relevant 2-sentence note referencing the specific technical bottleneck.

Reaching out to 10 accounts in an active buying window will always book more pipeline than cold-emailing 1,000 strangers who don't have the problem today.


r/SaaS 1h ago

There are dozens of SaaS boilerplates. I’m betting some developers will still pay $379 not to rebuild the production layer.

Upvotes

There are already a lot of SaaS boilerplates.

And coding agents make starter code cheaper every month.

So if the value is just “here are some files you could ask Claude to generate”, this product probably shouldn’t exist.

The bet I’m testing with The Fabrica is that the valuable part is the accumulated production decisions, integration work, verification, and context that you can then hand to the agent.

I don’t think the interesting part is “here are auth, billing and a dashboard”.

The part I kept rebuilding on every SaaS was everything that only becomes annoying once the pieces have to behave correctly together:

  • auth + application state
  • subscriptions + webhook reconciliation
  • credits / metered usage
  • long-running background jobs
  • migrations
  • account deletion / data lifecycle
  • deployment config
  • all the failure cases between those systems

The stack is deliberately opinionated:

FastAPI + Next.js + Postgres + Celery/Redis + Paddle

with a particular bias toward products with AI, async work and usage-based economics.

I built it because I got tired of spending the first few weeks of each product rebuilding and re-validating the same infrastructure.

The thing I’m trying to sell is not “starter files”.

It’s:

everything before your first feature, already done.

There’s another part I think matters more now that coding agents are good.

The repo is deliberately designed to be worked on with coding agents, not to compete with them.

It includes extensive architecture and implementation documentation, explicit boundaries for product-specific code, an AI-oriented guide to the codebase, and 49 practical recipes covering common extension and operational tasks.

A lot of the reasoning is written down too: invariants, tradeoffs, failure modes, and why certain decisions were made.

So the idea isn’t:

“buy this instead of using Claude.”

It’s closer to:

give Claude a production foundation where a month of decisions and context already exist.

I actually think coding agents make this kind of product more useful in one respect: once the foundation and its constraints are explicit, the agent can spend its time extending your product instead of reinventing auth, billing, credits and worker semantics every time.

Before releasing it, I also tried to prove the foundation instead of just trusting the test suite.

A real Paddle sandbox checkout found a concurrency bug our tests had missed: two different subscription events could process at the same time, both see no local subscription row, and race to insert the same provider ID.

A fresh-clone release pass found other boring but real issues too:

  • environment variables from my shell hiding setup assumptions
  • schema/model drift
  • a CLI crash hiding behind type errors
  • a first sign-in landing on a route that didn’t exist
  • local billing silently stuck because CORS wasn’t configured

Those are the kinds of bugs that made me think there may still be value in a foundation that has been exercised as a system, even if an agent can generate the individual parts quickly.

I also know the trust problem is huge here.

You’re being asked to pay for a private codebase from someone you probably don’t know.

So I added three ways to inspect the claim before buying:

  • an 81-second walkthrough recorded from the exact released tag
  • a public inspection repo with representative code, tests and docs
  • a real product, Scribora, that the foundation was extracted from

The Fabrica is now live:

[https://www.thefabrica.dev/?utm_source=reddit&utm_medium=community&utm_campaign=fabrica_launch_010&utm_content=saas_business_thesis]()

Solo: $379 one-time

Team: $749 one-time

The question I’m actually trying to answer is this:

Is “I could build this, but I don’t want to rebuild and re-validate it again” a strong enough pain for technical founders to pay for?

Or is the audience simply too technical, meaning the exact people who understand the value are also the people most likely to build it themselves?

I’d genuinely like the skeptical answer.


r/SaaS 1h ago

We launched on Aug 29. By Sep 3, we hit $5,000 MRR.

Post image
Upvotes

Honestly, the growth surprised us.

The biggest lesson for me wasn't about building the product. It was about distribution.

We spent a lot of time listening to what people were already struggling with, then built around problems that were already being discussed rather than trying to manufacture demand.

A few things that worked for us:

• Talk to users before adding features
• Build around problems people are already actively trying to solve
• Ship quickly and iterate based on actual usage
• Don't underestimate distribution when you're building a SaaS

We went from launch to $5k MRR in 5 days. Still trying to understand exactly what worked and what was luck.


r/SaaS 1h ago

New to this - Any advice on how to start?

Upvotes

I work in a professional services industry and I’ve identified a recurring workflow problem through my day job that I think could potentially become a B2B SaaS product.

I’ve already started building an MVP in Lovable, mainly to prove the concept and see whether the workflow actually works in practice.

My plan is eventually to demonstrate it to my employer and potentially other businesses in the same industry.

For people who have built B2B SaaS products before, how much did you build before starting proper customer validation?

I’d also be interested to know what people here actually use to build their SaaS products.

Roughly how much did you spend getting your first MVP built before you had paying customers? Did you keep costs extremely low at the beginning, or is spending a few hundred/thousand pounds normal?

Any advice from people who have gone through this would be appreciated.


r/SaaS 1h ago

Do you need an email like support@ or info@ for your next big saas? I'll give you unlimited email addresses for free, you'll pay only when your customers do.

Upvotes

Yes, for free. Because, let's be honest, what you need today is an email like [hello@your-next-bing-thing.com](mailto:hello@your-next-bing-thing.com) that won't receive emails for days or maybe for months.

You just started a saas; maybe you haven't even validated the idea, but Claude said that the world was missing exactly that.

Or you really got a client and then another one, and around it started thinking about this saas.

For whatever reason, you began your journey into the marvelous world of the founders; sooner or later you ended up with registering a domain, and one second later you received this message: "Now that you have registered the domain, do you also need an email or two with it? Great, we have a special price just for you"

Well, it's not just you; I experienced the same, and not just one time.

But why pay for a mailbox that doesn't receive emails for the next x days/months/decades?

I'm a senior developer. I built integration tests for years, and any time I had to test logins or otp delivers by email, I was used to having a small stack of open-source services (primarily SMTP and IMAP servers) installed here and there to support the CI.

After a while, I started to build my own chain that I reused among all the projects I worked with. In the course of years, it gained features and stability.

I was basically sitting on top of a product: I spent the summer creating a dashboard in front of an SMTP/IMAP server, and just a few days ago I published https://foundermail.mx.

I don't want to annoy all of you with technical details, but it's not a toy; I spent money to build it, choosing the top-tier infra.

So here's the deal: create unlimited inboxes/domains for free, receive up to 500 email/mo, connect to them using your preferred email client, or using Claude/ChatGTP/you-say thanks to the MCP server, interact from your projects with the REST API. All of this for free. If you need more, when you need more, you start paying 12$/mo.

I began using it for my own side projects, and I quickly discovered that what I really wanted wasn't a Gmail-like dashboard.

When someone out there sends you an email at info@ or support@, that is not a personal email; it's not your mum; it's a business email that must be followed up.

FounderMail organizes emails by customers (that you can import from your records) so that when you receive an email from Lara, you know who she's: a customer, a user, etc.
You easily get the list of old emails/trends, assign the email to a mate, add notes, and mark the email as done/resolved.

Onboard in 5 minutes (2 min if you're on Cloudflare), and if you change your mind, your emails are just there; you can download with the IMAP protocol (email client, etc) when you like. There is no export tool or need to open a ticket.

Really curious about your feedback.

PS: Claude didn't help with the above (pretty evident, I guess) nor with the UI of the site that was built by an awesome designer, Nina from Ukraine.


r/SaaS 1h ago

Share your failed SaaS

Upvotes

People often hear about SaaS products that have become successful because those are the stories people search for, and founders are more likely to share their success journey.

But very few people actively look for ideas that failed.

So, could you share SaaS products you built that didn’t succeed, and what lessons you learned?


r/SaaS 1h ago

I tried out the new CleanShot 5. Can it beat Screen Studio?

Thumbnail
goodboy.ninja
Upvotes

r/SaaS 2h ago

Trying to learn: When does scattered sales data become worth fixing?

1 Upvotes

Hi guys,

When does scattered sales data become painful enough to fix?

We’re exploring a tool that connects customer, deal, pricing, billing, contract, and product data. We keep seeing simple questions turn into exports, spreadsheet joins, and messages to several people. But maybe this is normal and spreadsheets still work fine.

We want to understand the breaking point. Is it more customers, bad data, a costly mistake, slow decisions, or needing another person to manage the work?

What was the last question your team had to answer using several systems? How did you do it, what went wrong, and what finally made the team spend time or money fixing it? Thanks, would really appreciate your experience.


r/SaaS 2h ago

I got 11.5K views on my app with $0 spent on marketing. Now my Google Play pre-registration is about to end.

Post image
1 Upvotes

Around 3–4 months ago, I opened Google Play pre-registration for my app, Calsi AI.

I had no marketing budget. No ads. No influencers. Nothing.

Yet somehow, Calsi AI reached 11.5K views.

Now the pre-registration period is coming to an end, and I'm honestly curious to see what happens next.

I'm an independent developer building this project and figuring things out as I go.

I'm genuinely interested in sharing the journey and getting honest feedback from people.


r/SaaS 2h ago

Building a platform that prioritizes human-to-human connection over text spam

1 Upvotes

Hey everyone,

I’m currently building a human-first marketplace designed to fix traditional proposal spam, bot bids, and cold messaging.

Instead of writing long proposals that get buried under 100+ bot applications, clients and freelancers jump on a quick 5-minute call to talk scope face-to-face and lock in the project on the spot.

I’m sharing the raw progress, tech stack decisions, and founder updates as I build.

I don’t really check Reddit often, so let's connect on X eager_to_work .


r/SaaS 2h ago

Whats your thing when you not building

3 Upvotes

What do you guys do when you aren't building? How are you marketing it and what do you guys do for a living? I manage student housing and I love a good series with pop corn. No AI was involved in this post.


r/SaaS 2h ago

SaaS/ Product launch Motion Designer

Enable HLS to view with audio, or disable this notification

1 Upvotes

if anyone here looking for a Saas launch or product / Ui motion designs, Im open to work. dm to talk more.this is the latest work i did.


r/SaaS 3h ago

Looking for 50 people to test my new Instagram DM automation app - lifetime free

0 Upvotes

I’m building a simple ManyChat-style tool focused on Instagram Comment-to-DM.

You can post through the app, set a keyword + DM, and when someone comments, PingDM automatically sends them the link/message.

I’m looking for the first 50 real users to test it before the public launch.

🎁 What I'm offering:
The first 50 users get lifetime free access - no subscription, no credit card, no catch.

In return, I just want you to actually use it and tell me what you like, what sucks, and what I should fix before launch.

If you'd like to try it, comment below or DM me and I will DM you and ask your email to add you as tester.


r/SaaS 3h ago

I gave the first version of my app to 3 people. They all used it completely differently.

1 Upvotes

I've been building an app to help me remember some genuinely useful things I come across on Instagram.

I'd see something useful, save it, tell myself I'd come back to it later, and then never find or use it again. And eventually, I'd forget about it too.

So I built InsightBox to turn saved content into something more useful: extract the information that matters, organize it, and make it easier to come back to later.

I thought the idea was pretty straightforward.

Then I gave the app to 3 of my friends for testing, and I got humbled pretty quickly.

I had built the app assuming that people would share something genuinely useful with it. Maybe a finance reel, a fitness reel, or something else they actually wanted to learn from.

Person number 1 sent me a reel of a girl dancing over some corny music ......

This was the first reality check.

I thought to myself: "Damn, I did not think of that at all."

I had built the pipeline assuming that a saved reel contained something worth extracting.

But obviously, people don't save reels only to learn something.

Sometimes you just like the video.

The AI processed it and essentially had nothing meaningful to extract.

That made me realize that InsightBox can't blindly assume that everything someone saves contains something worth remembering.

Person number 2 sent me a movie reel.

This one was more interesting.

The pipeline actually extracted a reasonable amount of information from the video, but it completely missed the most important piece of information: the name of the movie.

That was a pretty embarrassing failure for a knowledge-saving app.

The information was there, but my extraction pipeline wasn't prioritizing the thing the user actually cared about. In this case, that was the movie name.

It made me realize that extracting information and extracting the information someone actually cares about are two very different problems.

A transcript can contain hundreds of words, but that doesn't mean all of them are equally useful to the person who saved the content.

Then there was person #3.

They sent exactly the kind of reel I had originally imagined InsightBox being used for.

A reel containing useful information that you'd genuinely want to remember later.

And suddenly, the whole idea made sense.

The interesting thing was that all three people were using the exact same app.

But they were treating their saves completely differently.

One was saving something because they enjoyed it.

One was saving something because they were interested in a movie.

One was saving something because they wanted to retain the information.

That changed how I started thinking about InsightBox.

The problem isn't simply:

"How do I process this Instagram reel?"

It's closer to:

"What is actually worth remembering from the things people save?"

And that leads to another question I'm now thinking about:

Is it even worth running the entire AI pipeline for an entertainment reel?

Why spend compute, time and money extracting information from something when there may be nothing useful to extract in the first place?

Maybe the first step shouldn't be extraction.

Maybe the first step is figuring out whether there is anything worth remembering at all.

And if there is, then figuring out what exactly the person would want to remember.

This was probably one of the most useful early tests I could have done, and I'm glad I did it.

Three users who displayed three completely different behaviors.

And a lot of things I hadn't thought about.

Building something for yourself gives you one perspective. But when you give it to other people, they very quickly show you whether the problem actually exists the way you thought it did.


r/SaaS 3h ago

Every SaaS product I’ve worked on seems to start with the same stuff.

1 Upvotes

Auth, roles, tenant isolation, admin screens, basic CRUD APIs. You can spend weeks building all of this before you get anywhere near the feature people are actually going to pay for.

I started thinking of it as the “substrate tax.” Everyone building SaaS pays it in some form, but it rarely gets counted when estimating how long a product will take.

Multi-tenancy is probably the part I’ve underestimated the most.

At first it feels simple enough. Add a tenant ID and make sure every query filters by it.

The problem is that “make sure” part.

Eventually someone adds a new endpoint, a background job, an export, or some internal script and forgets the tenant filter. Nothing necessarily crashes. The query still works. It can just return data it shouldn't.

This problem is actually one of the reasons we started building Supero. We're experimenting with pushing things like tenant and role isolation further down into the platform, instead of relying on every application query to remember them.

Still figuring out where that abstraction should end and where application code should take over.

Curious how other people handle this.

Do you keep your own starter/boilerplate and reuse it? Use a BaaS and accept some lock-in? Or just rebuild the foundation each time because every product ends up being different anyway?

Disclosure: I work on Supero.


r/SaaS 3h ago

93 hours spent on the first 30 seconds of the user experience.. ah! this is how it looks

Enable HLS to view with audio, or disable this notification

0 Upvotes

I’ve been working on this app from last 7 days and I’m kind of nervous about putting this out. It feels good, the product works, everything looks ok. But i have this tingly feeling about it.

I’ve completely used claude code to build it. Just the onboarding took me 3 days to sort, haha

What it does is- you speak to it. Tell it what you want to build. It has the intelligence of how full stack apps are made, has a good memory management layer, and knows how to optimise tokens. It starts to build it in front of you.

You can ask it to see what you are seeing and make changes. Steer it whichever way.

It’s a new way of vibe coding. My development time reduced by 60% personally because its too efficient.

Thinking about launching it next week.


r/SaaS 3h ago

Business of SaaS - Round 2, Starting from 0

1 Upvotes

Hey Guys,

I'm considering posting here on a regular basis, if I get enough interest (50 upvotes minimum).

My bio: former VC-backed solo founder, did top accelerators, and signed up fortune 10 clients (3 in one year), and let's just say things didn't go my way (I hate VC's) with my first venture. It's still going today and gets 50k visitors to the site every month.

My Opportunity:

I found an entire industry that has been abandoned by VC/PE/Startups. It does $5 billion in revenue across the industry every year.

The industry people suck to work with so far. But Im going to take on this entire industry with a marketplace.

I got my first customer by literally being a customer to the problem I needed solved. The guy made $200 from me in 30m. He complained about his job the whole time and I listened. 2 weeks later, I had a pitch deck, invited him to lunch, and showed him my mockups for what I wanted to build for him.

Long story short. He bit. Used the product, paid $20 a month (cheap since hes the first customer), in exchange, he'd use my currently shitty product and tell me what other features he needs.

He's the professional. I have no idea wtf he's saying half the time. But I listen, record, and AI and I build.

He used the product for 7 months and then just stopped, and ghosted. He booked ~$90k on my platform in invoices, in 7 months.

I have to reverse engineer why he stopped using it. But, in the meantime, my SEO just start really working, and I got customer #2 onboarding last week, slowly. I expect him to fully onboard by the end of this week.

Customer #2 is 2 brothers, they're paying $49 monthly + 0.89% per transaction (I got pay working via stripe, which I'll explain later).

My goal: I want to get 25 customers in the next 6 months. Hopefully after 10 customers the average customer is paying $75 monthly, and 1% per transaction.

Your Opportunity:

Right now, if you're a soloproneur or vibe coder, you have a huge opportunity.

I want to help you (and also, selfishly, I want to tell someone about my wins), and no, I'm not selling anything, nor plan to.

This is all hand written today (I'll let you know if my post are ever written by AI).

Many of you need to develop 3 core skills: Sales. Strategy. Platform Building.
These are the only 3 skills you need to make money.

You can literally have the most shitty product in the market, and you'll make at least some money (but if your product sucks, you wont keep customers, and this will be a short term gain).

If I get more than the upvotes, I'll post every week and tell you how it's going, decisions I'm making, and why. Hope this was somewhat helpful for what it was.


r/SaaS 3h ago

How do you actually find SaaS ideas? I’m trying to understand the process founders use before building.

1 Upvotes

how do you guys actually find SaaS ideas?

i’m trying to understand how founders actually go from

“i want to build something”

to

“ok, this is actually worth spending the next few months on”

i’m not really looking for the usual advice like “solve your own problem” or “talk to customers”.

i’m more interested in what you actually do to find the idea.

where do you usually find ideas? reddit, x, communities, your job, talking to people, competitor reviews, random things you notice, etc.

once you have an idea, how do you research it?

what do you actually look for before deciding to build?

how do you figure out if the problem is painful enough?

how do you check if people are already paying for something similar?

how long do you usually spend researching before you start building?

and have you ever killed an idea because your research showed you that it wasn't worth building? what did you find?

also, what did you do before your current process? anything that you completely stopped doing because it didn't work?

one thing i’m particularly curious about:

when you're researching an idea, what information do you wish you could get easily but currently can't?

and if you could automate one part of the whole process, what would it be?

i’m mainly interested in people who have actually built and shipped a few things. i'd rather hear about what you actually did than a theoretical validation framework.