Centre of Franchise KnowledgeExpert interviews

Franchise Technology: Twenty Years of Building It, and No Sales Pitch

Tom Hill, FranchiseAir's technical director, on twenty years of building software for franchise networks: the state networks arrive in, why franchisees resent head office's system, who holds the customer data when a franchisee leaves, the nephew who builds your system, what AI is safe for, and the mistake that turned a three-month project into two and a half years.

Tom Hill

Tom Hill

Technical Director and Co-founder, FranchiseAir

31 min read Interview by Tony Johnston

A conversation with Tom Hill, technical director and co-founder of FranchiseAir. Interview by Tony Johnston, FranchiseAir.

This one is different from the rest of the series, and we should say so first. Every other guest has been an outside expert. Tom Hill is one of us: he co-founded this company with Tony in 2005, he is our technical director, and he usually sits on the other side of these interviews as co-host. We sell franchise software, so on this topic we are not neutral, and you should read what follows knowing that.

We ran it anyway because twenty years of watching franchise networks buy, build, abandon and replace software is a view that’s hard to get from anywhere else. The rule for the series still applies: the conversation is about franchising, not about our products, and none of ours is named. Tom is also plain about his own trade. “The software world is very good at promising and it’s slightly less good at delivering” is his line, not ours, and the last third of the conversation is about how a franchisor protects themselves from exactly that.

Tom Hill of FranchiseAir
Tom Hill, technical director and co-founder of FranchiseAir.

The full conversation — 33 minutes.

In this conversation

  • The three states a network's technology is in when it first asks for help: nothing but spreadsheets and a paper diary, a general-purpose system bent to fit, or a bad experience with another supplier
  • Why a general CRM struggles with franchising: head office sees everything, but "franchise A doesn't see franchise B's data"
  • Where the return is: turn five hours a week into one, and the four hours saved per franchisee "compounds"
  • Why franchisees resent a system that only gives head office visibility, and the cheapest way to win them over: "that thing you used to do, you don't have to do any more"
  • Who holds the customer list when a franchisee leaves, and why "all of the legal terminology in the world" doesn't help if the data sits in an account that head office can't open
  • The nephew who builds your system: a good idea "right up until the point that the guy goes on holiday"
  • Why a home-built system is still worth having when you move on from it
  • AI in three tiers: go ahead, go ahead but have someone who knows check it, and "hell no"
  • How a software team uses AI itself: treat it like a junior programmer, and review everything
  • The expensive mistake: a three-month project that took two and a half years, because nobody had written down what it was meant to do
  • Three lists to write before you speak to any software company: the deal-breakers, the nice-to-haves, and what it doesn't need to do

Twenty years of building software for franchises

Tony: Hello, I’m Tony Johnston of franchiseair.com, and today we’re going to do quite an unusual interview. That is because the interviewee is my colleague and co-founder of our business, Tom Hill. Now, the reason we’re going to interview Tom is because we’re going to talk about technology, and I don’t know anybody better at technology in franchising than Tom. In fact, I’d be hard pushed to find anybody better at technology, but he’ll blush when I say that. Anyway. Hello, Tom.

Tom: Hi there.

Tony: So why don’t you tell us a little bit about your background? Obviously, I know all about you, but why don’t you tell everybody a little bit about your background in technology and franchising?

Tom: Well, I’ve basically been building software for franchises for probably around twenty years now, which seems an awful lot when you put it that way. I came out of university, did a bit of work for other companies and then started a company with Tony, and we’ve been working in the franchise space ever since then. As part of that, we’ve built bespoke systems and out-of-the-box systems for a whole heap of networks across all sorts of businesses. So we’ve pretty much seen it all, I would say, in twenty years. And I’m hoping to be able to explain a little bit about what we’ve seen people do well, what we’ve seen people do badly in that time, and also what we’ve seen computer companies, ourselves included, do well and badly.

Three states a network arrives in

Tony: Okay, excellent. So let’s start at the beginning. If we get a prospective franchise customer, what do you usually see in their technology? What is the state of their technology when you first come across them?

Tom: I’d say they generally fall into one of three categories. At the start, the people who are literally just starting out, we get people who are coming to us with nothing. So they’re either using spreadsheets or they’re using some form of single-user technology, something like a phone or a paper diary. These are normally smaller-end customers who are realising that, as their network is growing, having that sort of single-user technology doesn’t give them the visibility that they’re going to need. And also it doesn’t give them any form of automation that can be repeated.

