Intelligence-to-Judgement Ratio: Scoring Your Portfolio for AI Readiness

The intelligence-to-judgement ratio is the cleanest operator score for AI readiness across a PE portfolio. It measures, for any given portco or workflow, the ratio of intelligence work (rule-driven, pattern-matching, high-volume) to judgement work (ambiguous, context-heavy, expertise-dependent) inside the cost base. High-intelligence-ratio portcos are AI-ready and deserve priority operating-layer deployment; low-intelligence-ratio portcos require different treatment. For PE operating partners building portfolio-wide deployment plans, the ratio is the diagnostic that sorts signal from noise.

Defining the Ratio

The ratio is computed at the level of work performed, not at the level of roles or departments. Every hour of labor inside a portco can be classified as intelligence work or judgement work based on the characteristics of the specific task.

Intelligence work: structured data extraction, rule-application, pattern-matching, benchmarking, routine reconciliation, high-volume transaction processing, standard-form document generation, scheduled execution of documented procedures.

Judgement work: strategic decision-making, ambiguous-situation resolution, relationship-building, creative problem-solving, novel-scenario analysis, executive communication, cultural and change-management leadership.

Dividing intelligence hours by judgement hours produces the ratio. Portcos where the ratio is high (70:30 or higher) have cost structures weighted toward AI-addressable work. Portcos where the ratio is low (50:50 or lower) have cost structures more resistant to current AI operating-layer capability.

Scoring at Multiple Levels

The ratio applies at multiple levels of analysis.

Portco-level ratio. The overall split across the full portco's cost base. A healthcare-services portco with heavy clinical-support and billing workflows typically has a high portco-level ratio. A strategy-consulting portco concentrated on senior-advisor engagements has a low portco-level ratio.

Function-level ratio. The split within specific functions inside a portco. Finance functions typically score high (most close and compliance work is intelligence work). Commercial functions score mixed (sales support is intelligence-heavy, but senior-sales relationship work is judgement-heavy). Executive functions score low (most executive work is judgement work).

Workflow-level ratio. The split within specific workflows. Most contract workflows score high at the standard-form level and lower at the strategic-deal level. Hiring workflows score high at the top-of-funnel and lower at interview-evaluation and offer-strategy levels.

Operating partners should run the ratio at all three levels. Portco-level guides portfolio-wide deployment prioritization; function-level guides portco-level deployment sequencing; workflow-level guides specific deployment targeting within functions.

Why the Ratio Matters

The ratio matters because it predicts where AI operating-layer deployment will produce material EBITDA impact and where it will not. High-ratio workflows produce large cost compression when operating-layer deployed. Low-ratio workflows produce limited cost compression because the judgement work cannot be automated and the operating layer can only support rather than replace human execution.

Operating partners who deploy without considering the ratio often end up in one of two failure modes. They push operating-layer deployment into low-ratio workflows where the technology cannot reliably execute, producing quality issues and stakeholder dissatisfaction. Or they confine deployment to only the obvious high-ratio workflows, missing adjacent medium-ratio workflows that would also benefit from selective operating-layer support.

Running the ratio explicitly across the portfolio avoids both failures. Deployments concentrate where the ratio justifies them. Adjacent workflows get appropriate copilot-level deployment rather than inappropriate autopilot-level deployment. The portfolio-wide deployment portfolio matches the underlying work structure.

Portfolio-Level Patterns

Applying the ratio across a PE portfolio reveals specific patterns operating partners should plan around.

Services-heavy portcos generally score high. Healthcare services, business services, outsourced support, TPA and RCM businesses, staffing platforms. These portcos have cost structures concentrated in intelligence work and are priority targets for operating-layer deployment.

Professional-services portcos score mixed. Accounting firms, consulting firms, law firms all carry significant intelligence work but also significant judgement work concentrated at senior-partner levels. Deployment focuses on the intelligence layer while preserving senior capacity.

Manufacturing portcos score mixed but with different distribution. Production workflows score lower (more physical judgement than rule-driven intelligence). Finance, procurement, and administrative functions score high and are similar targets to other portco types.

Technology-platform portcos score mixed. Engineering is heavily judgement work at senior levels. Customer support, operations, and finance are heavily intelligence work.

