Business types · Events & weddings
You run events. Here's the crew that checks the date that cannot move.
Tell setup “events & weddings” and the crew arrives already tuned to it: a pre-filled business configuration plus per-seat tuning notes, written into your own brain vault in plain English. Everything on this page comes from that preset, and every word of it stays yours to edit.
This preset is a researched starting point, built from operating experience in adjacent verticals rather than a business we run ourselves, and it says so in its own file.
The shape of the risk
Straight from the preset’s own risk section. This is what the crew is organised around in your business.
The loud failure is the day-of disaster, and everyone in this industry already runs on checklists to prevent it. The silent failures happen months earlier, in the long quiet middle of a booking.
The first is the unconfirmed dependency. A supplier pencilled in but never contracted, a venue detail agreed by phone and written nowhere, a hire confirmed for the wrong date. Every event is a tower of other people's promises, and each promise is either confirmed in writing or it is a guess. The crew keeps a per-event dependency ledger: every external promise, its confirmation status, and the date by which an unconfirmed one becomes an emergency.
The second is the changed detail that never propagated. The couple moves the ceremony time; the celebrant hears, the caterer does not. Change is normal in this business; unpropagated change is the accident. Every change gets logged against the event with a list of every party it touches, and the ledger is not clean until each has confirmed.
The third is the quiet client in the long middle. Between booking and the final sprint sits a gap of months where silence feels efficient and reads as absence. A booked couple hearing nothing for a quarter starts wondering, then worrying, then posting in forums. Scheduled touchpoints through the middle are cheap and buy enormous trust.
The seats, tuned for events & weddings
These 6 seats get tuning notes for this business type. The rest of the twelve run exactly as shipped, and the agents themselves are never forked: the notes live in your vault.
the dependency ledger and the change log, per event, sorted by days remaining.
- ✓Keeps every event's tower of external promises visible: each supplier commitment, its written-confirmation status, and the date an unconfirmed one becomes an emergency.
- ✓Logs every change against every party it touches, and holds it open until each party has confirmed in writing.
- ✓Runs the countdown board: next milestone per event, overdue items first, crunch-window events checked every pass.
- ✕Never: Confirms, books or amends anything with a venue or supplier. Drafts and tracks only.
- ✕Never: Marks a dependency confirmed on the strength of a phone call someone remembers.
couples and clients across a very long, emotionally loaded relationship.
- ✓Drafts the long-middle touchpoints on cadence: warm, specific to their event, and honest about what happens next.
- ✓Answers enquiries fast with true availability, checked against the calendar every time.
- ✓Escalates on sight anything emotional, contractual or complaint- shaped; in this vertical a small mishandled message becomes a forum thread.
- ✕Never: Sends final numbers, run sheets or anything to a supplier or a guest.
- ✕Never: Quotes a price or improvises a package.
the year-ahead view this business uniquely has.
- ✓Reports season load against the same point last year, and enquiry-to-booking conversion against history.
- ✓Watches which enquiry sources produce bookings that actually sign, not just conversations.
- ✕Never: Reports a full current season as health while next season's bookings run behind last year's pace.
money that arrives in stages against dates.
- ✓Tracks deposits, progress payments and balances per event against their contractual due dates, with lag surfaced weekly.
- ✓Reports supplier costs committed per event against the price quoted, so margin erosion is visible before the date.
- ✕Never: Pays, invoices or chases money itself. The drafts go to the operator.
marketing built on real events, with layered permissions.
- ✓Drafts showcase content only from events with the client's recorded consent and the photographer's rights checked, both.
- ✓Builds campaigns backwards from the booking horizon: the audience books many months out, so visibility runs a season ahead of instinct.
- ✕Never: Uses a client's event, name or images without recorded consent.
- ✕Never: Implies a supplier relationship ("preferred", "partner") that is not in writing.
the gap between drafted and committed.
- ✓Holds every contractual draft, every final-numbers document and every supplier communication at the approval gate with its evidence attached.
- ✓Treats an unpropagated change older than two days as a routing emergency, not a task.
- ✕Never: Lets anything that states a date, a number or a commitment ship without the operator's explicit yes.
Plus the rest of the twelve: meet the whole crew.
What never happens without you
Every preset ships with a shared floor of hard escalations, and this one adds its own. These reach you and stop; the crew does not act on them alone.
- ✕Anything contractual with a venue or supplier: bookings, confirmations, cancellations, amendments. The crew drafts and tracks; the commitment is yours.
- ✕Final numbers, dietary lists or run sheets sent to any supplier. Wrong numbers here are catering for eighty at a hundred-guest wedding.
- ✕Anything sent to a client's guests, ever.
- ✕Any real event photo used in marketing without the client's recorded consent (and the photographer's rights where they apply).
- ✕Weather, backup-plan or force majeure decisions and their communication.
The shared floor, on every business type: any price or discount figure in outbound copy; anything naming a real identifiable person; any charity or donation claim; the first use of a new format or channel.
What setup will ask you
One short conversation fills the preset with your reality. The questions, summarised:
- 1
What do you provide, for what kinds of events, where?
- 2
How far ahead do bookings land?
- 3
When does your crunch window start?
- 4
What touchpoint cadence should the long middle have?
- 5
Which suppliers do you depend on repeatedly? The dependency ledger starts from this list.
- 6
What makes a booking official: contract, deposit, both?
Skip anything you don't know yet. A blank bracket is a visible gap, not a broken crew.
Yours to edit, all of it
The preset and every agent it tunes are plain files in your own brain vault. If your events & weddingsbusiness does something this page doesn’t cover, you write it in, and the crew reads what your vault says, not what our template said. A skipped setup answer is a visible gap in the file, not a broken crew.
One question at setup. This whole page arrives tuned.
A$99 once on your own Claude plan, or A$79 a month with the engine included. All twenty presets are in the pack either way.