Team and processes, from one to ten creators

Going from one to ten creators does not take ten times more work, but a different kind of work. The lesson on roles laid out four functions; this one describes how they become positions, in what order, and what must exist before hiring anyone.

The roles, and when they appear

An operation with one creator holds up with one person doing everything. Roles then appear in a roughly constant order, because each one matches the first thing that overflows.

The conversation supervisor. Appears from the second or third creator, when you can no longer reread the conversations yourself. In an operation with chatters, this person runs the quality control described in the lesson on the chatter job. In an operation with AI, this person rereads, corrects, takes over conversations that go out of bounds, and reports what needs to change in the scripts. It is the most important and most misunderstood role, because it does not sell: it prevents selling badly.

The content editor. Appears when the catalog no longer keeps up with acquisition, often around three or four creators. This person cuts, subtitles, captions, and files everything in the vault. It is the easiest role to hand to a contractor, because the result can be checked by eye.

The acquisition manager. Appears when the number of accounts to feed exceeds what one person can handle with a scheduler, generally between four and six creators. This person runs the replacement queue, the acquisition table and the posting rhythm.

Administration. Appears last, around ten: invoices to creators, payout tracking, access register, contracts. Before that, it is you, half a day a week.

One role never becomes a position: steering. The five indicators, the running test, the decisions. You can delegate everything except judgment on the numbers.

In-house or contractor

The simple rule: contractor when the result can be checked, in-house when judgment is needed. Editing can be checked, administration can be checked. Conversation supervision requires knowing the personas, the scripts and the limits of each creator; it moves in-house as soon as it becomes a full-time role.

On what these roles cost, the course gives no pay grid and will not invent one. Public listings of the sector, collected on September 15, 2026 on a dedicated job board, give raw reference points: a team manager role listed at “$675-$2,000/mo” plus “1% of net rev”, chat moderator roles at “$3-$5/hr”, a part-time graphic designer role at “$2-$3/hr”. Chatter pay, with its press sources, is in the lesson dedicated to it. These numbers describe a global and heterogeneous market; they say nothing about the price of a competent person in your country.

Written processes: one document per routine

A process is not a manual. It is one page per routine, dated, written for someone who does not know you.

A routine is what comes back at a fixed interval: the morning reread, the day’s posting, onboarding a new creator, losing an account, the end-of-month invoice. Every page contains the same things: when, who, the steps in order, what to check at the end, and who to write to if it gets stuck.

The test of a good process is simple: a person who does not know the business reads it out loud and asks no questions. As long as they ask some, the page is not finished.

Two practical rules. The process gets written while you are still doing the routine yourself, never afterwards, because once delegated you no longer know it. And a process has a date: one that has not been reread in three months is wrong somewhere.

Tracking tools: a spreadsheet is enough

Up to several creators, a spreadsheet holds everything: the acquisition tab from module 4, the five-indicator tab from the daily routine, and a team tab with one line per person and one column per routine.

A dedicated tool is justified when a spreadsheet routine takes more time than the routine it tracks. Not before. Agency CRMs, described in module 8, bring what the spreadsheet does not: roles, shifts, named access. Those are security and access reasons before they are reporting reasons.

The meeting: one per week

Only one, weekly, short, with a fixed agenda: the five indicators per creator, the running test and its result, the accounts lost and replaced, the decision of the week. Anything that does not fit in that agenda gets settled in writing.

The weekly check-in from the daily routine becomes this meeting the day you are no longer alone. It does not change content, it changes audience.

Delegating access

This is the subject where most operations put themselves at risk, and it is settled by three rules.

Never a shared password. The sector’s tools provide the alternative. An agency CRM like Infloww describes on its home page team management with shifts and role assignment. The help center of a conversation AI like OnlyChat describes inviting a team member “with an invitation link”, choosing “the Admin or Moderator template or a custom set of permissions”, and the ability to “read every permission by group, edit a member, and remove one”. Telegram Business allows connecting a bot that handles messages without handing over the account. When a tool offers neither roles nor invitations, that is a selection criterion against it.

A register, kept the same day. The access register from module 6 gains two columns: the role granted, and the removal date. Access granted without a line in the register does not exist for you, and it always exists for the person who received it.

Removal is part of the exit process. The day someone leaves the operation, the first step is removing all their access, before the last pay. The lesson on roles and bans explains why the account loss procedure gets written in advance; this one is of the same kind.

The classic mistakes

Hiring before the processes. The person arrives, nothing is written, they learn by watching you, and you spend more time explaining than doing. Then they leave, and everything starts over from zero. Process first, person second.

Recruiting creators faster than you can serve them. The lesson on duplication showed it: the second creator is the most expensive. Every new creator requires a persona, a catalog, scripts, accounts. A poorly served creator leaves, and she leaves taking her access and her opinion of you with her.

Creating a manager position before having a team. A manager with nobody to manage becomes an intermediary between you and the work.

Delegating steering. The person who sells cannot be the only one judging whether they sell well. Neither can the person who manages the team.

Scaling is doing the same moves several times without redoing them. The team and the processes are how those moves survive your absence. The next lesson looks at what must also survive: cash flow.