Standardize the operating model. Keep the autonomy.
Deploy a shared operating system across the portfolio so cross-company comparison is finally apples-to-apples — without imposing a meeting culture that kills the founder energy you backed.
Forty-seven different meeting rhythms, six different scorecard formats, and three different definitions of 'on track.' Rollup data takes 30 days to reconcile.
Every portfolio request feels like extra work to the operators on the ground. They submit, they comply, they hate it. Nobody internalizes the system because it isn't theirs.
The value-add team caps out somewhere around eight companies per operator. Add more and the engagements get shallow. The framework was supposed to scale; the relationships don't.
Every bolt-on takes 6+ months to integrate operationally because the playbook lives in the heads of two people. Day 1 → Day 90 looks different at every deal.
Same four phases as every audience. Different entry point, different leverage, different two-quarter outcome.
Same Ops Health Check across the entire portfolio. Same five categories, same scoring rubric. The first time you can rank portcos on operating maturity without arguing about methodology.
Shared cadence template, shared KPI framework, shared decision-rights pattern — adapted at the company level. The framework is uniform; the surface area is local.
Wave rollout. First five portcos go in Q1, next five in Q2. Operating partners shift from advisor to chair of the cadence — same role at every company.
Quarterly cross-portco reviews where what worked at one company gets installed at three more. Bolt-ons integrate inside 90 days because the operating model is the same.
Every engagement starts with the Ops Health Check. From there, you typically pick one of three shapes depending on how far along the operating system already is — and how much of your own time you can hand over to it.
Pick the portco most likely to embrace the framework. Run the full 4A install. Then bring three more portcos to the post-mortem and decide if it scales.
Roll the framework across the portfolio in waves of three to five portcos per quarter. Operating partners trained as cadence chairs. Cross-portco dashboard live by Month 6.
For firms that already have strong in-house operating partners and just need the standardized blueprint. License the framework + artifacts; deploy in-house.
We rolled the framework into seven portcos in two quarters. The first time we did a cross-portco operating review, everyone was using the same words. That was the moment we realized this would scale.
Most portfolio engagements start with the Ops Health Check at a single, high-trust portco. It's the fastest way to feel the framework before committing the firm to a wave rollout.
If the portfolio already runs a shared cadence, we can start at Activate with cross-portco AI workflows or jump to Accelerate for M&A playbook work.
See Activate cross-portfolio →