When to hire staff and when to outsource operations for a local publication
A workload framework that sorts your tasks by type and growth trajectory, so you hire for the work that defines your publication and hand off the work that does not.
- Classify every task as editorial judgment or repetitive admin before deciding who does it
- Hire in-house for editorial voice, source relationships and sponsor relationships
- Hand off repetitive busywork, either to a contractor or to AI operations
- Match the decision to projected growth, not to this week's stress
It is Tuesday and the newsletter goes out Thursday. Two sponsors want renewal terms by Friday. The inbox holds a dozen routine messages, the events calendar needs updating, and the story you actually want to report sits untouched. Every growing publisher hits this week, and the instinct is to hire someone, anyone, to make it stop. The right move is not to hire fastest. It is to sort the work first.
A workload framework can tell you what to hire for and what to hand off. The idea is simple: classify each recurring task by type, then by what your growth trajectory demands, and the hire-versus-outsource answer falls out of the sorting.
Sort your tasks into two types
The first type is editorial work. This is work that requires judgment about your town and your readers: reporting, writing, choosing which story leads, deciding what a sponsor feature should say, and maintaining relationships with sources and advertisers. Get this wrong and your publication stops sounding like itself. This work sits closest to why readers open your newsletter, so it is the strongest candidate for an in-house hire.
The second type is repetitive admin. Formatting the newsletter issue, pulling in events and job listings, updating the site, chasing sponsor materials, answering routine email, and copying data between tools. None of it requires judgment about your town. It needs to happen reliably, on schedule, and it eats the hours you would rather spend reporting. This is the work to delegate, and the question is only whether a person or software does it.
Add the growth dimension
Task type tells you what kind of help you need. Growth tells you how much and in what form. A publication that is flat, with a stable subscriber count and a sponsor roster that renews on its own, has a capacity problem that fixed delegation can solve. A publication adding subscribers every week through Meta ads has a pipeline problem, and each new subscriber adds a little more admin and a little more revenue potential. Those two situations call for different decisions even when the Tuesday stress feels identical.
- Flat growth, mostly editorial overload: hire a part-time reporter or editor. The bottleneck is content, and delegation of admin will not fix it.
- Flat growth, mostly admin overload: delegate the admin, by contractor or by software, before adding headcount.
- Growing fast, editorial holds up: the growth is adding routine work faster than judgment work. Delegate the repetitive layer first so reporting capacity keeps pace.
- Growing fast, both are breaking: hire for editorial and delegate admin at the same time. Adding only one will just move the bottleneck.
What to hire in-house
Hire in-house for anything a reader or sponsor experiences as your voice. That means reporters, an editor if you publish several times a week, and eventually a sales person once sponsor relationships need regular attention. These roles compound. A reporter who knows the town gets better every month, and that knowledge cannot be bought back later at the same price. The test for a hire: does this person make decisions a reader would notice? If yes, the role belongs inside.
What to hand off
Hand off anything with a checklist. Newsletter assembly, calendar and listings maintenance, routine sponsor communication, and data entry all qualify. A freelancer or virtual assistant can run these on a fixed weekly schedule, and the cost scales with the work rather than with a salary. The trade-off is onboarding time: a contractor needs documented steps before the delegation actually saves you hours. Write the checklist as you do the task one final time, and the handoff becomes cheap.
Software can now take over part of this layer. Local Media HQ, which runs more than twenty local publications with over 175,000 subscribers, built AI into its own operations for exactly this reason: its lightbreak product pulls in news, homes, events, pets and jobs and writes the newsletter issue in the publication's voice, and greetform handles routine interactions, so the team spends its hours on editorial and sponsors rather than assembly work. The company offers AI operations as part of its ongoing advisory work. That is one option for the repetitive layer. A general contractor with a good checklist is another, and the framework above tells you which tasks either one should take.
Run the framework on your own week
- 01List everything
Write down every recurring task from last week, including email, assembly and admin.
- 02Label each task
Mark it E for editorial judgment or R for repetitive admin.
- 03Estimate hours
Put a rough weekly hour count next to each task.
- 04Check your growth
Note whether subscribers and revenue are flat or climbing, and at what pace.
- 05Add up the R column
If it exceeds ten hours a week, delegation pays for itself first.
- 06Pick one hire and one handoff
Choose the highest-hour E task for an in-house hire and the highest-hour R task to delegate this month.
Common mistakes
The most common mistake is hiring a general assistant when the real bottleneck is editorial. You gain admin hours you did not badly need and stay short on the reporting that grows the list. The second mistake is delegating without documentation, which turns the handoff into a second job of supervision. The third is treating the decision as permanent. A publication that is flat this quarter may be growing by summer, so revisit the framework quarterly rather than once.
