A White-Label Carpool Platform — Your Brand, Live in Days

Most organisations that ask us about a white-label carpool platform have already scoped an in-house build. The estimate usually comes back at six figures and nine months — not because ride-matching is hard, but because everything around it is: identity, privacy, mobile clients, notification infrastructure, and the reporting layer your sustainability team will ask for six months after launch. Here is the comparison we would want to see if we were on your side of the table.

The build column is not wrong for everyone: a national mobility operator or a consumer marketplace should own its code. For an employer, a campus or a business park, the question is simply how fast people start sharing rides under your name — and what it costs to keep that running in year two.

Because TeamWheels runs inside your Microsoft 365 tenant, it does not need a separate user directory. Employees are already there. Entra ID handles authentication, group membership drives who can see which ride pools, and site or department attributes let you scope matching to a single location — which is what makes commute matching work at a 300-person industrial site where a generic consumer app would not reach critical mass.

That is the real payoff of a white-label carpool app integrated with HR and identity systems: employees join with the work account they already have, and HR, payroll and ESG teams get clean data without manual exports. Here is how each piece fits.

Single sign-on and provisioning

Authentication runs through Azure AD / Entra ID SSO. There is no invitation to send, no password to set and no account to provision: anyone in the directory can open the bot in Teams and is recognised immediately. Offboarding is just as automatic — when an employee leaves the tenant, they leave the carpool roster the same day, so the programme never accumulates stale profiles or orphaned accounts. If you use Entra ID groups to manage access to other line-of-business apps, the same groups control who can see and join TeamWheels.

Mapping sites and departments

Commute matching only works when it is local. During setup you declare your sites (an address and a radius each) and map them to the attributes your directory already carries — office location, department, cost centre or a dedicated group. Matching is then scoped so that a night-shift technician at the northern plant is paired with colleagues on the same site and the same hours, not with someone at head office 80 km away. Multi-site organisations, campuses and business parks that host several employers can run one programme with separate pools per site or entity, and report on each.

What data leaves your tenant

Short answer: nothing that is not necessary to match rides and produce your reports. Trip declarations, site assignments and participation records stay in your Microsoft 365 environment; the platform processes the minimum needed for matching (site, usual hours, departure area) and does not sell, share or resell employee data. Payroll and commuter-benefit records — pre-tax programmes under IRS Section 132(f) in the US, UK schemes, France’s forfait mobilités durables — are generated from those trip records and exported by your administrators, on your schedule. Our team walks through the exact data flows, retention periods and the data-processing agreement during the demo, so your IT and privacy officers can sign off before anyone carpools.

Days, not weeks — and in four phases you can put on a calendar. This is the timeline we run with new customers, consistent with what the rest of this site promises: live in days.

The technical part is measured in minutes. What sets the pace is your own pilot: most organisations keep it to two to four weeks so they can announce the general rollout with real numbers — trips shared, cars off the car park, CO₂ avoided — rather than a promise.

When you buy white label carpool software from TeamWheels, you buy a subscription, not a development project. The pricing model is per seat, and the public grid is the same one every customer starts from:

• Free 30-day trial — the complete platform for up to 50 employees, no credit card, no commitment. Most white-label customers run their pilot on the trial.
• TeamWheels, €3 per employee per month excl. VAT (promo, down from €5) — unlimited employees, the Teams bot and matching engine, the administration dashboard, real-time CO₂ tracking, commuter-benefit and FMD records, Entra ID SSO, advanced statistics and priority support. Monthly or annual billing, cancel any time.
• Enterprise, on quotation — everything above plus the white-label package: your branding and domain, multi-site and multi-entity programmes, HR and payroll integrations through the API, a guaranteed SLA, a dedicated account manager, personalised onboarding and custom ESG reports.

What triggers a quote rather than the flat rate: volume (typically from several hundred seats or several sites), hosting or data-residency requirements beyond the standard Microsoft 365 tenant deployment, custom integrations with an HRIS or payroll system, and multi-employer programmes run by a campus or a business park. A quote is usually turned around within a week of the demo, and the trial keeps running in the meantime.

How to buy: book a demo, run the free trial with your pilot group, then sign either online for the flat per-seat plan or an annual Enterprise agreement for the white-label package. Purchase orders and bank transfer are accepted for annual contracts; the platform is also listed on Microsoft AppSource, which some procurement teams prefer.

Ready to see it with your own branding? Watch the 60-second demo or book a personalised demo → and we will size the white-label package for your organisation. The standard grid is detailed on the pricing page .