FlagshipOne of seven built for franchise development

The Morning Brief

One short list, before the day starts, of what is overdue, what is at risk, and the few things that genuinely need the CEO or the operator.

Tier
Flagship
Build order
5th of 5 on the franchisor track, and 3rd of 3 on the operator track
Shape of it
8 steps, 1 decision point, 1 escalation rule
At launch
Runs supervised, with you approving what goes out

The problem this solves

For the franchisor: the CRM shows candidates, the operations platform shows units, neither shows that four qualified candidates have had no contact in two weeks, that a discovery day cohort has had no follow-up, that an FDD waiting period expires Thursday, or that an opening has slipped past its escalation threshold.

For the operator: the POS shows sales, the brand portal shows compliance, neither shows that a unit's labour has drifted three days running, that a GM recruitment for a unit opening in nine weeks has not started, or that a draw is due.

How it works, step by step

Every wait, threshold and branch below is a value we set with you during the build, against your stages and your language. None of it is a default we impose.

  • What starts it
  • It decides something
  • It escalates to a person
  1. Step 1Trigger

    Every morning, one brief, ordered by what needs a decision.

  2. Step 2Escalation

    Franchisor, needs the CEO now: an FDD compliance date approaching, a high-value candidate stalled past escalation, an opening slipped past threshold, a franchisee in difficulty during their first ninety days.

  3. Step 3

    Franchisor, overdue: candidates without contact, discovery day follow-ups outstanding, validation calls not completed, onboarding milestones late.

  4. Step 4

    Operator, needs the owner now: a unit exception outside threshold three days running, an opening milestone at risk, a financing or draw date, a manager vacancy against an opening date.

  5. Step 5

    Operator, overdue: compliance submissions, period-end items, staffing pipeline behind lead time.

  6. Step 6

    Failed, and why: integrations errored, messages undelivered, data feeds missing.

  7. Step 7

    Nothing self-reported. Every line traces to an event.

  8. Step 8Branch

    If there is nothing to raise, one line says so.

How it gets built

Built inside what you already run

  • FranConnect
  • ClientTether
  • Naranga
  • Salesforce
  • HubSpot
  • or whatever your office already runs on

Nothing to log into and nothing to license. If a system needs a record your platform does not hold, we add the field to your platform rather than starting a second one beside it.

This is the actual build order, in the phases its own steps fall into. It runs in supervised mode first, with you approving what goes out, until you are happy with the tone.

  1. Agree the rules with you3 of 5 steps
  2. Build and connect it1 of 5 steps
  3. Prove it before it runs alone1 of 5 steps
  1. 1

    Agree

    Agree what genuinely requires the decision-maker, and be strict.

    The thresholds, the wording and the names are yours. We write them down with you and get the consequential ones signed off.

  2. 2

    Agree

    Set thresholds per metric and per candidate value.

  3. 3

    Build

    Build exception queries against system event data.

    Built inside the software you already run, against your stages and your language.

  4. 4

    Agree

    Set send time.

  5. 5

    Prove

    Review weekly for a month and cut every line not acted on.

    It runs with a person approving what goes out until you are happy with the tone. Nothing sends unreviewed on day one.

What changes after it goes live

How it runs today

For the franchisor: the CRM shows candidates, the operations platform shows units, neither shows that four qualified candidates have had no contact in two weeks, that a discovery day cohort has had no follow-up, that an FDD waiting period expires Thursday, or that an opening has slipped past its escalation threshold.

After this one is live

Problems surface at a day old. Compliance dates stop depending on a spreadsheet. And the decision-maker stops finding out last.

How to measure whether it worked

Your arithmeticRun with your numbers, not ours

No revenue calculation and it should not be given a fake one. Ask what one late-discovered problem cost; a franchisor will name a candidate or a compliance date, an operator will name a unit.

We agree the baseline before anything is built, and we do not take credit for things that were going to happen anyway. There is no figure on this page claiming what we have produced for somebody else, because there is no verified figure to publish.

What we will not do

This is from the same delivery document as everything above it. It is on the page because a supplier who has not thought about it will not tell you, and you would find out later.

Earnings claims are the hardest line in this series and it is a legal one.

  • Under the FTC Franchise Rule, any representation about actual or potential financial performance of a franchise is an item 19 financial performance representation, and a franchisor may not make one outside its FDD.
  • No system, message, template, dashboard or automated communication may state, imply or infer what a unit earns, could earn, or typically earns. That includes automated content sent to candidates, and it includes anything a system might assemble from real unit data and surface to a prospect.
  • System 6 handles real unit-level financial data for an operator. That data must never reach a candidate-facing system. The separation between the franchisor development systems and the operator reporting systems is a compliance boundary, not an architectural preference.
  • Every candidate-facing template requires review by the brand's franchise counsel before it goes live. No exceptions.

FDD timing is a legal deadline. Delivery, receipt and the mandatory waiting period before signature are regulated. System 3 tracks them as a record, and that tracking must be built with counsel and must not be treated as legal advice or as a substitute for the brand's own compliance process.

State registration. Several states register franchise offerings and regulate franchise sales communications. What may be said, and by whom, differs by state. Automated candidate communication crosses state lines by default.

Franchise agreements bind the operator. Before any operator-side system is designed, confirm the agreement permits parallel systems and data extraction from brand platforms. Some prohibit both.

Messaging. TCPA and CAN-SPAM apply. Consent per number, quiet hours in local time, immediate opt-out across every system.

Nothing here is legal advice. Franchise law is federal and state, it changes, and the penalties for earnings-claim violations fall on the franchisor personally as well as corporately.

Nothing here is legal advice. Rules in this area have moved more than once recently, and every template that states a commercial term or a guarantee goes to your own counsel before it goes live.

The full set

Seven systems forfranchise development.

We build one at a time and prove it moved before starting the next. The tiers are the dependency order, not a price list.

Tier 1Foundational

Nothing arrives late or unowned. These come first because everything above them assumes they are true.

  1. 1Candidate Capture, Qualification & Instant Response
  2. 2The Not-Ready Candidate Pipeline

Tier 2Growth

The recoverable money. These work the pools the foundational systems have made visible for the first time.

  1. 3Discovery Day & Validation Control
  2. 4Franchisee Onboarding & Opening

Tier 3Flagship

One connected system end to end, plus what the owner reads on a Monday. Only once the pieces are proven individually.

  1. 5Multi-Unit Opening & Expansion Control
  2. 6Multi-Unit Consolidated Operations & Reporting
  3. 7The Morning Briefyou are here

The tiers are the dependency order for franchise development, not a price list. Most firms do not start at the first one, because the order is a default and the call is where it gets changed.

A note on sequencing this trade

Do not sell both to the same organisation at the same time. A franchisor also operating corporate units has both problems, and the temptation is to combine them. They are different teams, different systems and different timelines, and combining them is how an engagement stalls.

Sequencing note. For franchisors, Systems 1 and 2 together are the entire first pitch. Lead source truth plus a worked not-ready pipeline usually recovers more than the engagement costs, and both are visible within a quarter, whereas System 4's results arrive only when a unit opens.

Back to the franchise development overview for the stage map and where these fit.

Is this the oneyou need first?

Often it is not. On the call we look at what is actually costing you most right now, which is frequently a different system from the one that brought you to this page. If there is nothing worth building yet, we will say so.

Fourteen questions, about seven minutes. No price, no purchase, and nobody calls you unless you ask them to.

Application1 / 14

Next question: where we send what we prepare.