Weddings run on a 12 to 18 month engagement cycle, a bride plus a groom plus two sets of parents as stakeholders, and a vendor web that quietly decides whether the day actually works or not. Strkr models all of it on one record, so the inquiry you take tonight is already the day-of timeline you run next October, and the vendors you book this spring are already the referral motion you lean on for next spring.
Wedding businesses sit between the service-business CRM world and the project-management world, and no tool from either side quite fits the shape of the work. The engagement cycle is longer than any other service category you can name, often stretching from the first inquiry email through the thank-you note sent at the one-year anniversary. The stakeholder list has more opinions and more sign-offs than any other service category, because every couple comes attached to a parent set, a budget sensitivity, and an in-law dynamic that quietly shapes every decision from venue down to seating chart. The day-of timeline is a project with 40 to 80 moving parts and zero room to miss a cue, because the ceremony starts when the ceremony starts and the band has a hard-stop at midnight whether the toasts ran long or not. The CRMs that most wedding planners, venues, and photographers start on were built for a quick-turn service business where a lead becomes a project in two weeks, and those tools begin to crack somewhere between the eighth booked wedding and the fiftieth, which is right about when the studio is making the kind of money that cannot afford a dropped email or a vendor that showed up to the wrong gate.
Most service-business CRMs are tuned for a 30 to 90 day sales cycle. Weddings are not that. A couple inquires in March, books in August, pays the venue retainer in October, finalizes vendors through the following spring, and gets married 14 months after the first email. A tool that times out automations after 90 days is a tool that drops couples in the middle of their own nurture. Strkr runs flows on the real wedding clock, measured in months to ceremony, not days since inquiry.
Every booked wedding is the output of a four-stakeholder conversation, and sometimes six when siblings or step-parents weigh in. The couple drives the vision, the parents often drive the budget, and all four sign off before a deposit moves. A CRM that has one contact per deal cannot model this. Strkr lets you link multiple contacts to the same wedding, each with their own role, communication preference, and view permissions, so you never send the dad-of-the-bride the sticker-price PDF before he has seen the couple-friendly version.
Every booked wedding involves 8 to 20 vendors: photographer, videographer, florist, caterer, cake, DJ, band, officiant, ceremony musicians, hair, makeup, rentals, transportation, planner, venue, bakery. On most CRMs vendors live in a shared Google Doc, which is where referral relationships go to die. Strkr ships a Vendors custom object with contact info, insurance expiration, preferred-partner tier, referral history, and the account record of every wedding they have ever worked with you.
Wedding contracts bill in milestones: 25 percent retainer at booking, 50 percent at 6 months out, final 25 percent at 30 days out, plus optional add-ons that get decided along the way. A generic CRM wants one invoice per deal. Strkr models the full payment schedule on the booking record, flows due-date reminders to the couple on the right cadence, and keeps a running total of what has been paid, what is due next, and what has been upsold since the contract was signed.
The wedding-day timeline is the single most important document in the business, and it is a project artifact: 40 to 80 tasks across 10 to 14 hours, assigned to vendors and family members, with buffers and contingencies. HoneyBook does not do timelines. Aisle Planner does timelines but not CRM. Strkr runs the day-of timeline as a project linked to the wedding record, so the ceremony time field flows into the vendor arrival times, the family photo window, and the reception entrance.
Wedding businesses live and die on referrals from past couples, past vendors, and venue partners. A spreadsheet of past couples is where that intelligence usually sits, which means half the referral motion never happens. Strkr tags every booked wedding with the referral source, keeps the preferred-vendor matrix live, and runs an automated post-wedding motion that asks for the review, logs the referral tag, and schedules the anniversary gift one year out.
Wedding planners, venues, and photographers share a sales motion that most CRMs do not understand. Inquiry comes in through a form or a referral. The first meeting is a consult, usually on video. The proposal is a styled PDF with pricing tiers. The booking is a signed contract and a retainer. Then the real work starts: 12 to 18 months of planning, hundreds of touchpoints, and a day-of timeline that cannot drop a beat. Strkr ships the shape of pipeline you actually run.
Website inquiry form captures the ceremony date, estimated guest count, venue (if booked), budget band, and how they found you. Strkr auto-creates the wedding record, links the couple as two contacts, and routes to the right planner based on date availability and booking tier. The welcome email goes out within 60 seconds with a Calendly link to the consult. The couple never waits for office hours.
Consult call notes land on the wedding record: vision keywords, must-haves, nice-to-haves, deal-breakers, parent dynamics, budget sensitivity. Strkr AI drafts the follow-up email referencing the vision words the couple used, so the proposal lands with the language the couple already loves. The second consult is scheduled before they hang up.
The proposal pulls from the wedding record: date, guest count, venue, service tier, vendor allocations, estimated total. Three options render into a branded PDF (good, better, best) with the planner studio logo and brand colors. The couple sees the right price for their inquiry, not a generic rate card.
The e-signature integration (DocuSign or PandaDoc) returns the signed contract to the wedding record. The retainer invoice fires automatically. A flow kicks off the planning phase: creates the 12-month planning timeline, assigns the production lead, drops the welcome packet, schedules the first planning call.
The planning phase runs on a flow that triggers tasks on a schedule anchored to the ceremony date: 12 months out book the florist, 10 months out book the stationery, 9 months out save-the-dates, 6 months out menu tasting, 90 days out finalize headcount, 60 days out seating chart, 30 days out final headcount to venue, 14 days out final payment, 7 days out day-of timeline lock. Nothing gets forgotten because nothing is manual.
Day-of timeline is a project linked to the wedding record. Each line has a time, a lead, backup lead, location, and dependencies. Vendors see their own slice via a shared link. The planner opens the timeline on mobile, works through the day in order, logs changes in real time. The ceremony delay at 4:17 pm reflows the cocktail hour by 20 minutes, and every vendor sees the update.
Three days after the ceremony, the review request fires with the three target platforms (The Knot, WeddingWire, Google). Two weeks after, the final-gallery share from the photographer lands with a thank-you note. One year after, the anniversary gift reminder hits the planner. Every past couple stays warm, which is where the next five bookings come from.
The couples who inquire but do not book this year are the pipeline for next year and the referral pool for the year after. A marketing cadence runs for 18 months with blog posts, seasonal inspiration, past-wedding features, and a one-click return-to-conversation link. The ghosted inquiries from last spring book in September.
Strkr pricing is per seat, with CRM, Marketing, Projects, Messaging, and Docs on every paid tier. No contact-tier escalator. No per-flow run meter below the plan cap. A two-planner studio pays for two seats. A ten-planner multi-venue group pays for ten. The pricing math is the only part of a wedding business that does not get more complicated as you grow.
The single most undervalued asset in a wedding business is the vendor network: the preferred florist who gives you a 10 percent discount, the photographer who sends you three couples a year, the venue coordinator who routes inquiries your way when the in-house option is booked. These relationships are the business, and they belong in the CRM, not in a spreadsheet.
The Vendors object stores contact info, service category, service radius, insurance expiration date, preferred-partner tier, referral fee arrangement, commission structure, pricing bands, and a notes field for the quirky stuff (which caterer refuses to work with which venue, which florist needs 48 hours notice for a quote). Searchable, filterable, reportable.
The link table between vendors and weddings answers questions a spreadsheet cannot: which five photographers have I used most in the last 18 months, which caterer has the best review scores from my past couples, which florist has been late twice. Insurance expirations surface 60 days before they lapse so you never book a vendor who cannot work the day.
Every booked wedding has a referral source: past couple name, vendor name, venue partner, Instagram, The Knot, or Google. The referral report answers the only marketing question a wedding business should care about: who sent me the top five bookings of the year, and did I thank them. Last year is the ad budget argument for this year.
When you build a proposal, the preferred-vendor matrix surfaces the right florist for the aesthetic, the right caterer for the headcount, the right band for the vibe, filtered by availability on the ceremony date. The couple sees a curated list, not every vendor in the city. Your fee comes from the match quality, not the volume.
Every vendor record has a COI expiration date. A flow fires 60 days before any expiration with a renewal request to the vendor and a flag to the planner. No wedding goes forward with an uninsured vendor on the roster, because the data says so, not because a planner remembered.
Vendors get a view-only link to the slice of the wedding they are responsible for: their timeline block, their contract, their final headcount, their load-in time, the venue address, and the planner cell phone. No email chain, no texting the week-of, no vendor showing up at the wrong gate.
Wedding contracts are not a single invoice. They are a four to six payment schedule stretched across 12 to 18 months, with upsells added along the way. The couple needs clarity. The studio needs predictability. The accountant needs clean books. Strkr models all of it.
Default template: 25 percent retainer at booking, 25 percent at 9 months out, 25 percent at 3 months out, 25 percent at 30 days out, with Stripe or square invoicing fired automatically on the right dates. Custom schedules supported for the mid-market venue or planner studio that negotiates per-contract. Every payment is a row on the wedding record.
Upsells happen through the planning cycle: additional hours of coverage, second photographer, custom lighting, late-night snack, parent-of-the-bride gift arrangement. Each one gets logged on the wedding record with a mini-invoice. The final total is the sum of the base contract plus every logged upsell, not a surprise.
A flow fires 7 days before each payment is due with a reminder, a 1-click Stripe link, and a short note from the planner. A second flow fires 1 day late with a softer nudge. The late-payment conversation becomes an exception, not a weekly task.
The booked wedding book maps to a monthly revenue forecast anchored by payment milestones. May looks heavier than April not because the ceremonies cluster there but because the 90-days-out payments stack. The forecast is the view that tells the studio owner when to hire, when to invest in marketing, and when to take a vacation.
Vendor gratuities land in the week after the wedding. The planner knows the recommended amount, the couple handles the envelopes. A line on the day-of timeline reminds the planner where envelopes need to be distributed and in what order. One of the small things that separates a studio that gets rebooked from one that does not.
Every contract has cancellation and reschedule terms. When a date change or cancellation happens, Strkr applies the right refund logic (fully refundable before X, 50 percent before Y, non-refundable after Z) against the paid-to-date number. The hard conversation is still hard, but it is not an accounting fight.
Everything in the business comes down to one 14-hour window. The ceremony starts at 4 pm, the reception ends at 11 pm, and in between every vendor has to be in the right place at the right time with the right gear. Day-of is where the wedding studio earns the review, the referral, and the next five bookings.
The day-of timeline lives as a project linked to the wedding. Each row has a start time, duration, lead, backup lead, location, dependency, and a 1-sentence note. Fifteen minute buffers at the structural moments (first look, ceremony, dinner service, reception entrance) absorb the real-world drift that always happens.
Ceremony time anchors the schedule. Photographer arrives at ceremony minus 3 hours for getting-ready coverage. Florist arrives at ceremony minus 4 hours for installation. DJ sound-check at ceremony minus 2 hours. Change the ceremony time by 30 minutes and every arrival time shifts, because the schedule is formula-driven, not hand-typed.
The family-formal shot list is on the wedding record: grouping names, who is in each shot, which side of the family they come from. The photographer sees the list on their shared view. The planner wrangles the groups in order. The 30-minute family-photo window stays a 30-minute window, which is where receptions start or do not start on time.
Outdoor ceremonies carry a rain plan: tent, indoor backup, hybrid. The decision tree is on the wedding record with a decision deadline (usually ceremony minus 12 hours). The planner makes the call once, the flow notifies every vendor, and nobody shows up to the wrong setup.
On mobile, the planner opens the timeline, taps each row as it completes, and the whole project moves. A delay at the ceremony cascades through the cocktail hour, the dinner service, and the reception entrance. The DJ sees the updated announcement time, the catering sees the updated meal service, the photographer sees the updated couple-portrait window.
Monday after the wedding, the planner spends 20 minutes closing out the project with notes: what worked, what did not, which vendor was great, which vendor was late, which family member was difficult. Those notes feed the vendor record, the referral record, and the next proposal with better accuracy than any memory ever would.
The common wedding-business stack is HoneyBook for inquiry and contracts, Aisle Planner for day-of timelines, and a Google Sheet for vendors, payments, and referrals. Three tools, three data stores, three subscriptions. Strkr replaces all three with one record per wedding.
| Feature | Strkr | HoneyBook + Aisle Planner + spreadsheets |
|---|---|---|
| Single record for the full wedding | One wedding record from inquiry through anniversary | Three tools, data copied by hand or not at all |
| Multi-contact couple + parents model | Four to six contacts per wedding, each with role and permissions | One primary contact per record, parents in notes |
| Vendor database | First-class Vendors object with insurance tracking and referral history | Google Sheet, no reporting, no COI tracking |
| Payment milestone schedule | Multi-milestone contract with automated due-date flows | HoneyBook payments at single or two-step; spreadsheet for the rest |
| Day-of timeline | Project module linked to wedding, formula-driven arrival times | Aisle Planner timeline, disconnected from CRM |
| Marketing cadence for ghosted inquiries | Full marketing module on every paid tier, 18-month cadence support | Email templates, no cadence engine |
| Referral attribution | Referral source tagged per wedding, reportable by past couple or vendor | Spreadsheet column, not reportable |
| Native SMS and MMS | Day-of texting with vendors and family, logged on wedding record | Personal cell phone, nothing logged |
| Mobile day-of interface | First-class mobile with offline queue for venues with bad reception | Aisle Planner mobile; limited offline |
| Workflow automations | Flows across inquiry, planning, day-of, and post-wedding on every paid tier | HoneyBook has basic automations; cross-tool flows do not exist |
| Transparent pricing | Flat per seat, full product on every paid tier | HoneyBook subscription + Aisle Planner subscription + sheet of logins |
| E-signature integration | Native integration with DocuSign and PandaDoc | HoneyBook has native e-sign, locked to the platform |
A wedding business that outgrows HoneyBook usually has the same five motions in mind: capture inquiries without dropping them, automate the 12-month planning cycle, run the day-of without a clipboard, close the referral loop, and model the vendor network as data. These are the plays that make the move worth it.
A solo wedding planner takes 40 to 60 inquiries a year and books 18 to 24. Strkr auto-creates the wedding record from the website form, routes a Calendly link, drafts the follow-up email after the consult with the vision words the couple used, and fires the proposal when the discovery conversation hits the right stage. The planner stops losing couples to the ones they forget to email.
A three-planner studio shares inquiries. Strkr routes the inbound based on who has availability on the ceremony date, who matches the aesthetic, and who is up next in the rotation. Each planner sees their own book, the owner sees the combined forecast, and no two planners send dueling proposals to the same couple.
A wedding venue takes 18 to 36 inquiries for every date it books. Strkr runs the tour-scheduling flow, drops the preferred-vendor packet after the tour, and tags the inquiries that go cold for the next-year nurture. The venue owner sees the booked dates, the forecast, and the inquiries by season, which is the view that tells them when to adjust rates.
A wedding photographer books 25 to 40 weddings a year and manages a rotating second-shooter network. Strkr tracks every past couple with gallery links, every second shooter with pay rate and availability, every venue with lighting notes, and every vendor with referral history. The booking pipeline runs separately from the production pipeline, and both live on the same wedding record.
A hospitality group with four wedding venues runs 180 weddings a year across the properties. Strkr segments by venue, tracks preferred-vendor lists per property, routes inquiries to the right in-house coordinator, and rolls up the combined revenue forecast. The group owner sees the business as one view instead of four separate HoneyBook accounts.
Start a 14-day trial with CRM, Marketing, Projects, Messaging, and Docs enabled from day one. Model your couples, your vendors, your payments, and your day-of timeline on one record. See transparent per-seat pricing with the full product on every paid tier.
Yes, if you want to start on a CRM you can grow into without replatforming at the ten-wedding mark. Strkr Starter at the entry tier gives you CRM, Marketing basics, Projects for day-of timelines, and Flows for the 12-month nurture cycle, all on one record. The alternative at this stage is HoneyBook plus a spreadsheet plus Aisle Planner plus a Google Doc for vendors, which collapses the moment you book your eighth wedding. For wedding businesses specifically, we recommend starting on Strkr Pro so the full automation layer, vendor custom object, and marketing module are available on day one.
The honest short list: a Vendors custom object with insurance tracking and referral history (not just a contact tag), a day-of timeline project linked to the wedding record (not a separate Aisle Planner subscription), multi-contact per wedding so bride, groom, and both sets of parents are all on the record with their own permissions, payment schedules with four or more milestones (not just one or two), native SMS and MMS for day-of coordination, and marketing cadences that run across the full 18-month engagement cycle. HoneyBook is a great starter CRM for a single service business. Weddings are not a single service business; they are a four-stakeholder, 12-vendor, 18-month project with a single immovable deadline, and Strkr models all of it.
Yes. Wedding venues share most of the same primitives as a planner studio: inquiries, tours, proposals, booked dates, payment milestones, preferred-vendor lists, day-of coordination, and the long-tail of past-couple relationships that drive referrals. Strkr adds date-availability routing so inquiries land with the right coordinator the first time, blackout-date management so you never accept two retainers for the same Saturday, and seasonal pricing bands tied to the booking record so your peak-season Saturday rate flows into the proposal automatically. For venues with on-site food and beverage, the beverage package and the menu tier live as linked records on the booking so the final headcount at 30 days out triggers the right catering order. For multi-venue groups, Strkr segments by property and rolls up combined revenue forecasting, which is the view the ownership team wants when deciding whether property three needs a second coordinator next spring.
Vendors are a first-class custom object in Strkr with contact info, service category, service radius, insurance expiration, preferred-partner tier, referral fee structure, pricing bands, and a link to every wedding they have worked with you. Insurance expirations surface 60 days before they lapse with an automated renewal request to the vendor and a flag to your production lead, so no wedding ever goes forward with a lapsed COI on the roster. Referral history is reportable: you can see your top five referring vendors ranked by booked weddings this year, your most-booked florist by month across the last 24 months, which caterers your past couples rated highest, and which videographer has been late more than once. The vendor-wedding link table turns the kind of question a Google Sheet cannot answer into a one-click report, which is also the view you want open the next time a vendor asks for a bigger slice of the preferred-vendor rotation.
Strkr imports contacts, past weddings, past-couple records, vendor lists, and templates from CSV exports. HoneyBook and Aisle Planner both export cleanly to CSV. The deeper work is rebuilding your inquiry forms, your proposal templates, and your day-of timeline template, which usually takes 2 to 4 weeks running the old tools and Strkr in parallel. Most studios time the cutover between seasons (January for a May-October wedding season, or August for a late-fall season) so there is no live wedding in flight during the switch.
The Strkr mobile app runs an offline queue. The planner can tap through the timeline, log changes, mark rows complete, and send vendor updates without a signal. When the phone reconnects, every change syncs. For venues with reliable Wi-Fi but no cell, the web app runs the same way in a browser. For the small number of truly off-grid venues, the printable timeline PDF covers the day with the digital record syncing on the ride home.
A single-service wedding photographer booking 5 to 10 weddings a year without an assistant and without preferred-vendor relationships is probably fine on HoneyBook for another year. Below that volume the full product is more capability than you need. On the other end, a 500-wedding-per-year destination-wedding operator with on-site coordination teams in six countries is a bigger implementation than a wedding-focused page can speak to; we have run that scope and are honest that it is a 4 to 8 week onboarding, not an afternoon.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
