Playbook 06 · New / hiring

They are hiring junior or admin headcount for repeatable work that a well-designed process, service, or tool could do for less. The hiring manager rarely sees the alternative until somebody shows it to them, and this playbook makes you that somebody.

Playbook 06 / junior headcount vs redesigned work
Who it targets The senior owner of the function: Head of Ops, Finance, CS, or the founder still wearing that hat.
The signal Junior / coordinator / clerk roles, JD language about spreadsheets, manual reconciliation, invoice processing, basic reporting, or repeated hires of the same seat.
Where it is visible LinkedIn Jobs, Indeed for some markets, careers pages, sometimes a founder complaining about “ops drag” in a post next to an open junior role.
Time cost ~45 minutes per live target through the tradecraft pipeline. Screening is faster than on the senior playbooks. Trust still dies if you sound like a tool vendor. Do not short-cut the waterfall into a feature blast.

How to run it

Step 01: Look for repeatable-work roles in the monitor feed.

Tradecraft stages 1 and 2. Junior data clerks. Bookkeepers. Scheduling coordinators. Reporting assistants. The title alone is often the signal. Multiple open reqs for the same junior seat is louder: they are scaling a mess, not a system. Agency strip still applies.

Step 02: Scan the description for tells, then expand.

“Spreadsheet entry.” “Manual reconciliation.” “Process invoices.” “Compile reports.” “Copy data between systems.” These are signs the work was never systematised. If the JD is really about judgement-heavy work dressed in a junior title, skip. Run tradecraft stage 3 on keepers: the same brief often sits on other boards and at other companies running the same mess.

Step 03: Find the senior person responsible.

The tradecraft stage 4 ladder applies: Head of Ops, Finance, or CS, or the founder still wearing that hat. Confirm they own the decision and whether this is hire one or hire five. If you can see three people already in the same junior role, your note should talk about redesign, not a single hire substitute.

Step 04: Bring the alternative as a two-paragraph note, not a pitch deck.

Waterfall, send, log (tradecraft stages 5 and 6). Name the pattern. Offer a short conversation or a one-page comparison of hire vs process/tool path. Do not lead with software brands unless your offer is literally implementation of a named stack you are known for. Lead with reclaimed time and error rate.

What to say

Head of Ops / data operations coordinator role

Ravi, saw Cinder hiring a Data Operations Coordinator for spreadsheet entry and manual reconciliation across three tools. I have seen three companies your size move that exact work onto a process plus light automation and reclaim roughly two days a week per person, with fewer month-end surprises.

Not asking you to cancel the hire. Worth twenty minutes to compare the hire path with the redesign path before the role is filled?

How this playbook fails

  • You sound anti-hiring. You are pro-fit-for-purpose work design.
  • You pitch a tool they already evaluated and rejected.
  • You target a role that needs human judgement you cannot replace.
  • You write like a product marketer, which spends status the way a seller does. Operators delete that on sight.