Your franchise development team is using AI. The question isn't whether — it's whether anyone is running it well.
Your reps are pulling up ChatGPT or Claude for candidate follow-ups, leaning on HubSpot's Breeze and slugging through FDD review prep with whatever AI assistant happens to be handy. None of that is going away. The question worth asking is whether all that AI usage adds up to anything coherent across your team, or whether you have twenty people each running their own private version of AI with twenty levels of quality, twenty different versions of your brand story, twenty different read-outs on what "good" looks like in your process.
Closing the gap and bringing the team together doesn't take a new tool or a bigger budget. It takes AI Fluency and everyone working from the same playbook. The three guidelines below are what separates AI work that compounds across your team from AI work that creates new versions of the problems you already had. It's the underlying foundation that will help your franchise adopt AI to actually drive franchise growth.
1. Always Bring Context (ABC)
AI doesn't understand your business. It can fake it, which is worse than not faking it, because the output looks coherent until someone who actually knows the business reads it. AI struggles to stay inside franchise reality. It will go off the rails into non-franchise assumptions if you don't keep it on track.
Whatever you don't tell AI, it fills in by default. And if the people on your team are each filling in those blanks independently with different ideas about the Owner Avatar, different explanations of your process, the AI outputs drift further apart with every prompt. Twenty team members using AI with twenty versions of "context" is really twenty different brands.
A good AI practice defines context at three levels and equips the team with all of them:
- Franchise-wide context — products and services, Target Market, the Owner Avatar, brand Tone and Voice, and the Policy and Regulatory constraints that make franchise different from every other vertical.
- Team-level context — each team's goals, focus areas, processes, and methodologies. The FranDev team's context isn't the marketing team's context, even when they're using the same tools.
- Task-level context — the outcome, the requirements, and the inputs for the specific thing being done. A Discovery Day follow-up email needs different context than a Broker recap.
The strategic point isn't "write better prompts." It's that consistent context is what makes the body of AI work across your team add up to something. Without it, every prompt is a one-off, and your team's AI output looks like the work of twenty contractors who never met each other.
2. Keep Your Tools Where You Work
There's a reason you don't keep your hammer in the refrigerator. Tools belong where the work happens.
The same applies to AI. AI tools that live inside the systems your team already uses — HubSpot, your CRM, your sales room platform, your email — beat external chat tools on three fronts that matter in a franchise context:
- Security. Data stays in systems you control and have already vetted. External chat tools are a data exfiltration vector waiting to happen, and franchise's Policy and Regulatory environment is unkind to teams that have to explain where the candidate's financial information ended up.
- Speed. Tool-switching has a tax. Every time a rep stops what they're doing, opens a separate browser tab, copies a chunk of context, pastes a prompt, and copies the result back, you've lost most of the productivity AI promised.
- Consistency. Native tools have access to the real data — the actual Deal, the actual Contact, the actual Broker record. The AI is reasoning about your data, not about a paraphrase someone pasted into a prompt window.
The order of preference is clear:
- Native tools first
- Integrated tools second
- External chat tools last
Pick the tool that does not need a copy-paste. Pick the one with a real integration before you pick the one with no connection to your stack at all.
And one rule that isn't negotiable: AI tools your team uses for work should live on company-owned accounts, not personal ones. Personal accounts walk out the door when the person does, take your context with them, and leave your data sitting in a tenant you don't control.
3. Sculpt Your Data and Tell AI What Matters
AI doesn't know what's important to your business unless you tell it. It will make assumptions. It can describe what's there. It can't tell you what isn't there that should be.
Feeding AI everything is not the same as feeding AI what matters. A FranDev team that points AI at raw data will get a competent summary of a useless dataset. The AI did its job. The dataset didn't. Nobody sculpted it down to what matters.
Sculpted data looks like this in practice:
- The data your franchise needs lives in the systems where you'll actually use AI. Lead and Deal data in HubSpot. Candidate financials in the sales room. No stale spreadsheets on someone's desktop.
- The data is reliable enough that you can trust the AI outputs that draw from it. Dirty data plus AI equals confident-sounding wrong answers. Speed and scale don't matter if they're wrong.
- The team knows when and how to bring the right data to the table. A rep prepping for Discovery Day doesn't paste a generic prompt; they pull the candidate's Territory analysis and feed it in with the rest of the context.
This guideline is what makes Guideline 1 actually work. Consistent context only adds up when you've sculpted the data behind it down to what matters. Otherwise, the team is bringing the same wrong dataset to every prompt, just with slightly different framing.
How the Three Reinforce Each Other
These aren't independent. They're three legs of the same stool.
Context (Guideline 1) tells AI what to optimize for. Native tools (Guideline 2) give AI access to the right, real data without manual reentry or data leakage. Sculpted data (Guideline 3) makes that access useful instead of noisy.
A FranDev team running all three has AI that compounds and produces output the team can trust and re-use. A team running one or two has AI that creates new problems. Native tools without sculpted data give you fast access to bad answers. Sculpted data without consistent context gives you precise answers to the wrong questions. Context without native tools means your reps are doing copy-paste gymnastics every time they want to use AI, and it takes as much time as doing it without AI.
Where to Start
You don't need to fix all three at once.
Pick the guideline where the gap between your team's current state and the standard is biggest. If your reps are each pasting whatever context occurs to them into ChatGPT, start with Guideline 1. Get your franchise-wide context documented and equip the team with it. If they're all working in external tools when HubSpot's native AI would do the job or you want to standardize on Claude, start with Guideline 2. If they're feeding AI a swamp of unreliable data and trusting the output, start with Guideline 3.
Whichever one you pick, the move is the same: name the standard, give the team what they need to meet it, and stop accepting AI work that doesn't.
If you want help mapping your team's current AI practice against these three guidelines, that's exactly the kind of working session we run at FranDev Lab.