Reviews per completed event
Normalizes review volume by event count.
Event businesses depend on reputation. Couples read reviews on The Knot, WeddingWire and Google, and corporate clients ask colleagues. Planners and venues refer caterers they trust. Yet review requests are often sent once, weeks after the event, when the glow has faded, and referral partners rarely hear a thank-you.
We would time review requests to the days after a successful event, route concerns to the owner first, and keep a simple record of who refers business so planners and venues are thanked consistently. The owner decides how to respond to feedback and how to reward partners.
Two or three days after the event, the client receives a short thank-you from the event manager and a simple question about how it went.
Clients who mention a problem are flagged to the owner for a personal call, while every client can still choose to leave a public review.
Wedding clients get links to The Knot or WeddingWire and Google, corporate clients to Google, matched to where they found you.
Each lead records who referred it, such as a planner or venue, so the owner can see which partners send business that books.
When a referred lead books, the referring partner receives a thank-you, and the owner sees a quarterly summary to plan partner relationships.
How we deliver this: AI automation for small business or fractional CTO leadership, scoped in writing and run over 90 days. See pricing or the sample scope.
Normalizes review volume by event count.
Requests sent sooner usually get more responses.
Shows which relationships are worth investing in.
Measures whether the private feedback step works.
For example, a caterer completes 20 events a month in season but adds two or three reviews. After timing a check-in two days after each event and linking to the right platform, reviews rise to eight or ten a month. A referral report shows that three Denver planners sent most booked weddings, prompting the owner to schedule regular lunches with them. That is an illustrative case of data guiding where relationship time goes.
In the first 30 days we would count reviews and referral bookings for the past year, review how events close out today, draft check-in and review messages with the owner, add referral source tracking, and pilot the sequence on upcoming events.
Usually within a few days of the event, when the client is still happy and has seen photos or heard from guests. Wedding couples may be traveling, so a second gentle reminder a week or two later helps. We would test timing and watch response rates.
Many review platforms, including Google, discourage or prohibit incentives for reviews. It is safer to ask every client consistently and make it easy. Rewards for referral partners are a different matter, governed by your agreements with them.
Add a referral source field to every inquiry and make it required for sales. Many event platforms support this. A quarterly report then shows leads and bookings by partner, which is useful for both thanking them and deciding where to spend time.
Illustrative defaults for an event company. Replace them with your numbers.
a month in staff time, before any lost sales
Illustration only, not a forecast or guarantee. Recovered staff time becomes a cash saving only if spending actually declines or the time goes into paid work. Tool costs are an assumption; we replace every number here with yours before recommending a scope.
Review and referral requests: full guide
In 30 minutes we look at one recurring workflow, what it costs you today and whether there is a credible case to improve it. If there is not, we will say so.
30 minutes with Phil or Martin. No technical brief, no pitch deck. Phil or Martin replies personally, usually within one business day.