Breaking Spiffy’s blue vans were the lab  •  Four million services became the data set  •  Now dealerships buy the operating system

Company profile / Automotive technology

Spiffy Spent a Decade Washing Cars. The Real Product Was Hiding in the Van.

The North Carolina company started with blue vans and an app. After four million services, it is selling dealers the software, hardware and hard-won operating manual behind the fleet.

In the beginning, Spiffy had a tidy elevator pitch: tap an app and a blue van appears to wash your car while you work. It was 2014, Uber had trained the world to summon real life with a phone, and co-founders Scot Wingo and Karl Murphy saw a neglected errand ready for the same treatment. Wingo brought e-commerce software instincts from ChannelAdvisor. Murphy brought a soldier’s appetite for logistics and years operating brick-and-mortar car washes. The pairing looked eccentric until you watched the vans move.

Twelve years later, the washing is almost a decoy. Spiffy now describes itself as a mobile service operating system for dealers. Its package includes scheduling and routing software, dealer-branded van upfits, connected tire and fluid tools, recall outreach, DMS integrations, payments, training and field-tested launch plans. There is still plenty of soap in the company’s history. The business it wants to be judged on, however, is dealership infrastructure.

A clean vehicle interior with a blue Spiffy service van visible outside
The driveway is the new service bay. The blue van in back would like your Quick Lane to know it has wheels.

The first thing that failed was software

Spiffy did not set out to build a vertical SaaS company. It first tried to license software from somebody else. The problem was mundane and decisive: the team says nothing on the market was designed for mobile car care. Ordinary field-service tools could dispatch a worker, but a profitable automotive visit also involved vehicle records, job duration, technician skills, parts, routing, inspection evidence, customer messages and payment. So Spiffy built its own system.

The van needed the same treatment. Spiffy says its upfit went through roughly a dozen versions. A van that looks convincing in a launch photo can be miserable in daily use: tools sit in the wrong order, clean and dirty fluids cross paths, weight is poorly distributed, or a technician burns minutes hunting for a fitting. Each revision converted an irritation into a standard. Each service created another data point about travel time, job mix and what customers would accept in a parking lot.

“The blue van was not just a delivery vehicle. It was a rolling product-development lab.”YesPress analysis

That distinction matters. Many software companies interview operators, translate complaints into tickets and ship a dashboard. Spiffy was the operator. Its employees had to arrive on time, reclaim wash water, touch a customer’s expensive asset and make the unit economics work. By its 2023 Series C announcement, the company said it was completing 3,000 to 4,000 services a day across more than 45 markets with over 350 vans. Today it says the cumulative count exceeds four million.

4M+Mobile services completed, company figure
12Approximate van-upfit iterations
$30MSeries C raised in 2023

The pivot was one layer down

The change of mind was less a sharp turn than a discovery. In 2020, Spiffy introduced Digital Servicing for dealers. COVID had made contact-light convenience newly urgent, but the product drew on six years of internal tooling and field work. Instead of merely bringing Spiffy’s own service to more cities, the company could equip existing automotive businesses to go mobile under their own brands.

This is the elegant part of the strategy. Dealerships already own customer relationships, parts operations, technicians and repair authority. What they often lack is a coherent way to run those assets beyond the building. Spiffy moved down the stack and began selling the missing layer. The software now branded Mobile 360 handles appointments, dispatch, routes, inspections, messaging, reporting and payments. Recall Capture targets owners with open recalls and lets them self-schedule. Easy Tread scans tires quickly enough to turn inspection into a sales workflow. Van upfits and training keep the digital promise from collapsing in the physical world.

That bundle is Spiffy’s clearest difference from generic dispatch software and from mobile-mechanic networks such as RepairSmith’s successor, AutoNation Mobile Service, Wrench or YourMechanic. It does not ask a dealer to stitch together a scheduling vendor, an upfitter, diagnostic hardware and a consultant. It sells the stack and the scars together. Public pricing is quote-led; the economic pitch is that a dealer can add repair-order capacity without pouring concrete for another bay.

What it costs - and what the dealer gets

