The ‘key person’ risk: hiring fractional RevOps without a system you can’t run

The real fear of hiring a fractional RevOps lead isn't the rate. It's the space station.

Someone senior comes in, builds something intricate and clever, hands you the keys, and leaves — and now you own a system only they understood. The dependency didn't end when the contract did. It got worse.

It's a fair fear. It happens. And it's avoidable, if the person you hire is building to leave from day one.

Documentation isn't the last step — it's built with the system

The tell is simple. Ask when the documentation gets written. If the answer is “at the end, as a handover,” walk away — because it won't be, or it'll be reconstructed from memory once the details have gone fuzzy. Good operators document as they build, because the doc is the design. The workflow and the note explaining the workflow are the same act. Data governance that isn't written down is just one person's habit.

A real fractional lead builds to hand over, not to be needed

There's a quiet incentive problem in this work: complexity creates dependency, and dependency extends the contract. The operators worth hiring build against their own interest — the simplest system that does the job, documented so plainly your internal team can run it without them. A system you can't run without the person who built it isn't an asset. It's a hostage situation with a Gantt chart.

The anatomy of a playbook your team can keep

When I hand back, what stays isn't a diagram. It's an operating playbook: what each object and field means and why, who owns what, the weekly hygiene checks that keep the data clean, and the “if this breaks, do this” runbook for the three things most likely to break. Modular, so your team can change one part without understanding all of it. That's the RevOps model we run — built to be handed back.

Handover is a design constraint, not an event

This is the reframe. “Can they run it without me?” isn't a question you answer at the end of the engagement. It's a constraint you design under the whole way through. It changes what you build — simpler, clearer, more documented — and it's the difference between senior help and senior risk.

Hire the architect who's already planning their exit. Not because they're not committed — because they are. The best thing a fractional operator can leave you is a system that doesn't miss them.