How Freedom Cars Runs a 400-Vehicle Subscription Fleet - and What Changed When the CRM Went Live

Freedom Cars is not a car rental company. It is a vehicle subscription business - a model that sits between traditional car ownership and short-term hire. Subscribers pay a weekly, fortnightly, or monthly fee to drive a vehicle they do not own. When their circumstances change, they can exit. When the vehicle needs servicing, Freedom Cars handles it. When the subscription ends, the vehicle goes back into the fleet and the next subscriber picks it up.

At the surface level, it sounds simple. At the operational level, running 400 vehicles across 300 active subscribers, two franchise entities, an on-site workshop, and two separate financial rails is one of the more complex operational structures a small business can carry.

How the Business Is Structured

Freedom Cars operates two franchise entities under a single management umbrella. Both entities share a brand, a leadership team, and an operational site - but they are financially distinct. Each entity has its own Xero organisation for accounting and its own Ezidebit account for direct debit collections. An invoice generated for a subscriber of Entity A goes to Entity A's Xero, and the weekly collection runs through Entity A's Ezidebit account. Entity B's transactions stay entirely separate.

This structure matters for tax, for reporting, and for the integrity of each entity's financial records. It also means that every operational decision - which vehicle gets assigned to which subscriber, which job card gets raised at the workshop, which payment schedule gets created - has to carry an entity attribution so the downstream financial events route correctly.

Staff work across both entities. The workshop serves vehicles from both. The management team needs visibility across both. But the financial records have to stay separated. That is the structural problem Freedom Cars was solving before the CRM existed, and it is the structural problem the CRM was built to handle correctly.

What a Subscriber's Journey Looks Like

A new subscriber contacts Freedom Cars, goes through an approval process, and gets matched to a vehicle. The match is not arbitrary - it depends on what is available in the fleet, which entity owns the available vehicles, and what the subscriber's circumstances suggest about the right vehicle type and price point.

Once matched, a subscription is opened. The subscription is the central contract - it records the subscriber, the vehicle, the weekly fee, the setup fee, the billing cycle, and the direct debit agreement. A payment schedule is generated from the billing cycle. Ezidebit collects against that schedule automatically.

From that point, the subscription is live. The subscriber drives the vehicle. Payments come in weekly. The workshop handles any servicing that comes up. Compliance dates for registration, insurance, and inspection are tracked against the vehicle. If a payment fails, an alert surfaces and the collections team follows up before the arrears threshold is reached.

When the subscription ends - because the subscriber exits, or because the vehicle needs to be reassigned - the subscription closes with a full audit trail. The vehicle status updates. If the same subscriber takes a different vehicle, a new subscription opens. The customer's history carries through.

The Workshop as an Operational Domain

The on-site workshop is not a peripheral operation. It is central to the fleet management cycle. Every vehicle that enters the fleet needs a pre-delivery inspection. Every vehicle that comes in for service gets a job card. Every job card has a scheduled date, an assigned technician, a service type, and a cost estimate.

When a job is completed, the vehicle's service history updates. If the job involved an odometer reading, that reading is recorded against the vehicle. If the job addressed a compliance issue - a rego renewal, an inspection, an insurance update - the compliance dates update and the alert that triggered the job closes.

The workshop team works from a jobs list. The operations team can see service history from the vehicle record or from the subscription. The compliance team can see which vehicles have outstanding work before their due dates. All of this is the same data, viewed from different angles.

Two Entities, One Financial System, Separate Rails

The most operationally complex part of running Freedom Cars is keeping the two entities financially separate while running a single unified operation. Before the CRM, this required manual discipline at every step - manually routing invoices to the right Xero org, manually ensuring the right Ezidebit account was used for each subscriber's collection, manually reconciling the cross-entity picture each month.

The CRM eliminates the manual routing. Every subscriber's subscription is attributed to an entity. When a payment is collected, it goes to that entity's Ezidebit account - automatically. When a Xero invoice is generated, it goes to that entity's Xero organisation - automatically. The routing is a consequence of the entity attribution on the subscription record, not a decision that has to be made at the point of invoicing or collection.

The management view is unified. A director looking at the subscriber list sees all subscribers across both entities. The fleet list shows all vehicles. The compliance dashboard shows all due dates. The financial events stay attributed and separated underneath. The operational view stays unified on top.

Compliance at Fleet Scale

A 400-vehicle fleet has 400 registration due dates, 400 insurance renewal dates, and 400 inspection schedules. Not all of them land at convenient times. Some cluster. Some get missed under manual tracking. A missed registration is not a minor administrative failure - it can take a vehicle off the road, interrupt a subscriber's service, and create a liability exposure.

The CRM tracks compliance dates against every vehicle and surfaces alerts before deadlines arrive. When a compliance date approaches, an alert is raised. The alert is linked to the vehicle and visible from the vehicle record, from the subscriber's subscription, and from the compliance dashboard. When the renewal is completed and the new date is recorded, the alert closes.

The same mechanism covers payment compliance. When payments fail and arrears accumulate past a threshold, an alert surfaces requiring human review before any suspension action is taken. The business keeps control of the escalation decision. The system ensures the decision gets made before the problem compounds.

What the CRM Changed

The operational model at Freedom Cars was not broken before the CRM. The business was running, subscribers were being served, and vehicles were being managed. What the CRM changed was the ceiling on what was operationally tractable.

A subscriber's complete history - which vehicles they have driven, every payment they have made, every note ever recorded about their account, every document on file, every alert ever raised - is now visible from a single screen. A vehicle's complete record - every subscriber who has driven it, every job card raised against it, every odometer reading, every compliance event - is in one place. A payment that fails creates an alert that surfaces to the right person without manual monitoring.

The two-entity structure that previously required discipline and manual routing now works automatically. Staff log in once and work across both entities within their provisioned scope. Financial events route correctly without anyone making the routing decision in the moment.

The operational ceiling is not where it was. The team can run a larger fleet, serve more subscribers, and maintain tighter compliance without adding coordination overhead proportional to the growth. That is what purpose-built software does when it fits the business it was built for.