The Most Dangerous Feedback Is Encouragement

Most startups don't fail because the founders are lazy.

They fail because nobody asked them the uncomfortable questions before they started building.

Friends encourage you.

Investors meet you too late.

AI usually answers the question you asked, not the one you should have asked.

The expensive mistake isn't building the wrong company.

It's never discovering the better one sitting right next to it.

I'm building a platform that challenges your original idea, generates stronger nearby opportunities, and makes them compete on evidence before you commit months of your life.

Because the idea you fall in love with shouldn't automatically win.

I'm looking for a small group of early founders who want to put their ideas through a proper due-diligence process before they commit months of work.

If you're building something, or even just thinking about it, and want to find out whether your current idea is actually your best one, react or reply to this post.

I'll send you a private early-access link to try IdeaTwister.

reddit.com
u/srkgupta — 5 days ago

The Most Dangerous Feedback Is Encouragement

Most startups don't fail because the founders are lazy.

They fail because nobody asked them the uncomfortable questions before they started building.

Friends encourage you.

Investors meet you too late.

AI usually answers the question you asked, not the one you should have asked.

The expensive mistake isn't building the wrong company.

It's never discovering the better one sitting right next to it.

I'm building a platform that challenges your original idea, generates stronger nearby opportunities, and makes them compete on evidence before you commit months of your life.

Because the idea you fall in love with shouldn't automatically win.

I'm looking for a small group of early founders who want to put their ideas through a proper due-diligence process before they commit months of work.

If you're building something, or even just thinking about it, and want to find out whether your current idea is actually your best one, react or reply to this post.

I'll send you a private early-access link to try IdeaTwister.

reddit.com
u/srkgupta — 5 days ago

The Most Dangerous Feedback Is Encouragement

Most startups don't fail because the founders are lazy.

They fail because nobody asked them the uncomfortable questions before they started building.

Friends encourage you.

Investors meet you too late.

AI usually answers the question you asked, not the one you should have asked.

The expensive mistake isn't building the wrong company.

It's never discovering the better one sitting right next to it.

I'm building a platform that challenges your original idea, generates stronger nearby opportunities, and makes them compete on evidence before you commit months of your life.

Because the idea you fall in love with shouldn't automatically win.

I'm looking for a small group of early founders who want to put their ideas through a proper due-diligence process before they commit months of work.

If you're building something, or even just thinking about it, and want to find out whether your current idea is actually your best one, react or reply to this post.

I'll send you a private early-access link to try IdeaTwister.

reddit.com
u/srkgupta — 5 days ago

Laid off with six months of runway and how do you figure out which idea can actually survive?

Something I keep noticing after layoffs: quite a few people either return to entrepreneurship or finally start working on ideas they’ve wanted to build for years. With only a few months of runway, they usually pick the version of the idea they can explain the fastest.

The 90-second pitch becomes the decision filter. It feels rational because the idea sounds clear, coherent, and easy to sell to friends or ex-colleagues. But I’m starting to think that’s often the wrong signal. A good narrative is not the same thing as a business people will consistently pay for.

The people I’ve seen make better decisions approached it differently.

Instead of committing early, they wrote multiple variations of the same idea and forced every version to answer the same questions:

  • Who pays?
  • How much do they pay?
  • How quickly can revenue happen?

Nothing fancy. Just short drafts, rough positioning, and tiny paid tests.

A couple spent 30–60 minutes generating variations, then ran small pilots over the next week. The results were surprisingly clear. Some versions got repeat interest almost immediately. Others sounded impressive in conversation but completely fell apart once real buyers were involved.

A few real examples:

  • One founder found a niche monthly-paying customer segment within two weeks.
  • Another realized his preferred GTM path required long enterprise sales cycles and burned months of runway before closing anything.

That second lesson seems especially brutal when you only have six months.

Curious how others think about this:
What early signals do you trust most when evaluating ideas under runway pressure?

And what micro-experiments actually cut through the noise fast?

