Most descriptions of portfolio operations focus on what the role is for. Fewer describe what it actually does on a Tuesday.
The gap matters. When funds hire for this role without a clear picture of the daily work, they end up with someone who facilitates introductions and writes frameworks. That is not portfolio operations. That is a very expensive advisor.
What people imagine
The imagined version of portfolio operations looks like this: a senior operator who sits across the portfolio, identifies strategic patterns, connects founders to resources, and synthesises insights for the fund. A kind of ambassador between the GP team and the companies.
That work exists. It is not the hard part, and it is not where the value is.
What the work actually is
The actual work is infrastructure. It is mapping a hiring funnel inside a Series A energy storage company and finding that the process has seven steps, four of which require the founder, and the median time to hire is eleven weeks. Then rebuilding that process to four steps, removing the founder from the first three, and getting median time to hire below fourteen days.
It is sitting inside a pre-commercial synthetic biology company and watching how leads are qualified. Finding that qualification is not happening — that every inbound gets a meeting, that no one is tracking which meeting types convert, and that the founder is spending twelve hours a week on calls that produce nothing. Installing a qualification framework, a structured outreach cadence, and a pipeline review rhythm. Then measuring what changed.
It is looking at the onboarding process for a new commercial hire at a grid software company and finding that there is no process. That every new hire gets a laptop, a Slack invite, and two weeks of confusion. Then building a thirty-day onboarding plan specific to the role, the product, and the commercial context.
This work is not glamorous. It is diagnostic, operational, and repeatable. That is what makes it valuable.
How the role differs by fund stage
The specific work changes depending on which stage the fund focuses on.
At a seed-focused fund, the portfolio companies are typically five to twenty people. Founding teams are operating on shared context and informal process. The operating problems are existential in the sense that the company is still deciding what it is. Portfolio operations at this stage is about installing the minimum viable infrastructure — enough hiring process to make the next five hires without the founder running every search, enough GTM structure to test which customer segments respond, enough reporting cadence to give the GP team visibility without burdening the company. The work is lightweight by design. You are not installing an enterprise operating system. You are building the scaffold that will eventually hold one.
At a Series A and B-focused fund, the companies are past proof of concept. They have fifteen to fifty people, commercial traction, and a board that expects professional operating cadence. The problems are different: hiring is no longer experimental but the systems are still founder-dependent; GTM has a playbook on paper but the execution is inconsistent; internal workflows are straining because the founding team's informal communication style stops working at thirty people. Portfolio operations at this stage is more intensive — the diagnostic goes deeper, the installation takes longer, and the handover requires more training. But the leverage is higher because these companies are spending real money and the cost of operational dysfunction is measurable in revenue.
The mistake funds make is applying the same model across both stages. Seed-stage companies do not need the same operating intervention as a Series B company burning two million dollars a month.
The specific infrastructure that gets built
Across climate portfolios at the pre-Series B stage, three categories of infrastructure come up most frequently.
Hiring infrastructure is the most common gap. The typical state is: founder writes job description, posts it, reviews CVs manually, runs all first-round calls, makes offers on gut feel, and has no structured onboarding for the first ninety days. The rebuilt version has a structured role specification built from the commercial output the company needs, an AI-enhanced screening layer that surfaces the top ten percent of applicants without founder review, a two-stage structured assessment that produces a clear hire or no-hire recommendation, and a role-specific onboarding plan that gets a new hire productive in thirty days rather than sixty. The difference is not about working harder. It is about removing founder time from the steps where founder judgment is not required.
GTM systems are the second most common gap. The typical state is a pipeline tracked in a shared spreadsheet, no defined qualification criteria, inconsistent follow-up, and a close rate that does not reflect the quality of the product. The rebuilt version has defined ICP criteria — which companies, which buyers, which use cases — a structured qualification process at the first meeting stage, a follow-up cadence with defined touchpoints and templates, and a monthly pipeline review that produces decisions rather than updates.
Operating cadence is the third. The typical state is ad hoc check-ins, decisions that bounce back to the founder because no one else has the authority or information to make them, and reporting assembled manually by someone who could be doing something more valuable. The rebuilt version is a weekly team rhythm with defined inputs and outputs, a monthly management review with standardised metrics, and a quarterly planning process that connects resource allocation to commercial targets.
Why climate specifically is different
Climate tech is not like enterprise software, and the portfolio operations approach cannot be imported wholesale from that context.
Three things make it different.
The talent pools are smaller and more specialised. Hiring an experienced electrochemical engineer for a battery technology company is not like hiring a senior account executive for a SaaS company. The qualified pool is global, not local. The candidate's motivations are different — many are leaving tenured academic positions and need to understand the company's technical credibility before they will move. The assessment criteria are different — you are evaluating someone whose relevant work may be unpublished or behind an NDA. A generic hiring process designed for commercial roles does not work here. The infrastructure needs to be built for the specific talent market.
The commercialisation timeline is longer and less linear. A software company can move from product to revenue in months. A company commercialising a novel electrolysis process or a carbon capture material is operating on a timeline measured in years, with regulatory gates, pilot programmes, and customer validation cycles that have no equivalent in software. GTM systems need to reflect this. Qualification criteria that make sense for a twelve-week sales cycle do not make sense for a twenty-four-month enterprise partnership cycle. The pipeline metrics need to be calibrated to the actual decision process of the customer, not imported from a different industry.
The science-to-scale transition is a unique management challenge. Most climate tech companies are led by scientists or engineers who built the technology. The transition from technical leadership to commercial leadership — from running a lab to running a company — is not automatic, and the operating infrastructure needs to support it. That means building systems that give technical founders visibility into commercial performance without requiring them to become commercial operators. It means installing reporting that surfaces the right decisions without burying them in data. It means creating the conditions where the founder can stay focused on the technical work that created the company's advantage while the commercial and operational systems run without them.
How the work compounds across a portfolio
The first time you install a hiring system inside a climate deep-tech company, it takes four weeks of diagnostic work and six weeks of installation. The second time, the diagnostic takes two weeks because you already know which questions to ask. The installation takes four weeks because you are not starting from scratch. By the fifth company, you have a library of role specifications, screening frameworks, and onboarding plans that cover most of the hiring categories a climate portfolio company will need. The setup time drops. The quality improves.
That is the compounding effect that makes portfolio operations meaningfully different from doing the same work as a series of individual consulting engagements. The knowledge accumulates. The playbooks sharpen. The deployment accelerates.
For a fund with twelve companies at similar stages, this compounds into a real operating advantage — not for one company, but across the portfolio as a system.
If you run a climate or deep-tech fund and want to map what this infrastructure looks like against your current portfolio, book a session.