The other thing that’s worth mentioning is that nowadays, with most franchise networks, when somebody comes to buy a franchise, they expect some form of technology in place. So that’s another reason people come to us. When they’re trying to sell this to their second, their third, their fourth franchisee, if the franchisee turns up and says “right, how do I do my job?” and the answer is “well, get a paper diary and here you go”, people look at that and they don’t see it as very professional. So that’s, I suppose, the early-stage franchisors.

If you’re talking about the people who come to us once they’ve actually got a few franchises up and running and they’re a bit more established, there are two sides that we tend to see. The first one is people who have tried to bend a non-franchise system to the franchise model. In other words, you might go out there and you might find a generic CRM. I’m not going to name them; there are tons of them out there. And you might think “well, okay, this is a decent CRM, so why don’t we try and make it work for franchises?” What you find is that franchising has a very specific security model. You need that concept of head office getting the visibility of everything, but it’s very important that franchise A doesn’t see franchise B’s data. And generic systems don’t generally handle that very well. You also have problems with things like: what happens if you have to terminate one of the franchisees? Where does the data live, and all that kind of stuff. So twisting a generic system, a non-franchise system, into the franchise model can be a lot more work than it seems. We quite often get people who have tried it and just found it clunky. So they come to us and say “we need something specific.” But they generally then have some idea, at least, of what they want, because they’ve spent some time with software before.

The third category is, I suppose, the one that I find slightly saddest, which is the people who have come to us from other vendors and they’ve had a bad experience. Sadly, the software world is very good at promising and it’s slightly less good at delivering. So we do see a lot of people who are migrating from systems where they’ve been oversold something, or alternatively where it’s been built by a mate of a mate who knows technology, and they’ve then realised that they actually do need professional support for this, because it’s running their business. So those are probably the three main categories, I’d say.

The problem they think they have

Tony: One thing that interests me is the problem that companies think they have versus the problem that you find they actually do have, and the solution they need. Is there always a match there? And if there isn’t, tell me about one.

Tom: There is a mismatch, I think, is the honest answer, because a lot of what you see in terms of sales stuff talks very much about generic needs: CRM, marketing, all that kind of stuff. Whereas the reality is that where the time goes in a franchise business is quite often operational. What you’re really looking to do, and this is what we always recommend to people, is what used to be called time and motion. You need to have a look at your business and go “where are we actually spending our time? And of that time, is there anything that we could automate?” Because that’s where your return on investment is. If you can take something that a franchise spends five hours a week on, and you can turn that into an hour a week with technology, then all of a sudden that four hours a week that each franchise saves compounds, and it adds up. Every year after that, you’re saving that time every single week. And the value of software that can do that is enormous.

So what you often find is there’s generic software out there to do some of the standard stuff, a customer list, that kind of thing. But if you are a franchise and you have a very specific business model, whatever it might be, house-sitting for cats, you have a process that you go through, and you have to follow that process each time, because that’s the whole point of your franchise. You’ve built this business model. You want your franchisees to follow the same process that you’ve been following, to make sure you get a consistent service to your customers. Well, if you can build that into the software, then you lose all of those problems of “are they doing the right thing? Are they doing it well?” You can build in all the steps that you normally follow yourself, to make sure they’re right.

Why franchisees resent head office’s system

Tony: Okay. So looking at the next step, once people do get a system, do you see problems of take-up, problems of understanding amongst the franchisees of what this is all for, and getting the benefit from the system?

Tom: Yes. The biggest problem is that head office doesn’t always think, when they’re building software, about what the franchisees are getting out of this. If as a franchisor you focus entirely on what’s in it for you, “I get this visibility, I get the control” and all the rest of it, and you don’t give the network a reason to want to use it, then all they see is “I’ve got to do a bunch of admin work for no apparent benefit to me.” That doesn’t necessarily mean they won’t use it, because when it comes down to it, you can tell them that they have to. But if you just enforce something like that, it’s going to build a bit of resentment in the network.

When it’s done well, it’s a collaborative thing, where the franchisor talks to the franchisees and says “right, look, we’re thinking about getting a software system in place. Which parts of your day-to-day business take a lot of time, where you think: actually, this should be automated, I shouldn’t be typing this in multiple times, or I shouldn’t be having to sync this system up with this system manually? Is there a way that we can get this all to just work fluidly?” If you can take time off their business which is purely admin overhead, and nobody likes admin, nobody likes filling forms in, if you can take that off their plate, then all of a sudden you get buy-in for the software system.