Would love specifics:

  • outreach numbers
  • test durations
  • pilot pricing
  • landing page tests
  • pre-sales
  • red flags you ignored and later regretted
reddit.com
u/srkgupta — 1 month ago

Laid off with six months of runway. How do you figure out which idea can actually survive?

Something I keep noticing after layoffs: quite a few people either return to entrepreneurship or finally start working on ideas they’ve wanted to build for years. With only a few months of runway, they usually pick the version of the idea they can explain the fastest.

The 90-second pitch becomes the decision filter. It feels rational because the idea sounds clear, coherent, and easy to sell to friends or ex-colleagues. But I’m starting to think that’s often the wrong signal. A good narrative is not the same thing as a business people will consistently pay for.

The people I’ve seen make better decisions approached it differently.

Instead of committing early, they wrote multiple variations of the same idea and forced every version to answer the same questions:

  • Who pays?
  • How much do they pay?
  • How quickly can revenue happen?

Nothing fancy. Just short drafts, rough positioning, and tiny paid tests.

A couple spent 30–60 minutes generating variations, then ran small pilots over the next week. The results were surprisingly clear. Some versions got repeat interest almost immediately. Others sounded impressive in conversation but completely fell apart once real buyers were involved.

A few real examples:

  • One founder found a niche monthly-paying customer segment within two weeks.
  • Another realized his preferred GTM path required long enterprise sales cycles and burned months of runway before closing anything.

That second lesson seems especially brutal when you only have six months.

Curious how others think about this:
What early signals do you trust most when evaluating ideas under runway pressure?

And what micro-experiments actually cut through the noise fast?

Would love specifics:

  • outreach numbers
  • test durations
  • pilot pricing
  • landing page tests
  • pre-sales
  • red flags you ignored and later regretted
reddit.com
u/srkgupta — 1 month ago

I kept rearranging the same 4 startup ideas for 8 months

Started last year with one idea I couldn't stop thinking about.

By August I had four.

Not four launched projects. Four tabs in a notes file. Four half-shaped futures I kept rotating every Sunday like the answer was going to reveal itself if I stared long enough.

I'd rank them.
Re-rank them.
Rename them.
Open competitors.
Close competitors.
Convince myself Idea #2 had better distribution.
Then suddenly panic that Idea #4 had more urgency.

Nothing actually moved.

The embarrassing part is I called this "research" for months.

But most of it was just avoidance with prettier vocabulary.

I wasn't scared of building the wrong thing. I was scared of finding out I wasn't good enough to make any of them work.

The moment that finally snapped me out of it wasn't some framework or customer interview.

My wife asked me at dinner which idea I was building this month.

And I gave literally the same answer I'd been giving since March.

I think even she noticed I sounded tired of hearing myself.

The next morning I picked the idea I felt least emotionally attached to. Mostly because I knew I could look at it more honestly.

Instead of building immediately, I forced myself to generate around 75 variations of it. Different customer types, different pains, different angles, different ways it could spread.

Some were terrible.

Some were basically the same idea wearing different clothes.

But a few of them accidentally exposed something uncomfortable: three of my "different" startup ideas were solving the exact same emotional problem. I had just been changing the wrapper each time to trick myself into feeling momentum.

Deleted all three from the notes file that afternoon.

Still don't know if the remaining idea is good.

But at least I'm finally building something instead of reorganizing my uncertainty every weekend.

reddit.com
u/srkgupta — 2 months ago

I kept rearranging the same 4 startup ideas for 8 months

Started last year with one idea I couldn't stop thinking about.

By August I had four.

Not four launched projects. Four tabs in a notes file. Four half-shaped futures I kept rotating every Sunday like the answer was going to reveal itself if I stared long enough.

I'd rank them.
Re-rank them.
Rename them.
Open competitors.
Close competitors.
Convince myself Idea #2 had better distribution.
Then suddenly panic that Idea #4 had more urgency.

Nothing actually moved.

The embarrassing part is I called this "research" for months.

But most of it was just avoidance with prettier vocabulary.

