Before starting Kiefern, I co-founded and scaled a B2B SaaS company in Berlin. We grew to 200 employees, navigated three major enterprise contract negotiations that each took longer than twelve months, rebuilt our onboarding infrastructure twice after realising the first version did not survive contact with German procurement processes, and eventually completed a strategic exit. I do not raise this as a credential claim. I raise it because the question I get most often from founders evaluating whether to take our check is whether having a former operator on the cap table actually changes anything, and the honest answer is: it changes specific things, it does not change everything, and understanding which is which matters.
What changes: the first meeting. When a founder walks me through a product that automates a procurement workflow, I have a mental model of what the workflow looks like from the inside of a 150-person company — the specific friction points, the workarounds the operations team has built, the procurement software integration that never quite worked, the annual contract negotiation with the main supplier where someone has to pull data from three systems to prepare for the call. This means I can ask questions at a level of specificity that a non-operator investor often cannot. Not better questions necessarily — experienced non-operator investors ask excellent questions from different angles — but questions grounded in operational experience rather than pattern-matching from comparable deals. For founders who are themselves deep operators, this resonates in a way that is genuinely useful.
What does not change: the fundamental VC evaluation framework. We still assess market size, team composition, product differentiation, and capital efficiency trajectory using the same underlying logic as any disciplined seed investor. My operational experience does not make a bad market opportunity a good one, and it does not change the fact that a weak technical team at seed stage is the most reliable predictor of eventual product failure. Where I have seen operator-investors go wrong is in over-weighting their own operational experience when it conflicts with what the market data is showing. Having successfully scaled one company through a particular channel does not mean that channel is right for every company in the same sector. The confidence that comes from experience can produce blind spots as easily as it produces insight.
The more nuanced value is in portfolio support rather than investment evaluation. When a portfolio company is working through their first enterprise contract negotiation and needs someone who has sat across the table from a German procurement director at a €200M manufacturing company, that specific operational memory is useful in a way that general frameworks are not. When a founder is trying to figure out whether to hire a head of sales from an enterprise software background versus promoting an internal account manager who knows the product deeply, I have made both decisions and can speak to the specific failure modes of each. This is not advice that can be derived from first principles — it comes from having been wrong in specific ways and remembering the cost of each mistake.
We are not saying operator-investors are categorically better than non-operator investors. The VC landscape has produced exceptional returns from people who never ran a software company, and the systematic thinking that comes from deep investment experience has its own compounding value. What we believe is that for a fund focused specifically on enterprise software automating the kinds of operational workflows that Kiefern targets — document-heavy, process-embedded, sold into buyers who have been disappointed by previous software deployments — having an investment team with direct operational context in that problem space changes the quality of diligence in ways that compound over the life of a fund. That is the specific bet we are making.