Whitney Farm Estate
Wedding Venue
2 People
2 Days
A full client portal (names, date, photos, messaging, vendors, documents) generated from a single click on their record.
Couple communication moved off late-night texting into one thread per wedding, with email notifications.
One master certificate database shows instantly which vendors already have insurance on file this year.
Whitney Farm Estate runs a full wedding season from spring thaw through fall, and Megan Woonton was managing all of it herself (inquiries, couples, vendors, documents, and inventory) across a patchwork of disconnected tools.
The day-to-day was running on tools that never talked to each other:
The symptoms were exactly what you would expect from a fragmented stack.
Updating a single PDF meant re-uploading it everywhere it lived. And because certificates of insurance were collected per wedding rather than per vendor, a repeat caterer could be asked for the same paperwork two or three times in one season, a small indignity that quietly costs goodwill with the vendors a venue depends on.
The deeper constraint was that all of the translation between tools happened inside one person’s head. As a self-described non-technical owner, Megan was the integration layer.
One Notion workspace running every wedding from first contract to final vendor sign-off.
Wedding operations
The couple experience
Vendors & compliance
Inventory & logistics
The build was shaped in the walkthrough itself. Megan corrected the system live, renaming statuses to match her real intake flow, and asking for the couple relation to be pulled out of the COI database because a caterer serves many weddings, not one. Both changes came from her, not from the architecture.
The client’s verdict on the experience:
This is really cool. It's just like a lot more than I expected. I think this is perfect. I love it.
Inquiries, bookings, vendors, documents, and inventory now live in one connected system instead of a spreadsheet plus several disconnected apps.
I used to keep half my brides in my head and half in a spreadsheet. Now I just open one couple's portal and everything about their wedding is right there.
The master COI database lets Megan instantly check whether a returning vendor already has a certificate on file for the year.
I asked the same caterer for the same insurance paperwork three times last year without realizing it. That doesn't happen to me anymore.
Each couple has a dedicated portal thread directly addressing her most persistent frustration.
The best part isn't even the portal, it's my phone. Nobody texts me at 11pm asking about chairs anymore. They just leave it in their portal and I answer it with my coffee.
Portal creation, document access, and vendor tracking are automated from the intake form onward.
My brother's wedding was the test, and honestly, it felt like cheating, I clicked one button and his whole portal just existed.
Guest permissions are scoped so couples can only ever see and edit their own portal page.
I'm not a tech person. I didn't think a system built for me could actually feel like it was built for me, but this one does.
Running a wedding or event venue out of a spreadsheet and your own inbox?
If your couples can’t see their own wedding details without texting you, let’s talk.
A pile of tasks isn’t task management. Real task management is knowing, at any moment, what to do next, and that takes more than a list. This is a step-by-step tutorial for using Notion for task management.
Entrepreneurs can replace expensive tools with Notion by consolidating the overlapping ones, notes, docs, projects, wiki, simple CRM, into a single subscription, while keeping only the specialized tools that genuinely earn their price.
New to Notion? Discover the most common beginner mistakes and how to avoid them so you can build a smarter, simpler, and stress-free Notion system.
No pitch deck. No obligation. 30 minutes to understand your business and tell you honestly what I think, including if I’m not the right fit.
Built for the businesses that build everything else.
No product pitches. No padding. One weekly read for serious operators.