How Whitney Farm Estate Runs Its Wedding Season in Notion

Client

Whitney Farm Estate

Industry

Wedding Venue

Team size

2 People

Delivery time

2 Days

Headline results

One click per couple

A full client portal (names, date, photos, messaging, vendors, documents) generated from a single click on their record.

Texts → portal threads

Couple communication moved off late-night texting into one thread per wedding, with email notifications.

No duplicate COI asks

One master certificate database shows instantly which vendors already have insurance on file this year.

The challenge

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:

  • A personal spreadsheet for booked couples, separate from the ad-driven CRM handling inquiries
  • Texts, emails, and phone calls arriving through whichever channel a couple happened to prefer
  • Contracts, guidelines, and vendor files scattered across Canva, PDFs, and Google Drive
  • Vendor certificates of insurance collected wedding by wedding, with no shared record
  • Tables, chairs, and rental inventory tracked informally, with requests arriving ad hoc

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.

The solution: the Whitney Farm Estate operating system

One Notion workspace running every wedding from first contract to final vendor sign-off.

Wedding operations

  • Wedding Master: one record per couple, fed automatically by the intake form
  • Intake form: gender-neutral “Number 1 / Number 2” fields instead of assumed roles
  • Status flow: customized from “Inquire” to “Booked” to match how Megan actually works
  • Unified dashboard: active weddings, season calendar, tasks by priority, all at a glance

The couple experience

  • One-click portals: generated from a couple’s record, complete and branded
  • Messaging thread: replacing texts; a mention triggers an email with a direct link back
  • Shared document library: inherited automatically by every new couple
  • Scoped guest access: couples can only see and edit their own page, never the source data

Notion Wedding Clients Portal

Vendors & compliance

  • Per-portal vendor table: name, email, phone, COI checkbox, filled in by the couple
  • Master COI database: fed by its own form, showing every certificate on file this year
  • No couple relation: removed at Megan’s request, since one caterer serves many weddings
  • COIs-by-vendor chart: gaps visible without opening a single wedding record

Inventory & logistics

  • Client-facing inventory sheet: tables, chairs, and rentals as couples see them
  • Requests in the portal thread: logged ahead of the wedding date, not over email
  • PDF export: an entire portal with all subpages, in one click
  • Duplicable template: copy into her own workspace, start free, upgrade with zero data loss

How it changes daily reality

  • Setting up a new couple takes a couple of clicks. Intake form to portal to document access to vendor tracking, automated end to end.
  • The 11pm text is gone. Couples write in their own portal thread; a mention sends Megan an email with a link straight back to it.
  • Repeat vendors stop getting asked twice. One glance at the COI database answers whether a certificate is already on file for the year.
  • Documents update once. A single shared library instead of the same PDF re-uploaded across three places.
  • Nothing leaks between couples. Guest permissions are scoped so a couple can only ever see and edit their own page.

Portal Messaging Thread

How we worked together

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.

  • Discovery. Mapping the season, the tools, the channels couples actually use, and the vendor compliance burden.
  • Build. Dashboard, intake automation, Wedding Master, portal template, COI tracking, inventory sheet, guest permissions.
  • Walkthrough (May 22, 2026). Megan saw the finished system for the first time and adjusted it in place.
  • Pilot. A live test on her brother’s wedding that July, logging in as a couple would, before any real client touched it.

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.

The results

🧵 From scattered to centralized

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.

📄 No more duplicate vendor asks

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.

📵 Communication moved off text

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.

🖱️ New couple setup dropped to a couple of clicks

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.

🔒 Zero cross-client risk

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.

Key takeaways

  1. Match the system to how the client already works. Changing the status from “Inquire” to “Booked” rather than asking Megan to change her intake process, kept the system feeling native to her existing workflow.
  2. Solve for the non-technical owner. Guest permissions, one-click portal creation, and a duplicate-and-upgrade path meant she didn’t need to understand Notion’s internals to trust the system.
  3. Design for repeat entities, not just repeat events. Decoupling the COI database from a single couple relation reflected the reality that vendors serve many weddings, not one.
  4. Move the client into the system, not just the team. The portal is what actually ended the texting problem, an internal-only build would not have.
  5. Right-size the plan. The whole thing runs on Notion Plus. Recommending a tier the business doesn’t need is a good way to lose a small operator.

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.

More Case Studies

Supplier Registration Form Mockup
Case Study
Chape

How Felize Botanica Scoped Its Notion System

Felize Botanica designs, installs, and maintains green walls, interior landscaping, and roof gardens across three service lines. The business already ran on a real tech stack. The problem wasn’t a missing tool. It was that the entire stack stopped at the sale.

Read More »

Let's See If We're a Fit

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.

Join Our Newsletter

No product pitches. No padding. One weekly read for serious operators.

© 2026 NotioStore. All Rights Reserved.

Discover more from Notiostore

Subscribe now to keep reading and get access to the full archive.

Continue reading