Even with the visibility stuff, that does tend to happen a little bit. Most franchisors want visibility of sales metrics from their franchisees. And if they don’t have a software system, right now they’re probably getting their franchisees to fill in a spreadsheet every month with a whole bunch of numbers. The franchisee’s got to pull those numbers together and fill them in. If you can build the software system to automate that, then that is automatically one tick. It’s “look, you don’t need to fill in that spreadsheet any more. It just comes to me automatically. You don’t need to do anything.” Anything like that, where you can say to the franchisee “that thing you used to do, you don’t have to do any more”, or “that thing that used to take you two hours now takes you thirty minutes”, well, that gets you buy-in, and it gets you a lot of points from the network.

Tony: So it’s quick wins for the franchisees?

Tom: Quick wins, yeah. Obviously, head office needs to think about what’s most important for them. All I’m saying is: don’t underestimate the goodwill you get by making sure that it actually works for the network, versus just enforcing something over their heads.

Whose data is it when a franchisee leaves?

Tony: Okay. Now, turning to something you mentioned in passing there: customer data. Sounds boring, but let’s say a franchisee leaves or sells up. What happens to customer data, and what issues do you see with customer data?

Tom: It’s actually two questions that you’re asking there. One is who’s got the legal right to the data, and the other is what happens with the technology. And strangely, in this one, the technology part is probably easier than the legal part.

In terms of legality, obviously you’ve got GDPR in this country and other data privacy laws around the world. The concept of that is that the person whose data is being stored needs to know who owns that data. So when you sort out your agreement with the network, clearly, as a franchisor, you generally want to keep control of the customers in case you have to kick out a franchisee because they’re not performing. If somebody sets up as a franchisee in London, and that franchisee is not doing well, but they’ve got a customer list of several thousand customers: if the franchisor decides they want to terminate that franchisee because they’re not hitting their performance targets, they want to keep that customer list. They don’t want it to disappear into the ether. That’s something they’ve spent a lot of time building up, the marketing and all the rest of it. So legally, and this is where having good advisors comes in, they need to make sure that their agreement with the franchisee says that all of the customer data in the network is owned by head office overall. That way, from a legal perspective, when the franchisee heads off out the door, that data is yours. That’s fine.

The trickier part, to some degree, is if you go down the route that some people do of getting individual software systems, so each franchisee goes off and signs up for their own CRM system. Then all of the legal terminology in the world doesn’t change the fact that their data is sitting in a system that you don’t have access to.

Tony: Have you seen a situation where the tech and the agreement disagree?

Tom: In that situation, yeah. When people have gone off and got their own account. Just giving an example, and we’re not going into specific ones, let’s say every franchise has their own Stripe account, or they’ve got their own Xero account, or something like that, to deal with financials, and that franchise leaves. Well, unless you’ve got a login to that system, that data’s gone. You could go and speak to Xero and say “hi there, I’d like access to it”, and they will say “no, our contract is with the franchisee who’s just left. You can’t have access to it. That’s not how data protection works.”

That’s one of the reasons why systems that are designed specifically for franchises, rather than individual pieces of software like that, are quite important. If you contract with a franchise software provider, the contract is between head office and the software provider. If the franchisee leaves, you just disable their access, but you still have access to all the data, because the contract is with you, not with the franchisee. So it’s a case of making sure that your legal terms and your technology are in agreement as to who owns that data.

The nephew who builds your system

Tony: Okay. Now, turning to another potential pitfall, or not: founders who build their own system. Here I’m thinking of the nephew who builds your system, or your mate who’s pretty good at software. Tell me what generally happens in those situations, and whether it’s a good idea.

Tom: It’s an interesting one, is the honest answer. In theory, it sounds like a great idea, in that if you’ve got somebody who can build software and can get you something going, then you can get up and running quite quickly. It’s somebody that you already know, you have that relationship, and you’re not going out there trying to find a company and trying to do due diligence to work out whether they’re actually any good. As I say, there is quite a lot of overselling in the IT world, so determining what is actually a good system versus what is a bit of vapourware can be quite tricky.

So having somebody you know sounds like a good idea, and it continues sounding like a good idea right up until the point that the guy goes on holiday. Then you discover that he’s in Bali for two weeks, he hasn’t got an internet connection, and your system’s just fallen over. Because he’s not a software company, he doesn’t have on-call support or any of the rest of it, and you’ve now got no operational system for running your business for the next five days, until he gets back off his plane.