Spiffy’s own cost is easier to see than its price sheet. Publicly disclosed rounds include $5 million in 2017, $9 million in 2018, $10 million in 2019, $22 million in 2021 and $30 million in 2023, plus strategic or growth investments whose amounts were not announced. Outside databases put total capital near $96 million; a supplied company record puts it at $99.6 million. Either way, this was an expensive apprenticeship in labor, fleet assets, acquisitions and geography.

The dealer’s return is presented in repair orders and gross profit. Chapel Hill Tire started with two vans and expanded to five; after a little more than a year, it reported nearly 3,000 services with an average ticket above $114. Athens Ford says four vans grew from 158 to 277 monthly repair orders in 90 days and added $214,000 in annual gross profit. McCluskey Chevrolet reports moving from 50 to 417 monthly repair orders in four months with nine vans, equivalent to $750,600 in annualized gross profit at the reported run rate.

These are vendor-published case studies, not controlled trials. They still show what Spiffy is selling: throughput, not novelty. A van is useful only when there is demand to fill it, a route that keeps it moving and a job mix the technician can complete safely outside the shop.

01

Find demand

Recalls, fleets and existing customers

02

Pack routes

Time windows, geography and skills

03

Do work

Standard jobs in a purpose-built van

04

Feed the shop

Escalate larger repairs back to bays

The thing founders can steal

Spiffy offers a useful playbook for founders who run service businesses: look backstage. The internal scheduler, quality checklist, equipment layout or training manual built to survive your own operation may solve a more valuable problem for the rest of the industry. Productizing it works best when the operation is not merely adjacent evidence but a repeatable laboratory.

Copy the sequence, not the penguin

  • Operate the ugly workflow long enough to learn where generic tools break.
  • Record each workaround as a product requirement, not tribal knowledge.
  • Bundle whatever the buyer must coordinate for the result: software, hardware and training if necessary.
  • Sell an operating metric such as repair orders per van, not a feature count.
  • Use the original service business as a test bed and credibility engine.

There is a second lesson in the shape of the pivot. Spiffy did not abandon car care for a fashionable category. It moved one layer deeper into the same market. The accumulated routes, employees, equipment and mistakes remained relevant. The consumer operation was not a failed prologue; it was paid research for the platform.

Where the model meets reality

Mobile service is not a universal solvent. It works when common jobs can be standardized, customers cluster tightly enough to create route density, technicians have the right inventory and a dealer treats the program as a real department. It weakens in spread-out territories, with uncertain or complex repairs, during punishing weather, or when a lonely van is purchased without demand generation and management discipline.

It works when…

Routes are dense, jobs are predictable, recalls create demand, customers self-schedule and the main shop accepts qualified follow-on work.

It stalls when…

Drive time eats the day, technicians carry the wrong parts, weather interrupts work or leadership mistakes a vehicle purchase for an operating plan.

There is also tension in Spiffy’s identity. Software investors like recurring revenue and light assets. Automotive service insists on steel, fluids, people and liability. The company’s answer is not to pretend the physical layer disappeared. It made that layer part of the product. That can improve outcomes, but it also makes execution harder than shipping another dashboard.

The customer mix explains why the compromise may be worth it. OEM programs want consistency across dealer networks. Fixed-operations managers want more capacity and better retention. Fleet operators want vehicles serviced without taking them off route for half a day. Consumers simply want the errand gone. One platform can coordinate those interests, but only if the field operation behaves as predictably as the software demo.

“Built by operators. Trusted by dealers. Proven at scale.”Spiffy

The market position is therefore unusually specific. Spiffy sits between dealership-management software, field-service logistics, vehicle upfitting and outsourced car care. Its buyers are fixed-operations leaders who need capacity, customer retention and recall completion without a construction project. Its end users are dispatchers, service advisers, technicians and drivers who mostly care that someone arrives when promised.

A decade ago, the visible magic was a clean car appearing in an office parking lot. Today the more interesting trick is making the van boring: a predictable unit of capacity, full of the right tools, arriving on a sensible route, feeding larger work back to the dealership. Spiffy’s wager is that dealerships do not need another mobile-service experiment. They need a system that has already survived one.