Your crew does the work twice —
once on the floor, once at the desk.
I build the software that closes that gap: one shared system instead of paper, spreadsheets, and re-typing. $3k to $10k, fixed price, quoted before any work starts. No monthly seats.
What a 20-minute call turns into.
A plan for your business
We look at how the work actually flows, then map what to fix first, what to leave alone, and what it costs.
Book a callNumbers you can actually see
Dashboards and metrics built from the data you already have — jobs, hours, materials, money.
Book a callInventory & operations systems
Stock, formulas, stations, logs — on a tablet where the work happens, not retyped at a desk.
Book a callCustom apps for the floor and the phone
Tablet apps, texting bots, voice receptionists. You own the code.
Book a callIf software isn't the fix, the call ends with that answer and a list of what to do instead. No quote, no pitch.
Five real changes, already running.
✕ Crew logged bunks on paper at each station; the office retyped it by hand.
✓ Tablets at every station feed one live board — nobody walks the floor to ask, and nobody retypes anything.
Stations / Logs_bunks — production
✓ Inventory in gallons, updated the moment stock moves, checked right from the tablet.
✕ "What's on hand?" meant walking to the shelf and counting.
Inventory / Stock_log — production
✕ Stain and tint formulas lived in one person's head — if they were out, nobody else knew the mix.
✓ Every colour and its formula, looked up on the tablet, with the math already done.
Colors / Add Color / formula.ts — production
✓ The queue heals itself — a dropped connection just catches up when it reconnects.
✕ Every wifi blip looked like an outage. Someone had to notice, walk over, and unblock it.
Sync queue — production
✕ A missed call was a missed job — nobody called back before the customer moved on.
✓ A texting bot and voice receptionist answer, capture the lead, and hand it straight to the owner.
Texting bot + voice receptionist — production
What happens after you book.
- 01
Book 20 minutes
Pick a slot, takes a minute.
- 02
The call
We walk through your actual workflow, not a slide deck.
- 03
A straight answer
A fixed quote, or “you don't need this” and what to do instead.
- 04
Built and handed over
You own it, no monthly seats.
One Real Shop. Zero Fluff.
A precoat and finishing shop, about 15 people. Job tracking ran on paper — no shared view of what stage a job was in, so someone had to walk the floor and ask. A wifi drop meant lost updates, not just a slow page.
Now: tablets at every station feed one live board. The sync is offline-first and self-healing — a dropped connection catches up on its own, no one has to notice or unblock anything. The same structured data that came out of tracking made an obvious next fix visible: printing labels in-house instead of paying a vendor $5 a label. That's recommended, not built yet — it's next, not a result I'm claiming today.
Client named on request. Read the full case study →
Book call to replicate thisWhy I build software for owner-operators.
I'm Alex. Before this, I built production AI systems — voice agents that hold up on a bad phone connection, texting bots that track a whole conversation, multi-tenant systems where one customer's data never touches another's.
I'm finishing a software engineering degree, one semester left. I'm one person and, right now, one named client — I'd rather say that plainly than dress it up. When you have a question or an urgent edge case, you talk directly to me.
[HEADSHOT] [NAME]
Frequently asked questions
Still have a question?
Ask on the call — there's no charge to find out if this is even the right fix.