Event & Wedding Kit
Fill in one Event Profile — type, date, city, venue, headcount, budget, culture, and the vibe — then run the six prompts in order. They interlock on purpose: your guest count feeds the budget, your budget and vendors feed the timeline and the backup plan, so $5 buys one plan tuned to your real date, city, budget and rituals, not six disconnected answers. It's built for the hardest case — the Indian multi-event wedding (haldi, sangeet, ceremony, reception) — and scales down cleanly to a birthday, a corporate event, or a Western wedding, in ₹, R$, or $. Claude helps you plan and draft: it can't book venues, pay deposits, message vendors, or set reminders — you do all of that yourself, so double-check every total and every date before you act on it. Think of it as a very organised planning partner, not a wedding planner or a legal contract.
What you'll be able to do
Fill in your event details once, then get a tiered guest list, a budget that adds up to your total, a minute-by-minute run-of-show, ready-to-send vendor messages, your full invitation suite, and a rain-or-shine backup plan — all tuned to your date, city, budget, and rituals.
Start here — the headcount this produces feeds every other prompt in the kit. Paste your names however messy, tell it the most guests your venue and budget allow, and it de-duplicates, tiers, and tracks everyone as one row per person while defusing the family politics.
Example · Input
About 260 names across both families for a wedding, pasted grouped by side; venue ceiling 180; per-plate ₹1,400.
Example · Output
A paste-ready guest tracker (Name | Side/Group | Tier A/B/C | Events invited to | Plus-one Y/N | Est. attending | RSVP status | Dietary/notes | Contact), a tier summary with running headcount, a 'does this fit?' over/under number, a per-side quota plus a family-politics script, and a cut-off date with an RSVP timeline.
Buy once. Copy every prompt whenever you need it.
Building a bundle? Add more packs and save up to 15%.
Run after the guest list so you're working from a real headcount. Give it either your total to divide up or your guests-and-venue to price out, and it returns a line-item budget that sums exactly to your total, contingency included, sanity-checked against what things cost in your city.
Example · Input
Total ₹15,00,000 for 180 guests across 4 functions in Jaipur, Hindu wedding — allocate it.
Example · Output
A budget table (Category | % of total | Amount | Notes/assumption | Status) that sums to your total with contingency as its own line, a per-event sub-breakdown, a reality-check on your implied per-plate vs local rates with 2–3 levers if it doesn't fit, and a 'what to lock first' order.
Use once you know your venue hours and vendors. Give it your access window, the fixed anchor moment (muhurat, cake cut), and your rituals, and it builds a printable, sendable schedule with buffers and a named owner for every block — so you're not the one running the day. If your vendors aren't booked yet, run “Draft Vendor Messages” first so you have their real arrival times.
Example · Input
Venue 4pm–11pm, phere muhurat 9:12pm, baraat → varmala → phere → vidaai; photographer, caterer, DJ, décor.
Example · Output
A time-blocked schedule (Time | Duration | What's happening | Location | Point person | Vendors | Notes) from load-in to send-off, buffer rows, 'no later than' flags on fixed moments, a vendor call-sheet with a 'who to call' strip, and — for multi-day — a master overview plus per-function sheets.
Use whenever you need to contact, compare, or negotiate with a vendor. Tell it the category, the stage you need, and your budget line, and it writes ready-to-send messages filled with your real details — WhatsApp and email versions — plus the exact questions to ask that vendor.
Example · Input
Photographer — want inquiry + quote request + negotiation; budget ₹1,50,000 for photo & video; WhatsApp + email.
Example · Output
Ready-to-send messages for each stage, a question checklist tailored to that vendor (photographer: hours, shooters, deliverables, delivery timeline, raw files, travel), a quote-comparison table (Vendor | Price | Included | Extra | Deposit/terms | Notes), and a 'before you pay' red-flag list.
Use once names, dates, and venues are fixed. Give it the details exactly as they should appear plus your RSVP channel, and it writes the save-the-date, the main invite in a few tones, per-event cards, and RSVP wording — in the correct words for your culture, with working RSVP mechanics.
Example · Input
Hindu wedding, both families hosting; mehndi/sangeet/ceremony/reception with times and venues; RSVP via WhatsApp by 20 Jan; warm tone.
Example · Output
Labelled paste-ready blocks: a no-RSVP save-the-date, 2–3 tone variants of the main invitation with the correct invocation and host line, a card per function with its dress code, an RSVP block with deadline and an events checklist, and a short 'what goes where' note.
Run last, once your vendors and people are known. Tell it your venue, season, and day-of decision-maker, and it turns the things that could actually go wrong into if-then rules with named owners and deadlines, plus a physical emergency kit tailored to your event.
Example · Input
Outdoor farmhouse, Mumbai August (monsoon), coordinator Priya, final call = groom's brother, caterer buffer TBD.
Example · Output
A risk table (Scenario | Likelihood for this event | Trigger threshold | If-then action | Owner | Decision deadline), a weather Plan-B with a rain-call deadline and notification method, a backup-vendor contact list to fill now, a printable emergency-kit checklist, and a 'who's in charge' strip.