Backend manager: you run the machine
Chatters win conversations; the backend manager makes sure the whole operation runs — every shift staffed, every conversation up to standard, every week reported honestly. This is an operations job in an industry that mostly runs on chaos. We do not.
The job in one sentence
Chatters win conversations; you make sure the operation around them holds — every shift staffed, every conversation up to the standard the creator was promised, and every week reported honestly enough that she can act on it.
Concretely: you own the chat schedule across time zones, review conversation quality against each persona doc, catch boundary problems before they become incidents, and turn raw account data into the weekly report creators actually read. You are also the escalation point. When a chatter, a fan situation or a creator concern needs a decision, it reaches you first.
Four situations you would have to make a call on
Operations jobs are described in verbs — schedule, review, report — and the verbs tell you nothing about whether you would be good at it. These four are ordinary weeks here. If you already know what you would do, you know the job.
Situation 1
A shift is forty minutes old and nobody started it.
It is the highest-revenue account on the roster. The inbox has been building since the last hand-off, and the chatter who was scheduled is not answering messages.
What is actually at stake
Not just the lost hour. Fans who message at their usual time and get nothing learn something about the account, and the ones who learn it are disproportionately the ones who spend.
The call we would expect
Cover it now — yourself, or by reassigning — and find out what happened afterwards. In that order, without exception. The instinct to resolve the people problem first is the one that costs the most, because it loses both the revenue and, eventually, the conversation.
Situation 2
A chatter is selling well and drifting off-persona.
The numbers on her shifts are among the best on the account. Reading twenty of her conversations, the voice is not the creator’s any more — it is hers, and it is working.
What is actually at stake
The cost is deferred, which is why this gets left alone. The creator reads those conversations. And the fan who bought from a person who does not exist churns the moment the voice snaps back on somebody else’s shift.
The call we would expect
Correct it early, with the persona doc open in front of both of you, while the numbers are still good. That is the only moment when this conversation is easy. Wait until the numbers dip and you are now having two difficult conversations that have merged into one.
Situation 3
A creator asks why her revenue dropped, and part of the honest answer is us.
Maybe coverage slipped on a weekend. Maybe a pricing change we suggested did not work.
What is actually at stake
Every agency in this industry has a version of this moment, and most manage it with tone instead of fact. It works for about a quarter. Then the account leaves anyway, and it leaves believing it was lied to, which is the part that reaches other creators.
The call we would expect
The report goes out with the real reason in it, next to what changes this week. This is the part of the job that needs a spine on a Monday morning, and it is most of why the seat exists.
Situation 4
A fan crosses from customer to something else.
Sustained pressure on a documented boundary, or something that has stopped being about content. The chatter needs an answer in the next few minutes, not a policy discussion.
What is actually at stake
Blocking a large spender costs real money, and sometimes it is still the only defensible call. Getting this wrong in the permissive direction is how creators end up feeling unprotected by the people they pay to protect them.
The call we would expect
Decide fast, decide on the creator’s side, and write down what happened so the pattern is visible if the same account reappears under a different name. What we are hiring for here is the judgement to tell a difficult fan apart from a dangerous one, quickly.
What the weekly report has to contain
This is the single most visible thing you produce, and it is where most agencies quietly fail their creators. A report that lists numbers is a receipt. A report she can act on contains:
- Revenue split by where it came from — subscriptions, PPV, tips, customs — not one total.
- What changed against last week, with the reason, including when the reason is us.
- Churn, and specifically who churned: a name she recognises is worth more than a percentage.
- What was tried that did not work. A report with no failures in it is not being read carefully enough.
- What is different next week as a result. Without this line the rest is just history.
What you would inherit, and what you would build
Inherited
Persona docs and boundary lists, the hand-off standard, the shift structure and the reporting format. You are not starting from a blank page or from chaos.
Yours to build
Quality review at a size where you cannot read everything — which means sampling that reliably catches the conversations that matter, not the convenient ones.
Yours to build
Onboarding that gets a new chatter to standard predictably, instead of by whoever happened to train them.
Yours to build
The escalation ladder, written down rather than living in your head. That is the difference between a role and a person.
The failure modes of this job
Named honestly, because they are the reasons operations managers burn out rather than get fired, and because recognising one of these in yourself is more useful than a list of requirements:
- Covering every gap yourself until you are a full-time chatter with a manager’s title.
- Reviewing the accounts and the people you enjoy, and calling that a sample.
- Letting reporting slide because nothing breaks that day. It breaks in month three, all at once.
- Being liked instead of being clear. It is the same trap as situation three, one level down.
This job is not for you if
- You want someone else to set your priorities each week. Nobody here will.
- Spreadsheets and metrics are a chore rather than how you think.
- You avoid conflict. Half of the value of this seat is a difficult sentence said kindly and on time.
- You never want to be reachable outside your own hours. The operation runs around the clock and occasionally needs one decision at an awkward time — not your presence, one decision.
How pay works
A fixed base plus performance upside tied to the accounts you oversee. The specifics depend on experience and on how much of the roster is in scope, and they are discussed openly in the interview.
Where this goes
This is already a leadership seat rather than a step towards one — you would work directly with the founders, with real authority over scheduling, quality standards and escalations, and no middle layer to route decisions through. As the roster grows the seat grows with it: more accounts, more chatters, and a genuine say in how the operation scales.
Questions people ask before applying
It is a strong plus, not a requirement. Leading chat, support or sales teams transfers directly; what does not transfer is assuming this industry is like the last one, so we look for people who ask before deciding.