Franchise Validation Calls: What Candidates Ask Your Franchisees — and How to Prepare the Network

At some point in every serious franchise sale, the process leaves your control. The candidate has read the FDD, attended discovery day, and met your development team. Then they do the thing every competent advisor, lender, and franchise attorney tells them to do: they call your existing franchisees and ask what it's really like.

This is the validation stage, and it has a property the rest of your development pipeline doesn't: you're not in the room. A candidate on the phone with one of your operators hears an unfiltered account from someone with no commission at stake. Whatever that operator says is your brand, for that candidate, forever.

Franchisors respond to this loss of control in one of two ways. The insecure way: curate the call list, coach the talking points, and hope. The durable way: run a network where validation takes care of itself, and build the light process around it that makes the calls go smoothly. This piece is about the second way — starting with an honest look at what candidates actually ask.

What Candidates Actually Ask on Validation Calls

Every candidate's list differs, but after enough cycles the questions cluster into five groups. Your franchisees will be answering these whether or not anyone prepares them:

Notice two things. First, "would you buy again?" is the whole call compressed into one question — most candidates weigh it more than any financial detail. Second, the support and franchisor-relationship questions are answered from the operator's most recent experiences, not their overall average. A franchisee whose last three support tickets went unanswered will validate poorly even in a good system. Validation quality is a trailing indicator of operational quality, with a short lag.

What Not to Do

The failure patterns are well-worn, and candidates — especially those working with franchise consultants — recognize every one of them:

Don't hand-pick a shortlist of your three happiest owners. Sophisticated candidates ignore your list entirely and cold-call from the FDD's franchisee directory (it's disclosed, with contact information — that's the point of it). If your curated three tell a different story than four random dials, you haven't just lost the sale; you've confirmed the candidate's worst hypothesis about how you operate.

Don't script or muzzle franchisees. Beyond being legally fraught in several jurisdictions, coaching operators on what to say produces stilted calls that experienced candidates read instantly. And a franchisee who feels handled will often make a point of going off-script.

Don't punish honest negatives. If word gets around that an owner caught friction from HQ after a candid validation call, your entire network learns the lesson — and the next candidate hears not just complaints, but complaints plus "and they don't like us saying so."

Don't treat validation as a sales stage to optimize. It's a diagnostic stage that happens to occur during sales. Treating it as something to manage rather than something to earn is how networks end up growing on momentum while their unit-level truth deteriorates — until validation collapses and development stalls with a two-year lag.

What You Can Legitimately Do

Accepting that you can't control the calls doesn't mean doing nothing. Four practices are both ethical and effective:

Prepare franchisees for the mechanics, not the content. Tell your network what validation calls are, that candidates will call them directly from the FDD directory, roughly how long calls run, and that honest answers — including criticisms — are expected and welcome. Many franchisees have never been told any of this; their awkwardness on calls gets misread as evasiveness. A one-page explainer and a segment in initial training covers it.

Distribute the load. In networks with active development pipelines, the same articulate owners get called constantly — it's a real time cost on your best people. Some franchisors gently rotate a "recently opened" and "long-tenured" reference set each quarter (in addition to, never instead of, the full directory) and thank participating owners visibly. Respecting franchisees' time here is itself a support signal.

Close the loop. Ask candidates — win or lose — what they heard. Not to litigate it; to learn from it. Recurring themes in validation feedback are the cheapest operational audit you will ever receive. If four candidates in six months mention that owners feel training quality dropped, that's not a sales problem. That's a finding, and it should route to the same place your franchisee satisfaction survey results go.

Fix the systems that generate the answers. This is the real lever, and it's the whole game. Walk back through the question table above and notice that every answer is downstream of something operational: support responsiveness, training quality, honest unit economics, how change gets communicated. Which leads to the uncomfortable, liberating conclusion —

Validation Is a Product of Operations, Not Communications

A franchisee's validation-call answers are generated by their lived experience of your system. That experience is built from concrete, improvable things:

• "How was training?" is answered by whether your onboarding actually made their first 90 days survivable — whether their staff could be trained to standard without heroics, whether the launch playbook held up.
• "Do they support you?" is answered by ticket response times, field-visit usefulness, and whether the last three problems they escalated got solved or acknowledged-and-forgotten.
• "Do they listen?" is answered by whether field input has any path upstream — an advisory council with real dispositions, procedures that visibly change based on operator feedback.
• "Would you buy again?" is answered by all of it, plus the numbers.

Networks with strong validation aren't lucky and aren't better coached. They're operationally legible: standards are clear and current, training is consistent across locations, support is measurable, and franchisees can see the system working — dashboards instead of black boxes, changelogs instead of surprise memos. An operator who experiences their franchisor as organized and responsive says so on the phone, in their own words, unprompted. That's the only script that works.

There's a compounding effect, too. Strong validation attracts stronger candidates, who become stronger operators, who validate better. Weak validation forces the development team to sell harder against headwinds, which pulls in less-qualified buyers, who struggle, and validate worse. Both loops are self-reinforcing. Which one you're in was decided by operations long before any candidate picked up the phone.

A Quick Self-Test

Want to know what your validation sounds like without waiting for a lost deal to tell you? Do what candidates do: pick five franchisees at random — not your favorites, random — and imagine each answering "would you buy this franchise again?" tomorrow, to a stranger, with no one from HQ listening.

If you're confident in four of the five answers, your development pipeline is standing on rock. If you're not — you don't have a validation problem. You have an operations to-do list, and you just wrote the first draft of it in your head.