Each pattern produces different deployment priorities. A services-heavy portfolio concentrates deployment across many high-ratio portcos. A technology-platform portfolio concentrates deployment on finance and customer-support workflows within portcos rather than across them.

The Diagnostic Process

For operating partners running this analysis, the diagnostic follows a specific process.

Step one: decompose the portco's cost base into labor categories. What functions employ how many people at what loaded cost?

Step two: for each labor category, classify typical daily work as intelligence, judgement, or mixed. Mixed categories get further decomposed to estimate the intelligence-vs-judgement share of total hours.

Step three: aggregate the classification to produce the portco-level, function-level, and workflow-level ratios. Identify the highest-ratio workflows and the largest absolute intelligence-work dollar amounts.

Step four: map the findings to available operating-layer deployment options. Where is the technology mature enough to execute the intelligence work reliably? Where is the deployment path clear and de-risked?

Step five: sequence deployments against the map, prioritizing the intersection of large absolute intelligence-work spend, high readiness of operating-layer capability, and clear deployment pathways.

This diagnostic should run at acquisition (to inform the first-100-day plan) and periodically through the hold period (to recalibrate deployment priorities as work content shifts).

The Cross-Portfolio Prioritization

At fund level, the ratio diagnostic applied across portcos produces a prioritized portfolio-wide deployment plan. Portcos with higher ratios and larger absolute intelligence-work spend get earlier and deeper deployment attention. Portcos with lower ratios get more modest deployment focus, concentrated on the specific functions where intelligence work still dominates.

Resource allocation at fund level — operating-partner attention, deployment-team capacity, capital investment in operating-layer infrastructure — should match this prioritization. Funds that allocate attention evenly across portcos without regard to the ratio typically underperform funds that concentrate attention on the highest-readiness opportunities.

This cross-portfolio prioritization pattern is the same one covered in the six-to-one rule: why services spend dwarfs software in every portco — understanding where the spend concentrates and where the readiness concentrates lets operating partners direct capital effectively.

The Ratio Evolves

The ratio is not static. It evolves as operating-layer capability expands and as portcos restructure their work. Workflows that were genuinely judgement-heavy three years ago — some legal research, some complex medical billing, some specialized compliance work — are increasingly intelligence-addressable as operating-layer technology matures. Workflows that look judgement-heavy today may become intelligence-addressable over the next 24-36 months.

Operating partners should re-run the ratio periodically through the hold period and update deployment priorities accordingly. A portco that scored low on initial acquisition may score meaningfully higher two years into the hold period as new operating-layer capabilities become deployable. Re-evaluation keeps the deployment plan aligned with current capability rather than ossifying around the initial diagnostic.

The Ratio Produces the Exit Story

The intelligence-to-judgement ratio also shapes the exit narrative. Portcos approaching exit with high ratios that have been successfully migrated to operating-layer execution present a specific story to buyers: the cost base has been systematically flipped from labor to software, and the margin profile reflects the shift.

Buyers recognize and reward this story. The ratio-driven exit narrative concentrates on the specific workflows that moved to operating-layer execution, the measurable operating metrics that document the shift, and the remaining judgement layer that continues to be human-delivered. This story supports higher multiples than a labor-heavy exit narrative would.

The re-rating logic here is the same one covered in how AI increases exit multiples for PE-backed services firms. The specific contribution of the ratio diagnostic is making the exit narrative concrete and defensible rather than aspirational.

The Score That Drives the Plan

For PE operating partners, the intelligence-to-judgement ratio is the diagnostic that converts abstract "AI readiness" discussions into concrete deployment plans. It produces a number. The number indicates where the opportunity sits. The opportunity drives the deployment.

Every portco in every PE portfolio has a ratio. Every operating partner should know what it is — and should be using the score to drive where operating-layer capital deploys next. The portfolios that execute on the ratio-driven plan capture the margin expansion the category makes available. The portfolios that deploy without the diagnostic end up with fragmented deployments that produce smaller absolute impact than the operating-layer opportunity actually offers.

Score the portfolio. Act on the score. That is how AI readiness converts into realized value.