A VC platform lead recently asked: "I have eleven portfolio companies on HubSpot, six of them are messy, where do I start?" The instinct is to triage by company, pick the messiest, embed for a quarter, move on. That model does not compound. By the time you finish company three, four and five have drifted further. Portfolio RevOps support only scales when the unit of work is the audit, not the company. Run the same 90-minute pass across all eleven, sort them into four buckets, and intervene on the bucket, not the logo.
Why this matters now
Founder underinvestment in RevOps is structural. Poyar has argued at length that combining product-led motion with traditional sales: the standard shape of an early-stage B2B SaaS portco: creates operational complexity around org structure, hiring, comp, and account assignment that founders systematically undersize until forecasts start missing. At that point the platform team is asked to intervene downstream of a year of accumulated debt. Multiply that across eleven companies and the platform team is staring at eleven simultaneous cleanups, all urgent, none building on each other. The support model has to flip, define the audit upfront, run it on every portfolio company on intake, and accept that 60% of the value of platform RevOps is the diagnostic, not the implementation.
The platform-team trap
Most VC platform teams are staffed by one or two senior generalists who have run RevOps inside a portfolio company before. The instinct is to help the way they used to help, embedded, hands-on, sleeves up inside one company at a time. That model worked when they were the operator. It does not work when they are the fund.
The issue is that bespoke help across a portfolio is uncapped in time and unrepeatable in output. Every engagement starts from zero. Every recommendation is one-off. The platform team becomes a slow internal consultancy, and the portcos that actually get help are the loudest at the LP meeting, rarely the same set as the ones with the highest leverage from intervention.
The 90-minute portfolio audit
What scales is the inverse, define a single audit template, fixed scope, fixed time, fixed output. Run it on every portfolio company at the same depth. Use the audit, not the company, as the unit of work.
The version we run at Checkpoint covers four areas in 90 minutes:
- Pipeline definitions. What are the deal stages? Does each one have a one-sentence definition, an entry criterion, and an exit criterion? Can two reps describe "qualified" the same way? Most portfolio companies fail this in the first 15 minutes.
- Lead source attribution. Where do contacts come from, and is the source actually populated on creation? Is there a single source-of-truth field, or three competing ones? Can the platform team reconcile a campaign spend number against a sourced-pipeline number without a manual export?
- Marketing-contact accounting. How is the HubSpot contact tier being managed? Is there a workflow that auto-marks marketing contacts on lifecycle change, and does it match the actual paid tier? This is where seat costs leak.
- Renewal and post-sale hygiene. Is there a renewal pipeline distinct from new business? Are subscription objects in use, or is renewal tracked in a custom property nobody updates? Is customer success operating against a system, or against a spreadsheet?
Ninety minutes is not a deep dive. It produces a one-page diagnostic and a triage decision.
The four problem categories
Every portfolio company audit lands in one of four buckets. The intervention is matched to the bucket, not designed from scratch.
Category 1, Greenfield install
Seed or pre-Series A, founder-led GTM, HubSpot was set up by a founding AE in a weekend. There is no debt because there is no system. The intervention is a templated install, standard pipeline, standard lifecycle stages, standard lead-source schema, standard renewal pipeline. We have a portable HubSpot template the platform team deploys in a sandbox, validates against the company's actual deal data, and ships in two weeks. No bespoke design work.
Category 2, Brownfield triage
Series A or B, HubSpot has been live for two-plus years, custom property count is in the hundreds, and three former RevOps hires each left their fingerprints. The intervention is a keep / edit / delete pass, covered in a separate post, and the output is a cleaned-up schema the next hire can actually operate against. This is most of what platform teams inherit.
Category 3, Replatform candidate
Sitting on Pipedrive, Attio, or a Salesforce instance the team has outgrown but cannot afford to migrate alone. The intervention is a migration scoping doc and a vendor decision, not an implementation. The platform team's value is the unbiased platform-selection conversation, they have done it five times across the portfolio, and the founder is doing it once.
Category 4, Operating model gap
The CRM is fine. The problem is upstream, there is no defined ICP, the buying persona is fuzzy, the territory is undefined, the comp plan punishes the wrong behavior. No HubSpot intervention will fix this. The platform team's job is to flag it to the board and connect the founder with a fractional GTM lead, not to spend three months tuning workflows that will be rewritten in six.
Sharing patterns across portcos without leaking data
The compounding only works if the platform team can move learnings between portfolio companies. The fastest path is a private, anonymized pattern library: of the eleven companies audited, eight had the same lead-source attribution gap, here is the workflow shipped to fix it. The library is the asset; the portcos are consumers, not contributors-by-name. No portco data moves between portcos. What moves is the recipe: a templated workflow export, a property schema, a pipeline definition, rebuilt in clean form, free of any source company's identifiers.
Pattern from the field
A DACH-based early-stage fund's platform lead came in with eleven portfolio companies on HubSpot and a quarter to show LPs measurable progress. The instinct was to embed in the two messiest. The actual project was different. We ran the 90-minute audit on all eleven in three weeks. The triage came out, four greenfield installs, five brownfield triage, one replatform candidate, one operating-model gap that needed a fractional GTM hire rather than a CRM project. The greenfield four shipped in eight weeks against a single template. The brownfield five each got a scoped keep / edit / delete project with a 30-to-50% custom-property reduction. By month four, the platform team had measurable improvements across nine of eleven portcos, on roughly the headcount that previously got bespoke work into one and a half.
Resolution, a portfolio RevOps playbook
For a platform team setting up portfolio RevOps support from scratch:
- Define the audit before you offer help. Write a 90-minute audit script with four to six questions per area and a one-page output template. The audit is the product.
- Run the audit on every portfolio company on intake. Make it part of the post-investment 30-day plan, not a reactive call when something is on fire. Cadence creates the dataset.
- Triage into the four categories. Greenfield install, brownfield triage, replatform candidate, operating model gap. Force the choice; do not invent a fifth bucket per company.
- Build templated interventions for categories one and two. A portable HubSpot install template, a keep / edit / delete spreadsheet, a renewal-pipeline schema. These are reusable assets, not bespoke deliverables.
- Run "office hours" for everything else. A weekly two-hour open slot the platform team holds for any portco RevOps question. Most issues do not need an embedded engagement; they need 20 minutes of senior judgment.
- Maintain a private anonymized pattern library. Workflows, schemas, and process documents stripped of source-company identifiers, indexed by problem category. The library compounds the audit dataset.
- Outsource the embedded work. Categories three and four, and the deep brownfield projects in category two, are external engagements. The platform team stays scarce and senior; the implementation depth comes from a vetted partner.
Step seven is where most platform teams resist. It is also where the model becomes durable. A platform lead doing implementation inside one portco cannot run the audit on the next eight.
Where Checkpoint comes in
We run portfolio audits and the templated interventions that come out of them as a standing service for venture funds and family offices in DACH and EMEA. The economics work because the audit is fixed, the four interventions are templated, and the platform team keeps senior judgment in-house while we carry implementation depth across multiple portcos. If you are a platform lead trying to scale RevOps support across more than five portfolio companies, talk to us about how VC portfolio support can compound rather than burn your team out one company at a time.
Sources
- Poyar, Kyle. "PLG and Sales in 2023: How to Combine Them for Efficient Revenue Growth." OpenView, June 13, 2023. openviewpartners.com
- Lemkin, Jason. The RevOps playbook: how Owner.com's CRO scaled from 0 to $1B ARR. SaaStr. saastr.com