Live case study · updated 2026-09-05
One car. Three jobs.
One vehicle is the denominator under three income tracks. Software is the one the other two are funding. This page is the reason the rest of this site counts every mile: a cost per mile is only interesting if something is riding on it.
The denominator, measured
10.9¢/mi
Every mile below runs at this cost. It is the number all three tracks are charged against, and the reason the gig track is worth taking at all. Working: the Ledger.
-
01
Paddock20 the lead
Race teams prep here before they win. We build your software the same way.
Agentic engineering studio. Custom software and automation, built by one architect with no handoffs. Also courses and a one-day Nashville build session.
- $125M+/mo processed through client builds
- 14 apps in production right now
- 4 to 12 wks scope to ship
- 1 architect, every build
Lot Assistant Daily lot operations for a $125M+/mo exotic and luxury dealership. In production. Supercar IQ Vehicle identification from a photo. Launching September 2026. iGot Receipts Mod and mileage tracking for collectors. Paddock Mail Internal comms for a team that lives on the move. - Custom builds from $749, 4 to 12 weeks
- Courses $49 each, $799 all access
- AI Mastermind, Nashville $499, VIP $999
What it asks of the car: Client sites and the Nashville build day. Low miles, high presentation. This is the track the decals advertise.
reported source: paddock20.com
-
02
PaddockGavin track 02
I find cars for people.
Vehicle sourcing and an owner audience. Concierge broker and vehicle sourcer, retail or wholesale, shopping with a dealer's licence so every auction is open. Plus the vertical video audience that brand deals are sold against.
- 78 cars found for other people
- 8,088 Instagram followers, checked 2026-09-03
- ~1M views a month, reported
- 200+ events run
Sourcing Retail or wholesale, every auction open with a dealer's licence. Consignment The retail lane. Brand deals An audience of owners and collectors, sound off, captions on. Events Private floor bookings and event days. - Find me a car concierge sourcing
- Sell my exotic car intake
- Pitch a brand deal affiliate and paid, disclosed on the piece
What it asks of the car: Lot days and event days on a fixed corridor, plus hauling gear. This is the track that puts the most miles on the odometer.
reported source: paddockgavin.com and instagram.com/itspaddockgavin
-
03
Instacart track 03
Until software, events and brand deals pay the bills.
The bridge. Gig delivery, run deliberately as a bridge rather than a business. It converts spare hours and an already owned vehicle into cash flow while the other two tracks mature.
- Bridge not the destination
- Variable hours, by week
- 5h19m door to door on 6 September 2026
- 3 / 4 / 89 batches, orders, items
- 0.4 mi it did not need to drive
- $3.19 of electricity for the day
What it asks of the car: Stop and go miles, cargo space, and a cost per mile low enough that the run is still worth taking. This is the track the cost per mile was built to answer.
measured source: the shopper app's own screens and the car
Colophon · how this site was built
The build behind the numbers.
This site is a production artifact, not a portfolio mock. What follows is the engineering behind it, including the parts that went wrong, because a build log that only lists wins is a brochure.
Stack
- Delivery
- Cloudflare Workers static assets on a custom domain. Edge 301s via a _redirects manifest, evaluated before asset resolution. No server, no runtime dependency, no external request at view time.
- Generation
- A deterministic Python static site generator. One JSON snapshot renders every page, so a figure cannot be current on one page and stale on another. No framework, no hydration, no client bundle.
- Data plane
- Vehicle telemetry and charging records via MCP connectors, normalised into a dedicated Postgres schema on Neon, then baked to a versioned JSON snapshot at build time.
- Identity
- Tesla Fleet API partner authentication: OAuth 2.0 client credentials for the partner token, authorization code flow for user scope, and an EC prime256v1 public key pinned at a well-known path inside the vehicle pairing chain of trust.
- Presentation
- A depth-graded glass design system on three elevations, with backdrop filtering, film grain over a full-bleed plate, and per-breakpoint art direction. Mobile first with safe-area insets and a 16px input floor.
- Visualisation
- Charts generated as SVG at build time. No charting library ships to the browser.
What went wrong, and what it cost
01
A 1 MB page that was mostly one photograph
Symptom. The legacy vehicle profile was 1,054 KB. Ninety per cent of it was base64 image data pasted inline, including one 70 KB photograph repeated three times in the same document.
Fix. Content-addressed extraction with SHA-1 deduplication moved every image to a real file and rewrote the references. The heaviest page fell from 1,054 KB to 37 KB and the images became cacheable for the first time.
02
A stylesheet that was only ever an overlay
Symptom. Each legacy page carried its own CSS reset inline, so the shared stylesheet had never needed one. Generated pages inherited no reset at all: the body fell back to a serif, and the layout gained a horizontal scrollbar on every screen.
Fix. Diagnosed by measuring documentElement.scrollWidth against clientWidth rather than by eye, which located the missing box-sizing rule in one pass. The base layer now lives in the shared stylesheet where it can never be page-local again.
03
SVG text does not scale like HTML text
Symptom. Charts authored in a 720 unit viewBox rendered at 309 CSS pixels on a phone, which shrank nine pixel labels to roughly four. The charts were technically correct and practically unreadable on the primary platform.
Fix. Label sizes are now expressed in user units and tuned per breakpoint so they resolve near ten pixels on screen at every width, and a value label that overflowed the viewBox on the longest bar was caught by measuring getBBox against the box rather than trusting the layout.
04
Art direction that survived the desktop and died on the phone
Symptom. Backdrop plates are 2.39:1. Under background-size cover on a portrait phone the browser scaled them to roughly 1939 pixels wide against a 375 pixel viewport, presenting a nineteen per cent centre slice under a veil running to eighty-two per cent black. The photography read as a gradient.
Fix. The plate is now anchored and scaled per breakpoint with the veil lifted on small screens, so the composition survives the crop instead of being destroyed by it.
05
A 3D preview built from an invented shape
Symptom. A wrap previewer was built on hand-authored extrusion coordinates rather than a real vehicle mesh. The engine underneath was sound, the geometry was a fabrication, and it shipped before that distinction was taken seriously.
Fix. Pulled from production the same day and held until a correctly licensed mesh is in hand. The standing rule that came out of it: when a reference asset exists, use the asset or stop, never approximate it and never present the approximation as the thing.
What this build exercised
- Static site generation and data-driven templating
- Edge deployment and edge redirect policy
- OAuth 2.0 client credentials and authorization code flows
- Asymmetric key provisioning and well-known endpoint pinning
- MCP connector integration
- ETL and privacy-preserving spatial aggregation
- Relational schema design and multi-tenant separation
- Information architecture and content migration at scale
- Accessible data visualisation, CVD-validated
- Responsive art direction and progressive enhancement
- Policy as code and pre-deploy gating
- PII redaction and geoprivacy
None of the above is unusual on its own. The point is that one operator carried it from telemetry ingestion to typographic standard without a handoff, which is the same shape every client build takes.
This is what an engagement produces
Everything above came out of one build. If there is a part of your week that should not exist any more, the studio scopes it, prices it in writing, and ships it.
paddock20.com · custom builds from $749, four to twelve weeks.