I'm an electrician, not a software vendor. My company, The Electricians, runs residential electrical service across the Denver metro and Colorado Springs on ServiceTitan. This is the story of how frustration with my own website turned into the product this site sells — with the actual numbers.
The part where I was the customer
We were spending real money on Google Ads and doing honest local SEO. Traffic was fine. Phone calls were fine. But online bookings — the thing that's supposed to capture the 9pm couch browser — were embarrassing. Our website ran a standard multi-step scheduler: pick a service, enter your address, pick a date, pick a time, confirm.
One night I watched a session recording of a visitor on their phone. They typed their name. They typed their phone number. They got to the calendar screen... and left. That lead — a real homeowner, with a real electrical problem, whose name and phone number were sitting right there on screen one — did not exist anywhere in our systems. Not in ServiceTitan, not in an email, nowhere.
We weren't losing leads because people didn't want us. We were losing them because our software demanded six correct decisions before it would admit a lead existed.
The insight: capture first, schedule second
The fix seemed almost too simple. What if the form fired the lead into ServiceTitan the moment someone hit Submit on that first screen — and the calendar became a bonus step instead of a gate?
So we built exactly that. A short form — name, phone, email, ZIP, service — that creates a real booking in our ServiceTitan Bookings tab instantly through the API. Then, only after the lead is safe, it offers self-scheduling. If the customer picks a window, the same booking gets the time. If they bail, our CSR sees the booking and calls. Nothing after the first click can lose the lead.
The four-month result
We swapped the old scheduler for the lead-first form on the same pages, with the same ad spend and the same traffic. Over the next four months, ServiceTitan online-booking volume rose more than 200% versus the prior period. The full breakdown is in the case study, but the mechanics were plain to see in the data:
- The abandons became leads. People who would previously have vanished at the calendar step now existed in our Bookings tab with a phone number attached.
- CSR callbacks converted hot. "You started booking a visit with us —" is the easiest opening line in the trade.
- Attribution got honest. Every website booking carried its campaign ID, so we could finally see which ads produced jobs, not just clicks.
What we learned the hard way
A few lessons that ended up baked into the product:
- APIs fail at the worst times. Early on, an expired credential cost us a weekend of submissions. Now every lead is stored on the site first, failures email us instantly, and syncing retries hourly. Zero-loss backup isn't a feature bullet — it's a scar.
- Fake availability annoys everyone. Offering time windows you can't staff creates reschedule calls. Pulling real capacity from ServiceTitan fixed it.
- Duplicates poison trust in the system. Self-scheduling must update the original booking, never create a second one, or your CSRs stop trusting the Bookings tab.
From internal tool to product
After four months of results, the obvious question was whether this was an Electricians thing or a physics thing. It's physics: any home-service shop where an urgent homeowner meets a long form has the same leak. So we hardened the tool — security review, spam protection, guided setup with a Test Connection button, the lead-first flow you can watch here — and turned it into LeadCapture ST.
I still run it in production on my own shop. Every update ships to my site first — my leads are the canary.
Your website is already generating these leads. The only question is whether your booking flow admits they exist.
Start Your 7-Day Free Trial