Getting a laptop or phone fixed here is a genuinely bad experience. You call four shops to compare prices, half of them say "bring it in and we'll take a look," and then your main work machine is gone for 3–5 days. For anyone whose laptop is their job, that's not a repair, that's an outage.

So I built the opposite. I come to your desk, home or wherever you're working across Metro Vancouver, and fix MacBooks, PCs and phones on the spot — usually 30–90 minutes. No drop-off. No "we'll call you."

The part I actually want to talk about here is the software, because it's the only reason one person can run this.

I've been building it part-time with AI-assisted tooling — Claude Code, Cursor, Cline — mostly from the driver's seat between Uber rides, laptop on the passenger seat and phone hotspot, in whatever parking lot I'm waiting in. 1,112 commits since April 2025, launched properly this February.

What it does, and what it replaces:

\- Quote in \~10 seconds, no forms, no email gate. The chat agent has 18 real tools wired into the database — it prices your exact model, checks live availability, books, reschedules, cancels, looks up your warranty. It replaces me answering the phone.

\- Pricing is upfront and honest about parts. Every repair shows a value and a premium tier with the actual part quality named, priced off a wholesale catalog of 13,770 SKUs synced over OAuth. Nobody in this industry does this, because vagueness is where the margin hides. I'd rather compete on being the one who says the number.

\- Booking slots are real. Availability is computed from actual part stock, supplier hours and lead times per city — not a calendar widget that promises tomorrow and then calls you to apologize.

\- A technician PWA I run the whole job from in the field, plus an email bridge: the customer just replies to a normal email and it lands in my app as a chat message. No app for them to install.

\- Invoices and warranty certificates generate themselves on job completion. 3 months on value parts, 12 on premium.

175 API endpoints, \~153K lines. Zero dollars on advertising, ever — the site pulls about 221K search impressions a quarter on its own, which is the one part I'd call properly finished.

Two things I'm actually here for:

1. Does on-site device support matter to a small team? If someone's machine dies mid-sprint right now, what do you do — AppleCare, a shop, a spare in a drawer, just eat the day? I want to know whether same-day at-the-desk repair is worth paying for at team scale or whether it's a consumer-only thing. Honest answers more useful than polite ones.

2. I'm taking on contract work. Everything above — the quoting agent, the automated ops, the booking logic — is the kind of thing most small service businesses are still doing manually with three people and five SaaS subscriptions. If you're building something and want that layer built fast, I've got bandwidth. Same if you just want to compare notes on AI-assisted dev workflows; I've shipped a lot through them and have opinions about where they fall over.

Site's travelling-technicians.ca — try the chat and see how fast it quotes you, or tell me where the funnel loses you. Happy to grab a coffee in Burnaby or downtown.

I run a doorstep repair business in Metro Van with no shop, no staff and no phone calls — automated the whole thing myself between Uber rides. Would this actually be useful to your team?