JM
Just Marry!
Claude Guide
Checking authentication…
✦ Just Marry! Suite 🏠 Hub Dashboard Team Manual Claude Guide
JM
Claude Guide
What Claude already knows about Just Marry!

Claude has memory. Susan has worked with Claude extensively to build context about Just Marry! — so when you open a conversation, Claude already knows a lot. You don't need to explain who we are. You can just get to work.

Claude already knows this

What Claude knows about JM

  • Just Marry! is based in Orlando, founded 1992 by Susan Southerland
  • We coordinate ~300 weddings/year including Disney and luxury resorts
  • Woman-owned, Knot Hall of Fame, featured on TLC, People, Wall Street Journal
  • The Suite tools — Dashboard, Manual Index, BEO Tool, Timeline Extractor
  • Team member names and roles (ER, SL, JP, DS, EM, KM, NW, Mairead, Danielle, Ellis)
  • Internal terms: ECS, COI, BEO, TG, turnover workflow
  • JM brand voice, colors, and design system
⚠️
Claude does NOT know this automatically

What you still need to provide

  • Specific couple names, wedding dates, venues for a current wedding
  • The content of documents (BEOs, timelines, vendor emails) — paste or upload them
  • Anything that happened in a past conversation — Claude's memory is a summary, not a transcript
  • Your personal preferences if they differ from JM defaults
  • Real-time info: current vendor pricing, updated timelines, today's news
🔒
Confidentiality — important

What NOT to paste into Claude

  • Full names + addresses of couples together (use first names only)
  • Credit card numbers, bank details, or payment info
  • Passwords or API keys
  • Sensitive medical or personal information about clients
  • Anything marked confidential by a venue or vendor

When in doubt: use "the couple" or first names only. Claude doesn't need full personal details to do great work.

💡
How to get the best results

Tips for using Claude effectively

  • Be direct. "Write a vendor follow-up email for a missing COI" works better than "Can you help me with something?"
  • Upload documents. Claude reads PDFs natively — drag them right in.
  • Say what tone you want. "Keep it warm but firm" or "make this more concise."
  • Iterate. If the first draft isn't right, say what to fix. Claude doesn't mind.
  • Ask Claude to check its own work. "Does anything look off?" often catches errors.
Ground rules
🚫

Never share API keys, passwords, or financial credentials

This applies to Claude.ai conversations and any other chat tool. If you're ever asked to paste a key or password into a chat, stop and contact Susan.

👁️

Claude.ai conversations are not stored by JM

Anthropic processes your conversations to run the service. Don't paste anything into Claude.ai that you wouldn't want processed by a third-party AI provider. Use first names only for couples.

Always review before sending to a client or vendor

Claude produces excellent drafts, but it doesn't know everything. Read every email, proposal, or document before it leaves your hands. You're responsible for what you send.

📋

Floral proposals: always mark DRAFT and send to your Event Manager first

The floral proposal workflow produces a ready-looking PDF — but it goes to the EM for review before it ever reaches the couple. Mark it DRAFT until it's approved.

All prompts assume Claude already knows Just Marry! — no setup needed. Fill in the highlighted fields and go.

💌

Client Emails & Communication

6 prompts
First contact / inquiry response
Write a warm first-contact reply to a couple who just inquired about our wedding coordination services. Couple's names: [names] Wedding date: [date or "TBD"] Venue: [venue or "not yet chosen"] What they said in their inquiry: [paste or summarize] Keep it warm, confident, and personal. End with a clear next step.
Check-in / planning update
Write a friendly planning check-in email to a couple. Couple: [names] Wedding date: [date] What we need from them: [e.g. vendor selections, final guest count, timeline review] Tone: [casual / professional]
Difficult client — setting expectations
Help me write a professional but firm email to a couple who is [describe the situation — e.g. making last-minute changes, requesting something outside our scope, being unresponsive]. I want to: [e.g. reset expectations, push back on a request, re-establish the timeline] Keep it warm but clear. Don't apologize for our policies.
Bad news / unexpected issue
Write an email delivering difficult news to a couple. The situation: [describe the issue — e.g. vendor cancellation, venue change, weather backup plan needed] What we're doing about it: [describe our plan or next steps] Be honest, calm, and solution-focused. Don't catastrophize or over-apologize.
Post-wedding thank you
Write a post-wedding thank-you email to a couple. Couple: [names] Wedding date & venue: [details] A specific moment or detail to mention: [something memorable — optional] Warm, genuine, not template-y. Mention leaving a review naturally without being pushy.
Rewrite / improve a draft I've already written
Please improve this email draft. Make it sound more like Just Marry!'s voice — warm, professional, and confident. [paste your draft here] Specifically: [e.g. make it shorter / warmer / more direct / fix the tone]
📋

Vendor & COI

