Case Study
Case Study: Wedding Planner CRM & Client Automation
We built a connected set of automations for a small wedding and event planning studio: one CRM pipeline for every inquiry, an AI assistant that drafts personal replies in minutes, contracts and payment schedules that chase themselves, vendor confirmations and change notices, and RSVP collection with clean counts for caterers. The planners now spend their evenings on clients and design rather than admin, and every decision about pricing, vendors and the day stays with them.
- Business type
- Wedding and event planning studio, full planning and day-of coordination
- Team involved
- Lead planner and owner, associate planner, coordinator
- Systems connected
- Planning platform, website form, Gmail, DocuSign, Stripe, Google Sheets, Twilio, n8n
- Delivery
- Scrum, 1-week sprints, about 8 weeks, scheduled outside peak season
The challenge
Where the practice started
Inquiries came from the website, two wedding directories, Instagram and venue referrals, and replies often waited until after a weekend of events.
The planning platform was used for contracts, but follow-ups and payment reminders depended on the lead planner remembering, and late balances meant awkward conversations close to the day.
Vendor details lived in spreadsheets and email threads, and the final week before each wedding was spent calling vendors to check they had the latest timeline.
RSVPs arrived through couples in batches, meal choices were often missing, and final numbers reached caterers later than anyone liked.
Goals
What the project had to change
- Every inquiry gets a personal reply within minutes and lands in one pipeline.
- Contracts, retainers and milestones run on a consistent schedule.
- Vendors confirm on time and every change reaches the right people.
- RSVPs, meal choices and dietary needs are complete before the caterer's deadline.
- The planners decide everything that matters; the workflows handle the chasing.
What we built
What we built, as one connected system.
Planner CRM pipeline
We connected the website form, directory lead emails, Instagram and referrals to one pipeline in the planning platform, with consult booking, stage follow-ups, lost reasons and a monthly source report.
Service detailsAI inquiry assistant
An assistant drafts personal replies in the lead planner's voice within minutes, asks qualifying questions, saves answers to the lead and hands qualified couples to the planner. It ran in approve-before-send mode for the first month.
Service detailsContracts and payment schedules
Accepted proposals trigger the contract and retainer invoice, signature reminders, milestone reminders calculated from the wedding date, late-payment alerts and sync to accounting.
Service detailsVendor coordination
A vendor record per wedding, confirmation requests at one month and one week out, change notices when the timeline changes, and a daily not-confirmed list for the coordinator.
Service detailsRSVPs and guest communication
An RSVP form with a QR code on invitations, matching to the guest list, reminders before the deadline, live meal counts and a caterer pack the couple approves.
Service detailsArchitecture
How the studio's workflows connect
- Input
- Logic and services
- AI step
- Data
- Output
- People
How it flows
- 1 Inquiries, planning platform events and RSVP replies feed one n8n instance.
- 2 Five workflows update vendor and guest records, send emails and texts and use an AI step to draft replies.
- 3 The coordinator works the vendor and RSVP lists; the lead planner approves replies, prices and changes.
- 4 Every step is logged, and a monthly summary shows the measures the studio agreed to track.
How it behaves
How the system behaves day to day
What couples see
- A personal reply within minutes of their inquiry
- Contracts and invoices right after they say yes
- Polite payment reminders and a paid-in-full note
- An easy RSVP form for their guests
What the team sees
- One pipeline, one vendor list and one RSVP dashboard per wedding
- Drafts to approve and qualified leads to call
- Late payments and unconfirmed vendors flagged
What the automation does
- Replies, reminds, confirms and counts on schedule
- Applies consent and opt-outs across every workflow
- Logs every step and alerts the lead planner if anything fails
Edge cases and fallbacks
- A couple asks for a custom quote
- The assistant collects details and passes it to the lead planner; no price is invented.
- A wedding date moves
- Payment milestones and vendor confirmations are recalculated and the planner approves the new schedule.
- A vendor replies with a question instead of confirming
- The coordinator handles it personally.
- A guest changes their RSVP after the deadline
- The planner is alerted and updates the caterer.
- Zapier or n8n has an outage
- Inquiries queue and retry, and the lead planner gets an alert.
Integrations
What we connected
HoneyBook
Client management platformInquiries, projects, stages, meetings and payments for the CRM, contracts and reminders.
HoneyBook's Zapier triggers (New Inquiry, Project Booked, Project Stage Changed, Payment Paid and more) and actions (Create Client, Create Project).
DocuSign
E-signatureContracts sent and tracked from a workflow.
DocuSign eSignature REST API.
Stripe
PaymentsRetainer and milestone invoices and payment links.
Stripe Payment Links and the Stripe API.
Google Workspace
Documents, sheets and emailTimelines, run of show, vendor records, RSVP forms and email.
Google Sheets, Docs, Forms and Gmail APIs.
Twilio
SMSRSVP reminders, day-of updates and opt-out handling.
Twilio Programmable Messaging API.
n8n
Automation platformRuns every workflow, self-hosted or on n8n Cloud.
Your own n8n instance; we hand over every workflow.
How we delivered it
Week by week, one workflow at a time.
Delivery timeline
Typical time to launch: about 8 weeks, then support
-
01
Discovery
Week 1
We reviewed a season of inquiries and replies, mapped contracts, payments, vendors and RSVPs, and agreed the tone guide and hand-off rules.
-
02
Design and access
Week 2
Platform and Zapier access, contract and reminder wording, consent rules, RSVP form fields, Twilio number and A2P 10DLC registration.
-
03
Sprint 1: CRM pipeline
Week 3
Built and shadow-ran inquiry capture, stages and follow-ups; demo and sign-off.
-
04
Sprint 2: contracts and payments
Week 4
The pipeline went live. Built the contract trigger, retainer invoices and milestone reminders.
-
05
Sprint 3: AI assistant
Week 5
Payments went live for new bookings. Built the inquiry assistant in approve-before-send mode.
-
06
Sprint 4: vendors
Week 6
The assistant went live with approvals. Built vendor records, confirmations and change notices.
-
07
Sprint 5: RSVPs
Week 7
Vendor coordination went live on the next wedding. Built the RSVP form, reminders and caterer pack.
-
08
UAT and handover
Week 8
The team ran acceptance tests on every workflow, then we handed over the run book and trained the associate and coordinator.
-
09
Support
Ongoing
Weekly check-ins during the first season, then monthly care.
Who does what
What the team does, and what automation does.
Automation does
- Captures every inquiry and drafts a personal reply
- Sends contracts, invoices and milestone reminders
- Requests vendor confirmations and pushes change notices
- Collects RSVPs, meal choices and dietary needs
- Keeps counts, lists and logs up to date
The team does
- The coordinator calls unconfirmed vendors
- The associate planner approves reply drafts and books consults
- The coordinator checks unknown guests and unclear RSVPs
- The team follows up late payments personally
Lead planner decides
- The lead planner sets pricing and decides which events to take
- The lead planner chooses and replaces vendors
- The lead planner and couple approve timelines and final numbers
Compliance handled
Privacy, consent and safety, built in.
Electronic contracts
Contracts are signed electronically, which the ESIGN Act recognises in the US; contract wording stayed with the studio's own lawyer.
Source: www.law.cornell.eduTexting rules in the US
Texts go only to people who gave their number for the event and agreed; anything promotional needs prior express written consent.
Source: www.law.cornell.eduA2P 10DLC registration
The studio's texting number was registered for A2P 10DLC before launch.
Source: www.twilio.comDietary needs as health data
The RSVP form asks for explicit consent and caterers get only what they need, in line with Article 9 GDPR for EU guests.
Source: gdpr-info.euAI disclosure
Live chat discloses the assistant is automated, in line with Article 50 of the EU AI Act.
Source: artificialintelligenceact.euCard data stays with providers
Payments are taken on Stripe and the platform's hosted pages, so card numbers never pass through our workflows.
Source: www.pcisecuritystandards.orgOutcomes
What changed for the practice
- Every inquiry now gets a personal reply within minutes, even during a weekend of events.
- Every lead sits in one pipeline with a clear next step.
- Contracts and payment reminders run on a consistent schedule, and late payments reach the planner early.
- Vendors confirm on time, and timeline changes reach every affected vendor.
- RSVPs and meal choices are complete before the caterer's deadline more often.
- The planners spend their evenings on clients and design rather than chasing.
What we track
The measures the practice watches.
Reply time
Time from inquiry to first reply, and share of inquiries qualified.
Pipeline
Consults booked, proposals sent, booking rate and lost reasons by source.
Payments
Payments on time and overdue balances by month.
Vendors
Vendors confirmed on time and change notices acknowledged.
RSVPs
Response rate by deadline and days between final numbers and the caterer's cut-off.
Cost estimate
What a project like this costs
-
Discovery and design
Season review, data flows, wording and the backlog for all five workflows.
$1,000 – $2,000
-
CRM pipeline module
Capture, stages, follow-ups and the source report.
$700 – $1,600
-
AI assistant module
Voice guide, drafting, qualification and hand-off.
$1,300 – $3,200
-
Contracts and payments module
Contract trigger, invoices, milestones and alerts.
$600 – $1,500
-
Vendor module
Vendor records, confirmations and change notices.
$700 – $1,700
-
RSVP module
Form, reminders, counts and caterer pack.
$500 – $1,200
-
Integrations
Planning platform, DocuSign, Stripe, Google and Twilio.
$300 – $800
-
Testing, UAT and launch
QA, acceptance testing, launch and training.
$400 – $1,500
-
Total project estimate
$5,500 – $13,500
Optional monthly care after launch is quoted with your proposal. Typical range for a project of this scope: four workflows at our fixed per-workflow range plus an AI assistant. Every studio gets its own fixed quote after a free call.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- Twilio SMS (US): About $0.0083 per message segment plus carrier fees, and about $1.15 a month per local number (Twilio's published US pricing), plus A2P 10DLC registration fees.
- n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
- Planning platform, DocuSign and Zapier: Each vendor's own plan.
- AI usage: Pay-per-use model fees, usually small at studio volumes.
What pushes cost up
- Systems without an API, or with integration access that must be requested from the vendor
- Writing data back into your core system rather than only reading from it
- Several locations, brands or very different processes to support
- Custom apps, dashboards or a voice line on top of the workflows
What keeps cost down
- One location and one clear process to start with
- Cloud software with a documented API
- Using tools you already pay for instead of adding new ones
- Approved wording and sample data ready at the start
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
- 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
- 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
- 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.
How scope stays under control
- Product backlog
- Every feature, fix and question in one prioritised list you can see at any time.
- Acceptance criteria
- Plain-language conditions for "done" on each item, agreed before work starts.
- Change requests
- New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
- User acceptance testing (UAT)
- Before launch your team tests the real workflow against the acceptance criteria and signs off.
Tools we use
Project manager / Scrum master
Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.
Business analyst
Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.
Automation engineer
Builds the n8n workflows, integrations, AI steps and error handling.
Backend developer
Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.
Frontend / mobile developer
Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.
QA engineer
Tests every workflow against the acceptance criteria, including edge cases and failure paths.
DevOps engineer
Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.
Who does what at each phase
- Free call
- Project manager, business analyst
- Understand the problem, check it is worth automating and outline a rough range.
- Discovery
- Business analyst, automation engineer
- Map the current process, systems and data, and agree success measures.
- Design
- Business analyst, automation engineer, backend developer
- Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
- Sprints
- Automation engineer, developers, QA
- Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
- UAT and launch
- QA, DevOps, project manager
- Your team tests and signs off, we switch on, monitor closely and train the team.
- Support
- Automation engineer, DevOps
- Stabilisation window, then optional monthly care with monitoring and changes.
A point of contact
One person who can answer questions and approve decisions, with about an hour a week during the project.
Access
Admin or API access to the systems involved, created as separate accounts with the least access needed.
Sample data
Real but non-sensitive records (or de-identified ones) so we can design and test against reality.
Approved wording
Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.
Vendor agreements
Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.
Time for testing
A few hours from the people who will use the system, for the demos and user acceptance testing.
Working system
Workflows, integrations and any apps running in your accounts, under your keys.
Documentation
Workflow specification, data-flow map, run book and exported workflow files.
Training
A walkthrough for the team and a short recorded video for new starters.
Handover
All access, credentials and code handed over; you can keep us or take it in-house.
Stabilisation window
Fixes for anything that does not meet the agreed acceptance criteria after launch.
Support options after launch
No plan
You run it yourselves after the stabilisation window and contact us when you need a change.
Monthly care
Monitoring, error alerts, small changes and updates each month, with an agreed response time.
Priority care
Faster response times for business-critical workflows and a monthly review call.
How a project moves through our team
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
Tools we built
Free tools we built and use every day.
The Make It Flow platform
Website audits, monitoring and reports
- Website Speed Test FreeLighthouse score, Core Web Vitals and ranked speed fixes
- SEO Audit FreeTitles, meta, headings, indexability, sitemaps and schema
- Email Deliverability Check FreeMX, SPF, DKIM, DMARC, MTA-STS and BIMI with ready DNS fixes
- Website Monitoring Scheduled re-scans, score emails and 5-minute uptime alerts
Free website tools for practices
Services in this case study
Wedding & event planner CRM automation
Capture every inquiry from your website, directories, Instagram and email into one planner CRM pipeline, with stage-based follow-ups, consult booking and a monthly view of where booked clients come from.
From $1,000 · About 4 weeks Details
AI inquiry assistant & wedding inquiry responses
Reply to every wedding and event inquiry in minutes with a personal, on-brand response, ask the qualifying questions, answer FAQs from your approved wording and pass hot leads to the planner.
From $2,500 · About 5 to 8 weeks Details
Contracts, retainers & payment schedules
Send the right contract and retainer invoice the moment a proposal is accepted, chase signatures politely, and remind clients of every payment milestone until the final balance is paid.
From $1,000 · About 3 to 4 weeks Details
Vendor coordination & confirmations
Keep every vendor's contract, arrival time, contact and final details in one place, send confirmation requests and change notices automatically and see who has not confirmed before the week of the event.
From $1,000 · About 4 weeks Details
RSVPs, meal choices & guest communications
Collect RSVPs, meal choices, dietary needs and travel details through one form, send reminders to guests who have not replied and give the caterer and venue clean, up-to-date counts.
From $1,000 · About 3 to 4 weeks Details
Lead planner decides
-
Wedding Planner Website Checklist: Portfolio, Enquiries and Guest PrivacyGuides · 9 min read
-
Photography Booking Workflow: From First Inquiry to Booked ShootAutomation · 9 min read
-
Client Document Collection Automation for Accounting FirmsAutomation · 8 min read
-
What Are AI Agents? A Plain-English Guide for Small BusinessesAutomation · 10 min read
Free 20-minute call
Want this built for your event & wedding planner?
Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.
Sources we checked
Rules and product facts on this page come from these pages, checked in November 2026. This is general information, not legal advice; confirm the rules that apply to your practice with your own adviser.
- Zapier: HoneyBook integrations
- Zapier: Aisle Planner integrations
- Zapier: Planning Pod integrations
- Zapier: Dubsado integrations
- Tripleseat API OpenAPI specification
- DocuSign eSignature REST API
- 15 U.S.C. 7001 (ESIGN Act)
- 47 CFR 64.1200 (TCPA rules)
- Kelley Drye: FCC limited waiver of the TCPA consent revocation rule
- UK PECR regulation 22
- GDPR Article 9 (special categories)
- GDPR Article 28 (processors)
- EU AI Act, Article 50
- FTC: Final rule banning fake reviews and testimonials
- Twilio: A2P 10DLC
- Twilio US SMS pricing
- PCI Security Standards Council
- HubSpot API overview
- Stripe Payment Links
- WhatsApp Business Platform docs
- n8n pricing
- Google autocomplete phrasing checked for keywords (wedding planner CRM, event planner CRM, wedding inquiry response, wedding planner contract, event vendor management, wedding RSVP reminder text, wedding day timeline, run of show template, wedding planner website)