Asking for more people on a Trust & Safety team

To the people who set the budget, a Trust & Safety team looks like a cost, right up until the quarter something goes badly wrong. And the people holding the money are rarely the ones watching the pile of reports grow. So you make the case in their language, with proof you collected before you needed it.

The teams that grow aren't the ones with the worst backlog. They're the ones whose leads kept receipts.

Three arguments, and who each one convinces

Make all three, starting with whatever the person across the table cares about most:

• Risk, for the lawyers and the board. Your proof: letters from regulators (the government bodies that enforce the rules), close calls, and the disaster that almost happened.
• The law, for compliance and finance. Your proof: specific legal requirements with deadlines, and what missing one costs.
• Money, for product, sales and finance. Your proof: money lost to fraud, sellers and advertisers leaving, and markets you can't enter unless people trust you.

"Keeping people safe is the right thing to do" is true, and it won't win the room. Everyone already agrees with it, and it has no number attached. Say it once, briefly, then switch to figures.

Collect the proof before you need it

• A close-call log: things that almost went wrong, one dated line each. Nothing argues for more staff like a disaster you dodged by luck.
• The math on reports: how fast they're growing compared with how many your reviewers can get through, updated monthly. The memo below is built on it.
• A list of things the team stopped doing to keep up, with the date each one got dropped.
• Missed deadlines, counted. "We miss the child safety deadline eleven times a month" survives a budget meeting. "We're stretched" doesn't.
• What the last real incident cost in engineering hours, legal time and PR work. Write it down while people still remember.

Build the memo around a date

Reports in    9,400/week, growing ~6% a month
              (12-month trend attached)

Capacity      11 reviewers x 950 cases/week
              = 10,450

Today         About 1,000 cases/week to spare

January       Reports pass capacity. A backlog
              starts.

March         Wait times blow past the 72-hour
              target at current staffing. Two
              hires in November push that date
              past the end of the year.

A memo like this doesn't have to raise its voice. It doesn't argue that safety matters. It shows the date the team runs out of room, and it turns your request into a choice finance already knows how to make: pay now, or pay later.

What weakens your case

• Comparing yourself to another company. "That platform has forty people" gets you "they have different problems," and the conversation is over.
• Scary stories with no math. A list of worst cases with no sense of how likely they are sounds like lobbying.
• Asking for everything at once. Ask for the two hires that move the date, and call the rest phase two.
• Quietly covering the gap. Every quarter your team survives short-staffed is more proof, to the budget people, that it can.

When the answer is still no

Sometimes it's a no. Then the grown-up move is to put the risk in writing: a short note to whoever decided, saying what you asked for, what was turned down, and what the team won't be covering as a result.

It's not a threat. It's bookkeeping. It's the honest record, it concentrates minds wonderfully, and it's the first thing you'll pull out the next time budgets come around.