4 prompts
COI request email to a vendor
Write a COI request email to a vendor. Vendor type: [e.g. florist, photographer, DJ] Vendor name: [name] Venue requiring the COI: [venue name] Wedding date: [date] Keep it professional and specific. Include what the COI needs to show.
Vendor follow-up (no response)
Write a follow-up email to a vendor who hasn't responded. Vendor: [name and type] What we need: [COI / contract / confirmation / pricing] How long since we first reached out: [timeframe] How urgent this is: [low / medium / urgent — wedding is in X days]
Summarize a vendor contract or BEO
Please read this document and give me a plain-language summary: 1. What is the vendor committing to provide, and when 2. Any minimums, deadlines, or payment commitments 3. Cancellation or change policy 4. Anything I should flag or confirm before the event [paste the document or upload the PDF]
Compare two vendor proposals
I'm uploading two vendor proposals for the same wedding. Please compare them: 1. Side-by-side table of matching items (original prices, before any markup) 2. Items in one proposal but missing from the other 3. Grand total comparison 4. Plain-language summary of the key differences 5. Your overall read on which appears more complete [upload both PDFs together]
⏱️

Timelines & BEOs

4 prompts
Extract timeline items from a document
Please read this wedding timeline and extract every item in chronological order. Format as a clean list: Time | Item | Who's responsible (if mentioned). Flag anything that seems incomplete, conflicting, or missing a responsible party. [paste timeline or upload PDF]
Compare BEO to timeline — find discrepancies
Compare this BEO against this timeline. Tell me: 1. Everything in the BEO that's missing from the timeline (ADD) 2. Anything that conflicts between the two documents (FIX) 3. Critical issues that need confirmation before the wedding (FLAG) 4. Items that match and are confirmed (NOTE) Be thorough — check every time, count, room, vendor name, and setup instruction. [upload timeline PDF and BEO PDF together]
Build a day-of cheat sheet from a timeline
From this timeline, extract only what I need on the day: key vendor arrivals, ceremony start, major transitions, and anything I need to personally initiate. Format as a compact list I can glance at quickly. [paste or upload full timeline]
Emergency coverage — get up to speed fast
I'm stepping in last-minute to cover a wedding for another coordinator. Here are the notes and timeline: [paste notes and timeline] Give me: 1. The 5 most critical things I need to know before I arrive 2. Any red flags or potential issues in these notes 3. Questions I should try to get answered before the event
🌸

Floral Proposals — Markup & Rebrand

4 prompts
How this works — read first

Claude can take a florist's PDF and produce a finished, client-ready branded proposal in one session. Upload the florist's PDF and the JM logo, run the Power Prompt, review the output, download the PDF. Always mark the result DRAFT and send to your Event Manager before it goes to the couple. Use the step-by-step prompts if the power prompt needs corrections.

Step 1 — Read the PDF and show me all prices first
Use this before making any changes to confirm Claude read the PDF correctly.
I'm uploading a florist's proposal PDF. Before we change anything: 1. List every line item in a table: Item | Qty | Unit Price | Line Total 2. Note the florist's grand total as shown 3. List every page and describe what's on it 4. Flag any pages that are legal/contract/T&C — don't remove them yet Don't make any changes — just show me what you're working with. [upload the florist's PDF]
Step 2 — Apply markup and confirm math
Run this after Step 1 to verify all pricing before rebuilding the PDF.
Using the line items you just extracted, apply Just Marry!'s markup. Margin: [30% ÷0.70 or 40% ÷0.60] Formula: sell price = floor(florist price ÷ [0.70 or 0.60]) Floor every result to the nearest whole dollar — never round up. $0 items stay $0. Show me a new table with: Item | Florist Price | JM Price | Difference Then show the new subtotal and confirm it against the florist's original. Don't rebuild the PDF yet — I want to verify the numbers first.
Step 3 — Rebuild PDF after approving the numbers
Run this after confirming pricing in Step 2.
The pricing looks correct. Now rebuild the PDF using those approved numbers. - Single HTML file + WeasyPrint - Use EB Garamond + Poppins fonts - Replace florist branding with JM logo on every interior page - Remove all T&C and legal pages - Keep all product photos, swatches, and item descriptions verbatim - Footer: "[Coordinator Name] | Page X of Y" on every page - Grand Total in JM mauve (#A35A60) Show me page previews before delivering the final file. Once I approve, copy to outputs.
📝

Admin & Notes

3 prompts
Meeting or call recap
Turn these notes into a clean meeting recap. [paste your rough notes] Format: Date + attendees at top, then bullet points by topic, then a clear "Next steps" section with owner and deadline for each item.
Write or improve an SOP / process doc
Write a clear step-by-step SOP for this process: Process name: [name] Who does this: [role] What it covers: [describe the process or paste existing rough notes] Anything that trips people up: [common mistakes or edge cases — optional]
Proofread and polish a document
Please proofread this and fix any grammar, spelling, or awkward phrasing. Keep the meaning exactly the same — don't rewrite it, just clean it up. [paste document]
💍

Day-of Support

3 prompts
Quick problem-solving on the day
I'm at a wedding right now and need a fast answer. The situation: [describe what's happening] What I need: [a decision / a script to say to someone / a quick plan] Time I have: [e.g. 2 minutes / right now] Be direct. Give me the action first, explanation second.
What to say in a difficult moment
Give me a script for what to say to [person — e.g. an upset family member / a late vendor / a panicked bride]. The situation: [describe briefly] My goal: [calm them down / redirect them / set a boundary / get them moving] Keep it short — I need to say this in the next few minutes.
Post-event debrief notes
Help me write a post-event debrief from these rough notes. [paste your notes] Format: what went well, what to improve, vendor notes (good or bad), anything to flag for the next team handling this couple or venue.
Brand Identity

