Alton's estimators went from three hours a takeoff to ten minutes
How I built the drawing reader behind ElectricBid Pro — and why we changed the default setting before release.
- 5–10 min
Per takeoff, down from 2–3 hours by hand, as Alton’s estimators report
- 58% → 1%
Over-count on the setting we almost shipped, versus the one we did
- v1.0.0
Shipped 4 Sep 2026 and running on live bids
The job before
Alton Electric bids electrical work across the GTA. Every bid started the same way: an estimator, a set of drawings, and counting. Outlets, lights, switches, sheet after sheet — two to three hours before anyone knew whether the job was worth bidding at all.
Nobody sells software for that part. Counting isn’t hard. It’s just slow, and it happens at the worst possible moment: at the front, while you’re still deciding where to spend the week.
What I built
ElectricBid Pro was built by a team of six. I built the part that reads the drawings.
It sorts the pages, reads each sheet one small section at a time, counts every device once, and hands the estimator a draft count to approve.
The estimator approves every number. That was never negotiable.
I counted a sheet by hand to find out if we were wrong.
Reading a sheet in sections raises an obvious question: how many sections? We were going to ship with nine. So I counted a real sheet by hand — thirty-nine devices, one at a time — then ran the same sheet through the system.
9 sections — what we almost shipped
4 sections — what we shipped
We changed the default to four before release. That test is the only reason I will quote you an accuracy number at all — and one hand-counted drawing is a small test, which is why I run the same check on your drawings before you rely on a single number.
Shipping it
Software that lives on an estimator’s machine has to survive a real week. Beyond the reading, I worked on keeping data in sync across machines, the automated checks that run on every change, acceptance testing and the release itself. My share of the build:
- 37 / 36pull requests opened / merged
- ~16,400lines of code
- 29test suites
- 4 Sep 2026v1.0.0 shipped
“He didn’t pick the fancy-sounding answer; he picked the one that was actually right, and he proved it.”
Send me one drawing set.
I’ll send back the audit.
First one’s on me. Leave your name and email, I’ll reply so you can send the PDF, and you get the device count back, with every count showing where on the sheet it came from. Pricing it and drafting the contract is the paid work. If the count is useful, we book thirty minutes.