CASE_STUDY // SERVICETRACKR · 2014–PRESENT

ServiceTrackr

Shop management software built, deployed, and operated across automotive and powersports dealers in Texas

70%
CYCLE TIME REDUCTION
↓ 100 days → 30 days avg
150+
ACTIVE ROS MANAGED
Peak concurrent throughput
3
DEALER DEPLOYMENTS
Auto + powersports
PROBLEM_STATEMENT // DEALER_VISIBILITY

Specialty dealers were running blind

High-complexity automotive builds — custom upfits, Kevlar coating, suspension lifts, audio installs — don't fit neatly into standard DMS workflows. Off-the-shelf shop management software was built for straightforward service lanes, not multi-stage build pipelines that span weeks or months.

The result: shop floors with no real-time visibility into job status, no accountability by stage, and no reliable data to manage profitability or technician throughput.

No stage-level visibility across active builds — status lived in people's heads or on whiteboards

RO cycle times ballooning to 100+ days with no early warning system

P&L data arrived too late to course-correct on individual jobs

Existing tools — R.O. Writer, DealerSocket — built for franchise service lanes, not multi-stage specialty builds

Competitive context

R.O. Writer and DealerSocket are designed for high-volume franchise service departments — oil changes, warranty work, standard repair lanes. They have no native concept of a multi-week build pipeline, stage-level job ownership, or upfit-specific workflows. Whiteboards filled the gap, which meant status was only as current as whoever last walked the floor.

SYSTEM_DESIGN // PIPELINE_FIRST

A pipeline-first shop management system

ServiceTrackr was designed around a core insight: an automotive build is a pipeline, not a ticket. Each vehicle moves through defined stages, each stage has an owner, and management needs real-time visibility into where every RO sits at any moment.

The first version (2014, Starwood Motors) was purpose-built for high-complexity upfit operations. The second version was rebuilt on Google Cloud with expanded service capabilities — broadening from specialty upfit to include standard repair offerings — allowing deployment across both Starwood Powersports and Reserve Customs.

Stage
Initial intake, RO creation, VIN assignment, job type classification
Parts
Parts ordered, sourced, and staged for build
Build
Active build stages: Kevlar, suspension, engine, audio, assembly
QC
Quality control inspection and sign-off
Alignment
Final alignment, test drive, prep for delivery
Completed
Delivered. RO closed. Job data captured for P&L.

// OUTPUT: Capabilities shipped across v1 + v2

DEPLOYMENTS // THREE_DEALERS

Three dealers. Two codebases. One system.

Dealer Type Version Focus
Starwood Motors Automotive v1 · 2014 Custom Jeep/truck upfits — Kevlar, suspension, audio, specialty builds
Starwood Powersports Powersports v1 · 2014 Same system adapted for powersports service and upfit operations
Reserve Customs Automotive v2 · GCP Luxury/performance vehicle customization + standard repair services
TECH_STACK // PRODUCTION_OPS

Built to run production shops, not demos

Google Cloud
Infrastructure (v2)
Pipeline UI
Kanban-style build board
RO Engine
Core work order system
VIN Tracking
Vehicle-level data model
Stage Logic
Configurable workflow stages
GNU GPL v2
Open source licensed
OUTCOMES // CYCLE_TIME_AND_MARGIN

Cycle time cut by 70%. P&L finally visible.

Average RO cycle time dropped from over 100 days to approximately 30 days — a 70% reduction — after deploying ServiceTrackr across the shop floor. Stage-level tracking surfaced where jobs were stalling, allowing managers to intervene in real time rather than discovering delays at delivery.

With 150+ active ROs managed concurrently at peak, dealers gained a live picture of shop capacity and job profitability that didn't exist before. For the first time, P&L analysis could be done at the individual job level — enabling operators to identify which build types, technicians, and job categories were driving margin and which were eroding it.

Faster throughput meant more jobs completed per month, higher revenue potential per bay, and the operational data to make informed decisions about staffing, parts sourcing, and job mix. Dealers could finally answer the question every shop owner asks but rarely has data for: which jobs are actually making us money?

GO_TO_MARKET // REFERRAL_LED

Sold through trust, not a pipeline

ServiceTrackr was never marketed in the traditional sense. Every deployment came through the dealer network — word of mouth between operators who trusted each other's recommendations. In a tight-knit specialty automotive community, that's the only channel that matters. A shop owner doesn't adopt new software because of a Google ad. They adopt it because someone they respect told them it solved a problem they recognize.

The go-to-market strategy was deliberately relationship-led and boutique. Each new deployment was evaluated on fit, not volume. That constraint was intentional: solo-operated software with one person handling build, training, support, and ongoing maintenance can only scale as far as the quality of the relationship allows.

Acquisition

100% referral-driven. Dealer-to-dealer relationships within the Texas automotive and powersports network.

Model

Internal tooling at Starwood. Cloud-hosted SaaS with a maintenance contract at Reserve Customs.

Retention

Every dealer that deployed ServiceTrackr expanded usage and requested features. Zero churn.

I owned every function a SaaS company would split across four teams: product development, onboarding, training, customer success, and ongoing support. Running a lean, high-retention product for specialty operators taught me exactly what shop owners value — and what causes them to dismiss software that doesn't speak their language. That's not a lesson you get from a job description.

MARKET_PERSPECTIVE // BUYER_EMPATHY

What a decade in the shop teaches you about selling to it

The shop management software market — Tekmetric, Shopmonkey, AutoLeap, Mitchell1, R.O. Writer — is ultimately selling the same promise: give operators visibility, reduce friction, and help them run a more profitable business. The technical differentiation matters less than most vendors think. What actually moves a shop owner is whether the product understands their specific pain and whether they trust the company selling it.

ServiceTrackr gave me something that pure marketing experience can't: I built the product, trained the users, handled the support tickets, and watched in real time how shop owners interact with software under pressure. I know where they disengage, what language lands, and what objections surface when a service advisor is in the middle of a busy day. That's the buyer empathy that makes inbound marketing convert — not just traffic.

ROADMAP // BUILD_AND_DEPLOY

From first deploy to multi-dealer scale

ServiceTrackr shipped in phases — each dealer deployment validated the pipeline model before the next expansion.

2014
v1 — Starwood Motors

Purpose-built pipeline UI and RO engine for specialty upfit and complex build stages.

2014
Starwood Powersports

Same operational model extended to powersports service and upfit workflows.

v2 · GCP
Reserve Customs

Cloud rebuild with broader repair capabilities — luxury/performance customization plus standard service lanes.

VISUAL_MODEL // VERIFIED_BASELINE

Cycle time improvement vs baseline

The headline 70% figure reflects average RO cycle time moving from over 100 days to approximately 30 days after system adoption — the same numbers shown in the hero metrics above.

Reduction vs 100-day baseline (target state ~30 days) 0%