That tends to be what we see. It can actually be useful for building almost a sort of prototype, which helps you understand what it is you’re trying to build. But what we generally find is that as companies get bigger, they realise that what you’re paying software companies for is partly the expertise in building things, but it’s actually because they have the support and the help available to deal with “what happens if this falls over?” or “what happens if I need you to do something urgently?” I need to be able to get in touch with somebody. You wouldn’t run the rest of your business that way, and so generally we would recommend people don’t do that for technology either. If you were a shop and you needed new shops, you wouldn’t turn round to your mate who’s done a bit of DIY and say “I need a new shop in London, can you go and build me one?” So we generally recommend not doing the same with technology.

Moving on from a home-built system

Tony: Let’s say somebody already has done that. How would you get beyond it? Say they’ve encountered that problem, the niece or nephew’s gone off to Bali, and the owner realises perhaps now is the time to change to a bigger vendor.

Tom: To some degree they’re in a really good position, because they already have a system. They already know what it does well, they know what it does badly, and they know what it’s missing and what they’d like to add, because they’ve run with it for a bit. One of the harder points in technology is that if you’re starting off with a blank sheet, it can be difficult to see in your mind’s eye how it might look, how it might work, how it might help things for you. Whereas it’s very easy to criticise an existing system. You can turn up to a software provider and say “look, we’ve got this. This bit’s good, this bit’s awful, oh God, I wouldn’t do it that way again if I had my chance, we need to swap this, we need to do this.” It’s much easier.

And because you can put it in front of the technology company, they find it much easier to work out what the scope of the product is. If you’re starting from scratch, one of the harder problems in technology is that every time, a technologist needs to learn how your business works. It’s almost like we have to be a new employee in your business and understand: what are the steps you go through when you’re doing invoicing? What are the steps you go through when you’re doing your jobs? We need to understand that before we can build the software. If we’ve got something that’s already there, it’s a lot easier, because we can go “oh, right, I see. So you’ve got a list of these things, you filter them down, then you click on buttons there and you do this. Right, okay, fine.” That makes it a lot easier to spec up and cost up how much it’s going to be to migrate from one to the other. And generally, if the software has been relatively well built, it’s fine to extract the data out and migrate it across into another system.

Tony: So at least there’s a silver lining.

Tom: There is, yeah.

AI in three tiers

Tony: Well, turning to a technology that has good and bad in it, and its implication for franchising: AI. I know you work a lot with AI. Tell us how you see AI impacting on franchise software, on the industry and so on.

Tom: It’s an incredible technology. It’s moving on practically every week, and making it virtually impossible to keep up to date, as a technologist, with what’s going on. From the point of view of franchising, people say “what should I use it for?”, and I think I would rate things, when I’m thinking about AI, in three tiers.

There’s stuff that I would just happily let it loose on, no problem. There I’m thinking about anything that I would consider low-stakes text generation. When I say low stakes, I mean something where, if it gets it wrong, worst case, you’re going to look a little bit foolish. You haven’t got any legal liability, you haven’t got any financial issues caused by it. Classic example: you want to generate a set of social media posts themed around holidays, Easter, Christmas, all that kind of stuff, to go out over the next three months. You can sit there and type them yourself, or you could give an AI system context on what your business does, what sort of products you offer, and just set it off and say “I need a bunch of social media posts themed around Easter, then I want one themed around Valentine’s Day”, so that I can hand those out to my franchisees and say “here you go, here are some pre-made posts that you can use over the next three months or so.” There’s virtually no risk to that. It will churn them out, it will do a good job, probably a better job than you necessarily will at checking it and making sure it’s all right, and it will do it vastly faster than you could. So for me that is very much the “yeah, just go ahead” tier of AI. Anything like that: marketing copy, even suggested email responses to things. That sort of stuff I don’t have a problem with.

There’s then a second tier, which is “yes, go ahead, but understand the caveats, and run it by somebody who knows afterwards.” There I’m talking about things like policies, procedures, contractual changes, that sort of stuff. It’s good, but you need to understand its limitations, which is that this thing doesn’t really fully understand your business, and it doesn’t necessarily fully understand the regulatory regime that you’re working in. A lot of AI comes from the USA, so unless you give it a lot of context, what you can see is it referring to laws and regulations that don’t exist in this country. I’ve got a friend who does HR, and they regularly see things that have come from AI which refer to a law that is only relevant in California, because people have just dumped it into ChatGPT and said “I’m having this problem with my employer, please write me a letter”, but not specified that they work in the UK. So it’s picked up some random US laws and stuck those into a complaint letter. For that sort of stuff, what I would recommend is: yes, use it, but use it as a way of reducing the amount that you might need to spend on a lawyer. You still need to run it past a lawyer if it’s a contract, just to make sure that it’s got it right. But you might want to use it to structure what you’re thinking of putting in there.

