Episode 20
The Couple Portal: Stop Being the Google Doc Middleman
Give couples a place to work so you stop being the human API between two inboxes and a spreadsheet.
Listen on SpotifyAbout this episode
Midnights spent forwarding vow drafts and seating spreadsheets are optional. In this episode of Wedding Studio by You Had Me At I Do, Mike and Jen explain what couples should own, what you approve, how async collaboration works, vow privacy, and when to lock for day-of. Brought to you by Studio — Couple portal and Vow Workshop.
Based on
The Couple Portal: Stop Being the Google Doc Middleman at Midnight
Show notes
Mike and Jen on ending the Google Doc middleman pattern with a real couple portal workflow.
Ownership
- Couples own: story details, contacts, draft preferences, private vows.
- You approve: final script structure, procession, seating publish, day-of package.
Async without chaos
- They work on their time; you review on yours.
- Vow Workshop keeps partners from spoiling each other while still matching length.
- Lock before day-of so the altar tablet matches the approved plan.
Tips & suggestions
- Define couple-owned fields vs officiant-approved fields early.
- Keep vows private between partners until they choose otherwise.
- Batch your review windows — do not live in notifications.
- Lock the ceremony package before you leave for the venue.
- Callback to refine-not-replace for AI polish inside vows.
- Publish procession/seating only after your approval pass.
Couple portal
Vow Workshop
Async collaboration
Day-of lock