Operations Playbook for a PE-Owned $30M Company | OAG

Why This Matters Now

PE deal activity in the lower-middle market has stayed competitive even as rates have shifted.^[1] When a sponsor closes on a $30M company, the first 100 days aren't ceremonial. Portfolio operations teams are pulling the real data, not the deck. If your operating system lives in someone's head, that shows up fast, and it shows up as a valuation problem.

Most $30M companies arrive at close still running on tribal knowledge, the founder's memory, and a patchwork of SaaS contracts nobody audited. A PE board isn't looking for a polished org chart. They're scanning for EBITDA drag, undocumented dependencies, and single points of human failure. If your GM left tomorrow, what would survive? That question has a price tag attached to it, and most companies at this stage don't like the answer. That's exactly the problem an Operations Architect engagement is built to solve.

What PE Boards Are Actually Scanning For in a $30M Ops Review

They're not impressed by the number of tools you use or the size of your management team. They're reading the operational structure for risk. Here's the short list of what shows up on every portfolio ops review at this revenue level.

• EBITDA drag from undocumented processes that create rework loops nobody can cost out.
• Key-person dependency: if the GM or ops lead exits, which critical workflows disappear with them.
• SaaS sprawl and overlapping contracts that don't show up cleanly on the P&L.
• No written operating system, meaning a new hire or incoming operator can't get up to speed without months of tribal knowledge transfer.
• Compliance gaps that only surface when the portfolio team asks a question nobody inside the company can answer in writing.
• A 100-day plan with no operational substance behind it: slides, no systems.

The standard PE boards hold portfolio companies to is simple. Can a competent operator pick up your playbook and run the business? At most $30M companies, the honest answer is no. Not because the people aren't capable, but because the system was never written down. Tribal knowledge scales to about ten people. After that, it becomes a liability. By $30M, it's already a liability.^[2]

I spent a decade running enterprise operations across Amazon, International Paper, Spirit Halloween, Maersk, and Levi Strauss, across roughly $3B in operational impact. (OAG receipt: cedric.career_summary) The playbook problem is not unique to one industry. It shows up the same way at every stage: people-dependent systems running on habit, not documentation. The fix is the same whether you're in distribution, services, or light manufacturing. Write it down, stress-test it, and hand it back.

The Axis Method: Five Stages That Map to a PE Timeline

The Axis Method is the five-stage sequence OAG runs inside every Operations Architect engagement. It was built specifically to fit a PE timeline, not a three-year consulting retainer. The goal is a documented operating system returned to your internal team before the engagement ends. If we're still essential at month twelve, we did our job wrong.

1. Diagnose: pull the real data, not the deck. Map every process that touches margin. Identify where the system is held together by a person instead of a process.
2. Stabilize: stop the bleeding before building anything. Stable beats elegant in this phase. We're not optimizing; we're stopping the operational bleeding that drains cash quietly.
3. Document: every core process gets a written, executable SOP. Not a slide. A document someone can follow alone on their first week.
4. Hand-off: the deliverable is the documented system, returned to the internal team. The engagement's success is measured by how little the team needs us after this point.
5. Compound: once the system is stable and documented, identify where it improves without adding headcount or cost. This is where the real return on the engagement shows up.

The full Operations Architect engagement using the Axis Method runs $3,000–$7,500/month and is multi-month and embedded. We're not advising from the outside. We're inside the system, running the Diagnose-to-Hand-off sequence in real time. For stage-by-stage detail, see /axis-method.

For context on what an Operations Architect engagement actually covers versus a full-time hire, see /fractional-coo. The comparison matters because PE boards often ask whether to hire internally or bring in an operator. The answer usually depends on what stage the company is in, and whether there's a documented system to hand off to a hire in the first place.

OIL Framework: Cut Before You Build Anything

PE-backed urgency creates a bias toward adding. New tools, new processes, new reporting layers. That's almost always the wrong direction. Before you architect anything, you have to run the OIL Framework. The order is not optional.

• Interrogate: every workflow that touches margin gets questioned. What does it cost? Who owns it? Would it exist if you started the company today from zero?
• Delete: remove every process that exists because of habit, not because it produces output. Most companies are running four to six of these at any given time.
• Simplify: reduce what's left to its minimum viable form before touching a single automation tool.
• Automate: only after the first three steps. Automating a broken process makes it faster and more broken. Most $30M companies automate broken processes and wonder why the output is still broken.

The OIL Framework isn't abstract. In a PE context it maps directly to the 100-day value-creation plan. If you're adding process layers in the first 30 days without running Interrogate and Delete first, you're compounding the drag your board is trying to measure. Operational waste at this revenue level is rarely obvious on the surface. It shows up in headcount hours, rework cycles, and tool costs that don't connect to outcomes.

The framework also applies to your technology stack, which is where the OIL pass feeds directly into StackOS. See the next section for what that audit typically surfaces at $30M.

StackOS: The SaaS Cost Layer PE Teams Miss Until the First Audit

SaaS sprawl is nearly universal at $30M. Multiple point solutions, overlapping contracts, seats nobody uses, and annual renewals that auto-renew without review. PE portfolio operations teams often don't see the full picture until the first audit, and by then the company has been paying for unused capacity for years.

