Marketing from the guest record.
A content calendar that fills itself from cultural moments and from what each venue is doing, with campaigns built from live guest records rather than from an export.
A month planned before anyone opens it.
Deepavali, a Beaujolais release, a new menu, a quiet Tuesday. The calendar fills from cultural moments and from what each venue is doing, and the agents draft against both. Each brand gets the moments that matter to it.
What it does differently
The calendar fills itself
Cultural moments, menu changes, events and quiet nights land on the calendar as they appear, and the agents draft against them. The team edits a month that already exists instead of starting from a blank one.
Every claim is checked against the venue
A dish named in a post is live at that site, the stock covers the demand the post should bring, and the allergens match the recipe. A campaign cannot promise what the kitchen cannot serve.
Sends wait for the room
Before anything goes out, it reads bookings, capacity, the roster and stock. A full Friday holds the offer and moves it to a night that needs the guests.
What it writes to the model, and what Launchpad does with it.
An audience is built from the same guest records loyalty and messaging write, so a campaign lands on people the venues actually know.
- Reads & writes
- guests, audiences, campaigns, offers, brands
- Launchpad
- Builds audiences from live guest records. Drafts campaigns against what each venue is actually doing. Times sends to the operation.
- Autonomy
- Set per capability, from off to unattended, and movable back
- Works with
- Loyalty, Messaging, Events, Recipes
What the agents actually do.
Two capabilities, start to finish, on the same model the venues run on.
A campaign, drafted from a menu change
The autumn menu goes live in Recipes, and a campaign is drafted within the hour: a post, an email and a message, each written for its channel and pointed at the regulars who order those dishes. Every dish it names is checked against the menu at that site, the stock against the demand it should bring, the allergens against the recipe. The harbour site gets its own version, because uni is not on the menu there.
A send, held until the room can take it
An oyster weekend is scheduled for Friday. Friday is nearly full, and the oyster delivery comes in short, so the send would fill tables the kitchen cannot serve. It holds the send, moves it to the quiet nights after the next delivery, leads with the crudo instead, and tells the marketing lead what it did.
Upgrade the way campaigns get made.
FAQ
A cultural calendar for the markets you operate in: public holidays, festivals, trade dates such as a wine release, and retail moments. You choose which apply to which brand, and add your own, such as a venue’s anniversary.
Menus and recipes, stock and deliveries, bookings and capacity, events, the roster and guest records, all from the one operational model. That is what lets a draft name a dish that is on, at a site that can take the table.
Only if you let it. Planning and drafting usually run unattended, scheduling acts and tells you, and publishing asks first until the team decides otherwise. The setting is per capability and per brand, and it moves back as easily as forward.
Each brand carries its own rules: tone, words to avoid, how offers may be stated, which photography may be used. Drafts are written inside them, and anything that falls outside is flagged for a person.
No. Most groups keep the sending tools they already run, and Marketing hands them finished, approved work. Move the sending across later if it suits you.
They stop filling in calendars and start directing them: which moments matter to the brand, what the voice is, which campaigns deserve real craft. The scheduling, the resizing and the per-site versions are what is left to the agents.