u/Fragrant-Status-9634

Not productively. Not in a "rest is part of the process" motivational way.

Just genuinely weird.

Woke up with no list. Nothing urgent. No reason to open the laptop. Sat with that for about an hour doing nothing and feeling increasingly uncomfortable about doing nothing which told me something about where my head has been for 4 months.

Went for a walk. Actual long one. No podcast. No voice notes. Just walking.

Somewhere around the 40 minute mark my brain solved a problem I'd been circling for three weeks. Not attacked it. Solved it. Completely. The kind of solution that makes you stop walking and just stand there for a second.

I'd been too close to it. Looking directly at it every day. Sometimes the answer lives just outside the edges of the thing you're obsessing over and the only way to find it is to stop looking directly at it.

Came home. Wrote everything down. Back to work.

The day off lasted about 4 hours before I was back at the laptop. But those 4 hours did something that the previous 3 weeks hadn't.

I don't think I'm good at resting. I'm not sure founders are supposed to be.

But I'm starting to think doing nothing on purpose occasionally is actually part of the job and not a break from it.

When's the last time you actually stopped and did it change anything?

Not to investors. Not to users.

To yourself.

There's this performance you do every morning where you open the laptop and act like yesterday's doubt didn't happen. Like the 2am thought that maybe none of this was going to work has been resolved somehow by sleeping on it. Like you're the confident founder you describe yourself as in every conversation with anyone who asks how it's going.

How's it going.

Fine. Good. Making progress. Exciting stuff happening.

Meanwhile you're refreshing a dashboard that hasn't moved in four days and trying to figure out if that means something is wrong or if that's just how this goes and you're catastrophizing again.

The internal experience of building something is so far from the external version of it that sometimes they feel like two completely different stories happening to two different people.

I have a product that works. Real users. Real feedback. Some days I feel completely certain about where this is going.

Other days I am genuinely unsure if I'm building something real or just doing an increasingly elaborate version of keeping busy so I don't have to face the possibility that it might not work.

Both of those things are true on alternate days. Sometimes on the same day.

Nobody talks about this part because it doesn't have a clean resolution. There's no moment where the doubt permanently leaves. You just get better at working next to it.

Is it just me or does everyone doing this live in that gap between the external version and the internal reality?

I'd built the product. I'd tested it. People had used it for free and said good things. Everything was technically ready.

But the moment I had to put an actual number on something I'd made with my own hands and send it to a real person and wait for them to decide if it was worth that something completely different happened in my chest.

What if they said no. What if they laughed at the price. What if they paid and then felt cheated three days later.

All of that hit at once while I was staring at a payment link I'd spent 20 minutes constructing.

I sent it anyway.

They paid within 4 minutes.

I sat there for a while doing nothing. Not celebrating. Just sitting. Something about that transaction felt more real than anything that had happened in the previous 8 months combined. All the building, all the late nights, all the "almost ready" conversations at dinner — none of it felt as real as that one notification.

₹90k is not life changing money. I know that.

But it was the first time someone who didn't know me, didn't owe me anything, had no reason to be generous decided what I built was worth something to them.

That's a different feeling entirely from everything before it.

First paying customer was harder emotionally than I thought it would be. Anyone else find that the money part hits differently than you expected?

Last month someone offered me a position. Good company, decent package, the kind of thing you'd be stupid to say no to on paper.

I said no.

Sat with that decision for about 3 days after. Not because I regretted it. Because I couldn't explain it to anyone around me in a way that made sense to them.

My parents have watched me spend 8 months building something they can't fully see or touch or show their friends. There's no offer letter. No designation. No answer to "beta kya karta hai" that lands cleanly at a family function.

What there is a product that real people are using daily now. People who didn't know me before, had no reason to be nice about it, and still came back the next day.

That part I can't explain to my relatives either. But it means something completely different to me than any offer letter ever could.

The hardest thing about building something from scratch in India isn't the technology or the market or the competition. It's the sustained weight of everyone around you quietly waiting for you to come back to something that makes sense to them.

Some days that weight is motivating. Some days it's just heavy.

8 months in. Still building. Still getting the same questions at every family function.

Anyone else navigating this? How do you handle the gap between what you're building and what the people around you can understand?

People go quiet.

Not confused quiet. Processing quiet. There's a specific 10 second window after someone sees it work for the first time where they just stare and don't say anything.

