Freedom Tires is a mobile tire sales and service franchise. Each location runs its own day-to-day — dispatch, service, billing — while training, playbooks, and reference data move across the network. As the franchisor opens new territories, the operating system has to do two things at once: give every franchisee enough autonomy to run their week, and keep every franchisee on the same standards.

When Kenny came to us, no off-the-shelf SaaS could cover the shape of the work. The franchise model, the policies, the franchisor/franchisee split, the field reference data technicians need mid-call — every piece of it had to be understood before we could configure anything.

Before any module was turned on, we spent weeks understanding Freedom Tires. Where the franchise grows and why. What the market actually rewards in mobile tire service. What franchisees struggle with most when they go solo. What the owners care about — the calls they want every location to handle a certain way, the standards they refuse to compromise on. The policies and processes that have to live inside the system once it ships.

That work shaped every decision that followed. The franchisor/franchisee role boundaries. The 760-row Lugnut Torque Specs schema, indexed by make, model, and year because that’s the question a technician asks ten times a day. The training units in Launchpad , structured around what a new tech actually needs to know on their first solo call. The portal’s scope — exactly what each location should see, exactly what the franchisor keeps to themselves. The brand: from the public marketing site through every franchisee’s screen, one Freedom Tires.

When the discovery work was done, nine modules came on. Onboarding flows through Launchpad . The handbook and safety protocols live in Documents . The 760-row Lugnut Torque Specs sits in Data Tables , indexed for the way a technician actually asks the question. Time Tracking runs payroll-clean across the franchisor’s payroll cadence; Project Management tracks every install and service call across the network. Recurring operational tasks live in Playbooks . Custom Fields hold the franchise-specific data — store IDs, territory codes, the things every Freedom Tires location needs to track. Every franchisee gets their own scoped view through Platforms Portal .

None of those modules is bespoke — they’re the same ones any Platforms customer can turn on. What’s specific to Freedom Tires is the configuration: the franchise model, the role boundaries between franchisor and franchisee, the Lugnut Torque Specs schema, and Freedom Tires branding from the sign-in screen all the way through every franchisee’s portal.

A new technician at a franchisee starts Monday. By the end of the week, they’ve worked through the certification units in Launchpad , signed the handbook out of Documents , and sat next to a senior tech on three calls. The franchisee owner watches all of it from the portal, signs off on the certifications, and the new tech shows up ready on their first solo call — with the full Freedom Tires reference library in their pocket.

On a tough call, they pull up the Lugnut Torque Specs table, find the spec for the customer’s vehicle, and finish the job. Later, with a question on escalation policy, they ask Riley, our AI assistant. Riley pulls section 4.2 of the safety guide and cites it inline. No call to the franchisor, no Slack thread, no waiting on someone else to find the right document.