The need
Align pays for each person using its roofing software.
I’m building Trueline to replace that system. It follows how Align’s office handles a job and keeps the records on a server the company controls.
What I built
One record per job, in software the company owns.
A job record holds the customer’s details and the work being planned. Estimates, invoices, photos, and work orders belong to that job, along with its tasks and notes. The office will use those records in the calendar and dashboard too.
The application runs on Align’s own server. Staff use their existing company Google accounts to sign in. Job photos upload directly to storage.
Trueline / In development
One record per job
The office keeps the customer’s details and job paperwork on this record.
- PaperworkEstimates, invoices & work orders
- ScheduleCalendar & office dashboard
- Job historyPhotos, tasks & notes
Estimates, scheduling, and the dashboard use the same job details.
Implementation
What’s built so far, and how the office will use it.
Customers and crews keep texting.
Customers and crews will still call or text the office. I’m building Trueline for the office staff to use, so the people on the roof and the customers won’t need another portal.
Where the build stands.
The office core is built. I’m still working on estimates, invoices, work orders, the calendar, and the dashboard. Later, I plan to add draft job updates from crew texts and insurance emails. Staff will check those drafts before saving them.