Sold hours per item
Every pricebook line carries its book time, per unit. A job's estimate is the sum of its lines times their quantities, plus setup and cleanup.
Pricebook & sold hours
Job length that corrects itself
Flat-rate book time on every item, adjusted for who is actually going, and measured against what really happened — so the schedule gets more accurate the longer you use it.
Per-technician pacing
Each technician has a speed factor per service category — 1.0 is book par, below is faster. Assign someone and the duration recomputes.
Par versus actual
Real start and finish times are stamped against the estimate, and completion-efficiency reporting proposes a corrected factor when someone consistently beats or misses par.
What's in it
- Pricebook items with sold hours, cost, price and category
- Good/Better/Best tiering at the item level
- Per-technician category factors, per-team factors, and both combined
- Manual override when a job is not a pricebook job
- Date-only jobs that show as Anytime rather than a midnight bar
- AI Smart Start seeds 40–60 items with sold hours from your trade
- CSV import, including a ServiceTitan pricebook migrator
- Technician performance and completion-efficiency reports
- Sold-hours tracking per technician on the team roster
Questions
What if a technician is faster on one kind of work and slower on another?
That is exactly what the factors model. They are stored per service category, not per person overall, so someone can be quick on tune-ups and average on installs.
Do I have to build the pricebook by hand?
No. Smart Start generates a first pricebook from your trade mix and truck count, with sold-hour estimates already attached, and you correct it from there.
See it running on your own numbers
Twenty minutes, screen-shared, your trade's pricebook already loaded.