ServiceTitan implementation for an electrical contractor has one structural difference from most trades: a large share of the work is not a single visit. Panel upgrades, generator installs, EV charger work, and service changes involve permits, inspections, material lead times, and sometimes a utility that sets the schedule. Configuration that assumes one job equals one visit will fight the business every day.
This is a walkthrough of the work, not a client story. Our one published case study is a roofing contractor — you can read that account in the owner's own words. What follows is the engagement itself.
What makes electrical different
- Permits and inspections sit between sold and complete. A job can be sold, partly performed, waiting on a municipality, and not yet invoiceable — all at once. That state has to exist in the system or it will live in someone's head.
- Project-length work alongside service calls. A generator install and a tripped-breaker call are the same company but not the same workflow, the same capacity planning, or the same billing.
- Material lead times drive scheduling. Panels and generators are ordered, not stocked. Scheduling that ignores procurement produces confident dates the field cannot hit.
- Multi-visit jobs. Rough-in, inspection, and trim are separate visits against one sold job, and reporting has to hold them together.
The sequence
1. Discovery and scoping
Map how work actually flows today: how an estimate becomes a sold job, who pulls the permit, who books the inspection, what happens while waiting on materials, and when the customer is billed. The output is the set of decisions configuration depends on — business units, job types, and the job statuses that represent your real states.
For electrical, the highest-value question in this phase is usually the simplest: what are all the states a job can be in between sold and paid? Most companies have more than they expect, and most have never written them down.
2. Job types, statuses, and the board
This is where electrical implementations differ most from a generic setup. Service calls and project work need different job types, different capacity treatment, and different visibility on the dispatch board. Waiting-on-permit and waiting-on-material need to be visible states rather than tribal knowledge, or the board stops reflecting reality and dispatchers stop trusting it.
3. Pricebook
Service work benefits from a flat-rate structure with good-better-best options. Project work is often estimated rather than priced from the book. Both need to exist, and the boundary between them needs to be a deliberate decision rather than an accident of how the first few jobs were entered. ServiceTitan's own pricebook documentation is the reference for how the structure behaves.
4. Data migration
Customers, locations, equipment, and open work. Open project work is the hard part: jobs that are mid-flight at cutover have to land in the right state on the other side, which is a mapping exercise agreed before the migration runs, not during it.
5. Role-based training
CSRs on intake and job types. Dispatchers on capacity across both service and project work. Technicians and electricians on the mobile workflow, including documentation that inspections may later depend on. Managers on the reports that show project margin, not just service revenue.
As with any trade, product knowledge and your process are different subjects. General coursework covers the first; training on your own configured account covers the second.
6. Go-live and the weeks after
The first inspection cycle after go-live is the real test, because it exercises the states that are hardest to get right. Expect the exception list to arrive then, and plan capacity to handle it.
Where it usually stalls
- Job statuses are treated as an afterthought. They are the backbone of electrical work in the platform.
- Project and service get one shared configuration. It seems simpler at first and becomes the reason reporting is untrustworthy later.
- Permit and inspection tracking stays in a spreadsheet. The system then tells only half the story, and leadership keeps running the business off the spreadsheet.
- Nobody internally owns the migration. As with every trade, this is the most common failure and it has nothing to do with software.
An honest note on proof
We do not have a published electrical case study. We do not publish client work without written approval, and we do not publish figures a client has not released. When an electrical contractor approves one, it will appear on our case studies page.
What we can show now is the method. To have it applied to your business, start with a free account analysis.
See also: ServiceTitan for electrical contractors and ServiceTitan implementation services.