Kandji vs Rippling IT for a Multi-Unit B2B Franchisee

A franchisee running fifteen units doesn't have a help desk, and unit managers already have a full-time job running the location. Whatever platform gets chosen has to be simple enough for a non-technical unit manager to follow a short checklist, because there's no one else who's going to do the hands-on setup at each location.

This rules out any platform with a genuinely steep learning curve, regardless of how capable it is on paper. The right test isn't what an IT professional could do with the platform, it's what your least technical unit manager can actually follow without a phone call.

A franchisee can mandate a specific platform and configuration, or simply recommend one and let unit managers opt in on their own timeline. Mandating gets to full coverage faster but requires the operator to actually enforce it, while recommending is easier to introduce but risks a slow, incomplete adoption across units that never quite finish rolling out. Most operators land on mandating the platform itself while leaving some configuration flexibility for a unit's specific software needs.

Older units acquired years ago often run different point-of-sale hardware and older computers than a newly opened unit, simply because nobody went back and standardized after the fact. Auditing each unit's actual devices, rather than assuming they match a template, is the step most franchisees skip and regret when a rollout stalls at half the locations.

This audit doesn't need to be elaborate. A simple walkthrough at each unit, noting what's running Windows, what's running something else, and what looks close to end of life, is usually enough to catch the surprises before they derail a platform rollout.

Point-of-sale hardware is often locked down and managed by the POS vendor itself, separate from the office computer or back-of-house tablet a unit manager actually uses day to day. Trying to fold vendor-managed POS terminals into a general device platform usually runs into support conflicts. Scope your device platform to the office and back-of-house hardware you actually control, and leave POS terminals to their own vendor relationship.

This scoping conversation is worth having explicitly with each unit manager, since it's easy for them to assume the new platform covers everything in the building, including the POS system, and then be confused when a POS issue isn't resolved through the new process.

Franchise units commonly run Windows for back-office and inventory software, which points toward Rippling IT over Kandji for most multi-unit operators. Rippling IT's simpler onboarding flow also matters more here than in a business with dedicated IT staff, since a unit manager needs to be able to follow the setup with minimal hand-holding.

A franchise concept that specifically standardizes on iPad for order-taking or customer-facing displays is the exception where Kandji's depth on Apple hardware could make sense for that slice of the fleet, even if the back office stays on Windows under a separate process.

A franchisee handling device issues by driving to each location or talking a unit manager through it over the phone is spending real time that doesn't scale past a handful of units. National wage data puts the median salary for a general operations manager, a role commonly asked to cover this kind of cross-unit troubleshooting, at $105,770 a year¹, which is worth comparing honestly against a platform's per-device cost across your actual unit count.

Say you're adding a sixth unit this year. Under the current unit-by-unit approach, that's another location added to an already stretched informal support process; under a standardized platform, it's another device count added to a subscription that's already configured to handle it.

A unit manager who hasn't had a device problem in months has little patience for a new process that adds friction to something that already works from their point of view. Introduce the change gradually, starting with the units that have actually had recent problems, and let the quieter units see it working before asking them to adopt it. Forcing a simultaneous rollout across every unit tends to generate the most resistance from exactly the managers whose buy-in you need least urgently.

A gradual rollout across units can follow these steps:

1. Audit each unit's actual devices instead of assuming they match a template, since older units often run different hardware than newly opened ones.
2. Scope out vendor-managed point-of-sale terminals so they don't create support conflicts with the general device platform.
3. Start with the units that have had recent device problems, where the benefit is easiest for a unit manager to see.
4. Give unit managers a short checklist they can follow without central IT, then let the quieter units adopt after seeing it work.