The Operator's Playbook: How a Family Office Vets, Buys, and Runs LMM Companies on EOS

Running a family-office portfolio of lower-middle-market businesses is not a series of unrelated deals. It's one operating system applied again and again. The family offices that do this well treat an EOS-style cadence as the connective tissue between diligence, the first 100 days, and the long-term operating plan. Here's how the playbook works in practice.

Stage 1: Vetting — the operator gates everything

Every diligence file we open starts with the same question: is there a credible person other than the seller who can run this business 12 months from now? If the answer is no, the deal pauses. Not killed — paused. We either find that person before close or build the search into the LOI as a condition of funding.

The financial work matters, but it's downstream. A clean set of books with no second-in-command behind them is a harder business to own than a messier one with a strong general manager, because what changes hands is ongoing operations, not a snapshot.

Stage 2: Buying — diligence outputs feed the operating plan

Most acquirers run diligence and operations as separate workstreams. We run them as one. Every QoE finding, every customer-call note, every IT review turns into either a rock for Q1 or a line on the issues list the new operator inherits on day one.

The four diligence artifacts that become operating tools

• QoE adjustments become the first month's accounting clean-up project.
• Customer-call summaries become the new GM's first 30-day relationship map.
• Owner-dependence map becomes a 90-day succession plan, owner-by-relationship.
• IT and systems review becomes the first technology rock — usually accounting, then CRM, then ops.

Stage 3: Running — EOS as the portfolio operating system

Once the deal closes, the company gets the same scaffolding every other portfolio business runs on. Different rows, same structure.

Vision/Traction Organizer (V/TO)

Drafted in week two with the operator. Core values, 10-year target, 3-year picture, 1-year plan, quarterly rocks, and the issues list. The family office reviews and pressure-tests; the operator owns it.

Quarterly rocks

Three to five per company. No more. The temptation in year one is to list fifteen — every broken thing demands attention. Five forces choice, and choice is what separates a portfolio company that compounds from one that stays busy.

Weekly L10

Every portfolio company runs the same 90-minute weekly meeting on the same agenda. Scorecard, rock review, customer/employee headlines, to-do list, issues list (identify, discuss, solve). The cadence is non-negotiable.

Scorecard

Five to fifteen weekly numbers. Leading indicators where possible — sales activity, not just sales; A/R aging buckets, not just A/R total. If the scorecard is green for two months and the P&L is red, the scorecard is measuring the wrong things.

What scales across a portfolio — and what doesn't

Scales

• The meeting cadence and agenda.
• The scorecard format and review rhythm.
• The quarterly rock-planning session.
• The monthly close timeline and reporting package to the family office.

Doesn't scale

• Sales playbooks — too industry-specific.
• Pricing — has to be set inside each company by people who know the customer.
• Hiring profiles — a controller for a manufacturer isn't the same role as one for a services firm.
• Customer experience — every business has its own.

The family office's actual job

Once the system is running, the family office is not running the businesses. It's running the system that runs the businesses. That means three things:

1. Picking the right operator for each company at acquisition and replacing them quickly when the seat is wrong.
2. Holding the cadence — making sure quarterlies happen, monthly packages land on time, and scorecards are reviewed.
3. Allocating capital across the portfolio based on which companies are converting commitments into durable operating improvement.

First 90 days: role boundaries and escalation

Most friction in the first quarter after close is not strategic. It is two capable people both believing a decision is theirs. Writing the boundary down in week one costs an hour and saves a quarter.

Illustrative only. Actual authority comes from the governing documents of a specific transaction, not from a table on a website.

What escalates immediately

Separate from the routine approval path, a short list should reach ownership the day it is known, not at the next monthly meeting: a safety or compliance incident, a threatened or filed legal claim, loss of a license or key certification, loss of a top customer, a covenant or payroll cash risk, suspected fraud, a data or security breach, and the resignation of anyone on the leadership team. The rule is "surprises travel fastest" — an early call is never treated as a failure.

How escalation should work

1. One named contact on each side, with a backup, and a stated response-time expectation.
2. A short written note — what happened, what is known, what is being done now, what decision is needed and by when.
3. A decision recorded in the decision log with the date and the person who made it.
4. A brief follow-up at the next monthly review, so the pattern gets fixed and not just the incident.

The five questions to ask before you acquire your next company

1. Who's the operator on day 91 — and do they want the job?
2. What are the three things from QoE that become Q1 rocks?
3. What scorecard do we install in week one, and who owns it?
4. What's the monthly reporting package the family office actually needs?
5. What's the 24-month thesis, and which two rocks per quarter make it real?