How a small hotel fills a month of social video
Overview
Section titled “Overview”
If you run social for a small hotel, the hardest part of the week is deciding what to post — not shooting, editing, or publishing. This playbook gives you a 4-bucket system for the whole month.
In 5 chapters: 4 buckets · 3 guest asks · 16 posts/month from 40 minutes on Monday · 2 metrics that matter.
01 · Invention is the bottleneck
Section titled “01 · Invention is the bottleneck”Starting from scratch every week is what burns out one-person social — and “post more” advice quietly makes the burnout worse.
In short: Stop inventing. Curate four standing footage sources instead.
The bottleneck for small-hotel social isn’t cadence — it’s invention. Manufacturing a week of ideas from nothing, every Monday.
It’s giving up on invention. A small hotel doesn’t need fresh ideas every week — it needs four standing sources of footage that refill on their own.
02 · Four buckets that fill themselves
Section titled “02 · Four buckets that fill themselves”Four standing sources that fill themselves with what your property and guests are already producing — no new ideas required.
In short: Guest content, behind-the-scenes, location, transformation — each refills on its own.
Guest content
Footage guests already make and tag.
Refills: every booking
Behind-the-scenes
Staff and property moments guests never see.
Refills: every shift
Location-led
The destination, not the hotel — yours, or pulled from a library.
Refills: instantly (library) or seasonally
Transformation
Before/after of any operational change.
Refills: every shift change
Guest content. The slow-mo of espresso on the terrace, the dog meeting the room slipper, the pan across the bed at check-in. Some lands in your tagged feed without asking. Some needs a one-line ask at checkout (chapter 03).
Behind-the-scenes. What guests never see — the chef pulling tomatoes apart at 7am, the gardener watering the lemon trees before breakfast service. Three minutes of phone footage from any staff member, once a week, fills the bucket faster than it empties.
Location-led. The destination a guest would Google before booking — a sunset point ten minutes up the road, the Saturday market two streets over, the €14 trattoria with no website. Half of “should I book here” is “what’s around here”.
Transformation. Before-and-after of anything — empty room vs turned-down room, raw cod vs the plated dish at 8pm, same terrace at sunrise vs sunset. The drama of the change is what the algorithm rewards, and it’s already what you do every shift.
03 · Three asks that earn yes
Section titled “03 · Three asks that earn yes”Three moments in a stay when guests are most open to sharing — and the exact line that gets a yes.
In short: Ask at first wow, mid-experience, or checkout — never produce, only tag.
Moment 1 — The first wow
Section titled “Moment 1 — The first wow”The first ten minutes of delight: welcome cocktail, first sunset, walking into the room and seeing the bay. Their phone is already out.
“If you post any of this, our handle is @yourhotel — we love seeing the property through guest eyes.”
Moment 2 — Inside the experience
Section titled “Moment 2 — Inside the experience”The boat trip, the cooking class, the dinner on the terrace. The guest is already filming for themselves. You’re asking to be included, not asking them to produce.
“If you share any of this, tag us — we always reshare guest stories from this trip.”
Moment 3 — Checkout
Section titled “Moment 3 — Checkout”The experience is closed; the next email is the review request. Same email, one extra line.
“If you posted anything from your stay, send us the link or tag @yourhotel — we’d love to share it.”
You’re not asking guests to produce content — you’re asking them to tag what they were already going to make.
04 · Sixteen posts, one decision
Section titled “04 · Sixteen posts, one decision”A 28-day grid where each bucket has a home day — so you stop deciding and start posting.
In short: One bucket per home day — Mon location, Wed behind-the-scenes, Fri transformation, Sun guest.
One fixed slot per bucket, every week, the same way. The calendar runs on autopilot.
The week, by day
Section titled “The week, by day”Four posts a week, four weeks a month, sixteen posts — realistic for a one-person social lead through a real season. Forty minutes on Monday schedules the whole week.
Surviving high season
Section titled “Surviving high season”When staff is at capacity, social is the first thing dropped. The grid survives because each bucket has a different failure mode:
- Location-led is the easiest to pre-shoot — bank three weeks on a quiet Tuesday in February
- Behind-the-scenes barely needs editing — shoot-and-post, vertical, no captions
- Guest content scales by itself in high season: more guests, more tags, zero extra work
- Transformation breaks first when staff is underwater — pre-shoot one a fortnight in low season as backup
05 · Two metrics, the rest is noise
Section titled “05 · Two metrics, the rest is noise”Two signal numbers tell you the system is working — the rest of the dashboard is noise in week one.
In short: Track only saves and profile visits. Ignore likes, views, followers.
| Metric type | Examples | What it really tells you | Use it when |
|---|---|---|---|
| Vanity | Likes, views, follower count | Did people see it and react | Never in week one |
| Signal | Saves, profile visits, link-in-bio clicks | Are viewers becoming bookers | Always |
| Mixed | Shares, comments | Engagement quality unclear on its own | Secondary check only |
Saves are the closest thing social gives you to booking intent — would I bother if I weren’t planning a trip?
Profile visits are the next funnel step made visible — choosing to leave the feed for your profile is the highest-intent gesture short of booking.
The bottom line
Section titled “The bottom line”The system, in five lines:
- Four buckets that fill themselves
- Three asks that earn yes
- A 28-day grid → sixteen posts a month from forty minutes on Monday
- Two metrics that say whether it’s working
- Permission to break it — three times, deliberately
The shift isn’t that you publish more. It’s that you stop deciding what to publish.