The night I knew I was the bottleneck, I was standing in a client's parking lot at 7:40 p.m. answering a scheduling text with one thumb while a voicemail from a different customer sat unheard. The work was getting done. The business, technically, was growing. But every dollar of that growth ran through my attention, and my attention had run out around 4 p.m. If you've felt that exact squeeze, the answer is usually hiring your first operations person — the one who absorbs the coordination, the follow-up, and the dropped balls so the owner can stop being the switchboard. This is a field guide to doing it without it blowing up in your face, which it often does.
I've made this hire well and I've made it badly. The bad version is fast: you're drowning, you grab a warm body, you 'show them around,' and ninety days later you're doing your job and supervising theirs. The good version is slower up front and quieter forever after. Here's how the good version actually works.
The signals that it's actually time — not just a bad week
Owners chronically hire too late and then hire in a panic. The trick is separating a hard season from a structural ceiling. A few signals tell you it's structural:
- Revenue-generating work is being delayed by coordination work. When quotes go out late because you were buried in scheduling, the admin load is now eating the part of the business that pays for everything else.
- You can name three tasks you do every single day that don't require you specifically — confirming appointments, chasing a signature, ordering materials, sending the invoice. That's a job description forming in real time.
- Things fall through the cracks on a predictable cadence. Not randomly — predictably, around the same volume, every time you get busy. A predictable failure point is a role, not a personal failing.
- Your effective hourly rate is upside down. Run the math honestly: take your monthly owner's income, divide by hours worked. If you're doing $20-an-hour data entry inside a business that bills your time at several multiples of that, the gap is the case for the hire.
One caution from experience: don't make this hire to escape a sales problem. If the phone isn't ringing enough, an operations person won't fix that and you'll resent the payroll. This hire is for when there's too much flowing through one person, not too little flowing in. If you're unsure which problem you have, the 10-point burnout audit is a faster diagnostic than another month of pushing through.
Coordinator or manager? Get this right before you write the job post
This is where most first hires go sideways. Owners feel overwhelmed and instinctively reach for an 'operations manager' — someone to take it all off their plate and run things. That's almost always the wrong first hire.
An operations coordinator executes inside your systems. An operations manager owns and improves your systems. You cannot hand someone systems to improve if the systems live only in your head. The manager hire fails because there's nothing to manage yet — just your undocumented instincts. The coordinator hire succeeds because you're handing off discrete, repeatable tasks with clear right answers.
Worth knowing: these aren't just vibes, they're different labor-market roles. The U.S. Bureau of Labor Statistics tracks Administrative Services Managers and First-Line Supervisors of Office Support under separate codes with meaningfully different median wages. The title you put on the post quietly sets the salary band you'll be competing in — so name the job for what it actually is on day one, not for who you hope they become in year two.
Most service businesses making their first ops hire want a coordinator: detail-oriented, reliable, comfortable on the phone, allergic to loose ends. The manager comes later, often promoted from that same seat once your standard operating procedures exist for them to steward.
What to hand off first — and in what order
You don't transfer everything at once. You transfer in the order of highest frequency, lowest judgment first. High-frequency tasks free up the most time per hour you spend training. Low-judgment tasks are safe to hand to someone still learning your business. Where those two overlap is your first week's hand-off list.
For a typical service business, the order looks like this:
- Inbound calls and scheduling. This is the one to move first, and it's the one owners cling to longest. In a service business, a missed call usually doesn't get a second chance — the customer just dials the next contractor who picks up. Getting a reliable human on the phone protects revenue immediately. It's the single best-ROI transfer you'll make.
- Appointment confirmation and reminders. The follow-up layer that prevents no-shows and the awkward 'are we still on?' texts. Pure execution, enormous return on your sanity.
- Invoicing and payment follow-up. Sending invoices on a schedule and chasing the ones that age past terms. This is where cash quietly leaks, and it's deeply satisfying to hand off.
- Vendor and materials ordering. Reordering supplies against a par level, placing standing orders, tracking deliveries.
- Light bookkeeping handoffs. Not the books themselves — getting receipts, statements, and documentation into one organized place so whoever keeps the books isn't chasing you. Clean operational discipline here is what makes the rest of the back office (good books, a working website, sensible automation) actually function instead of fighting you.
Notice what's not on the early list: anything requiring your specific expertise, pricing decisions, or relationship-defining client conversations. Those move much later, if ever. A common rookie mistake is handing off the high-judgment work first because it's what stresses you most — and then spending more time correcting than you saved. Hand off the boring, repeatable, frequent stuff first. The relief is real and the risk is low. For the mechanics of transferring work so it doesn't quietly bounce back to you, the deeper walkthrough is in how to delegate tasks as a small business owner.
The legal and payroll layer most owners skip until it bites
Here's the part nobody enjoys, and the part that turns a good hire into an expensive mistake if you wing it. The day you bring on your first W-2 employee, you cross into employer obligations that didn't exist when it was just you.
The federal checklist, per the IRS guidance on hiring employees, includes getting an EIN, collecting a signed Form I-9 and Form W-4, registering for federal and state unemployment insurance, and depositing payroll taxes on schedule. None of this is optional and none of it is hard — it's just unfamiliar the first time.
Two traps I'll flag specifically:
- Don't classify your ops person as a 1099 contractor to dodge the payroll setup. The Department of Labor's 2024 independent-contractor rule (effective March 11, 2024) uses a six-factor economic-reality test, and a coordinator who works your hours, on your systems, under your direction is an employee by almost any reading. Misclassification means back taxes, penalties, and a problem far larger than the payroll setup you were avoiding.
- Know the overtime rule that actually applies. After a federal court vacated the DOL's 2024 increases in November 2024, the standard salary threshold for exempt status reverted to its prior level — roughly thirty-five thousand dollars a year. A first ops hire paid below that is non-exempt, meaning you owe overtime past 40 hours and you need to track their time. Check the current DOL wage-and-hour guidance before you set a salary and call it 'salaried.'
This isn't legal advice and your state adds its own layer — but knowing these three things before you make an offer keeps a relief-giving hire from becoming a compliance headache.
A 30-day onboarding plan built on your SOPs — not on shadowing you
The default onboarding plan for a first ops hire is 'follow me around for a few weeks.' It feels efficient and it's a trap. Shadowing transfers vibes, not procedures, and it keeps you tethered to your new hire exactly when you're trying to get untethered. Build the onboarding around documented procedures instead, even rough ones. If you don't have SOPs yet, the act of writing the first few is the onboarding — start with capturing what's only in your head.
Here's the 30-day shape that's worked for me:
Days 1–5: One process, fully owned. Pick the highest-frequency task — usually inbound calls and scheduling. Document it together: you do it, they write the steps as they watch, then they do it while you watch. By Friday they own that one process end to end. Resist the urge to add a second thing. Depth before breadth.
Days 6–15: Add processes on a one-per-few-days cadence. Layer in confirmations, then invoicing, then ordering — each one documented as a written procedure before you move on. The rule: nothing gets handed off without a written SOP, and the new hire writes or edits it in their own words. That tests comprehension and builds your operations manual for free.
Days 16–25: Shift from 'how' to 'how do you know it's right.' Now you teach the quality bar — what a good day looks like, what counts as 'done,' which situations to escalate and which to handle. This is where a coordinator starts catching things instead of just doing things. Set a daily ten-minute check-in, not a hovering presence.
Days 26–30: Step back on purpose and watch the failure points. Deliberately stop touching the handed-off work for a few days and see what breaks. Whatever bounces back to you reveals a thin SOP or a missing decision rule — fix the document, not just the instance. End the month with a real conversation: what's clear, what's murky, what they need from you to own more.
The discipline that makes this stick is simple to say and hard to hold: fix the system, not the symptom. When something goes wrong, the question is never just 'how do I fix this one' — it's 'what in our process let this happen, and what document do I change so it can't happen again.' That mindset is what turns a first hire into the foundation of a business that runs without you rather than just a second pair of hands that still needs you for everything.
What good looks like at 90 days
You'll know the hire worked not when your to-do list is shorter — it might not be — but when the kind of work on it changes. The coordination, follow-up, and dropped balls are off your plate. What's left is the work that genuinely needs the owner: the client relationships, the judgment calls, the direction of the business. That's the whole point. You didn't hire someone to help you do your job. You hired someone so you could stop doing theirs.
At Turnkey Services we think about this as the first real seat in your operating system — the moment the business stops being a solo act and starts being something you build deliberately. If you want the bigger picture that this hire fits into, the operating system for a service business guide maps where the operations person sits among your other systems.
Frequently asked questions
How do I know if I need an operations person or a virtual assistant?
A VA is fine for narrow, remote, project-based tasks. A first operations person is a deeper, ongoing seat who holds context, owns recurring processes, and becomes the reliability layer of your business. If you need someone who learns how your business works and catches problems, that's an ops hire, not a task rabbit.
Should my first operations hire be full-time or part-time?
Start with the workload, not the title. If you can name 20-plus hours a week of frequent, transferable tasks, a part-time coordinator who can grow into full-time is often the safer first step. Hire to the documented work that exists, then expand the role as you document more.
What if I can't fully describe what I want them to do?
That's normal and it's diagnostic. If you can't describe the job, you can't hand it off, so spend a week writing down everything you do, then circle the repeatable, low-judgment items. That list is your job description, and the inability to write it is the clearest sign your systems live only in your head.
How long before this hire actually saves me time?
Expect to be slower for the first two to three weeks; onboarding always costs time before it returns it. Most owners feel the real relief in the second month, once the high-frequency processes are fully owned and documented. If you're still buried at 90 days, the issue is usually thin SOPs, not the person.