Operations Manager - Own Delivery For A Growing Remote Team (Real Authority, You Set The Cadence)

I run a small remote team across dev, marketing, creative and sales. It's growing - I have several
hires in the pipeline right now. My problem is not talent. My problem is me.

Everything routes through my head. What each person should work on next, whether the thing promised
last Tuesday actually shipped, who is sitting idle waiting on an answer fro ---------- . I am the bottleneck,
and I am spending my week chasing instead of doing what I'm actually good at - setting direction and
testing new ideas fast.

I want to hand that entire problem to one person.

WHAT YOU'D OWN

Throughput. That's it, and it's everything:

- Every person on this team always has clear work in front of them, deep enough that nobody ever runs
dry waiting to be told what's next.
- Every project has a named owner and a date. Things that stall get caught by you, not discovered by
me three weeks later.
- People who miss deadlines hear about it from you. Directly, early, without drama.
- The small decisions stop reaching me. You batch them, pre-d ---------- them, or just make the call.
- Anything we do more than twice gets written down so the next person can do it without asking.

I'm paying for outcomes, not hours logged. I don't want a timesheet and I won't be counting your
minutes. I want the team moving.

THE PART MOST PEOPLE GET WRONG

I am not hiring someone to sit online all day and answer messages. That would just replace one
bottleneck with a slower one - I answer in four hours, you'd answer Wednesday.

I'm hiring someone who builds a machine that runs when they're NOT there. Which means:

- Everyone's queue is deeper than the gap until you next check in. Nobody can run out of work.
- Blocked people unblock themselves, because you set standing rules and limits in advance instead of
being the person they wait on.
- You spot someone under-delivering from their OUTPUT - missed dates on visible work - not from
watching whether they're online.

The version of this role that fails is the one where you show up Friday and tell me what broke on
Tuesday. The system has to catch it on Tuesday, without you.

FIRST 30 DAYS

Get everything out of my head. Every open project, half-started idea, and promise I made to someone,
into one place with an owner and a date attached. Talk to every person on the team and find out what
they're ACTUALLY working on versus what I think they're working on. Then tell me, in writing, who's
idle, what's stalled, and what has no owner. That report is your first deliverable and I expect it to
be uncomfortable reading.

WHAT MAKES THIS DIFFERENT

You get real authority on day one, and I tell the team so. You set deadlines. You reassign work. You
reject deliverables that aren't finished. You escalate, and it means something. I've seen the version
of this role where someone just sends status updates and politely nags - that's useless to both of us.

You also pick your own tools. There is no system to inherit. No Asana instance, no legacy board with
400 dead cards. You build the way this team runs, from zero, however you think it should work. That
is deliberate, and yes, it's part of how I'll judge you.

And I want to be pushed back on. When I send you an idea at 6am that doesn't deserve to jump the
queue, the right answer is "not this week, here's why." If you can't do that part, the rest doesn't
matter.

WHO THIS FITS

- You've kept a team moving without being available in real time - fractional work, several clients,
or a big timezone gap. You've already solved this problem for someone else.
- You've built a work system from scratch that a real team adopted and kept using after you stopped
pushing it
- You've actually held remote contractors to deadlines, not just tracked them
- You manage people in writing, clearly and briefly, because that's where all of this happens
- You've told a boss "no, that's not worth doing" and been right
- You'd rather delete a process than add one

WHAT YOU GET

$500/month to start, growing with results as the team grows. You design your own working rhythm -
which days, which sessions, how long. Direct line to me. Full ownership of how this operation runs.
If this works, this role becomes chief of staff: you take over priority calls and team performance
directly, and I stay in my lane.

HOW TO APPLY

1. Start your application with NOBODY IDLE in capital letters, first line, nothing before it.

2. DESIGN YOUR WEEK. You set your own hours - I care about outcomes, not hours logged. Team of 5-8
people across dev, marketing, creative and sales, and I am NOT available on demand. Lay out your
week: exactly what sessions you run, how long each, what happens in each. And most importantly -
what does the team do between your sessions when someone gets blocked or runs out of work?

3. THE MONDAY SESSION. It's your Monday session. You have 90 minutes and then you're gone until
Wednesday. Six things are waiting:
a) A developer messages "finished the task, what's next?" - nothing is queued for him.
b) I sent a 6am voice note with a new idea I want tested "this week."
c) A deliverable promised to a partner TODAY is 80% done and the person who owns it has gone
quiet since Friday.
d) Someone asks you to build a weekly team productivity report. No format specified. Nobody has
asked to read it.
e) Two contractors have been waiting 3 days on a $40 payment approval only I can make.
f) An ad account got disabled overnight. Spend has stopped.
Tell me what you handle in those 90 minutes, what you deliberately do NOT handle, which ONE you'd
push back on me about, and what you'd change so this Monday doesn't happen again.

4. For (c) above - write the exact message you'd send that person. Copy-paste, word for word. Not a
description of what you'd say. The actual message.

5. THE RUN-DRY TEST. There's a 48-hour gap between two of your sessions. A developer finishes
everything in his queue at 9am, right in the middle of that gap. Nobody can reach me. Walk me
through what actually happens.

6. Have you run a team WITHOUT being available in real time - fractional, several clients at once, or
across a big timezone gap? How many people, how many projects, and how did you split your week?
What tools?

7. When you're only present for a few sessions a week, how do you tell that someone is
under-delivering? Then: tell me about a specific person who kept missing deadlines. What exactly
did you say to them, as close to your real words as you can remember, and what happened afterwards?
Include it if it went badly.

8. Name a process, report, or recurring meeting you REMOVED or cut down. Why, and what did it save?

9. Biggest measurable improvement in delivery you personally caused - on-time percentage, turnaround
time, hours handed back to the owner, backlog cleared. Real numbers, and how you measured it.

10. A decision you made without asking permission that you weren't 100% sure about. What was it, and
how did it turn out?

11. Which days and times would you actually run the sessions you designed in question 2? Your timezone
and overlap with Europe. And be straight with me about what else is on your plate at those times -
I care that the sessions are real and that you hit them.

Answer them numbered, in order. How you format this application tells me most of what I need to know
about how you'd run my team.