The need
Align’s office ran on a rented job system that charged for every seat.
The roofing system Align rents charges per user and decides how the work flows. I’m building Trueline around the way Align actually runs a job, with the records on a server the company controls.
What I built
One record per job, in software the company owns.
Contacts, the job pipeline, estimates, invoices, work orders, photos, tasks, and notes all hang off a single job record. The calendar and the office dashboard read from those same records, so the office sees one version of every job.
It runs on a server Align controls. Staff sign in with the company Google accounts they already have, and photos upload straight to storage.
Trueline / In development
One record per job
The job moves through Align’s stages with its information attached.
- PaperworkEstimates, invoices & work orders
- ScheduleCalendar & office dashboard
- Job historyPhotos, tasks & notes
The paperwork and office views draw from the same job records.
Implementation
A few choices I made on purpose.
Customers and crews keep texting.
Customers still call or text the company the way they always have. A crew’s day starts with messages to the office, and nobody outside the office has to learn a new portal.
Where the build stands.
The office core is done. Estimates, invoices, work orders, the calendar, and the dashboard are close behind. A later phase will draft job updates from crew texts and insurance emails for staff to check before anything is saved.