← Back to writing

Knowing When to Step Away

FounderReal EstateLessons

We spend a lot of energy celebrating the decision to start something. We say almost nothing about the decision to stop.

I built BetterCapital for five years. I co-founded it, I was the CTO, and for a long stretch I was also the only engineer. It came out of my own life — I was a real estate investor who couldn't get a straight answer about how my own portfolio was doing, so I built the tool I wanted: track your properties, understand your returns, find your next deal.

The product worked. People used it. I learned more about real estate, and about building, than any course or book could have taught me.

And I still wound it down.

The honest reason is the unglamorous one: the traction wasn't there — not the kind that tells you to pour the next five years in. I could feel myself holding on out of attachment — to the code, to the identity, to the sunk time — rather than out of conviction about where it was going.

Stepping away from something you built is a strange kind of grief. It's not failure, exactly, and it's not success. It's the quieter skill nobody teaches: being honest with yourself about a thing you love.

Here's what I'd tell the version of me who was still deciding:

  • The time wasn't wasted. The domain knowledge, the instincts, the scar tissue — I carry all of it into everything I build now.
  • Holding on too long has a cost too. Every month you spend propping up the thing that isn't working is a month you're not spending on the thing that might.
  • You're allowed to be proud of something and still let it go.

I don't think of BetterCapital as the one that didn't make it. I think of it as the chapter that taught me the most. I'm glad I built it, and I'm glad I knew when to close it.

Comments