Which channels produced revenue, unit by unit?

A franchisee paying two per cent of revenue into a national fund reasonably asks what it produced in their market. Impressions and reach are not an answer, and the absence of one strains the relationship.

Because each location's sales file is matched independently and reported per unit, the national fund can be shown to have produced specific revenue in specific territories — or shown not to have, which is equally worth knowing.

Rolling out call tracking or tag management across two hundred independently owned businesses is an operational problem that rarely finishes.

There is nothing to install. Each unit exports its sales, the franchisor supplies the campaign data, and every location is measurable from the first month — including the ones that joined last week.

Many disputes about a national fund are really disputes about routing. A lead generated by a national campaign lands with one unit, the customer later buys from a neighboring one, and both units conclude the fund worked for somebody else. ZIP code boundaries overlap, customers move, and a franchisee who watches inquiries arrive while revenue appears elsewhere decides the advertising does not work in their territory. Nothing in a lead report can settle that, because the lead report ends at the handover and the sales file belongs to whoever closed the business.

Matching each unit's own closed sales against the central campaign data resolves the argument by making both halves of it visible. Where the national fund produced revenue in a territory, that unit's report shows it. Where an inquiry was routed to one unit and the revenue appeared in another's file, the match follows the customer rather than the routing rule, because the customer's contact detail is what both files have in common. That may be the first time anybody in the network has seen what actually happened to a lead after handover, and it ends the argument faster than any policy.

There are two honest ways to organize a network, and they answer different questions. In one workspace, a unit column mapped as Location shows every unit's revenue and how much of it traces to a channel on one page, but everyone with a seat in that workspace sees all of it. On the Agency plan, each unit can instead be its own workspace — up to ten, sharing one monthly record allowance — with each franchisee invited only to theirs, so the isolation is real rather than a filter. That matters in a network of independent businesses that occasionally compete for the same customer. Separate workspaces are not combined into a group view: head office reads each one in turn, which is the price of separation that is real.

A franchisor runs two marketing operations that are nearly always reported as one. Customer acquisition produces revenue in units. Franchise development produces new franchisees, and a single one of those is worth an initial fee, a territory's future royalties and years of system revenue. They compete for attention, are sometimes handled by the same people, and are measured with the same inquiry counts despite being separated by two orders of magnitude in value. A quarter with forty customer inquiries and one signed franchisee looks like a poor quarter on every dashboard the group runs.

Kept in separate workspaces, each gets its own revenue file and its own answer. Development revenue — the initial fee and the royalties that follow it — credits the channel that produced the candidate, which for franchise recruitment is usually a long quiet path through portals, broker networks and content that no advertising platform holds together. The gap between a first inquiry and a signed agreement in this funnel runs to quarters and sometimes years, with no window to expire in between, so the signature credits whatever actually produced the candidate rather than whatever ran last.

Keeping them apart also protects the customer-side reporting. Franchise recruitment spend is lumpy and expensive per inquiry, and folding it into the same report drags every customer-acquisition metric in a direction that has nothing to do with customer acquisition. Two workspaces — on the Agency plan they draw on one monthly record allowance but keep entirely separate data — mean neither set of numbers contaminates the other. It costs no extra effort, because the two revenue files come from different systems and different people anyway. The only discipline needed is deciding which workspace a campaign belongs to before the spend starts.

A system-wide figure is the least useful number a franchisor can publish. Units differ in market size, tenure, staffing, competition and how well they answer the phone, and a channel producing excellent results in a mature territory can produce nothing at all in one that opened last year. The average sits between them and describes neither, while being quoted at every conference as though it described both. Franchisees know this, which is exactly why the average persuades nobody who is paying into the fund. A per-unit breakdown persuades because it is about their own customers.

The variation itself is the most useful output. Where the same national campaign produces strong revenue in six territories and nothing in four, the question stops being whether the fund works and becomes what the six do that the four do not — response time to an inquiry, opening hours, quoting practice, local follow-up. Those are operational answers and they are worth considerably more to a network than a change of media plan. A report that only ever produced one number could not have raised the question; one read unit by unit raises it on the first page.

New units are covered from the day their data exists. Nothing had to be installed while they were opening, so a location trading for six weeks can be measured across those six weeks, and one that joined last year can be measured across its whole first year retrospectively. For a growing network that is the difference between a reporting system which only works for established units and one which works for the units most in need of help. The mapping for a new unit's export is confirmed once and remembered, so onboarding takes minutes rather than an IT schedule.