Flow

Flow started as a simple observation from inside private markets: the capital was sophisticated, but the infrastructure around it was not. Too much of the industry ran on PDFs, email, and manual process. The friction was invisible until you lived it.

We built Flow to remove that friction. Not with another point solution, but with a system that treated private market operations as a real product category. The goal was to make investing feel closer to modern software: faster, clearer, and easier to trust.

At the core is a belief I still hold: operational clarity is not back office work. It is a prerequisite for good judgment.

Flow became a platform for the day to day mechanics of running private investments. Onboarding and KYC. Data rooms and document workflows. Entity management. Investor communications. Relationship management. The unglamorous, essential work that makes capital actually move.

We served GPs and their teams, and the downstream reality of their investors. Over time the product expanded, but the design constraint stayed the same: reduce time to clarity. Make the system legible. Make it easier for people to do the right thing without heroics.

I led Flow through product and company building, and eventually through its acquisition. The experience deepened my interest in how institutions scale without losing integrity, and how software can encode trust instead of bureaucracy.

Every market has its own version of "friction." In private markets, it shows up as delay, opacity, and uneven access.

Removing friction is not just about efficiency. It changes who can participate, how quickly decisions can be made, and how much energy remains for actual value creation. When systems are clean, judgment improves. When systems are messy, people compensate with politics, process, and exhaustion.

Flow taught me that the most leverage often lives in the unsexy layers, the workflows, the permissions, the handoffs, the moments where reality turns into a form.