Portfolio operating playbook · 2026
It's whether the engine actually runs.
A system moves only as fast as its weakest capability.
Score the demand engine across six capabilities and three levels. The lowest score is the constraint, and that's where the next dollar and next sprint go.
Six questions · 90 seconds · one constraint
Worked example · Portco scorecard
Data & CRM: lifecycle architecture
Reads as Expansion overall, but Data & CRM sits a level below. Every attribution report and orchestration play depends on it.
Executive summary
Most portfolio companies are scored on revenue and headcount. Neither tells you whether pipeline is repeatable, measurable and independent of the founder.
6 × 3
Six capabilities, three levels, one benchmark per capability. Every portco is scored the same way, so scores compare across the portfolio.
min()
A system moves only as fast as its weakest capability. The lowest score is the constraint, and that's where the next dollar and next sprint go.
2 gates
Each level has an explicit gate. A company doesn't move up because it raised a round. It moves up when the gate criteria are true in the data.
The model
Predictability and efficiency don't rise in a straight line. They inflect once the foundation holds, which is why fixing the constraint pays back faster than adding spend.
01
Prove it works · Seed–Series A
Prove your acquisition channels convert and build a demand engine you can actually scale on. The job here is signal, not scale.
The gate
Graduate to Expansion when a channel converts repeatably, your ICP is written from real data, and your CRM can be trusted.
02
Make it predictable · Series B–C
Turn what works into a predictable, measurable machine. The job here is velocity and ROI: pipeline you can forecast.
The gate
Graduate to Leadership when pipeline is forecastable, attribution drives budget, and the motion runs without the founder in every loop.
03
Make it compound · $50M+ ARR
Compound your advantage: expand share of wallet, open new markets, and let brand pull do the work push used to. The job here is efficiency at scale.
The frontier
The work shifts from building to defending: keep the system improving faster than it decays.
The 90-second self-diagnostic
Answer each question with what's true today. The gap is the point.
01 · Targeting & ICP
Pick one · sets this capability's level
02 · Channel Engine
Pick one · sets this capability's level
03 · Data & CRM Infrastructure
Pick one · sets this capability's level
05 · Orchestration
Pick one · sets this capability's level
06 · Ownership & Repeatability
Pick one · sets this capability's level
Self-assessments tend to run optimistic. When the evidence and the self-score disagree, score from the evidence. When the evidence doesn't exist, score Level 1.
Your capability profile
Average: 2 + 2 + 1 + 2 + 3 + 2 = 12 ÷ 6 = 2.00, rounds to Level 2
Constraint · fix first
Data & CRM Infrastructure
L1 · Foundation
Every report is suspect, every handoff drops leads, and no downstream play can be trusted.
First play
Lifecycle architecture
Define lifecycle and deal stages with written entry and exit criteria, then enforce them in the CRM.
KPI · % records correctly stagedExit gate
≥60% of records complete and correctly staged; routing runs without manual touch.
One-level rule
Pause incremental spend on the leading capability and redirect sprint capacity to the laggard until the spread closes.
Constraint logic
The six capabilities aren't independent. A Level 1 foundation corrupts every play built on top of it.
Foundation at the bottom. Fix ties in numbered order.
Data & CRM at Level 1 overrides everything. You can't prove a channel, trust attribution or route a signal on data you don't trust.
ICP before channel spend. A new channel pointed at the wrong accounts scales the waste.
Attribution before a third channel. If you can't measure two channels, you can't choose between three.
Ownership is last to build but first to diligence. Buyers price founder dependency as key-person risk.
Keep every capability within one level of the others. A company at Level 3 on channels and Level 1 on data is spending at scale and measuring nothing.
Spread of 2 levels = stop and rebalance.
The operating rule
Don't fund scale on top of a Level 1 capability.
Paid spend on a dirty CRM, SDR headcount before the message converts, or intent data with no ICP all spend money to amplify the constraint.
PE lens
Outlined cells are each company's constraint. The last column is where the first sprint goes.
Portfolio maturity heatmap · illustrative example
Deploy operating resources by score, not by volume of requests. A Level 1 constraint in Data & CRM or Ownership gets attention first. Those two block every other improvement and are the first things a buyer diligences.
How operating partners use it
The same six scores carry from the data room to the board pack to the next buyer's diligence.
01
Score the six capabilities from the data room and a CRM export. Verify self-reported answers against the evidence checklist.
You getA defensible read on GTM risk: founder dependency, data quality, channel concentration.
02
Identify the constraint and run the level-specific plays for it before funding growth spend.
You getA sequenced build plan instead of a list of ideas.
03
Re-score quarterly in the board pack. Track the KPI set for each company's current level.
You getBoard reporting on system health, not activity volume.
04
Run the same scorecard across every portco.
You getResources go where the scores are worst, not to whoever shouts loudest.
05
Target Expansion or better on all six capabilities, with reconciled GTM metrics.
You getA diligence-ready growth story the next buyer can underwrite.
Working with JayOh
The self-diagnostic tells you where to look. The full diagnostic maps these six capabilities against live data (CRM, pipeline, spend) and hands you the sequenced build plan. Then a growth pod runs the plays.
01
2 weeks
Our 18-metric scoring system run against live data: a defensible map of every leak and the prioritized plays that fix them.
02
Per-portfolio engagement
The same diagnostic across every portco, delivered as one comparable scorecard, so pods go where scores are worst.
03
Sprint-based delivery
A consultant plus developers embedded in the portco, owning the outcome and running the constraint's plays sprint by sprint.
We're not just another agency. We're your growth engineering team.
HubSpot Platinum Partner. Building GTM systems for B2B SaaS and PE-backed companies since 2016.
We engineer growth systems. JayOh builds the RevOps architecture, GTM execution and data infrastructure that turn messy revenue operations into predictable pipeline for B2B SaaS and PE-backed teams.