Then you’ve got the “hell no”. For me that’s anything to do with financials, agreeing financials with the customer in particular, and also anything that connects it directly to anything you’re not willing to have completely destroyed. AI at the moment is very new, and the guard rails basically just aren’t there. We see in our industry, every few weeks or so, another story of a company that has connected an AI agent directly to their production systems, the concept being that if any errors occur, the AI system sees the errors, goes off and works out what the error is, and tries to fix it. Unfortunately, the reason we see these stories in the news is that quite often it decides that the simplest solution to the problem is to delete the production database and rebuild it from scratch. At which point, yeah, customers are not too happy about that as a solution. And financials, for example: it can do analysis on financials, but you have to check it with a fine-tooth comb, because it hallucinates numbers, and you don’t want to be sending financial numbers to your tax people when you’ve run them through AI and not checked them. So those, for me, are the three levels of AI. You can do some stuff without any worry, and some stuff you shouldn’t touch.

How a software team uses AI itself

Tony: Right. And pushing you on your own use of technology as a technologist: where are you at, for those listening, and what are the trends you’re seeing in terms of code creation, technology creation, that sort of thing?

Tom: Code creation: it’s fantastic at syntax. This is what we’re talking about again on the “check, don’t just launch it”. We would never attach one directly to any systems, for the reasons I’ve already discussed, which is that it’s just too risky. You have no visibility of what it’s going to do. You can put in rules that try and stop it, but they are remarkably creative about getting around rules. If the goal is to fix a problem and they’ve found something that’s got in the way, they will quite often work their way around it. And obviously, if that rule is there to protect your customers' data, then that’s not a good thing.

On the code creation side of things, if you just let it loose, you end up with a ball of spaghetti. But if you work with it like you would with a junior programmer, then it’s fantastic. In a lot of programming, what happens is you spend a lot of time trying to work out how a piece of software should work, and once you’ve designed that nicely, there’s a load of busy work. By busy work I mean just making the computer happy with what you’ve written: making sure all the semicolons are in the right place and the syntax is right. Then you realise that the structure is not quite right, and you’ve got to do what’s known as refactoring, which is basically like redoing an essay. You move some chunks around and put things in different places, because it makes for a cleaner architecture in general. And that is just typing. It’s annoying, it’s boring, it’s just work that you have to do, because if you don’t do it, the computer won’t accept the code that you’ve provided.

So the great benefit of AI for us is that it pushes up the amount of time that we can spend thinking about the higher-level stuff. How do we make this maintainable? How do we make this run quick? How do we make this friendly for the user? It increases the amount of time we can spend on that by decreasing the amount of time we have to spend on boring busy work. We generate a lot of code, but we still review it all, to make sure that it hasn’t done anything nasty. What we’re looking at then is not so much “is the syntax right?”, because frankly it’s better at syntax than I am, probably because it’s seen eight million billion lines of code. What it’s not as good at is “actually, we already have something that does some of this, so why are we introducing a second copy of something that’s nearly already done in this part of the system? What we should do is pull that out into a single shared thing, so we’re not duplicating code in two places.” That sort of stuff is where the human in the loop is still way better.

The expensive mistake: they will say yes

Tony: Okay, interesting. So, turning to something less complicated and quite fun, my final question. You mentioned earlier on that technology occasionally over-promises and under-delivers, things like that. What’s a good example of an expensive mistake, and what happened?

Tom: The biggest mistake that I think anyone makes, and it is relatively common, is going in without a good idea of what you want. If you go to a software provider and you ask them whether a piece of software can do something, they will say yes. What they don’t say is “yes, if you pay us enough money”, but that’s what they mean, bluntly. And that means if you come with something which is vague, they will say “oh yeah, our software can do that”, because you haven’t given them enough detail.

Let’s take a very simple one, which could be anything from a couple of hundred quid to hundreds of thousands of pounds. If you say “can your software integrate with our accounting system?”, you could mean anything from “can you export a CSV file of customers that I can import into Xero?”, a matter of ten minutes’ work, it’s not complicated, to “I want full bi-directional integration. The moment anything changes in Xero, I want that reflected on my franchise system, and vice versa: the moment I do anything on that system, it needs to go to Xero. I want to be able to view accounts across all of my franchises direct from Xero”, all this kind of stuff. And that’s a much bigger problem. So when people come to you with a single bullet point that says “must integrate with Xero”, a software provider can give you a tick. But whether that tick is what you actually mean is another matter, if you haven’t specified it in detail.

