Engineering
Built on real jobs.
Plenum runs UniColorado's day in Denver. New work goes to their office and trucks first. When something is slow or wrong, they say so that day.
- Times near work already bookedBooking and dispatch
- Each company kept apartChecked by the database
- Works without signalField app
01
Times that fit the route
When a customer books, the times offered are weighed against drive time and the work trucks already have nearby. The office and the booking page see the same times.
- Times come from your hours, service lengths and who is working
- Drive time is part of the choice
- The slot is checked again when the customer confirms
booking.log
// sample day 07:02 Tune-up booked online, Lakewood 07:02 9 to 11 AM offered: truck 2 is working nearby 07:03 Slot checked again on confirm 07:03 Confirmation sent by text and email
02
Each company kept apart
Each company's records are kept apart by the database itself, not by each screen remembering to filter. If a request does not say which company it is for, it stops.
- Every read and write is checked for the right company
- Staff see what their role allows
- Card numbers stay with Stripe
access.log
// sample requests Office manager opens invoices: your company only Technician opens a job: cost hidden for this role Request with no company: stopped
03
The field app works without signal
Technicians have the day's jobs, history and pricebook on the phone. Work done in a basement or a dead zone is saved on the phone and syncs when signal returns.
- Job details, history and pricebook kept on the phone
- Notes, photos and signatures saved without signal
- Changes send when the phone is back online
field.log
// sample job 10:30 No signal in the basement 10:41 Photos and notes saved on the phone 10:52 Customer signs Option B 11:05 Back online: changes synced
04
Fixed on real jobs
New screens go to work on UniColorado's jobs first. When something is slow, unclear or wrong, someone in the office or the field says so that day.
- Every change runs the test suite before it ships
- Errors reach the team as they happen
- The office says what is wrong, in plain words
feedback.log
// sample note from the office "The reminder text shows the wrong pay link." Reproduced on a real invoice Cause found and fixed Checked on the next real reminder
How we work
A few rules the team holds itself to.
We start from the job
Every screen starts from a real task in a working HVAC office or truck.
We check the effect
A passing test is not the finish. We check that the invoice went out, the payment landed and the job is on the schedule.
We keep it plain
Plain words on screen. A dispatcher should be able to read a status without training.
We fix the cause
When the same problem comes back, we rebuild the part that keeps failing instead of patching it again.
Build for the trades.
We look for engineers and designers who want to see their work used on real jobs.