Weldone Events · The Team Hub — Custom Brief Artifact

The migration, side by side

Before. After.

Six paired comparisons of the operating layer Sri ran before the Custom Brief versus the system she runs now.

i.Before: Drive + WhatsApp

ii.After: Notion Team Hub

Source of truthNo canonical place. “What were the three seating chart options again?” No one could find them. Decisions disappeared into WhatsApp scroll.

Source of truthEvery couple gets a Client Room. Every decision lives there. “Check the Client Room” is the answer to every “what were the options again?” question.

Vendor coordinationVendor contacts duplicated across couple-specific Drive folders. “Did Raj quote us for that?” meant scrolling six weeks of WhatsApp.

Vendor coordinationOne shared Vendor Database across all weddings. Sixteen categories, five tier ratings (First Call · Reliable · Tested · Avoid · Untested), seven coverage regions. One bench, every couple.

Meeting cadenceCalendar invites said “Christina call” with a Zoom link. No agenda. No context for the team. Calls wandered: seating chart → itinerary → songs → back to seating chart.

Meeting cadenceEvery call uses the Meeting Template. Agenda sent 24 hrs ahead. Title format “[Couple] · [Topic]”. No more “the call.”

Decision permanenceCaptured verbally on calls, or transcription-dependent. ~13 action items per call, half of which would be lost if the AI transcript failed.

Decision permanenceDecisions captured live in the Meeting Template. The 24-hr rule: every WhatsApp decision gets copied to the Client Room within a day. Two months later you can still answer “what did Raj quote us?”

Team onboardingNew team members joining mid-engagement had zero context. Coordinators joining a call mid-way were five minutes behind every reference.

Team onboardingRead one page (the Client Room) and you’re caught up. Every locked decision, every open item, every vendor, surfaced on one screen. Five-minute onboarding for a new coordinator.

Day-of executionSri ran the timeline from memory + a printed sheet. Vendor arrival times in WhatsApp threads. “Raj will call back about linen pricing.” If no one logged it, it disappeared.

Day-of executionCall Mode page surfaces all 5 databases on one screen, used live during day-of execution. Critical lockstones (Baraat 9:00 AM · Telugu rituals 10:00 · 2:30 PM hard end) pinned and visible to the whole team.

Click a subsystem to load its working brief

Six subsystems: one operating layer.

Each subsystem ships as a Notion database or page pattern. Together they replace the scattered Drive + WhatsApp + voice-call combination Weldone used to operate on.

Subsystem 01 · Vendors

One shared vendor bench.

Before the Hub, vendor contacts were duplicated across couple-specific Drive folders. The same florist might be in three different formats across three weddings — with three different versions of Sri’s notes about their reliability.

The Notion Vendor Database is the single bench. One vendor, one record, all weddings. When Sri marks someone First Call, every coordinator on every wedding sees that rating.

Schema · 16 columns + 5 tiers + 7 regions

Vendor Name · Category (16 values, emoji-tagged) · Sri’s Tier · Coverage · Specialty · Pricing Band · Preferred Rate · Status · Phone · Email · Website · Instagram · Backup Contact · Last Used · Notes

Sri’s tier ladder

🥇 First Call — Sri’s go-to. Use without checking. Already proven.
🥈 Reliable — Used twice or more without issue. Default to.
🥉 Tested — Used once. Watch on the next booking.
⚠️ Avoid — Don’t book. Notes explain why.
❓ Untested — In the database, not yet booked.

Sample rows · anonymized

[Catering · NJ/NY/CT] · 🥇 First Call · Telugu / South Indian, scales 30–5,000 guests.
[Pandit · NJ/NY/CT] · 🥇 First Call · Traditional Telugu ceremonies. Used across 4 South Indian weddings, 2025–2026.
[Hair & Makeup · NJ/NY] · 🥇 First Call · Mother-of-Groom & Sister-of-Groom makeup specialty.

Subsystem 02 · Client Rooms

One page per couple.

Every couple gets a single Notion page that holds every open decision, every vendor quote, every deadline, every locked rock. The Client Room is the canonical answer to every “what were the options again?” question.

When a team member joins mid-engagement — Sharon or Lavanya on a Thursday call — they read one page and they’re caught up. No five-minute briefing. No catching up over WhatsApp.

The Client Room rule

Every open decision, every vendor quote, every deadline lives on one page. When a client asks “what were the options again?” the answer is always: check the Client Room.

Five databases inside each Client Room

👥 Vendors & Contacts · per-wedding view of the shared bench, scoped to this couple.
📅 Schedule (Itinerary) · full day-of timeline — every event, every vendor arrival, sorted chronologically.
📋 Open Items · action list with the 💌 For You — Cards view for the couple.
💰 Budget & Payments · quote tracker, payment status, add-on alerts.
🔑 Locked Decisions · the foundation. Couple-visible toggle.

Sample wedding hub · live counts

11 vendors in the per-couple view (filtered from the shared bench).
12 schedule events from 5:00 AM bridal makeup to 2:30 PM hard end.
13 locked decisions. 12 open items. 13 budget line items.

Subsystem 03 · Meetings

The 5-field template.

