What we got wrong about vertical AI in 2024
We passed on four companies for the same reason, and three of them are now doing well. Here is the mistake we made and the question we ask instead.
We publish when we have learned something, not on a schedule. Memos, field notes, and the occasional guide we wish had existed when we were operating.
We passed on four companies for the same reason, and three of them are now doing well. Here is the mistake we made and the question we ask instead.
We had a rule that vertical AI companies needed proprietary data to defend a position. It turned out that distribution into an unloved workflow was worth more, at least at this stage of the cycle.
The question we ask now is simpler: who is doing this work today, how much are they paid, and what would make them switch on a Tuesday morning.
We passed on four companies for the same reason, and three of them are now doing well. Here is the mistake we made and the question we ask instead.
Inference costs fall, usage climbs, and the pricing page you wrote at launch stops making sense. Notes from eleven portfolio companies that repriced.
Our talent team looked at hiring data across the portfolio. The pattern is unglamorous: teams that hired slowly at the start moved faster at Series B.
Most data rooms are either thin or bloated. This is the version we ask for, with the reasoning behind each item.
Tobias spent a decade inside one. He wrote down how procurement actually works, including who can say no and who can only say yes.
Ownership matters less to us than being early enough to be useful. An argument for writing the first cheque, including the part where it hurts.
A short format we use with early companies. Two pages, one decision, no theatre.
Three founders in our portfolio agreed to talk candidly about resetting valuation, telling the team, and getting back to work.
Investment thinking, including the times we were wrong. Usually written by whoever led the deal.
Short pieces from inside the portfolio. Pricing changes, hiring data, sales cycles that took longer than planned.
Practical documents founders can copy. Data room checklists, board formats, reference call scripts.
Send a short note. We read every one and reply within five working days, whatever the answer.