A Saturday evening in late February. A planner outside Franschhoek has fourteen suppliers confirming for a wedding three weekends out at Lourensford. The mother of the bride has WhatsApped twice in twenty minutes about the seating chart. The florist needs final stem counts by Tuesday. A separate enquiry has just come in for a fifty-guest microwedding at Babylonstoren next October, the third this week, and she has not yet replied to the first two.
None of this is the work. The work is the day itself, and the part of the planning that needs taste, judgement, and a quiet hand on the moving parts. Quote PDFs, vendor confirms, run-sheet revisions and "did you receive my deposit?" voice-notes are the cost of the seat.
South African wedding planners operate on a strange shape of margin. The season runs October through April, with a tight December-to-February peak where roughly half the year's revenue lands. Administrative load goes up exponentially in those months: three or four parallel weddings, twelve to sixty suppliers each, two sets of parents apiece, and a WhatsApp group nobody asked for. Most planners I have spoken to in the Boland and Joburg's northern suburbs are working from 06:00 Saturday through Monday afternoon during peak. The work that suffers is the work they got into the business for.
That work, the design and taste and family-managing and day-of judgement, does not automate. The administration around it does.
Where SA wedding planners actually lose the hours
Across the planners I have looked at in Cape Town, Stellenbosch, Hermanus, the Drakensberg and Joburg's northern suburbs, the same buckets show up. The names change. The pattern doesn't.
The first is quote turnaround. A couple enquires through Instagram, Hello May or your website. They want a bracket within 48 hours. To give them one, you have to ask a dozen questions, pull venue pricing from three or four PDFs that change yearly, sense-check the planner-fee band, and write a thoughtful enough note that the couple feels seen. Most planners are doing this from scratch for every enquiry. Most peak-season enquiries get a polite "I'll come back to you Monday" that loses half of them to a quicker competitor.
The second is supplier coordination. A 120-guest Winelands wedding pulls in around eighteen vendors: venue, caterer, bar service, florist, two photographers, a videographer, hair and makeup, DJ, MC or band, decor and draping, marquee hire, sound and lighting, stationery, cake, transport, a coordinator on the day. Each has a quote to sign, a deposit to chase, a confirm to send three weeks out, and final numbers to issue. The volume is high. The cost of dropping one is catastrophic.
The third is client communication. The bride. The groom. Both sets of parents. The maid of honour. The best man. Sometimes the mother-in-law adds herself. On peak weekends you are running three WhatsApp groups and seven one-on-one threads in parallel. Messages that need a fast factual reply ("what time is the florist arriving?") sit next to ones that need a slow human one ("my mother is panicking about the dress code on the invitations").
The fourth is run-sheet construction and revision. The minute-by-minute. Twelve revisions between booking and the day. Five sets of stakeholders to share it with. A single late change (the chapel pushed back by 20 minutes) cascades through everything downstream. Most planners do this in a single Google Doc or Excel sheet that nobody but them can interpret.
AI handles three of these well. The fourth, the slow-human messages to a panicking parent, it cannot do and should not try.
Quote turnaround that doesn't take three days
The fastest single change most SA planners can make is to stop drafting every quote from scratch.
A useful flow. The enquiry comes in. A short branded form (eight questions at most) collects what you need: date, venue or region, guest count, style, ceremony arrangement, accommodation, planner involvement, and whether the couple needs supplier sourcing. A model shown your last forty signed contracts, your venue pricing PDFs and your fee structure produces a first-draft quote in your voice, with the right brackets pre-populated. You read it, adjust the two numbers your eye says are wrong, and send it within four hours.
You are still writing the quote. The model is doing the assembly. The two-hour Tuesday-night drafting block disappears, and the couple in Stellenbosch who messaged six planners on Sunday gets your reply first.
A note on what to refuse here. Couples sometimes want a binding price from the first reply. Do not let the system give one. The first reply is a bracket. The binding price comes after the design conversation, and the design conversation is the part of the job you are getting paid for. A planner who quotes binding numbers from a form is a planner who eats the loss when the bride changes her mind about cabanas, signature drinks, or a second venue for the after-party.
Supplier coordination: the 47-message problem
The wedding industry runs on WhatsApp. Not Slack, not Asana, not a planner-CRM with elegant dashboards. WhatsApp. Trying to move suppliers off it is, in my experience, a fight you lose.
The right pattern is to leave the human conversations where they are and put the structured ones somewhere else. The structured ones: deposit chases, confirm-three-weeks-out reminders, final-numbers requests, the "did you get the contract?" follow-up. Mechanical, time-sensitive, identical across every wedding you run.
A light coordination layer behind a WhatsApp Business API number takes those off your plate. The florist gets a deposit reminder seven days after the contract. The caterer gets the final-numbers prompt fourteen days before the wedding. The transport company gets the timing brief three days out. None of it goes through your phone. Your phone is for the conversations that need you: the videographer who is double-booked and wants to swap dates, the caterer who needs to know whether the halal requirement extends to the staff meal.
The output is the same one you have always cared about. Every supplier signed, paid, briefed, and confirmed by the time you need them to be. The difference is whether you spend Sunday afternoons sending the same six messages, or whether Sunday afternoons go back to design.
Run-sheets that survive the day
The run-sheet is the document that holds the wedding together. It is also the document most likely to be three versions out of date by the morning of, because the venue requested a 15-minute push, the band confirmed only one set break, and the florist now needs an extra 40 minutes of setup.
AI does not write your run-sheet. You write your run-sheet. The taste in it is yours.
What AI can do is keep the downstream versions in sync. The master run-sheet lives in a single structured document. Each supplier has their own filtered view, generated from the master. The florist sees floral setup, ceremony arrangement, and the strike. The DJ sees the ceremony music cue, the reception start, the first-dance window, the cut-off. When the venue pushes the chapel by 20 minutes, the system runs through the dependencies and flags the three downstream items that need your attention: the photographer's golden-hour window, the catering plate-up time, the band's start cue.
This is scaffolding around your work, not a replacement for it. The judgement calls (the gentle word to the MoB about pacing, the call to the caterer about the photographer's ceremony exit) stay with you. The system keeps the document honest while you do them.
What this should not be doing
A few hard lines, because the wedding industry has more bad AI proposals circulating than most.
A general AI chatbot on your website that prices weddings autonomously. It will quote a Lourensford summer Saturday at the same number as a Tuesday afternoon at a coastal lodge. The first couple to sign on a chatbot quote is the first couple you cannot deliver for at that price. The planning industry runs on referrals. Do not.
An AI persona that messages couples in your name in the run-up to the day. The couple is paying for a relationship with a person whose taste they trust. The moment the bride realises the warm 22:00 reply the night before the wedding was machine-generated, the trust is gone. Use AI to draft the structured reminders. Sign the human messages yourself.
Anything touching family conversations on the day. The MoB who is anxious at 09:40 the morning of, the groom whose vest does not fit, the catering manager who needs a quick call about the staff meal — none of it routes through a model. You handle it because that is what the couple has paid you for.
Less obvious. Lobola coordination on traditional weddings, and the cross-cultural negotiation that often runs in parallel to a white wedding for the same couple. The conversations between families are weighted, cultural, and human. A planner who tries to template that conversation through an AI assistant is a planner who loses the family. Stay close to the elders who are doing the work.
One more. POPIA. Couples and suppliers hand you a lot of personal information across a planning cycle: ID numbers for the venue accommodation register, dietary and medical notes for catering, banking details for supplier deposits. Anything touching that data should sit on infrastructure you control, not in a free consumer model whose terms permit training on inputs. If you are unsure where a tool sits, ask the supplier for the data-processing agreement in writing. If they cannot send one, do not put client data through them.
Where to start
If you run a planning business and you are wondering what to wire up first, the order I would push is this.
Quote turnaround first. Highest-volume, lowest-risk piece, and the improvement in your conversion from enquiry to deposit is visible within a month. Build the form. Train the model on your last forty signed contracts. Use it for three weeks. Refine the brackets. By peak season you have an enquiry-to-quote time under four hours, and the Sunday afternoons that used to disappear into PDF-wrangling come back.
Then supplier reminders. Once the quote side is steady, move the deposit-chase and the three-week confirm reminders behind a WhatsApp Business API. You will get half a Sunday back per active wedding, and the suppliers will tell you, gently, that you have become easier to work with. That sentence is worth more than most marketing spend.
Run-sheet scaffolding last. It needs more set-up time and benefits the most experienced planners least, because the experienced ones already have their pattern in their head. The mid-career planner running four parallel weddings during peak is the one who gets the most from it.
Three pieces. Build each one properly before starting the next. The work that drew you into weddings, the design and the taste and the steady hand on the day, stays yours. The admin around it stops eating the weekends.