The Christina & Michael call had no published agenda, so it wandered: seating chart → itinerary → songs → linens → menu → back to seating chart. ~13 action items, captured only because Notion AI transcribed the call.

Every meeting now uses one template with five fields. The agenda goes out 24 hours ahead. Decisions get captured live, not retroactively. Transcription is a backup, not a system.

The 24-hour rule

Every decision in WhatsApp gets copied into the Client Room within 24 hours. The discipline is small; the payoff is that two months later you can still answer “what did Raj quote us?”

The five fields, every call

Agenda — sent 24 hrs ahead. Lets the client prep (“bring the song list”).
Attendees — confirmed in advance. No “oh Sharon’s joining” surprises in the first five minutes.
Decisions — captured live. You leave the call knowing what was chosen.
Action items — owner + due date. Nothing is “someone will follow up.”
Next call date — locked before hanging up. No chasing schedules over WhatsApp.

Calendar invite format

Title: [Couple Name] – [Meeting Type] – [Event Date]
Description holds the Client Room link + the agenda.
Zoom link in the invite, not in WhatsApp. Clients can’t lose it.

Subsystem 04 · Locked Decisions

The foundation database.

Every couple’s hub navigation reads: “🔑 Locked Decisions — 13 confirmed decisions — your foundation.” Once a decision lands here, it’s locked. Anyone on the team can see it. The couple can see it (or not — toggle per row).

This is what kills the “wait, we changed that to gold chain only, right?” question. The answer is in the database, with a date stamp and a category tag.

Schema · 7 fields

Decision (title) · Category (Date / Venue / Theme / Vendor / Logistics / Other) · Couple Visible (checkbox) · Date Locked · Detail · Notes · Source

Sample locked decisions · one wedding

The Marigold · Sunday June 7 · Baraat 9:00 AM
Two priests for cross-cultural ceremony — Telugu specialist + Marathi specialist
Mangalsutra: gold chain only — no other elements. Notes: “Exactly as bride asked.”
Live sax throughout ceremony — solo musician
Breakfast for 200 + wedding lunch for 400 — South Indian caterer locked
DJ + MC pair locked for reception

Across all 7 weddings

Arvind & Connor: 17 locked decisions.
Akaash & Sharanya: 16 locked decisions.
Anjali & Ram: 14 locked decisions.
Kalyan & Nikki: 10 locked decisions (T-3 months out).

Subsystem 05 · Team Access

Five named roles. One system.

The Hub is not a solo-founder tool. It is a multi-user operations system with explicit roles and permissioned views. Each team member has a defined responsibility on each wedding — lead, coordinator, technical, on-site, RevOps.

Each wedding hub has a “🚩 Flags for Swetha” callout pinned at the top — explicitly internal, instruction reads “resolve and delete this section when done.”

The team-only convention

Clients see a client-facing view. The 🛠️ Team workspace (internal only) collapsed section is team-only. Meeting Log is restricted — do not invite the couple to that page.

Access architecture

Clients · Can Comment on the Client Room. Can Edit on the “Quick Q for the Team” section.
Coordinators · Edit access to all subsystems except RevOps command center.
Founder · Sri · Owner access. Vision, vendor relationships, cultural direction.
RevOps · Ishaan · Edit + private command center. Backend systems, automations.
External partners (Vijaya for travel/MOU) · not internal edit — MOU-bound visibility.

Subsystem 06 · Playbook

The living knowledge base.

The Weldone Playbook is the operating knowledge that lives outside any one wedding. Strategy. Destinations. Vendor sourcing logic. Resort relationships. Pricing models. Cultural ceremony mechanics. Marketing.

Eight sections. Each fills through Thursday calls, site visits, and back-end work with Swetha. v1.0 locked at Week 8 review.

The Playbook positioning line

Indian & fusion destination weddings — designed with intention, produced with precision, performed on the world’s most extraordinary stages.

Eight sections, eight Thursdays

i. Strategy & Positioning — niche, demand, pricing lane.
ii. Destination Profiles (8) — operational intel per destination.
iii. Vendor Network — structure of the shared bench.
iv. Resort Relationships — contact map, permit notes.
v. Pricing & Packages · private — tier figures, fee models.
vi. Client Journey — inquiry → discovery → proposal → contract → phases → post-event.
vii. Cultural Ceremony Mechanics — pandit sourcing, havan fire permits, baraat route approvals.
viii. Marketing & Content — Instagram, SEO, referral partners.

From WhatsApp scrolls
to one source of truth.

Before. After.

Six subsystems: one operating layer.

One shared vendor bench.

One page per couple.

The 5-field template.

The foundation database.

Five named roles. One system.

The living knowledge base.

Five roles. One workspace.

One pattern. Seven engagements.

Eight sibling artifacts: one engagement.

From WhatsApp scrollsto one source of truth.

Before. After.

Six subsystems: one operating layer.

One shared vendor bench.

One page per couple.

The 5-field template.

The foundation database.

Five named roles. One system.

The living knowledge base.

Five roles. One workspace.

One pattern. Seven engagements.

Eight sibling artifacts: one engagement.

From WhatsApp scrolls
to one source of truth.