Side project Mobile tire service In production

Breaux's Roadside & Tire

A business run on software I created, end to end

A mobile tire business had run nearly a year on less than a job a week, with no website and no way to tell which calls were worth paying for. Fixing that meant building the site first, then the measurement behind it. As calls and revenue grew, the bottleneck moved to the paperwork behind every job — six manual systems to reconcile. Nothing off the shelf met the owner's needs, so I wrote the web app the business now runs on daily. Once the inbound work was measured and running, the question left was how much work is out there at all, which meant sizing the market itself.

breauxs-roadside.com Site · Attribution · Internal web app · Market sizing
The app's Jobs tab: a searchable, sortable list of job cards, each showing the request, call time, tire category, and status.
The job record everything else hangs off — the app the business runs on daily.
The app's Look up tab: a running stock count above a searchable list of tire sizes, each row showing the quantity currently in stock.
Inventory in the same app, so stock is checked against the job rather than a separate spreadsheet.
A map of Mississippi with every federal-aid highway drawn as a colored line, dark red for corridors carrying 9,000 or more tractor-trailers per day down through orange and pale yellow for under 150. I-20, I-55, and I-10 read as the heaviest lines on the map.
Truck corridor exposure — sizing the work that hasn't called yet.
The customer-facing breauxs-roadside.com site, the landing page ads point at.
breauxs-roadside.com — where the ads point, and where call tracking starts.
10× Ad spend increase Based on increased calls and revenue, now traceable to source
6→1 Manual systems replaced by software I wrote Call-source tracking, quoting, invoicing, inventory, expenses, accounts — one job record
Daily Production use of that app Built and operated solo, against a live database
§ 01 Chronological Steps

From no calls to custom software

This wasn't a list of separate engagements. It was one problem followed in order — and each step narrowed what the business actually needed built.

01 No website, no tracking, almost no calls Ads pointed at a Google Business Profile. Nowhere to place conversion tracking.
02 Built customer-facing site, rebuilt the advertising breauxs-roadside.com, then Google Ads search and Performance Max, plus Local Services Ads.
03 Made calls measurable end to end Joined three platforms to the one thing none of them knew: did the call become a job?
04 Measurement unlocked spend — and the business grew with it From reluctance to double the budget, to over 10× the original spend in one to two months.
05 Created the software the business now runs on No off-the-shelf tool fit the workflow the owner wanted, so I built one: a Cloudflare Workers and D1 web app putting call-source tracking, quoting, invoicing, inventory, expenses, and fleet accounts on a single job record. In daily production use.
06 Asked how much work exists, not just where calls came from Planning past the calls he already had meant estimating a number nobody publishes. A Python pipeline over federal highway and carrier data ranks Mississippi corridors by truck exposure and maps the fleets within 75 miles.
§ 02 Case Studies

The work in detail

First · Measurement

Getting calls and tracking their source

Joining GA4, Google Ads, and Local Services Ads to job outcomes. What made spend defensible — and surfaced where the real constraint was.

Read case study Then · Custom software · Workers, D1, R2

The web app the business now runs on

Quoting, invoicing, inventory, expenses, and fleet accounts on one job record. Schema design, 25+ migrations against live data, and an integration suite that gates every deploy.

Read case study Now · Market sizing · Python, MapLibre

How much work is out there?

No dataset counts tire blowouts, so I modeled exposure instead: federal highway data ranked into corridors, plus the registered fleets nearby.

Read case study
§ 03 Components

Shipping and running the app

Writing the app is half of it. The rest is everything that keeps a live system safe to change.

  • Cloudflare. Static customer-facing site, Workers, D1, DNS, and redirect rules.
  • Data layer. D1 schema design, migrations, and backups behind quoting, invoicing, inventory, expenses, and fleet accounts.
  • Safe deploys. An integration suite against real D1 that must pass before merge, migrations written to be additive, and a hook that blocks writes to the production database without a fresh backup.
  • GitHub. Organization setup, repositories, and deploy pipelines, with owner-level access held by the business rather than by me.
  • Continuity. Accounts, admin access, and email owned by the business — business maintains ownership throughout.
  • In progress. Call-capture automation with OpenPhone and structured extraction from call transcripts.