so for years i was the dev who insisted on writing tests before features. felt professional. felt safe. on big team projects it was clearly the right call. then i started a side project as solo dev. kept doing tests first. shipping was painfully slow because i was testing edge cases for features that might get deleted next week. ditched the tests, just shipped. mvp out in 2 weeks instead of 6. things were fine until month 3 when i refactored a core function and broke 4 other things i didnt know depended on it. spent a weekend debugging stuff that would have been caught by 3 lines of test code.

Learned the hard way that "no tests on side projects" is correct until your codebase has enough interconnections that a small change breaks something far away. around 2k lines of code is roughly when it switches for me. before that tests slow you down, after that they save you.

For the fullstack folks here, whats your rule for when to start writing tests on a solo project

So for the first few months running my saas i tried to act on every piece of feedback i got. user wants dark mode, ill build it. user wants integrations with notion, ill build it. user wants a mobile app, ill scope it.

3 months in i had a feature list 40 items long and shipped almost nothing because i was context switching constantly.

then i started a simple rule. if 1 person asks for a feature its an idea. if 3 people ask for it independently its a signal. if 5 people ask its a priority. anything below 3 goes in a parking list and i forget about it.

dropped my backlog from 40 to 7 features. shipped 5 of them in 6 weeks. retention went up because the features people actually wanted got built instead of buried.

for the indie founders here, do you ship every request or filter, and if you filter whats your rule

So for the longest time i obsessed over signups per week. it felt like the most important number. then i realized half my signups never came back after day 1, and the ones who paid were a tiny fraction with almost no correlation to total signup volume. signups was vanity dressed up as growth. switched to tracking weekly paid users only and a separate column for week 4 retention. way more honest, way less flattering. the dashboard got boring but decisions got clearer. curious what metric the saas folks here used to track religiously then stopped because it was lying to them

Genuinely stuck on this. been sitting on a list of 5 small saas ideas for the past 2 months. all of them sound reasonable on paper. all of them solve a real problem i can describe in one sentence. but every time i try to pick one, i convince myself the next one is better.ended up building nothing for 8 weeks.read a bunch of "validate before building" articles but honestly half my list is in niches where surveys wouldnt help, the users are too busy to fill forms and too small to find in big communities.

curious how the founders here cut through this. do you just pick the easiest one to ship and commit, do you ask your network which one they would pay for, or is there a smarter filter im missing. tired of writing down ideas and not picking one

So for months i was waiting for my first paid signup to feel "real". got the first one. felt nice for about an hour. then went back to wondering if it was just a fluke.

the actual moment it felt real was 3 weeks later. a user emailed me at 11pm pissed off because something broke on his end and he was about to use it for a client deadline. detailed, specific, angry email. fixed it in 20 minutes and emailed him back.

he replied "thanks man, this is exactly why i pay for stuff that has a real person behind it".

that was the moment. not the payment, the complaint. because a complaint means somebody cares enough to write you a paragraph at 11pm about a bug instead of just churning silently.

silent users are the dangerous ones. complaining users are the keepers.

curious for the indie founders here, when did your project actually feel real to you, what was the moment

So for the longest time i started every side project the same way. installed tailwind, then shadcn, then radix, then a fancy animation library, then a custom design system folder before writing a single feature. felt very professional. spent 3 to 4 days on the boilerplate before any real work.

then for my last project i tried something different. plain html and css with minimal classes. one font. one accent color. a single button style. no design system, no component library.

ugly at first.

shipped the mvp in 4 days instead of the usual 2 to 3 weeks. and the users who tried it gave feedback on functionality, not visuals. nobody complained the buttons werent perfectly rounded.

added polish only after i knew which features actually mattered. by then i had real usage data telling me exactly where the visual investment was worth it. way better return than guessing upfront.

the lesson i took, design polish before product market fit is procrastination disguised as craft. ugly working software ships faster and teaches you more than beautiful demos.

for the fullstack folks here, do you start projects with a design system or do you also ship ugly first

So for the first 6 months of running my saas i tracked everything. signups per week. trial starts. landing page conversion. email open rates. demo bookings. login frequency. session duration. had a notion dashboard with 14 numbers updated weekly.

felt very founder of me.

problem was, half those numbers went up while revenue stayed flat. signups doubled in month 3, mrr barely moved. session duration went up after a ui redesign, churn didnt change. i was getting positive signals from vanity metrics and ignoring the silence on the metric that mattered.

last quarter i deleted 12 of the 14 numbers. kept only two. weekly paid signups and weekly cancellations. thats it. every monday i look at those two numbers and decide what to do that week. nothing else.

revenue grew faster in the next 8 weeks than the previous 6 months combined. not because the numbers were magic, but because i finally stopped optimizing for things that made me feel busy.

the lesson, founders who track 20 metrics are usually hiding from the 2 metrics that actually matter. busy work is comfortable, revenue is uncomfortable, dashboards are an escape from the truth.

for the founders here, what numbers did you stop tracking that made your decisions easier

So for the longest time i started every side project the same way. installed tailwind, then shadcn, then radix, then a fancy animation library, then a custom design system folder before writing a single feature. felt very professional. spent 3 to 4 days on the boilerplate before any real work.

then for my last project i tried something different. plain html and css with minimal classes. one font. one accent color. a single button style. no design system, no component library.

ugly at first.

shipped the mvp in 4 days instead of the usual 2 to 3 weeks. and the users who tried it gave feedback on functionality, not visuals. nobody complained the buttons werent perfectly rounded.

