Detachment: Why I Shut Down a Startup with 800 Users

My cofounder slept on my couch for two months. Every night about the product, users, what wasn't working. Then one day I told him we should stop.

We had 800 signups. Real people using the thing. But I knew it wasn't going to work.

That decision came from detachment. Not apathy. Not giving up. Detachment.

Most people get this wrong.

They think detachment means you don't care. That's not it. You care about the mission. You care about building something real. But you detach from outcomes you can't control yet. You detach from the noise that pulls you off course.

If you're building something, you need to learn this. Because the alternative is emotional chaos. You'll panic in week two. You'll quit when you should push. You'll push when you should quit.

Let me explain how this works.

The Stock Trade That Changed Everything

One of the biggest decisions I ever made was putting a massive amount of my money into one stock. I didn't tell many people. The ones who knew thought I was fucking crazy.

And they were right to think that.

For most people, it would have been the wrong move. But for me, it ended up altering the entire course of my life.

The hardest part wasn't the risk. It was detaching from how it looked. I believed in the thesis. I had done the work. But I still had to sit with the fact that people thought I was being reckless. That I might look stupid. That I might lose everything.

As Kobe said: "Remove yourself from that. Remove the ego from this process and just focus on the act."

That's what I had to do.

I had to detach from the outcome. Not because I didn't care. But because caring about whether I looked smart or stupid would cloud the decision. I made the call. I accepted whatever would happen. I lived with it.

That's detachment.

The Problem with Caring Too Much

When you start a company, everything feels like a signal. Someone signs up and you feel like a genius. Someone churns and you question the whole idea. An investor says no and you spiral. A user complains and you rebuild the entire feature.

This is exhausting. It's also stupid.

Because in the early days, nothing means what you think it means. One person signing up doesn't validate your idea. One person leaving doesn't kill it. You're not trading on fundamentals yet. You're trading on noise.

Traders understand this better than most founders. When a trader buys a stock and it drops 5% the next day, they don't panic. They knew this could happen. Nobody times the bottom perfectly. The question isn't whether it went down. The question is whether the thesis still holds.

Same thing applies to building a company.

What to Detach From

You detach from the day to day. You detach from individual feedback. You detach from the emotional swings that come with putting something out there.

When we launched Quiib, people told us it was too slow. Fair. They told us the onboarding was confusing. Also fair. They told us the concept didn't make sense. Maybe true, maybe not.

At first, we listened to everything. Every critique felt urgent. Every suggestion felt like the missing piece. So we tried to fix it all. We got stuck in this loop of reacting instead of building.

That's what happens when you care about every data point. You lose the ability to see patterns.

What to Stay Attached To

You stay attached to the bigger picture. You stay attached to pattern recognition. You stay attached to why you started this thing in the first place.

With Quiib, the patterns started to emerge. Investors kept saying the same thing: you need more users. Users kept saying the same thing: this is too slow. Those two things were connected. More users required a faster product. A faster product required a complete rebuild. A complete rebuild was going to take months.

That's when I had to detach from the last eight months. From the fact that my cofounder had flown across the world to work on this. From the 800 people who signed up. From the sunk cost of time and energy and belief.

The risk reward wasn't there anymore. I didn't think we could pull off the rebuild. Even if we did, I wasn't sure it would matter. So I made the call.

That's detachment. Not because I stopped caring. Because I cared about the right thing: whether this was still a bet worth making.

The Trader Analogy

Traders think in probabilities. They know that even good bets lose sometimes. They know that timing matters but timing is also luck. So they focus on the thesis. They focus on edge. They focus on managing risk.

When you buy a stock and it drops, you don't sell immediately just because you're down. You ask: has anything changed? Is the reason I bought this still valid? If yes, you hold. If no, you cut.

Same thing with building. You launch something and traction doesn't come in week two. That doesn't mean the idea is bad. It means you're early. But if you're in month six and every piece of feedback points to the same fundamental problem, and fixing that problem requires resources you don't have, then you cut.

The hard part is knowing which one you're in.

When to Pivot vs When to Push

This is where most people mess up. They either give up too early because they can't handle the uncertainty. Or they push too long because they're attached to the wrong things.

You need rules. Not emotions. Not vibes. Rules.

Here's what worked for me:

If users are churning because the product is slow and buggy, that's solvable. You stay attached. You fix it.

If users are churning because they don't understand the value prop after using it, that's a thesis problem. You detach. You rethink.

If investors are saying no because you don't have traction yet, that's expected. You stay attached. You build traction.

If investors are saying no and users are saying the same thing they're saying, that's signal. You detach. You listen.

With Quiib, both groups were aligned. The product was too slow. That wasn't just a feature request. It was the core problem. And solving it wasn't a sprint. It was a rebuild. So I detached.

How to Practice This

Start by writing down your thesis. Not your pitch. Your actual belief about why this will work. What has to be true for this to succeed?

Then set milestones. Not daily check ins. Not weekly panic sessions. Real milestones. Month three. Month six. A year.

When you hit those milestones, ask: has the thesis changed? Are the patterns confirming what I thought or contradicting it?

If the patterns confirm it, keep going. Ignore the daily noise. Detach from the individual feedback. Stay attached to the bigger picture.

If the patterns contradict it, cut. Detach from the sunk cost. Detach from the identity you've built around this thing. Move on.

The Current Bet

Right now I'm building something new. It's high risk, high reward. I know traction won't come in week two. I know I'll hear feedback that makes me doubt the whole thing. I know there will be days where it feels like I'm moving sideways.

But I also know what I'm doing and why.

I know this wont be one shot and done.

I know the game I'm playing.

So I'm detached from the short term emotions. I'm detached from whether this feels like progress on day seven or day seventy.

I care about the outcome. But I don't care about the outcome yet.

That's the difference.

You can't build anything real if you're emotionally attached to every single data point. You'll quit too early or push too long. You'll ignore feedback you should hear or overreact to feedback that doesn't matter.

Strategic detachment lets you stay in the game. It lets you make decisions based on patterns, not panic. It lets you care about the mission without caring about the noise.

That's how you build. That's how you know when to pivot. That's how you know when to push.

Detach from the outcomes you can't control yet. Stay attached to the work that moves you forward.

Remove the Ego

The hardest part of detachment isn't the logic. It's the ego.

You don't want to look stupid. You don't want to be the person who quit too early or pushed too long. You don't want people to think you made the wrong call.

But that fear will kill you. Because you'll start making decisions based on how they look instead of whether they're right.

When I put most of my money into one stock, people thought I was crazy. When I shut down Quiib with 800 users, a user called me 6 months later and asked why I gave up. When I decided to build something new, people wondered if I learned my lesson.

None of that matters.

Kobe had it right. Remove yourself from the process. Remove the ego. Focus on the act. Focus on the decision in front of you and whether it's the right one based on what you know now.

Not what people will think. Not how it will look. Not whether you'll feel vindicated or embarrassed.

Just the act itself.

That stock trade worked out. It changed my life. But it could have gone the other way. The point isn't that I was right. The point is that I made the decision without being attached to needing to be right.

Same with Quiib. I shut it down because the thesis changed. Not because I needed to prove I could quit. Not because I was tired. Because the patterns told me to cut.

That's what strategic detachment gives you. The ability to make decisions based on reality. Not on ego. Not on sunk cost. Not on what other people think.

You care about the mission. You care about building something real. But you detach from needing to look smart while you do it.

That's the game. That's how you stay in it long enough to win.

Detach from the outcomes you can't control yet. Stay attached to the work that moves you forward. And remove the ego from the process entirely.

That's how you build. That's how you know when to pivot. That's how you know when to push.