Brand Essence

"Calm confidence that makes magic feel effortless."

Couples hire us because they want to be fully present on the most important day of their lives. We handle everything. They enjoy the day.

Our Voice

  • Warm and genuine — never stiff or corporate
  • Celebratory and joyful, but grounded and reassuring
  • Expert without being intimidating
  • Like a trusted friend who knows everything about weddings

Avoid these words

seamless experience · vendor (use "team" or name them) · client (use "couple" or "you") · synergy · leverage · solutions

Colors

Mauve
#A35A60
Mauve Dark
#8B4A50
Cream
#FAF8F6
Text
#2C1F20
Pale Mauve
#F5ECED

Mauve is the primary brand color. Cream is the background. Text dark for all body copy. Pale mauve for subtle highlights and backgrounds.

Typography

Cormorant Garamond
Headlines, titles, brand statements — elegant serif
DM Sans
Body copy, buttons, UI labels — clean sans-serif

Cormorant for anything that should feel luxurious or emotional. DM Sans for everything functional and readable.

Credentials & Proof Points

📺Featured on TLC
📰Featured in People Magazine
📰Featured in Wall Street Journal
🏆Knot Hall of Fame member
📅In business since 1992
💍~300 weddings per year
🏰Disney & luxury resort specialists
👩‍💼Woman-owned small business
Pioneered all-inclusive wedding packages in Orlando

What couples say about us

"These are the words real couples use. Use them as inspiration — not as copy to reproduce."

  • Peace, presence, and magic
  • Anticipated our needs before we voiced them
  • If issues came up, I was never aware of them
  • Holding our hand through every step
  • Calm, capable, kind
  • Didn't miss a beat
  • I didn't have to worry about anything
Social Media Prompts
Instagram & TikTok

Always paste the Brand Voice prompt first in a new session, then add whichever prompt you need.

Content Ideas — plan a week of posts
[Paste Brand Voice prompt first, then:] Give me [number] Instagram/TikTok content ideas. Context: [what's happening — upcoming weddings, season, a recent moment, a feeling you want to convey] For each idea: 1. The concept (what it's really about emotionally) 2. What to film or photograph 3. A caption draft in Just Marry!'s voice 4. 4–5 hashtags Make each one feel specific to Just Marry! — not generic wedding content.
Single Post — caption for a specific moment
[Paste Brand Voice prompt first, then:] Write a caption for this post: Platform: [Instagram / TikTok / both] What's happening: [describe the photo or video specifically] Feeling I want couples to have: [e.g. "they'll handle anything" / "I want this for my wedding"] Anything to mention: [venue, coordinator name, a detail — or leave blank] Write 2 versions: — Short: punchy, 3–4 lines, stops the scroll — Story: 6–8 lines, more narrative Include hashtags at the end of each.
Review Response — respond in JM's voice
[Paste Brand Voice prompt first, then:] Write a response to this review: "[paste the review]" Coordinator mentioned: [name or leave blank] Venue mentioned: [venue or leave blank] Guidelines: — Warm and personal, not a template — Reference one specific detail from the review — 3–5 sentences — End by celebrating the couple, not the company
PR & Press Prompts
Press pitch — media outlet
[Paste Brand Voice prompt first, then:] Write a press pitch for Just Marry! to send to [publication or journalist name/type]. The story angle: [what makes this newsworthy — e.g. Disney wedding trend, 30+ years in business, a unique couple story] What we're hoping for: [feature / quote inclusion / roundup mention] Keep it under 200 words. Lead with the story, not our credentials.
Award nomination write-up
[Paste Brand Voice prompt first, then:] Write an award nomination for Just Marry! for the [award name]. Category: [category] What to highlight: [specific achievements, milestones, or moments that stand out this year] Word limit: [if known] Lead with impact. Use specific numbers and examples where possible.
Bio or About Us copy
[Paste Brand Voice prompt first, then:] Write a [short / medium / long] bio for [Susan Southerland / Just Marry! / a specific coordinator]. For: [where it will be used — e.g. website, speaking event, industry profile, award submission] Tone: [authoritative / warm / conversational] Anything specific to include: [optional — milestones, personal details, credentials]
Speaking proposal / conference submission
[Paste Brand Voice prompt first, then:] Write a speaking proposal for Susan Southerland to submit to [conference or event name]. Proposed topic: [topic or angle] Audience: [who attends this conference] Key takeaways for the audience: [what they'll learn] Format: [keynote / panel / workshop / session length if known]