in testingField workforce
Crew hours on a phone
Payroll, Hours and the dispatch board
Crew hours came in on paper and by text, and straight time, overtime and double time had to be sorted by hand before payroll.
See how it was done
Case study · Electrical construction
Pinnacle Precon: one desk for the whole electrical shop
A web platform with 13 built modules under one sign-in: takeoff and projects, assemblies, an AI helper, Cost Control, Insights, Live Material, Drawing OCR, Payroll, Hours, Books, Accounting, Bid Board and Teams. Each module can be switched on per shop.
in testingRequest a quote
How it was done · told by Captain Parity
One desk for the whole electrical shop
- 1
The problem
A commercial electrical contractor in the Philadelphia area ran estimating, job cost, payroll and the office on an aging desktop database plus spreadsheets. Data lived in many places, and only a few people could find anything.
- 2
The bees make a plan
A web platform with 13 built modules under one sign-in: takeoff and projects, assemblies, an AI helper, Cost Control, Insights, Live Material, Drawing OCR, Payroll, Hours, Books, Accounting, Bid Board and Teams. Each module can be switched on per shop.
- 3
Build
- Mapped every screen and report of the old system into a parity checklist
- Built each module as its own switchable package
- Loaded and checked the shop's history against an answer key
- 4
Test
Ran staging first, with QA gates before anything went live
- 5
Where it stands
13 modules built and in daily use inside our own electrical company, with 2 more planned. Parity checking against the old system is still under way.
The technology we used
Named, because we really use it.
- TypeScript
- React
- PostgreSQL
- GitHub
- Windows Server
Technology names are text only. Naming a vendor is not a partnership or sponsorship claim.
More stories
liveAI operationsA team of helpers
The bot team and bot library
One person can't run several businesses alone.
See how it was done
