There is a specific stage in a growing organization where the founder or director is doing three jobs, one of which is invisible. The visible jobs are the work and the selling. The invisible one is operations: scheduling, invoicing, onboarding, chasing, filing, fixing. It never appears on a calendar, so it looks free. It is not free. It is the reason the other two jobs are behind.
The signals that you are already late
Very few teams hire an operations person too early. Most hire twelve to eighteen months after the need was obvious, because the role does not generate revenue directly and is therefore easy to defer. These are the signals that the decision is already overdue.
- Your most expensive person is doing your most repetitive work. If the person who closes deals is also reconciling invoices, you are paying a premium rate for admin hours.
- Work gets done but the follow-through does not. Projects deliver, then nothing happens: no invoice for two weeks, no wrap-up, no next step. That gap is the ops gap.
- Every process lives in one head. When one person is out and three things stall, you have discovered that operations is a role, not a habit.
- You are turning down work because of coordination, not capacity. The team could do the work; nobody has the hours to organize it.
- Nobody can answer basic questions quickly. How many clients did we serve last quarter? Which invoices are overdue? Who is booked next month? If those take a day to answer, the answer is not being maintained by anyone.
A rough test: add up the hours per week your senior people spend on scheduling, invoicing, data entry, onboarding, and chasing. If that number is above fifteen, you can justify a part-time hire immediately, and probably a full-time one within two quarters.
What the role actually is
The first operations hire is not an assistant and not a manager. The job is to own the systems that everything else runs on, and to take repeating decisions off other people’s plates permanently. The distinction matters because it changes who you hire and how you measure them.
| Not this | This |
|---|---|
| Does tasks you assign | Owns processes end to end |
| Asks how you want it done | Documents how it gets done and improves it |
| Reports activity | Reports status and exceptions |
| Fills gaps as they appear | Removes the cause of recurring gaps |
| Learns your tools | Owns and consolidates the tools |
If what you actually need is someone to execute a defined list, hire an assistant and be clear about it. Hiring an ops person to do assistant work is how good ops hires quit in month seven.
Hand over whole processes, not fragments
The most common failure is delegating pieces. You keep the judgment and hand over the clicking, which means every task still routes back through you and the handover never actually reduces your load. Hand over the entire process including the decisions inside it.
- Pick the process that repeats most. Usually client or member onboarding, invoicing and collections, or scheduling. Frequency beats size: a weekly process handed over completely returns more hours than a quarterly one.
- Do it together twice, narrating the decisions. The clicks are the easy part. The value is in the judgment: why this client gets net 15 and that one gets net 30, when to escalate, what an exception looks like. Say all of it out loud while they take notes.
- Have them write the SOP, not you. The person learning writes the documentation. Their version exposes the gaps your version would have skipped, because you would have written down what you meant rather than what you do.
- Watch them run it once, then stop watching. Review the output, not the steps. If you keep reviewing steps you have hired a helper, not an owner.
- Define the escalation line explicitly. What they decide alone, what they decide and tell you, and what they bring to you first. Money limits and client-facing commitments are usually where the line sits. Write it down so it is not renegotiated weekly.
The first 90 days
A good ops hire will try to fix everything in month one. Sequence the work so the early wins are real and the big changes happen after they understand why things are the way they are.
- Days 1 to 30: observe and document. Shadow the recurring work, write down every process as it currently exists, and list what breaks. No changes yet, apart from obvious quick fixes.
- Days 31 to 60: own two processes. Take full ownership of the two highest-frequency processes, including the decisions. Success is that nobody else touches them and nothing slips.
- Days 61 to 90: consolidate and clean. Now the improvements. Reduce the tool sprawl, fix the data, automate the reminders, and put the first dashboard in front of leadership.
- Ongoing: one improvement per month. A standing expectation that one recurring problem gets permanently removed each month, chosen by them and reviewed with you.
How to know it is working
Operations is easy to under-measure because the output is the absence of problems. Pick a few numbers before the hire starts so the value is visible later, when someone inevitably asks what the role is contributing.
- Days from delivery to invoice. One of the fastest-moving numbers after a competent ops hire, and it goes straight to cash flow.
- Percentage of invoices paid on time. Reminders sent consistently move this within a quarter.
- Hours of admin per senior person per week. Measure it before, measure it at 90 days. This is the number the hire is being paid to move.
- Time to onboard a new client, member, or staff member. Elapsed days from yes to fully set up.
- Number of undocumented processes. Should fall steadily. When it stops falling, the improvement habit has quietly stopped.
One structural note: an ops hire inheriting six disconnected tools will spend their first year being a human integration layer between them. Consolidating the record first, so people, projects, and money live in one place, is what lets the role be about improvement rather than re-keying. That is the case for a connected system like Studio Craft before the hire rather than after.
Key takeaways
- If senior people spend more than fifteen hours a week on admin, the ops hire is already justified.
- The role owns processes end to end. If you keep the judgment and delegate the clicking, nothing gets lighter.
- Hand over the highest-frequency process first, and have the new hire write the SOP.
- Sequence the first 90 days: observe, then own two processes, then consolidate and improve.
- Measure delivery-to-invoice days, on-time payment rate, and admin hours per senior person, starting before they arrive.
Common questions
Part-time or full-time to start?
Part-time works if the work is genuinely bounded and mostly execution. It does not work when the job is to own and improve systems, because ownership is hard to hold in ten hours a week spread across five processes. A common pattern is to start at twenty to twenty-five hours with a clear path to full time as processes transfer.
Should we hire someone from our industry?
Industry knowledge is helpful but rarely decisive. Process instinct is decisive. Someone who has run operations in a different field will learn your vocabulary in a month; someone who knows your field but has never built a system will still be improvising in a year. Interview for how they fixed a recurring problem somewhere else.
What if we cannot afford the hire yet?
Then reduce the operations load rather than absorbing it silently. Consolidate tools, automate the reminders, template the repeating documents, and be honest that some things will not get done. Absorbing the load into evenings and weekends is not a cost saving, it is a deferred cost that usually shows up as burnout or churn.
How does this apply to a church or nonprofit?
The same signals hold with different nouns. If your executive director is doing scheduling, donor receipts, and volunteer coordination, the invisible job is eating the visible one. Many organizations at this stage hire a part-time operations coordinator before a second program role, and it usually increases what the program side can deliver.
What is the biggest mistake in the first six months?
Letting the ops person become the person everything routes through. That is the same bottleneck you had before, wearing a different name badge. The measure of a good ops hire is that fewer things require any specific person, not that everything now requires them.