added polish only after i knew which features actually mattered. by then i had real usage data telling me exactly where the visual investment was worth it. way better return than guessing upfront.

the lesson i took, design polish before product market fit is procrastination disguised as craft. ugly working software ships faster and teaches you more than beautiful demos.

for the fullstack folks here, do you start projects with a design system or do you also ship ugly first

So i hired 3 different freelance devs in the past year for a small saas i was building. all three had clean portfolios, good github, decent reviews. first one delivered late and the code was a mess. second one ghosted halfway through. third one was actually solid.

the catch was, the third one had the worst landing page of the three.

trying to figure out if theres a real way to filter for actual delivery vs surface polish. some things i tried that helped a bit:

a tiny paid trial task before the real project. costs me 50 to 100 dollars but saved me thousands.

asking for a video walkthrough of their last project, not just a link. you learn a lot from how someone explains their own code.

checking how they handle one or two pointed questions in dm. fast clear answers usually predicted good work later. vague answers predicted ghosting.

curious how others here filter when hiring. anyone found a method that actually predicts who delivers vs who disappears

so for the first 6 months of running my saas i tracked everything. signups per week. trial starts. landing page conversion. email open rates. demo bookings. login frequency. session duration. had a notion dashboard with 14 numbers updated weekly.

felt very founder of me.

problem was, half those numbers went up while revenue stayed flat. signups doubled in month 3, mrr barely moved. session duration went up after a ui redesign, churn didnt change. i was getting positive signals from vanity metrics and ignoring the silence on the metric that mattered.

last quarter i deleted 12 of the 14 numbers. kept only two. weekly paid signups and weekly cancellations. thats it. every monday morning i look at those two numbers and decide what to do that week. nothing else.

revenue grew faster in the next 8 weeks than the previous 6 months combined. not because the numbers were magic, but because i finally stopped optimizing for things that made me feel busy.

the lesson, founders who track 20 metrics are usually hiding from the 2 metrics that actually matter. busy work is comfortable. revenue is uncomfortable. dashboards are an escape from the truth.

for the solopreneurs here, what numbers did you stop tracking that made your decisions easier

3 months into running my saas as a solo founder. revenue is finally paying rent which feels great. but here's what i didnt prepare for. every single customer email comes to me. every bug report, every billing question, every "how do i do x" comes to me. 80+ emails a week now. some of them at 2am from users in other timezones who genuinely think a company is on the other end. i dont have the heart to tell them its just one guy with a laptop. building was the easy part. being the entire support team forever is the part nobody puts in their hustle posts. for other solo founders here, how do you handle support at scale, do you outsource, batch responses, or just accept that you live in your inbox now

Genuinely curious. not asking for the famous ones everyone recommends like notion or chatgpt. asking for the small underrated stuff. for me its been keeping a simple text file open all day where i dump random thoughts and todos instead of switching to apps. sounds dumb but it saved me from context switching like 30 times a day. whats your boring but useful one

been working on a side project for 3 months now. like 20 users, no revenue yet, but they actually use it weekly. cant tell if its just a hobby that some people happen to like, or if its worth quitting other stuff to focus on. for the founders here who turned a side project into a real business, what was the moment you knew it was worth going all in. or did you wait too long, or jump too early

Quit my job last year. No co-founder, no funding, no team. Just me and one very specific problem to solve.

The Problem

Everyone chases big markets. But big = competition, complexity, and burnout. I wanted a niche so small no VC would ever touch it.

One question changed everything: What's a problem 1,000 people would pay $20/month to solve?

Not a million. A thousand.

The Niche

Freelance video editors managing client revisions. Painful, repetitive, ignored by big SaaS. Perfect.

The Build

• MVP in 3 weeks (Bubble + Airtable)
• Stripe + ConvertKit
• Total cost: under $200

The Launch

No Product Hunt. No ads. Just 4 subreddits and 2 Discords where my exact users hang out.

• Week 1: 12 paying users
• Month 1: $940 MRR
• Month 3: $3,200 MRR

What I Learned

1. Niche down until it feels uncomfortable
2. Charge from day one
3. You don't need a team, you need clarity
4. Distribution > product

Micro SaaS isn't about getting rich fast. It's about building small, owning it fully, and getting your time back.

What niche are you eyeing?

Genuinely curious. everyone talks about the cool features and launch posts. but whats the thing you actually struggle with daily that nobody mentions when they say "build a saas". for me its been customer support, didnt expect it to eat so much time.

i have been working on a small ai tool for tamil grammar and spelling correction. we already built something similar for hindi, and one thing i noticed is that regional language users have a real problem but not many polished tools are made for them. right now i am not focusing on big features. first i am trying to understand who will actually use it, like students, writers, teachers, book publishers, and content creators. one challenge is tamil has many writing styles, so simple correction is not always enough. context matters a lot. my current plan is to collect real examples from tamil books, publisher content, and user-written text, then slowly improve the correction quality. has anyone here built for non-english users before? how did you validate the first users before building too much?

I have been thinking about small business software ideas recently. many local businesses do not need a big platform, they just need one small tool that saves them time every week. but i am confused about where the line is between a custom tool and something that can become a micro saas. for people who have tried building micro saas, how do you decide if a problem is common enough to build for more than one customer? do you validate by talking to business owners, checking search volume, reading reddit problems, or building a small version first?