DemonstrationBuilt by AgentContext. Every candidate, franchisee, unit and figure below is invented — nothing here is a real record.
FDFranchise Development· multi-brand
Who you are right now

Camille Thibodeaux — VP Franchise Development. Camille runs development across all brands. She sees every candidate, every open unit and every figure — the only person here who does.

Sees 7 of 7 candidates · 9 of 9 open units. Breadth and depth are separate questions. Camille has both; nobody else on the list has either in full.

Where Claude fits

In a production build, Claude would draft candidate follow-ups and the disclosure email, working only from the candidate files the signed-in user can see: Everett’s own list, Priyanka’s North Texas territory, Lena’s one granted file.

It would not propose a signing or payment date inside the waiting period: 14 calendar days after the disclosure document is furnished, or 7 days after a materially revised agreement.

Candidates in view
7
of 7 in the system
Open units in view
9
of 9 in the system
Disclosure clock
1
file signed inside a waiting period
System average unit volume
$598,667
all 9 units

Candidate pipeline

Scoped to this viewer
Inquiry1
Application2
Discovery Day1
FDD Issued1
Franchise Agreement2
Site Selection0

What this is. A working demonstration of the access model underneath a franchise development system — who can see which candidate files, what a number means when the answer differs by viewer, and whether the history can prove a file was sold inside the disclosure waiting periods. The pipeline and the people are fabricated; the behaviour is not, and neither are the two clocks, which come from 16 CFR Part 436.

The demonstration date is fixed at Sep 16, 2026 so the waiting periods stay legible. Nothing on this page is legal advice.

This is a demonstration. Access boundaries here are simulated in your browser; in a production build, records a user isn’t permitted to see are never sent to it.