What the posting is really asking for
Read an ops manager posting from a 15-to-40-person company and you'll find three different jobs stacked on top of each other. The first is a system: intake, follow-up, scheduling, reporting and billing that run without someone pushing them. The second is a part-time job of judgment: exceptions, vendor relationships, the client who needs a call. The third is the founder's wish to stop being the person who knows how everything connects.
A hire can do the second. A hire will try to do the first by hand, which makes the company dependent on a new person instead of the founder, and the third never goes away by adding a layer. The test below pulls the three apart.
The test
- Days 1–5: write down what the founder actually does. Not the strategy. The operational week, in 30-minute blocks, for one week, honestly. Mark each block as rules-based (it has a trigger, a known procedure and a predictable output) or judgment (it needs context, a relationship or a decision).
- Days 6–10: pick the three rules-based blocks with the most hours. Across the companies we work with they are reporting, follow-up and intake, in some order. Design how each one would run as a system on the tools you already have.
- Days 11–25: build and run them. Fourteen days is enough for the first workflow if you build into the existing stack rather than migrating to a new one. The founder stops doing those three blocks the day each goes live, not after a transition.
- Days 26–30: re-count the week. How many founder hours came back. What is left on the list, and how much of it is judgment. Whether the remaining list is a full-time job, a half-time job, or a role someone already in the company could take with those hours freed.
The output is a one-page document: the three systems and what they absorbed, the judgment work that remains with hours attached, and a decision. The decision is the point of the test.
What it usually finds
Three patterns, in rough order of frequency.
- The half-role. Twenty to thirty of the forty hours were rules-based and now run as systems. What remains is a real job of twelve to fifteen hours a week, which an existing senior person takes on with the hours the same systems returned to them. No hire; revenue per employee moves by exactly the hire avoided.
- The wrong role. The judgment work that remains isn't operations at all. It is sales support, or client management, or finance. The posting would have hired an ops manager to do account management badly. Now the company hires for the right job, or doesn't.
- The real role. The rules-based work is absorbed and what remains is still a full week of exceptions, vendors, hiring and the hundred decisions a growing company makes. Make the hire. The difference is that the new ops manager inherits working systems and a documented week instead of the founder's head, and ramps in weeks rather than a quarter.
In every one of those outcomes the company is better off for having run the test, including the one where the posting goes up on day 31 unchanged.
The cases where you should just hire
Be honest about these; the test isn't a way to avoid paying people.
- The work is mostly physical or in-person coordination: dispatch across crews, site supervision, inventory in a warehouse. Systems help at the edges and the job is still a person.
- The company is past the point where one person's judgment can cover the exceptions: multiple locations, regulated work with sign-offs, a client base that expects a named human.
- The founder's remaining judgment work, after the three systems, is itself more than a full week. The ops manager is real; the test just made the job better.
What the test never supports is the hire whose first six months will be spent building spreadsheets to do what a connected system does on day fourteen. That person deserves a better job, and the company deserves not to pay a salary to discover a workflow.
What it costs to find out
Run in-house, the test costs the founder's attention for a month and whatever your tools already charge. Run with us, it is the Operations stack: $2,500 a month, first workflow live in 14 days, month to month after the 90-day kickoff, and the three systems the test builds are the ones you keep. Either way, the alternative is a $90,000 decision made from a job posting, and the posting is the one document in the company that was never tested.
If you'd rather have it mapped for you: the free Revenue-per-Employee Audit takes the hires you're planning, shows what a system absorbs from each, and prices the 90-day build. Written, within three business days.