I run a small agency. For a long stretch, “the content team” was me and one other person, and we were producing for our own site plus a handful of independent hotels. So when a hotelier tells me they can’t possibly keep up with content because it’s just them and a front-desk manager who “is good at Instagram,” I get it. I’ve lived the math.
Here’s the thing nobody tells you: the problem is almost never that you can’t write enough. The problem is that you’re producing content the slowest, most expensive way possible, treating every blog post, every email, every social caption as a fresh, from-scratch build. That’s the bottleneck. Not your headcount.
This post is about how a two-person team actually scales throughput, the whole pipeline, not one channel. I’ll show you the capacity math, the batching system we use, and the repurposing engine that makes it all multiply. No magic, no “post 5x a day” nonsense. Just a system a tired team of two can run on a Tuesday.
Why your output feels capped (and it isn’t headcount)
Let me name the real enemy: context switching. When you write a blog post Monday morning, switch to answering OTA messages, then try to “knock out some social” Monday afternoon, your brain pays a tax every single time it reloads a different task. Research shows that reload costs real minutes, and for creative work it’s brutal.
A small team doesn’t have spare minutes to burn. So the first move isn’t “do more,” it’s “stop paying the switching tax.” That’s what batching solves.
The second enemy is single-use thinking. You spend three hours researching the best walkable restaurants near your property, write one blog post, publish it, and… that’s it. Three hours, one asset. That’s the expensive way. The same three hours of research should feed a blog post, a Google Business Profile post, four social captions, one email segment, and a line in your local-area guide. Same research. Six-plus assets. That’s the cheap way, and it’s the entire game.
The unit of work for a lean team is not “a piece of content.” It is “a body of research.” You do the expensive thinking once, then harvest it across formats. Output scales with how many formats you harvest, not how many times you re-research.
Step one: figure out your real capacity
Before you plan output, you have to know what you’ve actually got. Most hoteliers wildly overestimate their available creative hours and then feel like failures when reality hits.
Sit down with your two people and count deep-work hours only, the hours where someone can close the door and produce. Not “I’m at the desk eight hours.” Real focused hours. For a front-desk-adjacent person, that might be three hours a week. For an owner wearing six hats, maybe two. Be honest and a little pessimistic.
Say you land on this:
| Person | Role | Deep-work hours/week |
|---|---|---|
| You | Owner / strategy | 3 |
| Teammate | Front desk / social | 4 |
| Total | 7 |
Seven hours. That’s your budget. Everything below is designed to make seven hours produce what most properties get from twenty, because most of those twenty are wasted on switching and single-use builds.
Step two: assign lanes, not tasks
Two people, one common failure: both people half-doing everything. Instead, give each person a lane that matches their strength, and protect it.
In our setup, one person owns cornerstone creation, the deep, research-heavy pieces that everything else flows from. The other owns derivative production and distribution, turning cornerstones into the social posts, GBP posts, and emails that actually reach people. The strategist drafts the meaty stuff; the distributor harvests it.
This matters because cornerstone work and derivative work need different brains. Cornerstone is slow and thinky. Derivative is fast and repetitive. Forcing one person to do both in the same sitting is how you get the switching tax all over again. Lanes kill that.
If your teammate is “good at Instagram,” great, that’s your distributor. Don’t make them write 1,500-word location guides. Make them shred your guides into fifteen posts.
Step three: batch by activity, not by topic
Here’s where most people get batching wrong. They think batching means “do all my October content in one week.” That’s a calendar batch, and it’s fine, but it’s not the lever.
The real lever is batching by activity type. Group the same kind of work together so your brain only loads the tool once. Our week, compressed into those seven hours, looks like this:
- Research + outline day (the strategist, one sitting): knock out three to five outlines at once. Research compounds, because hotel topics overlap. The research for “best coffee near the property” overlaps with “a perfect slow morning in the neighborhood.” Batch them and you research once for two outlines.
- Writing day (the strategist, separate sitting): write only. Outlines are done, so this is pure drafting with no blank-page friction.
- Repurposing day (the distributor): take finished cornerstones and explode them into derivatives. This is assembly-line work and it’s weirdly satisfying.
- Schedule + publish day (the distributor): load everything into the scheduler, set the GBP posts, queue the emails, done.
Notice nobody is doing two activity types in one sitting. That’s the whole point. You’re not working more hours; you’re working hours that aren’t leaking.
Step four: the repurposing engine (the actual multiplier)
This is the part that turns a seven-hour budget into twenty-hours-worth of output. One cornerstone piece becomes a cascade. Here’s a single blog post, fully harvested:
- The cornerstone blog post — your detailed, genuinely useful guide. This is the source of truth.
- One Google Business Profile post — pull the single best tip and post it with a photo. (If you want the full GBP system, I broke it down in our Google Business Profile playbook.)
- Three to five social captions — each one a different angle from the same post. One stat, one story, one tip, one question, one behind-the-scenes.
- One email section — drop the summary into your next guest newsletter or pre-arrival email with a link.
- One FAQ / chat snippet — the answer to the question the post answers, reformatted for your booking chat and your site FAQ.
- One AI-friendly Q&A block — a clean question-and-answer version that helps you show up when guests ask assistants like ChatGPT about your area. (More on why that matters in is your hotel invisible to ChatGPT.)
One body of research. Six-plus assets. Now run four cornerstones a month and you’re suddenly shipping twenty-plus pieces from a two-person team that “doesn’t have time for content.”
Repurposing isn’t lowering your standards. It’s refusing to throw away research you already paid for. The lazy move is starting from scratch every time, not reshaping what you’ve got.
A quick honesty note, because I won’t sell you fairy dust: this builds momentum, it doesn’t buy overnight rankings. Content compounds over months. Anyone promising you guaranteed top-of-Google placement from a content calendar is selling you something. What this system buys is consistent, compounding presence on the channels that feed direct bookings, which over time is exactly what loosens your dependence on the OTAs.
Step five: protect the system from yourself
Three habits keep this from collapsing the first busy week:
Keep a running idea bank. The fastest way to kill a research day is staring at a blank “what should we write about” doc. Every time a guest asks a question at the front desk, log it. Those questions are your best content topics because real humans actually asked them. Your distributor can keep this list growing without any deep work.
Template the derivatives. Your distributor shouldn’t reinvent the caption format every week. Build a simple template for each derivative type. Assembly lines run on jigs, not inspiration.
Defend the batches like appointments. If “writing day” keeps getting eaten by walk-ins and vendor calls, the system dies. Two protected hours beat eight interrupted ones. This is the single most common reason small-team content plans fail, not lack of effort, but unprotected time.
When to add a third person (and when not to)
A lot of owners think the answer is hiring. Sometimes it is. But here’s my rule: do not hire until your system runs. If your process is chaos, a freelancer just produces chaos faster, and now you’re paying for it.
Once your batching and repurposing engine is humming, a contractor slots cleanly into a lane. The obvious first hire is a freelance writer who takes your batched outlines and drafts the cornerstones, freeing your strategist to do more strategy. Or a part-time editor who polishes derivatives. Because the lanes already exist, a new person plugs in without you having to invent a job for them.
And honestly, a lot of properties never need the third person. Seven well-spent hours with a real system out-produces twenty chaotic ones. That’s not a motivational line, it’s just what happens when you stop leaking time and stop throwing away research.
The whole thing, on one page
If you remember nothing else:
- Count your real deep-work hours and plan against that number, not a fantasy.
- Give each of your two people a lane (cornerstone vs. derivative) and protect it.
- Batch by activity type so your brain loads each tool once.
- Make repurposing your multiplier, one body of research, six-plus assets.
- Protect the batches like guest appointments, or the system quietly dies.
This is the same backbone we use when we build a content and reputation program for a hotel, and it’s why a tiny team can punch way above its weight. Content is the long game that feeds everything else, your local visibility, your AI presence, and ultimately the direct bookings that keep more revenue in your pocket instead of handing 15 to 25 percent to an OTA on every reservation.
Where to go from here
If you’ve got the people but not the system, that’s a fixable problem, and it’s exactly the kind of throughput engine we set up so a lean team isn’t drowning. If you’d rather not build the whole machine yourself, that’s what we do. Book a call with me and we’ll map your real capacity, design your batches, and stand up a repurposing engine your two-person team can actually run, week after week, without burning out.