StackOS is a four-step method: Audit, Architect, Build, Own. It replaces rented SaaS infrastructure with owned infrastructure, cutting the recurring cost line substantially. The four steps are:

• Audit: catalog every SaaS contract, seat count, and actual usage rate across the stack.
• Architect: design the replacement infrastructure using owned tooling (Cloudflare Workers, Supabase, R2, Resend) instead of rented platforms.
• Build: execute the build in a single session or staged sequence depending on complexity.
• Own: the infrastructure belongs to the company. No seat-based pricing, no vendor lock-in, no renewal negotiations.

One receipt from a real build: a 500-person workforce management stack running on $75/month using Cloudflare Workers, Supabase, R2, and Resend. That replaces UKG, ADP, Dayforce, or Kronos at $48,000–$96,000 per year. (OAG receipt: spirit_halloween.system_cost) The headcount supported by that system was approximately 500 associates. (OAG receipt: spirit_halloween.headcount) That's not a niche edge case. That's a repeatable result from running the Audit-to-Own sequence on an enterprise-scale scheduling and workforce management problem.

For comparison, here's what the cost structure looks like between a standard enterprise platform and a StackOS-built equivalent:

PE boards don't typically ask about infrastructure costs until they're preparing for a recap or a sale. That's the wrong time to find out you're renting everything. The StackOS Framework PDF covers the full Audit-to-Own sequence for $29 (self-serve). The StackOS Build session runs $2,000–$3,500 for a single live build. Both options are detailed at /stackos.

I run Obsidian Axis Group itself on $74/month end-to-end. (OAG receipt: oag.monthly_run_cost) That's not a proof-of-concept. That's the production operating cost of a consulting firm that runs the same infrastructure stack it sells. The StackOS method is tested internally before it becomes a client deliverable.

DefaultFail: Stress-Test the Playbook Before the Hand-Off

A playbook that only works when everything goes right isn't a playbook. It's a hope document. DefaultFail is OAG's design principle: assume the system will fail, then build so that when it does fail, it doesn't take down the business.

Every SOP and workflow in the operations playbook gets stress-tested against a realistic failure scenario before it's handed back. At $30M, the failure modes that matter most are:

• The person who owns a critical process leaves without notice or documentation.
• A tool vendor changes pricing at renewal or deprecates a feature the business depends on.
• A PE portfolio review surfaces a compliance gap in a process nobody inside the company can explain in writing.
• A new operator or hire takes over a function and finds no written runbook to follow.
• A customer-facing workflow breaks and nobody in the company can trace the failure to a root cause because the process was never mapped.

The DefaultFail pass happens at the end of Stage 3 (Document) in the Axis Method, before Stage 4 (Hand-off) begins. We're not looking for every possible failure. We're looking for the five or six scenarios that would cause the most damage if they happened in the 30 days following the hand-off. If the playbook can't survive those scenarios on paper, it goes back for revision before it leaves the engagement.

DefaultFail is also the community where OAG systems get tested by real operators before they become consulting deliverables. That means the frameworks on this page were run through actual operational contexts before they were written up as method. The principles do their work. The labels do not.

The Hand-Off Is the Deliverable: What You Walk Away With

The goal of an Operations Architect engagement at a PE-owned $30M company is a documented, transferable operating system your internal team can run without us. That's the only metric that matters at the end of the engagement. Not hours logged. Not slides delivered. The system runs without us, or the engagement isn't done.

Here's what the documented deliverable set includes at the close of a full Axis Method engagement:

• A full process map covering every core operational function that touches margin or headcount.
• Written, executable SOPs for each mapped process, formatted so a new hire can follow them on day one.
• A complete tool and contract audit with a tiered recommendation: keep, cut, or replace with owned infrastructure.
• A 90-day compounding roadmap that shows the internal team where to apply continued improvement without adding cost or headcount.
• A DefaultFail stress-test report for every SOP, documenting what we tested and what we changed before the hand-off.

The engagement is multi-month and embedded. We're inside the system, not advising from a quarterly board meeting. The Axis Method runs Diagnose through Hand-off in a timeline that maps to a PE 100-day plan. For some companies, Stage 5 (Compound) starts before the formal engagement closes because the system is stable enough to begin improvement cycles earlier than projected.

If the playbook requires our continued presence to function, we built the wrong thing. That's not a marketing line. It's the design constraint the entire engagement is built around. The Operations Architect role is a finite engagement with a documented exit, not a permanent seat at the leadership table. For more on how OAG structures the hand-off and what the ongoing relationship looks like after the engagement, see /blog and the OAG homepage.

Sources

1. Bain & Company. "Global Private Equity Report 2024." Bain & Company, 2024. https://www.bain.com/insights/topics/global-private-equity-report/.
2. Deloitte. "The Future of Work: Human Capital Trends." Deloitte Insights, 2023. https://www2.deloitte.com/us/en/insights/focus/human-capital-trends.html.

OAG receipts cited

• cedric.career_summary
• spirit_halloween.system_cost
• spirit_halloween.headcount
• oag.monthly_run_cost