How do I run operations without hiring an ops manager?

Why spreading the role fails

The mistake most teams make after losing an ops manager is trying to spread the role thinly across everyone who is left. That fails within a quarter because ops work has hundreds of small decisions embedded in it, and if nobody owns those decisions the process quietly degrades.

The three-bucket split

Write down what the ops manager actually did, honestly and in detail. Then split the list into three buckets. Bucket one is repeatable rules-based work (intake routing, data entry, invoice creation, weekly reporting). That goes into Monday and Make. Bucket two is exception handling and judgment (which vendor to escalate to, when to flex a policy, when to bring the CEO in). That needs a human, but probably a fractional one, not a full-time hire. Bucket three is the strategic work (org design, process redesign, hiring plans). That is usually the founder or a senior operator who can do it in short bursts.

The math worth doing

An ops manager's total-loaded cost is real. A fractional operator plus a well-built automation stack typically costs less, ships faster, and does not require managing another employee. The tradeoff is that you need to invest up front in the documentation and build. Skipping that step is why "just automate it" projects fail.