Marketing Brief Engine
Deployed, in testing · Oct 2026
A daily "what to do today and this week" marketing brief for food-service operators.
Most marketing advice for food service arrives as a list of a hundred tactics. The Marketing Brief Engine turns that list into a dated plan: it reads the calendar of festivals, holidays, school breaks, match days and weather, matches them against a playbook of 99 plays, looks at the outlet's own sales rhythm, and files a small number of tickets per day with the steps, the ready text and the cost of each. It advises. It never posts, sends or spends on its own.
Who it is for
Owners and marketing leads of multi-outlet food-service groups who have the channels but not the time to decide what to do with them each morning.
What it does
- Keeps a researched calendar of events that move demand, with the reason each matters.
- Holds a playbook of 99 plays across 21 channels, each with steps, ready text, cost band, lead time and the proof behind it.
- Files tickets for the week ahead from the calendar and the weekly rhythm, within strict limits: a handful a day, no paid ads and no offers filed on their own, no play repeated within a week, a weekly spend ceiling.
- Shows a Today view, a week board, the playbook, the channels, proposed offers with a margin calculator, sales signals, and a tracker of what got done.
- Lets staff mark tickets done or skipped and note the result.
How it works
- Signals in: calendar, own sales totals, reviews, deal-app campaigns.
- Plays matched: triggers call plays; rules score and limit what gets filed.
- People decide: tickets are done, skipped or edited; offers are approved by the owner before any guest sees them.
Where Claude fits
In testing
The Brief Writer drafts each day's brief with Claude Opus 5.5 through the Claude API. It went into testing at Platform 65 in October 2026.
What goes in: the day's tickets, the calendar of events and the outlet's own sales signals.
What Claude does: picks the three to five tickets that matter today and says why, chooses which of each ticket's own wording to use and which fixed safety reminders apply, and writes private notes for the owner.
What comes out: a draft the owner approves or discards. Staff see only approved briefs: the tickets, their own wording quoted word for word, and the fixed reminders. Claude's notes stay with the owner.
The writer cannot create tickets, offers or prices, and nothing is posted, sent or spent by the engine.
Where it stands
Deployed in October 2026 and in testing at Platform 65. The calendar runs to mid-November 2026; the playbook is reviewed; the public API exists in design but is closed. The Brief Writer, which drafts each day's brief with Claude, went into testing in October 2026. Not available to outside businesses yet.