A business run on software I created, end to end
A mobile tire business had been running for almost a year on less than a job a week, with no website and no way to tell which calls were worth paying for. I built the site first, then the tracking behind it. As calls and revenue grew, the paperwork became the bottleneck: six manual systems that all had to be reconciled by hand. Nothing off the shelf fit what the owner needed, so I wrote the web app the business runs on every day. Once the calls were measured, the next question was how much work is out there at all, so I tried to size the market.
This wasn't a bunch of separate jobs. It was one problem worked in order, and each step showed me more clearly what the business needed built.
Joining GA4, Google Ads, and Local Services Ads to job outcomes. What let the owner spend with confidence, and what it showed about the real constraint.
Read case study Then · Custom software · Workers, D1, R2Quoting, 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, MapLibreNo dataset counts tire blowouts, so I modeled exposure instead: federal highway data ranked into corridors, plus the registered fleets nearby.
Read case studyWriting the app was only half the work. The other half is keeping a live system safe to change.