Inevitable / Private equity

Modernize.
Operate.
Defend.

Build AI into portfolio products. Turn diligence into company operating work. Keep a decision file that connects the investment thesis to what actually happens.

Start with the firm's method, apply it inside each company, and bring reviewed learning back into the portfolio playbook.

Illustrative / A method that travels with the portfolio
Firm playbook and separate company workspaces The firm's playbook informs separate software and energy company workspaces. Reviewed outcomes inform an updated method. Each deployment defines its data and access boundaries. Firm playbook Software co. Workspace Energy co. Workspace Reviewed outcomes Review → refine → repeat

Three connected jobs

Across the product,
the company, and the firm.

A portfolio thesis needs somewhere to become work. Connect product modernization, operating decisions, and investment oversight through the same evidence and review method.

01 / Modernize the product

Build the capability.

Add an AI module, encode a custom decision engine, or build a new product on shared infrastructure. Start with the customer workflow, domain logic, and integration requirements.

02 / Operate the company

Make the thesis actionable.

Connect pricing, go-to-market, retention, and roadmap choices to scoped execution. Give operating partners and company teams a common decision file, approved tasks, and editable financial deliverables.

03 / Operate the firm

Improve the playbook.

Carry diligence into investment committee files and portfolio monitoring. Review what worked, where assumptions broke, and which corrections belong in the firm's next version of the method.

The repeatable method

Your operating judgment.
Made repeatable.

Use the discipline of a consulting engagement: frame the question, collect evidence, compare alternatives, and agree the work. Encode that method in software so the next decision starts with reviewed experience.

  1. Encode

    Capture the firm's criteria, assumptions, required sources, and review gates.

  2. Reason

    Compare causal drivers and alternatives. Keep conflicting evidence visible.

  3. Decide

    Review the decision file and approve a bounded course of action.

  4. Execute

    Assign tasks, produce deliverables, and carry approved changes into company work.

  5. Observe

    Compare operating evidence with the original assumptions and expected effects.

  6. Improve

    Review corrections and version the playbook before reusing the method.

Software / Product and operating decisions

Disrupted or advantaged?

AI can compress seats while making a deeply integrated product more valuable. The investment question is which forces affect this company, which customers feel them, and what the product and commercial model should become.

Connect commercial diligence to a product modernization plan, pricing tests, go-to-market changes, and retention work. Build, buy, reprice, or retire a capability only after comparing the alternatives against company evidence.

Illustrative / Software decision fileOperator review required

Question

Which workflow earns the next product investment?

Sources
Customer interviews, contract terms, product usage, integration map, and support records. Retain source dates and conflicting observations.
Alternatives
Build an embedded AI module; buy a capability; reprice the workflow; retire low-value features.
Assumptions to test
Customers adopt the module; usage reflects value; model and support costs fit the margin case.
Approved work
A bounded product prototype, a pricing test, and a retention review with named responsible operators.
Deliverable edit
Revise the usage-pricing assumption in the financial model. Regenerate the dependent investment memo and flag the change for review.

Decision record: source evidence, commercial assumptions, approved scope, and revised deliverables.

  1. EvidenceGather customer, commercial, and technical context.
  2. Decision fileCompare build, buy, reprice, and retire with sources and assumptions.
  3. Approved tasksScope product and operating work for accountable teams.
  4. Revised deliverablesEdit the financial model and regenerate the dependent memo.
  5. Observed operationsReview adoption, retention, and unit economics against the thesis.

The result to inspect is observed customer behavior and operating economics. A model's prediction remains a hypothesis until company evidence supports it.

Energy and real assets / Capital allocation

Acquire, build,
or partner?

An attractive demand signal is only the beginning. Compare acquiring an existing asset, building capacity, or partnering with an operator against the physical constraints, commercial commitments, and capital required.

Strategy intelligence evaluates the investment alternatives. Asset origination separately identifies candidate locations, assets, owners, operators, and opportunities. Bring their evidence together in the decision file without confusing a discovered asset with an investable case.

Illustrative / Energy decision fileInvestment review required

Question

Which path meets the demand within the constraints?

Sources
Supply and grid records, water evidence, permit status, asset and operator records, capex inputs, and proposed offtake terms. Preserve dates and unresolved conflicts.
Alternatives
Acquire an operating asset; build new capacity; partner for capacity and operations.
Assumptions to test
Power arrives on schedule; gas and water are available; permits can be secured; offtake supports the capital case.
Approved work
Validate the shortlist, request technical and commercial evidence, and assign diligence tasks before a capital decision.
Deliverable edit
Revise the delivery date in the financial scenario. Regenerate the dependent committee memo and show the changed assumptions.

Decision record: site evidence, unresolved dependencies, diligence scope, and revised capital case.

  1. EvidenceResearch the strategy and discover candidate assets separately.
  2. Decision fileCompare acquire, build, and partner under physical and capital constraints.
  3. Approved tasksAssign technical diligence and commercial validation.
  4. Revised deliverablesUpdate the scenario and regenerate the committee memo.
  5. Observed operationsReview actual delivery, costs, commitments, and operating conditions.

Review observed delivery and operating conditions against the thesis. Source discovery and geographic resolution feed infrastructure hosted and operated in your cloud.

A foundation for the work

Use the software.
Encode the method.
Build the product.

Choose the starting point that matches the company. A working research flow, a custom engine built around your playbook, and a customer-facing AI product can use the same underlying services.

Use

Apply existing research and decision workflows to a live diligence or operating question. Keep sources, alternatives, and review gates attached to the deliverable.

Encode

Turn the firm's repeatable consulting method into domain logic: required evidence, causal drivers, scoring rules, assumptions, and approved task boundaries.

Build

Create an AI module or a new portfolio product with its own experience and integrations. Agree commercial ownership and delivery responsibilities for each engagement.

Product-specific experience. Shared operating services.

Product and domain layer
The company workflow, customer experience, integrations, and decision logic define what the product does.
Intelligence and execution layer
A model router, reasoning, task execution, and monitoring support that workflow and its approved actions.
Foundation services
Tenancy, access, commercial, and operating services sit beneath the product. Define data access, review controls, and deployment boundaries for each implementation.

Reviewed corrections can improve the firm's playbook. What evidence or learning may move between company and firm workspaces is specified for the deployment. Product and commercial ownership follow the agreement.

Explore custom portfolio software

Start with a scoped run

One portco.
One live decision.

Choose a company and a consequential product, operating, or capital allocation question. Agree the sources, alternatives, responsible operator, and approval boundary before the run.

Review the decision file together. Execute the approved scope, observe what happens, and record corrections as a new version of the method. Expand when the work earns it, or stop with a clear record of what was learned.