Key takeaways
- Portfolio operations should make recurring work visible and supportable across companies; it should not turn every local choice into a central approval.
- Standardize definitions, evidence and control interfaces before forcing one procedure or system onto every company.
- Reuse a workflow skeleton only where the trigger, output and control objective match. Keep local rules as explicit variants with named owners.
- A shared service needs a service boundary, request contract, exception owner and verified return state. A central inbox is not an operating model.
Portfolio operations is an interface between local companies and shared work
A holdco can own several companies without operating them in the same way. The useful portfolio layer is narrower: common definitions, a repeatable review cadence, a few shared capabilities and a clear contract for work that crosses the boundary. Local leaders still own customers, people, safety and operating decisions in their scope.
A ServiceTitan account of a multi-branch home-services group describes a centralized hub alongside partnership with continuing management teams and explicit integration priorities. It is one operator example, not a universal blueprint. The transferable lesson is that the hub needs a defined relationship with the local company; software alone does not create it.
| Layer | Portfolio responsibility | Local responsibility |
|---|---|---|
| Definitions | Common metric dictionary, reporting period and evidence contract | Explain valid local data and exceptions |
| Workflow skeleton | Shared states, control points and minimum audit record | Own local triggers, thresholds and destinations |
| Shared service | Published scope, intake, response clock, escalation and return state | Submit complete evidence and accept or dispute the result |
| Governance | Decide what must be common and review cross-company risk | Remain accountable for local commitments and execution |
Build the common layer in five passes
- 01Reconcile the wordsHuman approvalCompare what each company means by completed, urgent, active, approved and exception. Do not build a common report until the definitions agree or carry an explicit local variant.
- 02Inventory recurring workTriggerList the process, frequency, consequence, owner dependence, evidence and repeatability. Use actual cases, not department labels. “Finance” is not a process; “assemble the Friday branch pack” is.
- 03Select a reusable skeletonCodeChoose work whose trigger, output and control objective match. Reuse the state model and evidence contract; keep local thresholds and authorities as configuration that a named owner reviews.
- 04Publish the service boundaryHuman approvalState what the central team accepts, what it returns, the response clock, the exception queue and who decides a disputed case. Work outside the boundary stays local.
- 05Test one company before the portfolioAI judgmentRun normal and imperfect cases, reconcile the final state and record interventions. Expand only after the template survives a real local variant.
Centralize the repeatable service, not the accountable judgment
| Question | Candidate for shared execution | Keep local or narrow |
|---|---|---|
| Is the output the same? | Comparable record, reconciled report or complete evidence packet | Different customer promise or legal outcome |
| Can inputs be specified? | Named fields and sources with visible quality checks | Context arrives through private relationships or memory |
| Are exceptions routable? | Known types with owners, clocks and closure evidence | Novel cases require local authority with no fallback |
| Can the effect be verified? | Read-back, acknowledgment or reconciled source state | Success is subjective or visible only much later |
| Is authority portable? | The central role has explicit permission and limits | The local manager remains legally or commercially accountable |
A process can be split. The central team may collect evidence, normalize fields and prepare a proposal while a local manager approves a customer commitment. The human-in-the-loop guide shows how to keep that boundary permanent rather than treating it as temporary supervision.
Northline standardizes the pack but keeps branch exceptions visible
Northline is a fictional three-company home-services portfolio. Each branch sends a weekly operating pack. The headings look identical, but “completed job” means technician closeout in one company and customer sign-off in another.
The portfolio team first publishes a metric dictionary and an evidence field for local completion type. A shared workflow checks period, source completeness and arithmetic, then routes definition disputes back to the local controller. Adjustments and final sign-off remain human decisions.
The reusable part is the reporting skeleton and exception record. The local completion rules stay visible. Northline does not claim that one system or connector makes the companies identical.
Measure whether the interface works
- First-pass completeness: requests accepted without chasing missing evidence.
- Exception age: time unresolved cases spend without a named owner.
- Definition disputes: cases blocked because two companies use one label differently.
- Verified return: completed shared-service items whose intended source state was reconciled.
- Local overrides: permitted variants used, with owner and reason; track them instead of hiding them.
- Central interrupts: decisions that still reach the holdco because authority or service boundaries are unclear.
Start with the acquisition process inventory. It separates transition attention from definition strength and gives high-consequence work a control route rather than a readiness badge.
Limitations and when not to use this
- This is general operating guidance, not legal, tax, accounting, employment, cybersecurity, investment or transaction advice.
- A shared process can create a single point of failure. Define fallback ownership, recovery and local continuity before moving essential work.
- Local customer commitments, safety duties, licenses and employment decisions may require local accountable control even when evidence preparation is shared.
- Northline is simulated. No multi-entity dashboard, connector, customer result, staffing outcome or savings claim is made.
Sources
- How to Manage Multiple Service Locations with Len the Plumber — ServiceTitan Accessed 6 August 2026
- The State of Organizations 2026 — McKinsey & Company Accessed 6 August 2026
- Contingency Planning Guide for Federal Information Systems — NIST Accessed 6 August 2026
Inventory the first portfolio processes
Rank transition attention and definition strength before choosing a shared-service candidate.
Inventory the first portfolio processesUli Prantz
Builds and operates all-agents
Uli Prantz builds all-agents, the process-automation platform this site documents. He writes about the operational side of automating recurring business work: where deterministic code beats model judgment, where it does not, and where a human still has to approve.