Then they ask me to do it again.

That reaction has happened enough times now that I've stopped being surprised by it and started being curious about it. Because it tells me something about the gap between what people expect from AI tools right now and what they actually experience when something works differently than everything they've tried before.

Marrow runs locally on Windows. You talk to it naturally, it operates your machine. Opens apps, reads files, manages tasks, responds back. No typing. No clicking. No breaking whatever you were actually thinking about to go manage your computer.

The part that consistently surprises people isn't the technology. It's that it listens continuously without being activated by a wake word. You just talk. It figures out if you're talking to it or not.

That one thing changes the whole experience. Feels less like using a tool and more like having something in the room with you.

Sharing here because this community tends to give the kind of feedback that's actually useful rather than polite.

What's the first thing that breaks for you when you try a new AI tool?

Nobody told me. That's the part that gets me.

Not because people were dishonest. Because I wasn't asking the right people the right questions. I was showing it to people who were supportive by nature. Friends. People who wanted to see me succeed. People who said "this is cool" because they meant it but cool and necessary are completely different things.

I confused the two for 6 months.

The moment I put it in front of a stranger who owed me nothing the feedback changed completely. Not harsh. Just honest in a way that people who care about you can't really be.

I looked at what I'd built through though out these months, got some more ideas

Rebuilt the core of it in 3 weeks.

The version I have now is so different from what I started with that they barely share the same logic. Same problem being solved. Completely different understanding of what the problem actually was.

I think about how long I would have kept going in the wrong direction if that one stranger hadn't asked that one question.

Probably a long time.

Has anyone else built something for months only to realise you'd been solving the problem slightly wrong the whole time? What made it click?

The thing that gets me is I can demo it and people immediately get it. Something clicks visually in about 90 seconds and they go from confused to genuinely interested without me saying much.

But the moment I have to describe it with words before showing it I lose people every single time.

I've rewritten the landing page headline maybe 11 times. Each version makes complete sense to me. Each version has confused at least one person I've shown it to.

A friend who works in marketing looked at it and said "I understand every word you've written and I still don't know what this is."

That sentence has lived in my head rent free for three weeks.

I'm starting to think the explanation problem is actually harder than the building problem. At least with building there's a clear answer at the end. Either it works or it doesn't. Explaining something new to someone who has no reference point for it feels like it has no finish line.

How did you figure out how to talk about what you built to people who had never heard of anything like it?

Spent months building something I genuinely believe in.

The product works. I know it works because the few people who've actually used it told me so without me asking them to be nice about it.

The problem is I've never been the guy who's good at the part that comes after building. Posting about it feels weird. Talking about it constantly feels worse. I'm just not wired that way and I've accepted that about myself.

But here's where I'm stuck.

Every piece of advice I find online assumes you either have an audience already or you're comfortable becoming a content machine. Post every day. Build in public. Tweet your journey. Go viral.

I tried. Feels like performing. And when something feels like performing I do it badly.

What actually worked for people who got their first real users without an existing audience and without becoming a different person to do it.

Not looking for a framework. Not a blog post. Just what you actually did when you were at zero and nobody knew you existed.

How did you find the first people who genuinely needed it

What did outreach look like before you had any credibility

If you started over tomorrow with no audience what would you do differently

Genuine ask..

I'm not even sure how to explain this properly but I'll try.

Built something for months completely alone. No team, no co-founder, nobody to reality check anything. Just me and whatever made sense in my head.

Thought I understood the product deeply. Knew every corner of it. Could explain any decision I made and why.

Put it in front of people last week for the first time.

First guy spent maybe 90 seconds on it then pointed at a feature I had hidden three levels deep because I thought it was minor. Said that was the only thing he actually cared about. Everything else was noise to him.

Second person looked at me and asked "why wouldn't I just use my keyboard for this."

I knew the answer. But I had never once made that answer visible anywhere in the product. No where

Four months. Two comments. Twenty minutes.

I keep thinking about how many other assumptions are still sitting in there that feel obvious to me but make zero sense to someone using it for the first time. Probably more than I want to know.

Is this normal or its just me

Built a voice-controlled desktop assistant over the past several months. The kind that listens, responds, opens apps, reads files, handles tasks while you talk.

Technically it worked pretty early. Like embarrassingly early compared to how long I kept building.

