Why We Build Instead of Advise

For most of my career, I sat on the other side of the table. I evaluated companies, wrote checks, joined boards, and gave advice. Good advice, I think — hard-won from pattern recognition across dozens of companies and billions in capital deployed. But advice is not the same as building. I learned that slowly, then all at once.

The best outcomes didn't come from the best advice. They came from founders who were too close to the problem to see any other option but to solve it.

What investing taught me about building

The pattern I saw repeated across every successful company I backed was the same: founders who had lived the problem so completely that they couldn't imagine not solving it. They weren't building because the market was attractive. They were building because they had no choice. That obsessive, insider understanding is what creates products that actually work — not market research, not advisory boards.

I also saw the inverse repeatedly: smart teams with good capital and solid advice that built products disconnected from the real pain. The advice was correct in the abstract. The product didn't fit the specific, messy reality of how people actually worked.

The decision to build

When I founded Renn Labs, the question wasn't whether to build — it was what to build first. The answer came from the same place all good product decisions come from: a problem I knew intimately. The fundraising process for emerging fund managers is broken in specific, fixable ways. The workflow automation layer that commerce operators need doesn't exist in the form they need it. Those weren't hypotheses. They were things I had watched fail up close.

Advising is valuable. I still believe that. But it's a different leverage point than building. When you build, you bear the consequence of being wrong in a way that sharpens every decision. That accountability produces a different quality of product. That's why we build.