One of the most common questions we get from dealers who have not started mobile service is this: how do I go from zero to one?
It is the right question, and many mobile service partners skip right over it. There is plenty written about whether mobile service is profitable and very little about the first ninety days, which is where programs are actually won or lost.
Three decisions, and they are worth making before you order anything.
Decide what work the van does. Not everything, and not whatever comes in. The programs that start clean start narrow: light maintenance, open recalls, and software updates. Narrow scope means predictable job duration, which means a schedule you can actually plan and a technician who is not stranded by a job that needs a lift.
Decide where the demand comes from. This is the decision most dealers skip, and it is the one that determines whether the program survives. Before the van exists, you should be able to name the list you will campaign against. Open recalls in your PMA. Customers with no visit in twelve months. Declined work from recent visits. If the honest answer is "we will see what customers ask for," you have a vehicle, not a program.
Decide who owns it. One name. Mobile service that belongs to everyone belongs to no one, and it will lose every conflict against the fixed drive.
Days 1 to 30: Prove the loop. Book, dispatch, complete, close, collect. The goal in month one is not volume. It is a clean repeatable cycle where the RO closes correctly in your DMS and the customer experience does not depend on someone remembering to make a phone call. Expect low daily job counts. That is fine in month one even if it’s a problem in month four.
Days 31 to 60: Fill the schedule on purpose. Run your first real campaigns against the lists you identified. Recalls first, because they convert best and require the least persuasion. Watch what happens to daily job count. This is the month where you learn whether your demand mechanism works, and it is the single most predictive month in the program.
Days 61 to 90: Tighten the economics. Now the questions get operational. How long is a job actually taking versus what you scheduled? How much drive time is between stops? How much additional work is the technician finding and closing in the driveway? Is the advisor coordination load sustainable or is one person quietly absorbing it?
Four numbers, weekly, from day one.
Repair orders per van per day. The number that decides your economics. Roughly three quarters of a one-van program's cost is fixed, so a half-full schedule does not return half the profit. It returns a fraction of it. Watch this weekly, not monthly.
Campaign conversion rate. What percentage of a list you campaign against books an appointment. This tells you whether you can manufacture volume or only receive it.
Gross profit per repair order. Track it against the parts cost you are actually posting, not the one a model assumed for you. Margin on mobile work follows your parts pricing and your job mix, so the number worth trusting is the one coming off your own operating statement after ninety days.
Return-to-shop rate. What share of mobile customers subsequently come into the store. This is the retention value of the program, and it is the number that justifies mobile service to a dealer principal who is only looking at per-RO profit.
In our experience, almost never the vehicle, the technician, or the market. It is whether the program had a demand mechanism or a hope.
Stalled programs look like this: the van exists, the technician is on payroll, the software is running, and the schedule is half full because nobody owns filling it. Every month the economics look marginal, and at some point somebody sensible suggests shutting it down. The program was never given the one input that decides the outcome.
Programs that scale treat volume as manufactured. They campaign against owned lists on a cadence, they remove friction from booking, and they measure daily job count weekly. When they reach the ceiling of one van, they have the evidence to justify the second.
When the first one is consistently full and turning away work, not when volume looks promising. The second van inherits the operating model of the first, including its weaknesses. Scaling a program that has not solved utilization just buys a second half-empty schedule.
Twelve years and four million services into operating mobile service ourselves, that is the single lesson we would hand a dealer going from zero to one. The van is the easy part. Everything that fills it is the program.
How many vans should a dealer start with?
One or two. Prove the loop and the demand mechanism before adding too fixed cost.
What work should a first mobile van take on?
Light maintenance, open recalls, and software updates. Narrow and predictable beats broad and unschedulable.
What about my DMS?
Repair orders need to close correctly in your existing DMS without manual re-entry. If a program requires someone to rekey every RO, the coordination cost will eat the margin. Confirm the integration before launch, not after.
Will mobile service cannibalize my fixed bays?
The pattern we see is the reverse. Mobile absorbs work that did not need a bay and recovers customers who had stopped coming in, which frees bay hours for higher-margin work, while also filling those bays with work that was identified during the mobile service.
How long before the program pays back?
It depends on utilization and average repair order. We have dealers whose programs are projected to return their full startup investment inside twelve months. We also see programs that never pay back, and the difference is almost always the schedule.
What is the most common first-year mistake?
Buying the van before deciding where the appointments come from.