← Back

💍 A wedding

A wedding, without losing your mind.

A wedding is a big budget, a moving guest count, and a dozen vendors with deadlines — and a lot of cooks. Pango keeps the number, the list, and the calls straight so nothing's booked twice and nothing lapses.

What the AI actually builds

A real plan, kept current as you talk.

A snapshot from a Space mid-project. The artifact lives next to the chat and updates itself — no homework. Share read-only with anyone who needs to see where things stand.

📇

Vendors & deposits

1 deposit due Friday · 2 booked · 1 pending

  • Wildflower Catering

    Catering · 130 @ $145

    $18,850 total

    Booked
  • Roosevelt Hotel — ballroom

    Venue

    $3,000 deposit

    by Fri Sep 27

    Deposit due
  • Studio Linnea

    Photographer

    $4,800 total

    Paid in full
  • Verbena Florals

    Florist

    $500 deposit

    by Jun 1

    Booked
  • TBD — DJ vs band

    Music

    Pending
All deposits tracked against the timeline · the AI nudges 3 days before each due date

Sound familiar?

The budget is one spreadsheet, the guest list is another, and the vendor deposits live in someone's inbox. A parent invites twelve more people, the per-head cost jumps, and the venue deposit was due yesterday — and you find all three out separately.

Built for the whole arc

Different shape for every stage.

Each phase of a wedding has its own UX — different artifacts in play, different things the AI is watching. Not one generic chat with a kitchen-sink prompt.

  1. 1Vision + budget

    What you're building

    Style, size, vibe — captured. The budget gets set with the people paying; tradeoffs surface as real numbers, recorded with the why, so "why not the bigger venue?" has an answer six months later.

    💰 Budget cap⚖️ Decisions📍 Style notes
  2. 2Vendors + deposits

    Books straight, deposits paid

    Each vendor — venue, catering, photo, music, florist — lands with the deposit, the due date, the contact. The week-of view shows what's due, what's lapsed, who's on point.

    📇 Vendors💰 Deposits📆 Timeline
  3. 3Headcount + logistics

    The number that everyone agreed to

    Guest list lives in one place; RSVPs feed in via the link. A parent adds twelve, the per-head re-figures, the bar gets trimmed instead of an awkward call. Seating, transport, welcome bags — all sized to the real number.

    👰 Guests + RSVPs🎫 Seating🚐 Transport
  4. 4Day-of + after

    The minute-by-minute, no surprises

    The day's timeline, every vendor's contact, the backup plan. After: photos land in the Space, the thank-you list builds itself from the guest list, the receipts go to the budget for the final reconciliation.

    📋 Day-of brief📷 Photos✉️ Thank-yous

How it actually goes

The specific moments it earns its keep — not the demo video, the boring middle.

Setting the budget with the people paying

Both families in one Space, with the budget breakdown (venue, food, photos, attire, the floor) visible to everyone. The cap is the cap; tradeoffs surface as numbers, not awkward conversations.

A parent adds twelve guests

Headcount 118 → 130. The per-head total re-figures: catering +$1,740, the bar package re-evaluated, the venue deposit due Friday flagged. The cap goes red, but with a clear "trim bar to fit" option — not a vague "we'll figure it out."

Vendor quote arrives

Forward the email. The vendor lands in the vendor list with the deposit amount and the date it's due, calendared against the timeline. Compare-vs-quote-from-last-month is one tap. Nothing's booked twice.

Deposit week

The week-of view shows what's due this week, what's lapsed, who's paying. The AI nudges a couple of days early — not a panic the night before.

Six weeks out — final headcount

RSVPs roll in via the link, the headcount stabilizes, the AI ripples the final number through catering, seating, transport, the welcome bag count. The day-of timeline starts taking shape.

Day-of

One screen has every vendor's contact, the timeline minute-by-minute, who's on which logistic, the backup-rain plan. The AI surfaces "the florist hasn't checked in yet" before it's 4pm.

What you get

A budget that moves with the headcount

Guest count changes and the per-head total, the catering line, and what's left re-figure — not a spreadsheet you re-do at midnight.

Vendors and deposits, before they lapse

Each vendor, the deposit, the date it's due — tracked against the timeline so nothing's booked twice or missed.

The calls, kept across both families

Who's invited, what's the budget, which vendor — decided and recorded, so a parent's "just add a few" doesn't quietly blow it.

💰 Budget👰 Guest list📇 Vendors & deposits⚖️ Decisions
vs. a basic AI chat

You could ask ChatGPT. Here's what it can't do.

A basic AI chat
  • Hands you a generic wedding checklist with no budget and no idea of your real guest list.
  • Can't track which vendor's deposit is due Friday — that lives in someone's inbox.
  • Doesn't know what the group already agreed.
Pango
  • Keeps a live budget that re-figures the second a parent adds twelve guests.
  • Tracks every vendor, deposit, and due date against the timeline so nothing lapses.
  • Records the calls — the cap, the cuts, the vendor — so "just add a few" doesn't quietly blow it.

Out of the group chat. Into one place.

Free to start, on web and iOS. Your people in a minute.