The real bug was me explaining it wrong to everyone.

I'd demo it and people would go quiet in a good way. Then I'd open my mouth and say something like "it's like an AI assistant but actually useful" and watch their eyes glaze over immediately.

Took me longer than I want to admit to realize the product wasn't the problem. My ability to communicate what made it different was the problem.

I had built something genuinely specific. Voice commands that control your actual desktop. Not a browser extension. Not another chatbot. Your whole machine. And I kept describing it like every other AI product because I'd gotten too close to see what was actually interesting about it.

The demo did the work every single time. My words undid it every single time.

Fixed it eventually by just shutting up and letting people use it for 90 seconds before saying anything.

Has anyone else found that the hardest thing to build was actually the explanation, not the product?

No warning. No email. No reason.

Just woke up one morning. The account I had spent months building. Real posts. Real conversations. Real karma from actually contributing to communities. Gone.

The timing was the worst part. Three days into launch. Momentum was just starting to build. People were engaging, asking questions, some were even coming back to update me on how they were using it. And then silence. Because the account they were talking to just ceased to exist.

I sat with that for a full day doing nothing.

Then made a new account and kept going. Not because I had some inspiring moment of resilience. Just because stopping felt stupider than continuing.

But here's the thing that actually bothered me more than the ban itself I still don't know why it happened. Not knowing means I don't know what to avoid. Which means I'm building on a platform that can pull the rug with zero explanation and there's genuinely nothing you can do about it.

Reddit is simultaneously the best and most brutal channel for getting early customers. The organic reach is real. The conversions are real. But you are always one silent algorithm decision away from starting over completely.

Has anyone else been through this? How do you protect yourself from building too much on a platform you don't control?

Hii everyone how would you guys especially the ones who have grown saas to good MRR

How would get first few paid users

The challenge is your saas is completely paid

And those 3 are the only ones keeping me going right now.

Not because the other 47 don't count. But because those 3 did something nobody asked them to do.

They emailed me after signing up. No follow up from me, They just wrote

One guy sent four paragraphs about a specific frustration he has every single morning. Detailed. Almost angry. Like he'd been waiting for somewhere to put it.

A woman asked if she could jump on a call this week.

The third one just said "please don't abandon this."

That last one I keep coming back to.

Because building alone does something to your head that nobody really warns you about. Some days the conviction is so clear it's almost physical. Other days you're staring at your screen at midnight genuinely asking yourself if any of this is real or if you've just convinced yourself it matters.

The waitlist number doesn't help on those nights. It's just a number.

But that email does. Every time.

I've read it probably eleven times now. Not because it's some incredible piece of writing. Because it reminded me there's a real person on the other side of this thing who is genuinely waiting. Who noticed. Who cared enough to say something without anyone asking them

47 people signed up. 3 of them told me why.

Those 3 are the whole reason I opened my laptop this morning.

What was the moment that made you stop doubting and just ship?

Not looking for validation. Just sharing what happened because I genuinely couldn't find anyone talking about this specific situation.

I've been building an AI assistant. Not a chatbot. Something very similar like friday from iron man that reads your files, opens your apps, handles tasks, talks back. The kind of thing you describe to someone and they say "okay but does it actually work?"

It works.

So I got 20 people on live calls. People who asked to see it, not random cold traffic. Walked them through everything in real time.

Reactions were wild. Genuine ones. One guy just went quiet for half a minute staring at his screen. A few said they'd never seen anything do what it just did. Nobody was politely nodding. They were actually into it.

Then I asked about the paid beta.

"Let me know when it's fully out." "I need to sit with this." "Send me a reminder closer to launch."

Two people gave me actual objections. Specific ones. I showed them live on the call that I'd already fixed both of them. They said "oh that's actually solved, nice." Still didn't pay.

I spent days thinking the product was broken. It wasn't.

The people were wrong. Not bad people. Just not the ones with a painful enough problem to pay for a solution today. There's a version of your customer who thinks what you built is cool. And there's a version who genuinely needs it. I had spent four months finding the first kind.

Same demo. Same product. Wrong room.

Lesson, when you are building you should not be taking every advise, suggest too seriously from anyone becuase you're building this for some not for the whole 8 billion people so you gotta know your customers and make decisions accordingly I seen guys literally listening to everything and making the worst decision