Franchise email marketing case studies: what two vendor records show and how to set a baseline

What to take away

Four franchise email programs with public detail

Vendor case libraries are the only public record most franchise systems have for email programs. Two of the four entries are named client cases with a vendor record. The other two describe loyalty program mechanics, such as rewards and member emails, without a result.

KOA, the Kampgrounds of America franchise network, appears in a Constant Contact resource titled "How a Unique Campground Found a Unique Email Marketing Partnership." The public listing says a central program sends email for about 470 locations, which takes that work off internal marketing staff. It gives no open rate, click rate, holdout or cost line. The full piece is a gated download.

Pi Co., a fast-casual pizza chain with more than 20 locations in Ontario, Canada, appears in a Klaviyo customer case study. The case says Pi Co. franchisees recommended Klaviyo, and that a Square integration was a key factor. It reports that 54% of Klaviyo revenue came from flows year to date, and that 48% of flow revenue came from SMS. Those figures combine email and SMS, and the text gives no counts of messages, members or orders behind them.

Against the baseline standard, a holdout, a stated denominator and a cost line, none of the four qualifies. Read all four as evidence that a mechanism ran somewhere, not as a forecast for your system.

What a real baseline looks like

A baseline is your own locations, measured before the change, over a stated period, with a stated denominator. Build it from four numbers per location: emails delivered, unique opens, completed actions, and unsubscribe or complaint rate.

Do not benchmark against vendor rates. Your own before-and-after numbers are the only comparison that matters for your network. Google's sender guidelines ask senders to keep the spam rate in Postmaster Tools below 0.10 percent and to avoid ever reaching 0.30 percent, so track complaints per location as well.

Then hold part of the cohort back. If you roll the program to forty locations, run it in thirty and leave ten on the current process for the same eight weeks. That holdout is the only thing that turns a vendor number into a comparison.

Costs belong in the same sheet: platform fee, integration build, offer margin, and staff hours spent on local support. Platform pricing depends on list size and vendor, so get each vendor's current price sheet. A point-of-sale integration needs a quote from the integrator, or no extra cost where the platform already ships a connector for your system.

The arithmetic is simple. Incremental margin equals completed actions in the test group, minus completed actions in the holdout, scaled to equal group sizes or to a rate per thousand delivered, times margin per action, minus total program cost. A program that lifts completed actions but doubles support demand may still lose, so run that calculation with your own numbers.

The transfer test for a franchise case

The mechanism travels; the result does not. Before adopting anything from a published case, answer three questions about your own network.

Does the central team actually absorb the work, or does it push a new task onto a franchisee who already runs the counter? A program that adds local labor has to pay for that labor out of whatever lift it creates.

Does the local list survive contact with the point-of-sale system, including refunds, duplicate profiles and staff turnover? Does the franchisor or the franchisee own the sending account, and who keeps the list if the relationship ends?

That last one decides your exit terms. If the vendor holds the audience and the franchisee holds the relationship, a vendor change costs you the list.

Worked example: a hypothetical ten-location pilot

Take ten locations, five test and five holdout, matched on trade area size and average ticket. Run eight weeks. Record per location: delivered, unique opens, completed actions, and unsubscribes. Also record support tickets and staff hours.

At week eight, compare test against holdout on completed actions per thousand delivered, not on total revenue. Revenue moves with weather, season and local promotion. A rate per thousand delivered is comparable across locations of different sizes.

If the test group shows no gap, stop. If it shows a gap but support tickets tripled, price the support before you extend. Write the stop rule down before week one, or the pilot will be declared a success by whoever sponsored it.

Audit the published evidence

The FTC's advertising substantiation policy expects a reasonable basis for objective advertising claims before they are made. A franchise system that republishes a vendor result in recruitment material takes on that requirement. Confirm the current position with the FTC and qualified local counsel rather than relying on this summary.

The FTC's Trade Regulation Rule on the Use of Consumer Reviews and Testimonials, 16 CFR Part 465, took effect on October 21, 2024. It bars fake reviews, incentives conditioned on a positive or negative review, and insider testimonials shared without disclosing the relationship. Its principles are a useful check when a franchise case study names a provider and a result.

Keep four things apart in your file: provider claims, customer statements, measured records, and independent findings. Record selection criteria, commercial relationships, product version and missing evidence.

If the method is unavailable, file the item as a lead to test, not a verified result. Reproduce one material claim with local data before you recommend a provider.

For franchise email marketing decisions, keep the evidence record beside the decision so a reviewer can rebuild the reasoning without memory. Set a review date and name the change that triggers an earlier look.

Common questions about vendor claims, whether a restaurant case transfers to another franchise, and what an internal write-up should contain sit in our franchise email marketing questions page. Current benchmark ranges sit in the franchise email benchmarks reference, and other programs are listed in the franchise email examples guide.

Common questions

Are vendor case studies trustworthy?

They can support attributed facts about a named client. Review the method, the commercial relationship, what was omitted, and whether the mechanism transfers to your network before you decide anything.

Can a restaurant case apply to another franchise?

The mechanism may travel. Purchase cycle, data quality, margins, and location count usually do not. Audience and staffing usually do not either. Test on a matched cohort rather than assuming the result carries.

What should an internal case study publish?

An internal write-up should record the source, the baseline, the cohort definition, the intervention, the counts and their definitions, the costs, the failures, the customer effects and the unresolved limits. A number without a denominator is not a result.