A classic example was somebody who came to us initially and said “look, I’m looking for a new product”, and they gave us a very, very vague overview. We said “look, we’re not going to build that or quote you on it unless we sit down with you and turn it into something more concrete, because right now that could be anything from a very small number to a very big number. It’s just not detailed enough.” Unfortunately, one of our slightly less ethical competitors just went “yes, we can absolutely do that for you.” So the customer came to us and said “right, we’ve decided to go with somebody else. They say it’s going to be a three-month project.” That project wasn’t finished for two and a half years, and a lot of money. And it was solely down to the fact that before they went into it, they did not know exactly what it was that they wanted to build. So it started off as three months, and then they identified a few more things that it needed to do, and then it got to six months. And of course by the time it gets to six months you’re thinking “well, I’ve already spent quite a lot of money on this.” It’s the old sunk cost fallacy: “I can’t drop this now, we’re nearly there.” Then that becomes nine months, and it becomes twelve months. And at the end of it all, they ended up with a system that they didn’t actually like, which is also common if you haven’t specified it up front, because you’ve effectively built it by incrementally trying to fix problems with what you’re seeing, rather than having an overall view in your mind of what it should do.

Three lists to write first

Tom: So what I would recommend to any franchise is: before you start talking to a software provider, sit down and get clear in your head what it needs to do. The absolute deal-breakers. If you go to a software provider and say “it needs to do this” and they say “well, we can’t do that”, then that’s just an automatic no. It makes it very easy to get rid of software that you shouldn’t go forward with.

Then you want the stuff which is nice to have but isn’t a deal-breaker. So you can say “does it do this?” “Yes, it does.” Well, great, that’s a plus point in your favour. “No, it doesn’t.” Oh well, such is life. It’s a bit of a pain, but it’s not going to kill us.

But strangely, the one that I would flag up as possibly more important than anything is: what doesn’t it need to do? Because if you go to a software provider and you tell them how your business works, they will try and build everything in your business. But you won’t get a return on investment on a lot of it. What I mean by that is that there are things in every business which are exceptions. They build up over time. In twenty years, I would say that 99.9 per cent of our customers are billed in the same way, and then there’s 0.1 per cent which we signed up in year one, twenty years ago, and we agreed with them that they could pay every six months on the third Tuesday in Lent, or something along those lines.

Tony: I know the one, yeah.

Tom: For no apparent reason. And of course we still have to follow that now. Now, is it worth building that rule into a software system? No. It takes five minutes a month. The cost to implement it, to build that complexity of rule in, would just not be worth it. The same occurs in virtually every franchise system. There will be exceptions to every rule, and you could try and build a piece of software that would handle them. But much more sensible is to tell the software provider the point at which you’re not bothered any more. “Look, yes, we have these weird exceptions. We will deal with those manually. As long as there is a way that we can invoice that customer manually every month, that’s fine. We do not need to build in a scheduling system which deals with this one weird exception.” Because if you don’t, they will build in a scheduling system that will handle it, and it will be vastly more expensive than it needs to be.

Tony: Excellent. Well, Tom, that’s all great advice and analysis on technology. I think we’ve covered pretty much everything. I won’t ask you to say what your website is, because it’s the same as mine, which is franchiseair.com. So thank you, Tom.

Tom: You’re welcome.

Tony: And yeah, look forward to the next one. All right, bye.

Tom: Cheers, bye.

Recorded over Microsoft Teams on 17 November 2026. Transcript lightly edited for clarity.

FranchiseAir

Tom Hill is technical director and co-founder of FranchiseAir. He and Tony Johnston met at Newcastle University and started the company in 2005, and he has been building software for franchise networks ever since, both bespoke systems and ready-made ones. He usually co-hosts this interview series. FranchiseAir sells franchise software, so on this topic Tom speaks as a supplier, not as an outside expert.

Related reading: John Pratt on franchise disputes, including what the agreement says when a franchisee leaves · Liam Wilson on the management service fee · Five signs a network has outgrown its spreadsheets

From the people behind this series

Jobs360 runs a jobs-based franchise network from one system.

Scheduling, quotes, invoicing and management service fees. Head office and your first franchise are free, with no card and no time limit.