People ask me what it's like to have been part of six companies across three different parts of the world. They expect a success fairy tale, but the reality is that some of them failed. Not all of them, but enough that I stopped seeing failure as a rare and dramatic thing.
Most of the time, a startup dies slowly and quietly. You don't notice it's dying until it's almost too late. Here is what really killed the ones that didn't make it.
We Built Something Cool That Nobody Needed
The first one died because we built something clever that nobody was waiting for.
The tech was good. The demos went well. People said "cool" and then went back to their day. We thought that meant they liked it. But nobody ever asked, "When can I use this?"
When people really need something, they act differently. They ask about the price before you're ready. They tell their friends without you asking them to. But we kept building anyway, because we loved the problem more than we cared about the customer.
The lesson is simple: learn the difference between people being polite and people actually needing your product. They are not the same thing.
The Co-Founders Didn't Match
One of them died because of the people, not the product.
Working with a co-founder is like a long-term relationship. It rarely ends because of one big fight. It ends because of many small problems that nobody talked about early enough.
One company, which we worked on for a year, fell apart because we never agreed on how hard each of us would work. On paper, we were equal partners. In real life, one person treated it like a side hobby while the other spent their savings on it. You don't see this gap in a pitch deck. You see it at 11pm on a Sunday, when one of you is working and the other hasn't replied since Friday.
Now, before I join anyone as a co-founder, we have the hard talks first:
- How many hours will each of us work?
- What does "all in" mean?
- Who decides when we disagree?
Spread Across the World Too Soon
Building across three continents sounds impressive. In real life, it costs you something every single day. One of my SaaS startups couldn't pay that cost.
The first cost is operational. Time zones slow everything down. Things get lost when one team hands work to another, and by the time everyone is finally awake at the same time, half the day is already gone. A decision that should take an hour ends up taking two days.
The second cost is harder to see, and it's the one that actually hurt us. Customers don't behave the same everywhere. A US customer and an Indian customer behave differently - everyone knows that. But even an Indian customer and an Indian living in the US (an NRI) behave completely differently. We assumed a feature that worked in one market would work in another for the same customer base (India). It didn't. We were building one product for what were really three separate markets.
It can work. I've made it work in my other startups. But only when a company already has good habits and clear ownership - and a clear idea of which market it's actually serving.
Get strong first. Then spread out. Not the other way around.
Money Matters
When it's their own money, most founders count every rupee. Then the investor's money arrives, and the same person is suddenly on a spending spree. To me that's backwards. Investors trusted you with their capital, so the care you take should go up, not down. Spending OPM - Other People's Money - carelessly goes against my ethics.
But spending itself was never the problem. Paying your team well is not a waste; it is the best money you will spend. Paying for good tools, and using AI to make your team faster, is not a waste either. That is leverage, and you should use it.
The waste is paying for capacity you don't use. That used to mean over-hiring. Now it also means AI. It's easy to look busy running ten agents and a dozen subscriptions, but if the work doesn't need them, it's the same mistake in a new form. People or AI, the rule is the same: pay for what does the work, not for the appearance of doing it.
What I Learned From All of This
People say failure is a great teacher. Honestly, I don't fully agree. Mostly it just hurts.
And most of the "lessons" weren't even new. I already knew them. You probably know yours too. We ignore them anyway - that's human nature - because knowing something and actually feeling it are two very different things. Failure just makes you feel what you already knew.
Still, a few things genuinely changed in how I build now:
- I respect time - mine and other people's - as something I can never get back. That's why I do my homework before the first call, not during it.
- I trust it when customers seem impatient to buy. That impatience is the real signal.
- I have the hard co-founder conversations first, not later.
- I try to keep the feeling that we're low on funds, even when we aren't. It keeps the problem interesting to solve, instead of something to throw money at.
Six startups, three continents. Some worked. Some didn't. The ones that failed aren't things I'm ashamed of - they're the reason I know what to look for now. And as I write this, I'm heading into my seventh.
If you're in the middle of one that's slowly dying, you probably already know it. The real question was never whether you can see it. It's whether you'll act on it while there's still time.
If you're building something in AI or cybersecurity, I'd love to hear about it - whether you're looking for a technical co-founder, a sounding board, or just a second set of eyes on what you're building. Reach out. Let's talk.
Written By
Kunal Vohra
Technical Co-Founder & Fractional CTO
I've co-founded 6+ startups across India, the UAE, and the US, spanning AI, Web3, fintech, and cybersecurity. I write about the technical and strategic decisions that determine whether a startup thrives or stalls.