Wedding planning help, set in plain English.

Sign up with an email and password, or with Google. Then enter the wedding name, date, and a rough budget if you have one. The first workspace is yours — your partner or planner can be invited later from Settings.

Yes. The Help button inside the app re-opens the guided tour anytime. We built it because we noticed couples wanted a refresher after stepping away for a few weeks, not just on day one.

Add three or four broad budget categories — venue, catering, flowers, photography — even if you don't have numbers yet. Those buckets give every other surface (vendors, payments, exports) somewhere to attach.

In Google Sheets, choose File, then Download, then Comma Separated Values. In Excel, choose Save As and pick CSV UTF-8. Numbers exports CSV from the File menu under Export To. The file lands in your Downloads folder.

Name, side, group, RSVP status, and dietary notes. The importer is forgiving — extra columns are ignored, and you can map your column names to ours during the import step. Nothing is committed until you confirm the preview.

The preview shows duplicates side by side so you can decide which rows to keep before anything saves. We built this because spreadsheets accumulate trailing whitespace and accidental duplicate rows over months of edits.

Vendors yes, budget rows not yet. Vendor import is on the same Import menu. Budget rows are typed in directly because the schema (deposit, balance, due date) is too specific to map cleanly from a generic spreadsheet.

Yes — add the plus-one as their own row, linked to the host guest under the household. The seating chart needs every person counted individually, but the RSVP link still goes to the household.

Each household gets a unique link tied to its guests. When the household opens the link they see only their own names, can confirm or decline per person, and the responses flow back into the guest ledger automatically.

Don't. The link encodes which guests it represents — sharing one link across households means responses overwrite each other. Use the bulk send tool to mail unique links to every household at once.

They can re-open the same link and update their answer until the deadline you set. Every change is timestamped in the activity log so you can see who flipped from yes to no and when.

Filter the guest list by RSVP status equals pending. The bulk action menu can re-send the same link to the filtered set, or you can copy the chase list to a CSV for a manual phone round.

A budget row is a planned amount inside a category — like $4,000 for flowers. A vendor is a real company you're tracking — Acme Florals, with a quote, a deposit, and a contract. The vendor links to the budget row so totals reconcile.

Each vendor row tracks the quoted amount, the deposit you've paid, and the balance remaining. Category totals roll up automatically — the moment the florist deposit clears, the floral category subtotal updates without a formula edit.

Yes. Add each vendor with status set to Shortlisted or In Negotiation. The category total only counts vendors marked Booked, so shortlists don't pollute your running spend.

No. There's no marketplace, no paid placements, no affiliate kickbacks. Every vendor in your workspace is one you typed in yourself. We built it this way because the existing platforms quietly steer your shortlist toward whoever paid for visibility.

Wait until at least half your RSVPs are in. Building tables before that means re-arranging every time a Yes turns into a No. The chart pulls confirmed guests automatically, so the work compounds late.

Round, rectangular, and a separate head-table shape. Each table has a configurable seat count and an optional name (Family, College Friends) so the inspector panel can summarize who's where.

Yes — save a draft layout, branch a copy, and compare. Useful when you're trying out a family-only configuration versus a mixed table approach without losing the original.

The seat opens automatically and the inspector flags the table as under-allocated. Drag a replacement in from the unseated rail; nothing else has to change.

No. The draft is saved to your workspace only. The live website only updates when you press Publish. We built it this way because half-edited venue paragraphs shouldn't ship by accident.

Yes, on the Pro and Lifetime plans. Point your domain's DNS at the Kaiplan endpoint shown in Settings, then verify. The shorter kaiplan.app/w/your-slug URL keeps working too.

Each household RSVP link lives at /w/your-slug/rsvp/HOUSEHOLD-CODE. The website itself is public; the RSVP path is private per household so only invited guests can respond.

Toggle Unpublish in Settings. The page returns a polite archive notice. The data stays in your workspace — you can re-publish or export anytime, and Lifetime accounts keep everything indefinitely.

Open Settings, then Billing. Manage Plan launches a Stripe customer portal in a new tab where you can upgrade, downgrade, or cancel. Cancellation takes effect at the end of the current billing period.

Exports download as CSV files to your browser's default Downloads folder. The export menu lives on every list page — guests, vendors, budget — and we generate the file shape the most common downstream tool (caterer's spreadsheet, accountant's ledger) expects.

Don't share the password. Invite them as an Editor from Settings, then they sign in with their own email. The activity log records who changed what, which matters when two people are editing the same vendor row at the same time.

Nothing, until you tell us otherwise. Archive the workspace from Settings to lock it read-only. Lifetime accounts keep everything indefinitely; subscription accounts can export full CSV backups before the subscription ends.

Connections are encrypted in transit. Passwords are hashed; we never store them in clear text. Sessions expire on inactivity. We don't sell your data, ever — the business model is you paying us, not advertisers paying us for access to your wedding details.