Claude to track wedding contracts and drafts

Brit created a separate email address for wedding planning, then gave Claude access to that focused inbox. Quotes, contracts, payment terms and timeline decisions were scattered across messages and attachments, making it difficult to answer basic questions without another search.

Claude could retrieve what remained to pay for catering, identify overdue tasks and find what the photographer had said about timing. The workflow then moved from questions to draft replies. Claude prepared messages using previous decisions and open issues, while Brit reviewed the drafts and clicked send. It also surfaced a forgotten hair-and-makeup deposit.

Using Claude Code, she brought the inbox, contract folder and timeline document into a shared wedding-planning system hosted on Vercel. It displayed vendor status, current menu approvals, tasks and payments extracted from contracts. A script runs every Sunday at nine to scan new emails and update those records.

The agent's output supports coordination, while the couple still makes the wedding's design decisions. Brit describes creative visualization as helpful but keeps taste and tradeoffs with herself. The source does not report the wedding as completed, verify bank payments or show that contract interpretation was independently checked. The concrete result is a current planning hub and reviewed email workflow, rather than autonomous vendor selection or payment.

Prompt
Original prompt

Source: britbiddle.substack.com · Brit