Franchise development CRM
A pipeline for the people buying a franchise, not the customers buying from one: candidates captured from every portal, broker and campaign with their source, worked through qualification, discovery, disclosure, financing and approval with the compliance clocks enforced inside the stage, forecast by conversion between stages, and handed to opening the day the agreement is signed.
A franchise development CRM is the pipeline a franchisor uses to sell franchise units. Its records are candidates — people or companies considering buying a franchise — rather than the customers who buy from the locations, and its stages are the ones a franchise sale actually passes through: enquiry, qualification, application, discovery call, disclosure, discovery day, validation calls with existing franchisees, financing, approval and signature. Its sources are franchise portals, brokers and consultants, referrals from existing franchisees, advertising and events, and its most important metric is cost per signed agreement by source.
It is different from a customer CRM in ways that matter. The cycle is months, not days, so a candidate who has gone quiet for three weeks is normal and one who has gone quiet for three months is lost. Several steps are legal rather than commercial: the disclosure document has to be issued and the waiting period has to run before anything is signed, and the territory the candidate wants has to be reserved so it is not sold twice. Brokers and consultants expect commission on the deals they introduced, so the source has to be recorded correctly and kept. And when the candidate signs, they stop being a candidate and become a location that has to be opened, trained, marketed and charged royalties — in most networks by a different team, in a different system, with the record re-keyed.
A franchise development CRM inside a franchise ERP removes the last of those problems and most of the others. In Gorilla Dash the development pipeline is a corporate scope of the same CRM the locations use, with disclosure and territory as stages of the process, the marketing that fills the pipeline attributed by source, and the signed candidate turning into the location record that the opening tracker, the CRM, the reports and the royalty statement all run from. This page sets out what the software has to do, how a candidate moves through the pipeline, and how Gorilla Dash builds it into the platform the network runs on.
Stages are configurable by brand, but almost every network’s process is a version of this one, and the two legal stages are enforced by the system wherever they sit.
Every enquiry from every portal listing, broker introduction, referral, advertisement, event and recruitment page lands in the pipeline as a candidate with its source recorded. Tracked phone numbers on each channel record the calls. Nothing arrives in a personal inbox.
The first call, the qualification questions — capital, timing, territory of interest, experience — and the application form are recorded against the candidate. Unqualified candidates are closed with a reason so the source report stays honest; qualified ones move on with a next step and a date.
Discovery calls, the territory reservation on the map and the issue of the disclosure document happen inside the stage. The FDD goes out from the record, the receipt comes back signed, and the waiting period counts down on the candidate. The agreement cannot be generated until it has run.
Discovery days are scheduled on the network calendar, invitations sent from the pipeline and attendance recorded against the candidate. Validation calls with existing franchisees are logged, so the stage a candidate is at is a fact rather than a memory.
Financing status, background and credit checks, and the approval committee’s decision are recorded with their documents. The approval is a gate: the agreement is generated only for approved candidates whose waiting period has run and whose territory is still reserved.
The agreement is generated with the candidate’s territory and terms, signed and countersigned electronically. The candidate becomes a location with a target opening date, the broker’s commission is triggered, and the opening tracker starts from the same record without anything being re-keyed.
A customer CRM with the stage names changed handles the first two of these. The rest are the reason franchise development is its own category.
Candidates by stage with the date they entered it, the next step and its owner, value by territory or unit count, and conversion rates between stages — so the pipeline is a forecast and the slow candidates stand out before they go cold.
Franchise portals, brokers and consultants, referrals, advertising, events and the brand’s own recruitment pages, each captured as a source on the candidate, with tracked numbers per channel and cost per enquiry, per discovery day and per signed agreement.
Brokers as partners with their own candidates, commission terms and portal access scoped to their deals, so an introduction is recorded once, the commission is computed from the signed agreement and the dispute about who introduced whom never starts.
A candidate reserves a territory from the development map inside the pipeline; it is shown as unavailable to other candidates, expires if the deal stalls, and is written into the agreement when they sign.
FDD issue, signed receipts, waiting periods, re-disclosure and state registration checks happen on the candidate record at the disclosure stage. A development manager cannot skip them because the agreement cannot be generated until they are done.
Applications, financial statements, background and credit checks, financing letters and the approval committee’s decision stored against the candidate, with the approval as a gate the agreement waits behind.
Every call recorded and summarised, every email from a linked mailbox threaded, and nurture sequences — discovery-day invitations, financing information, franchisee stories — running between calls, with replies read and the engaged candidates handed back with a next step.
A deal can be one unit, a multi-unit or area-development agreement with a schedule of openings, or the resale of an existing location to a new owner — each with the stages, documents and disclosure it needs.
A signed candidate becomes a location: the record, the territory, the agreement and the target opening date carry straight into the store-opening tracker, and the operations team picks up where development closed.
A typical single-unit pipeline. Brands rename and reorder the stages; the exit criteria are what keep the pipeline honest and the forecast real.
| Stage | What happens | Exit criteria | Owner | What the system enforces |
|---|---|---|---|---|
| Inquiry | A candidate arrives from a portal, broker, referral, ad or recruitment page | Contact made within the response target | Development manager | Source recorded; first-response time measured |
| Qualification | Capital, timing, territory of interest and experience assessed | Qualified with an application sent, or closed with a reason | Development manager | Closed-lost reasons required; unqualified candidates leave the forecast |
| Application and discovery | Application received; discovery calls; territory reserved | Application complete and territory reserved | Development manager | Territory reservation with expiry; overlap check on the map |
| Disclosure | FDD issued, receipt signed, waiting period runs | Receipt signed and the earliest signing date reached | Development manager and compliance | Registration check; waiting period; re-disclosure on change |
| Discovery day and validation | Discovery day attended; validation calls with franchisees | Attendance recorded; validation complete | Development team | Calendar event and attendance on the record |
| Financing and approval | Financing confirmed; checks complete; committee decision | Approved, with documents on file | Approval committee | Approval is a gate the agreement waits behind |
| Agreement | Agreement generated, signed and countersigned | Countersigned; fees received | Legal and development | Generated only when disclosure, territory and approval are all satisfied |
| Handover | The candidate becomes a location with an opening date | Opening tracker started; broker commission triggered | Operations | Location created from the record with nothing re-keyed |
The candidate, the timings and the source are illustrative; the sequence is how the pipeline is designed to run.
Week 0
The platform
A candidate submits an enquiry through a franchise portal listing. It lands in the development pipeline with the portal as its source and the development manager is notified. They call within the hour from the tracked number on that channel; the call is recorded and summarised against the candidate, who is qualified and sent the application.
Week 3
The development manager
The application is in. The candidate wants the eastern territory of a new market; it is reserved against them for 60 days on the map and shown as unavailable to two other candidates. The system confirms their state registration is current and issues the disclosure document from the record. The receipt comes back signed two days later and the clock starts.
Week 5
The development team
The candidate is invited to the monthly discovery day from the pipeline, the event sits on the network calendar, and their attendance is recorded. Three validation calls with existing franchisees are logged. The nurture sequence has been sending financing information between calls; a reply about a lender is flagged to the development manager.
Week 9
The approval committee
The financing letter, the background check and the committee’s approval are recorded with their documents. The waiting period ran out weeks ago and the territory reservation has three weeks left. The agreement is generated with the territory schedule from the map, signed by the candidate and countersigned the next day.
Week 9, the same afternoon
Operations
The record becomes the location. Its territory is sold, its opening tracker starts with a target date six months out, and the operations manager picks it up in the same platform. The portal that produced the candidate is credited with a signed agreement, and next year’s development budget has one more real number in it.
Most networks start with a general-purpose CRM, a spreadsheet, or the development manager’s inbox. The failures are the same each time.
The problem
Portal leads arrive by email, broker introductions by phone, ad leads in a form provider. They are copied into a CRM when someone has time. The ones that go quiet are the ones nobody notices, and the network paid to find every one of them.
What good looks like
Every channel lands in the pipeline directly — forms, portal emails parsed, tracked numbers per channel, broker portal — with the source recorded. A candidate with an overdue next step is on the follow-up list, not in an inbox.
The problem
Portals report enquiries; brokers report introductions; nobody reports signed agreements by source. The development budget is allocated on last year’s allocation and on which portal’s sales rep called most recently.
What good looks like
Cost per enquiry, per discovery day and per signed agreement by portal, broker, campaign and referral, from the source on the candidate record — so the budget conversation runs on numbers.
The problem
Disclosure is a PDF the development manager attaches to an email; the waiting period is a note in their calendar; the territory is a promise. A keen candidate, a keen manager, and the agreement is signed a day early or into a territory already reserved.
What good looks like
Disclosure and territory are stages of the pipeline enforced by the system. The document is issued from the record, the clock runs from the signed receipt, the territory is reserved on the map, and the agreement cannot be generated until all three are satisfied.
The problem
A candidate was introduced by a broker in March, enquired through a portal in May and signed in September. Two parties claim the commission, and the record of who spoke first is in three people’s memories.
What good looks like
The first source on the candidate record and the broker’s registration of the introduction are dated facts. The commission rule is configured once, and the answer is on the record before anyone asks.
The problem
Every “how is the pipeline looking” from the CEO or the board means an afternoon assembling stages, sources and a forecast from three places, and the numbers are different every time.
What good looks like
Candidates by stage and source, conversion between stages, days in stage and the forecast are a live view leadership opens themselves, and the scheduled weekly report carries the same figures.
The problem
Development closes the deal in its CRM; operations opens the location in a spreadsheet; marketing sets up the website in a third tool; finance creates the royalty account in a fourth. The territory is typed four times, differently.
What good looks like
The candidate record becomes the location record in the same platform, and the opening tracker, the CRM, the website, the reports and the royalty statement all run from it.
Development is a corporate scope of the same CRM, marketing, calendar and reporting the network runs on — a franchise ERP rather than a sales tool bolted to the side of one.
Contacts, companies, opportunities by stage, call lists, follow-ups and activity reports — the CRM every location uses for its customers — with a head-office scope for candidates, so development gets a full CRM rather than a pipeline add-on.
Web forms, tracked numbers per channel, call recording and AI call summaries, linked mailboxes and source attribution are the platform’s standard lead machinery, pointed at candidates instead of customers.
FDD management and territory reservation run inside the pipeline on the candidate record, so the development manager never leaves the CRM and the clocks are enforced where the work happens.
With the Marketing Automation add-on, email and SMS sequences by stage keep candidates warm — discovery-day invitations, financing information, franchisee stories — and AI reads the replies and hands the engaged ones back with a suggested next step.
Franchise recruitment pages on the brand domain, built and hosted in the platform, send applicants straight into the pipeline with their source, and the store locator shows candidates the available territories.
A signed candidate becomes a location in the same platform, and the store-opening tracker, the website page, the tracked numbers, the training and the royalty account are created from that record — in minutes, not in four systems.
A franchise development CRM is the pipeline a franchisor uses to sell franchise units: its records are candidates rather than customers, its stages run from enquiry through qualification, discovery, disclosure, discovery day, financing and approval to a signed agreement, its sources are portals, brokers, referrals and campaigns, and its key metric is cost per signed agreement by source. It differs from a customer CRM in its cycle length, its legal stages, its broker commissions and its handover of the signed candidate to opening.
In Gorilla Dash it is the same CRM with a corporate scope. Each location works its own customers; franchise development works its candidates at head office with its own pipeline, stages and reports. Leadership sees both, and because it is one platform a signed candidate becomes a location without re-keying.
Yes. Portal leads arrive by email, form or integration and are captured as candidates with the portal as their source; brokers and consultants register their introductions through a partner scope with access limited to their own candidates; referrals, advertising, events and the brand’s recruitment pages are captured the same way. Tracked phone numbers on each channel record the calls. Zapier and the open API cover portals without a direct integration.
Yes — disclosure is a stage of the pipeline. The FDD is issued from the candidate record, the receipt is signed electronically, the waiting period counts down from the receipt, re-disclosure is triggered by a new version or a material change, and the agreement cannot be generated until the clock has run. State and country registration is checked before the document goes out. FDD management is covered in depth on its own page.
A candidate reserves a territory from the development map inside the pipeline. It is shown as unavailable to other candidates, expires automatically if the deal stalls, and its schedule is generated into the disclosure document and the agreement when they sign. The map also shows development what is sold, reserved and available across the market.
Brokers and consultants are partners with commission terms on their record. The introduction is registered against the candidate with a date, and when the agreement is signed the commission is computed from the terms and recorded for payment. Because the first source is a dated fact on the candidate, disputes about who introduced whom are answered from the record.
Yes. Candidates by stage with the date they entered it, historical conversion rates between stages and the average time in each give a forecast of signings by month, and the slow candidates — the ones past the typical time in their stage — are listed so they are chased before they go cold.
Yes. A deal can be a single unit, a multi-unit or area-development agreement with a schedule of openings tracked against the map, or the resale or transfer of an existing location to a new owner, which runs through the same disclosure and approval stages from the existing location record.
The candidate record becomes the location. Its territory is marked sold, the store-opening tracker starts with the target date and the standard milestones, the website page, tracked numbers, CRM and training are created from the brand template, and the royalty account is set up under the agreement’s terms. Operations picks up in the same platform development closed in.
The CRM, lead capture, call tracking and reporting the development pipeline runs on are part of the Gorilla Dash base platform at USD $52 per location per month with unlimited team members, so brokers and the whole development team can work in it without per-seat licences. FDD management, territory mapping and the store-opening tracker are part of the development and compliance module — talk to us and we will scope it with you.
Bring your stages, your portals and your brokers and we will walk a candidate from enquiry to a signed agreement, with disclosure and territory inside the process — book a demo with our team.
Book a Demo