I wasn't scared of building the wrong thing. I was scared of finding out I wasn't good enough to make any of them work.

The moment that finally snapped me out of it wasn't some framework or customer interview.

My wife asked me at dinner which idea I was building this month.

And I gave literally the same answer I'd been giving since March.

I think even she noticed I sounded tired of hearing myself.

The next morning I picked the idea I felt least emotionally attached to. Mostly because I knew I could look at it more honestly.

Instead of building immediately, I forced myself to generate around 75 variations of it. Different customer types, different pains, different angles, different ways it could spread.

Some were terrible.

Some were basically the same idea wearing different clothes.

But a few of them accidentally exposed something uncomfortable: three of my "different" startup ideas were solving the exact same emotional problem. I had just been changing the wrapper each time to trick myself into feeling momentum.

Deleted all three from the notes file that afternoon.

Still don't know if the remaining idea is good.

But at least I'm finally building something instead of reorganizing my uncertainty every weekend.

reddit.com
u/srkgupta — 2 months ago

What surprised me about using Resend as a lightweight CRM over the weekend

I had a side project that needed something CRM-shaped. A way to capture leads, tag them with where they came from, run a recovery drip if they started checkout and walked away, and pause everything the moment someone replied like a human. The right answer is probably HubSpot or Customer.io, but I really did not want a 200 dollar monthly invoice for an audience that was still mostly my mom and three friends from Twitter.

I already had Resend wired up for transactional email. The first time I poked around their dashboard I noticed a feature called Custom Contact Properties, where each contact can carry arbitrary structured data, and Automations can read it for conditions and personalization. That sounded like enough.

I gave myself a weekend. It took longer.

The thing I did not expect to learn was how much the boring infrastructure mattered. The interesting part of the project, in my head, was the lifecycle email itself. Recovery drips, onboarding sequences, reply detection. The actual time sink was the four or five rate-limit and ordering issues that hit me before I could send a single useful email.

The first one was the worst. Resend has a 5 req/s rate limit. I had a create-the-property-if-it-does-not-exist pattern in my submit handler, which seems sane until your serverless function cold-starts and fires twenty of those in the first quarter second. Some succeed. Some get rate limited and silently fail. Some succeed on retry but in a different order. The end state of my audience drifted depending on which lambda happened to win the race that day.

The fix was to take property creation out of runtime entirely and put it in a build-time bootstrap script. Idempotent, spaced at 250ms between calls. Wired into npm prebuild so every deploy syncs the schema. Twenty lines of code that I should have written on day one.

The second one was about reply detection. I wanted every drip to pause the moment a contact replied to me, so I set up Resend Inbound, a webhook that fires when an email hits a domain you control. I built the handler, deployed, sent a test reply, and got a forwarded email with an empty body. Turns out the webhook payload does not include the message body. Only metadata. To get the actual text you have to make a separate API call with the email_id. The docs say this in passing and my eyes had glazed right past it.

The third was a concurrency one I only caught in production. Two automations running for the same contact at the same time, both sending email, stepping on each other. Resend's workflow editor does not have a built-in concept of this contact is busy. So I built a per-contact lock using a property called last_automation, where the first step of every workflow checks it is empty or already equal to self, and the last step clears it. Easy, until I forgot to clear the lock on a timeout branch and silently broke automations for half my contacts.

I built a small tool called IdeaTwister around the same time, and the full writeup of the CRM hack is here in case it saves anyone the same week of head-scratching: https://ideatwister.com/blog/using-resend-as-a-lightweight-crm. The post has the actual code, not just the lessons.

The big takeaway, which sounds obvious in retrospect, is that lifecycle email is mostly state machines wearing a costume. Funnel state, attribution, locks, replied flags. Once that scaffolding is sane, the email content is the easy part. Most of the SaaS tools I was tempted to pay for are basically a UI on top of those four things and a sender.

I am curious if anyone else has stretched a transactional email tool into something CRM-shaped. Where did it break for you, and at what point did you give up and pay for something proper?

u/srkgupta — 2 months ago