Inside a Bohaus Sprint: An Electrical Contractor

The situation

The client is an owner-led electrical contractor doing residential service and light commercial work. Five electricians, two apprentices, an office manager, and the owner, who still writes most of the estimates at night. Jobber runs scheduling and invoicing. QuickBooks runs the books. Material pricing lives in a spreadsheet the owner updates when a supplier's prices jump, and sometimes forgets to.

Panel upgrades, EV charger installs, generator hookups and remodel wiring all need an estimate before they become a job. Those estimates sit. Some go out days after the site visit. Some never go out at all.

What the sprint finds

In Discover, we start with the money. Twelve months of card and bank statements, every recurring software charge, then a conversation with each person about what they actually open.

For a shop like this the lists rarely match. There is Jobber and also a separate estimating app the owner tried and abandoned. Two photo apps. A supplier portal login no one remembers. A shared Google Drive with old estimate templates. A texting app the office manager uses to reach customers outside Jobber.

Then we map how a site visit becomes an estimate. The electrician takes photos and notes on a phone. The notes are texted to the owner. The owner opens the spreadsheet, checks a supplier portal for current wire and breaker pricing, builds the estimate in Jobber from memory, and sends it when there is time. There is no follow-up unless the customer calls.

Jobber already supports a price book, line-item templates, and automatic estimate follow-ups. None of it is set up.

In Diagnose, estimating ranks first. It sits closest to cash, and the fix lives mostly inside software the company already pays for.

What it builds

In Build, we move the material spreadsheet into a maintained price book inside Jobber, with common assemblies, such as a panel upgrade or a charger circuit, built as templates.

Electricians capture site notes and photos in a structured form on the job. From those notes, the system drafts an estimate using the right assemblies and current prices. The owner reviews, adjusts and sends, often the same day. If the customer does not respond, follow-ups go out on a schedule, and quiet estimates are flagged for a call.

Duplicate apps are flagged for cancellation. The owner decides.

Hand over

In Hand over, the office manager becomes the owner of the price book and learns how to update it when supplier prices change. Electricians get a short session on the site-notes form. The owner learns the review queue. A short playbook covers the assemblies, the update routine and the follow-up rules.

The team gets a dashboard of estimates drafted, sent and won, plus a roadmap.

What changes

Estimates leave the same day or the next, instead of whenever the owner gets to them. Pricing reflects what materials actually cost. Follow-up happens without anyone remembering to do it. The owner stops writing estimates at the kitchen table.

The software list gets shorter. What remains is connected.

What this means for your business

A stack audit is a business review, not a technology project. List every charge. Ask what is used. Find the overlap. Map where information is retyped. Then cancel, consolidate, configure and connect.

An electrician finds estimating trapped between a phone, a spreadsheet and a supplier portal. A roofer finds it between an inspection app and an insurance adjuster. A garage door company finds it in a truck stock spreadsheet. The method holds.

A tool and data inventory opens every Bohaus Sprint for this reason: six weeks, fixed scope, one live system, and a team trained to run it.