VAD in Practice: A Multi-Location Training Franchise

Status: illustrative scenario. This is not a published case study of an existing customer. It is a walkthrough of how Visitor-Aware Design changes the site experience for a recognizable kind of business — a multi-location professional training franchise. We use it to show how the paradigm and patterns work together against a problem most readers will recognize.

The setup

A professional sales-training company operates as a franchise with 200+ locations across North America and Europe. Their public marketing site is the front door for three very different audiences:

• Visitor A — corporate buyer. An HR or L&D director researching enterprise sales training for a team of 50–500 reps. Long evaluation cycle, comparing competitors, sensitive to ROI and case studies in their industry.
• Visitor B — individual learner. A sales professional or sales manager looking for a public open-enrollment course. Price-sensitive, location-sensitive, decides in days not months.
• Visitor C — prospective franchisee. A successful sales executive considering buying a franchise territory. Researches business model, financials, training, and territory availability. Year-plus evaluation.

These three visitor types share almost nothing in common except the URL bar. They want different content, in different order, with different CTAs. They convert through different paths to different teams.

The traditional site

A conventional CMS-driven site treats them identically. Same hero, same navigation, same case study carousel rotating through random industries. The "Talk to Sales" button leads to one form that asks every visitor the same six questions.

The handoff to a salesperson is a cold start. When Visitor A finally books a call, she has read four manufacturing-industry case studies, used the ROI calculator with assumptions for 150 reps, and returned to the site three times over a week. None of that reaches the rep. He opens with "So tell me a bit about what you're looking for." She rolls her eyes, mentally drops her interest level by 30 percent, and re-explains everything she already told the website implicitly.

This is the cold-start problem in a single conversation.

The visitor-aware version

The same site, rebuilt around the principle that the experience composes itself per visitor.

Visitor A's second visit

• The hero leads with corporate training, not individual programs. The "Sales Coaching Programs" link is gone from the top nav; "Enterprise Engagements" is in its place.
• The ROI calculator section is collapsed by default — she's already used it. A small line of text says "Pick up where you left off →" with a link back to her saved scenario.
• A new section appears: "Case studies in manufacturing" — the industry she's been reading. The carousel of random industries from a generic CMS is gone; in its place is targeted depth.
• The footer surfaces three more case studies in the same industry, not nine across all sectors.
• The "Talk to Sales" button now reads "Schedule a corporate training discovery call." When she clicks, the form is pre-populated with her industry (inferred), team size (from the calculator), and a behavioral summary attached: "Three visits over a week. Read 4 manufacturing case studies and engaged with the ROI calculator at 150 reps. Pattern consistent with enterprise evaluation; expected sales cycle 8–12 weeks."

When she books the call, the rep opens the meeting with: "I see you've been looking at how this would work for a manufacturing sales team of about 150. Let's start there." The 30-percent interest drop never happens. She leans forward.

Visitor B's first visit

• Hero leads with open programs near him — zip code resolved from his approximate location, three nearby franchises listed by date.
• Pricing is prominent, not buried. (Visitor A didn't see pricing on her hero — it was further down.)
• Testimonials come from individual learners with photos and names, not enterprise buyer logos.
• "Compare programs" is a primary navigation item.
• The CTA reads "Reserve a seat" — direct action, not a sales conversation.

Visitor C's first visit

• Hero is entirely different: "Own a training franchise territory" with the value proposition for franchisees.
• The site composes around territory availability, training-the-trainer programs, and financial expectations — none of which appear on the corporate or individual versions of the homepage.
• The CTA: "Talk to franchise development" — routes to a different team entirely.

What changed under the hood

None of the three visitors are looking at "the same page with different popups." They are looking at different compositions assembled from a shared component library. The intelligence layer:

1. Infers visitor type from referrer, search query, behavioral history, and signal patterns — never from a "What brings you here today?" form. (Intent Inference Pattern)
2. Composes the page by selecting which components to include and in what order, based on the inferred type and journey. (Dynamic Composition Pattern)
3. Recognizes returning visitors with explicit, visible controls. Visitor A can see what the site knows and adjust it. (Cross-Session Memory + Privacy-First Context Layer Patterns)
4. Provides smart defaults for first-time visitors so the experience is rich even before signals accumulate. (Cold-Start Graceful Pattern)

All five patterns are catalogued in the Patterns Library.

The cold-start arithmetic

Conservatively assume a 200-location franchise's central sales team takes 1,500 enterprise discovery calls per year. The traditional cold start adds 15 minutes to each call for re-discovery — that's 375 hours of senior sales time annually, roughly $70K at fully loaded rates. The visitor-aware version eliminates most of it.

That number is not the point. The point is that in the traditional model, every visitor's behavioral journey is collected and then thrown away at the moment the human handoff happens. The expense is invisible because it's distributed across every conversation in the company. Visitor-Aware Design asks a simple structural question: why are we throwing it away?

What this scenario demonstrates

The training franchise is an unusually clarifying example because its visitor types are unusually divergent. A typical B2B SaaS site might have 80 percent of visitors in one persona; a franchise site routinely sees three or four with near-zero behavioral overlap. If VAD can serve all three well, simpler cases get easier as a matter of course.

The patterns at work here are not exotic. Intent inference, dynamic composition, and a privacy-respecting context layer cover most of the lift. None of them require AI breakthroughs; they require treating intelligence as architecture rather than as a personalization widget bolted onto a CMS.

Further reading

• Whitepaper 2: Behavioral Journeys — the four journey types and how to detect them
• Whitepaper 7: Eliminating the Cold Start — the handoff problem in depth
• Patterns Library — the implementation patterns referenced above
• Glossary — definitions for behavioral journey, cold start, composition, intent inference, and the rest of the canon

When a published customer engagement is available, it will live in this section alongside this walkthrough. The walkthrough is not a substitute for evidence — it is a clear demonstration of what the paradigm asks of a site, before that evidence is shared.