tooBooked — The Coordination Chapter (Product Brief)

Executive summary

Booking software is a commodity. The defensible thing is being the place where the whole event happens — every conversation, document, payment, and plan, across every vendor, with the couple in the middle. This chapter built that surface and the network effects around it.

🔒 The moat

A multi-vendor hub a couple shares with their photographer, DJ, florist, and planner at once. Single-vendor tools (HoneyBook, DJ Event Planner, Aisle Planner) structurally can't do this.

📈 The wedge

tooBooked still leads with dynamic pricing / BookLine — forecasting underbooked months and pricing to fill them. No competitor does this; it's the reason a vendor switches.

1 · The Hub became a real messaging product

The per-client chat is the daily habit that makes everything else sticky. We made it feel like iMessage — for business.

💬 Reactions new

What: long-press any message → tap-backs, drawn as neutral monochrome icons (no skin-toned emoji). Why: fast, human acknowledgement without a reply.

Now possible: lightweight back-and-forth that feels native, in vendor↔couple, groups, and DMs.

📦 Send anything in chat new

What: brochures, contracts, and invoices post as rich cards — live & clickable for couples, read-only for fellow vendors. Why: the deal happens in the conversation, not a detached email.

Now possible: quote → review → pay → sign without ever leaving the thread.

2 · A vendor network, not an island

Vendors refer each other constantly. We turned that real-world behavior into product.

👥 Group chats & private DMs new

What: create a group for a wedding's vendor team; private 1:1 DMs unlocked by friending. Why: coordination between pros (timeline, logistics, referrals) lives in-app.

Now possible: a photographer pulls the DJ + planner into one thread for a shoot.

🪪 Profiles + friend requests new

What: tap any vendor → a profile card (company, IG, email, phone) with ＋ Friend. Why: builds the network that powers referrals and groups.

Now possible: a referral marketplace effect — every connection grows the graph.

The Chats page — ⭐ Favorites, Recent Activity, all conversations with filters.

The couple's portal — their wedding hub, first open.

3 · The couple sees everything, calmly

A white/blush, editorial portal where a couple manages every vendor in one place — message, pay, approve, schedule.

One hub, all vendors — photo/video, florist, DJ, planner — each a tap away.
Profile + chat per vendor — Call · Text · Email, with the conversation below (mirrors the real app).
Pay, approve, add a service — right inside each chat.
A real calendar — week strip with week-by-week navigation, shared from their vendors.

The couple's vendor hub — every pro for the big day, in one place.

4 · The shared Event Timeline the new moat

The feature single-vendor tools (Timeline Genius @ $55/mo, Aisle Planner, DJ Event Planner) sell whole products around — but built shared-first.

🕒 Run-of-show, built once

What: a run-of-show of moments (time · title · who), occupation-aware templates (DJ / Planner / Photographer / Classic), and a ＋/−15 cascade ("push the rest of the night"). Why: it's the planner's #1 deliverable and the DJ's set list — now native.

🔗 One timeline, everyone sees it

What: the vendor builds it; it publishes live to the couple's portal (and co-vendors), filtered by who's assigned. Why: competitors re-create a copy per vendor — we keep one shared source of truth.

Now possible: the DJ sees song moments, the photographer sees shot windows, the planner owns the master — one document, live.

📍 In-person meetings + .ics

What: schedule any meeting type — video, phone, or a plain in-person meetup with free-text details — saved internally and exportable to Apple/Google calendars via .ics.

💸 Free-tier showroom

What: free vendors see a fully-populated fictitious dashboard (12-mo forecast, revenue, score, booked + leads) so they experience the moat before paying.

5 · See it move

Both demos are real DOM, animated in real time (no GIF) — looping below. Tap "Watch with sound" for narration (when added).

Vendor side — inquiry → brochure → packages → contract → pay & sign.

Couple side — one hub, four vendors: pay, schedule, add a service, change a song.

6 · Why this wins

Against the category, the combination is unmatched: dynamic pricing + a couple-facing, multi-vendor hub + a shared timeline.

Capability	tooBooked	HoneyBook	DJ Event Planner	Aisle Planner
Dynamic pricing / BookLine	✓	—	—	—
Couple hub across ALL vendors	✓	—	—	—
Shared event timeline	✓	—	per-vendor	planner-only
In-app chat + reactions + groups	✓	partial	—	partial
Contracts · invoices · payments	✓	✓	✓	✓

7 · What's now possible

The foundation unlocks a clear runway — each item reuses infrastructure already built this chapter.

Shipped since v1 of this brief: the DJ music layer (Spotify song on each moment), a printable PDF run-sheet, and the couple's song-request / do-not-play planner. Next:

Day-of reminders — "grand entrance in 30 min" to each vendor, via the existing reminder cron.
Per-vendor timeline filters — each pro sees only their moments highlighted.
Apple Music — a second song source alongside Spotify (MusicKit).
Tasks & checklists — assignable to-dos for planners and teams.
Multi-op (Studio tier) — sub-DJs / second shooters / assistant planners with scoped permissions.
Narration — drop an ElevenLabs track into the demos (the cue engine is ready).