Sound familiar?
What water, fire and mold restoration companies tell us before a project starts.
- Emergency calls come at night and the intake notes are on a sticky note by morning.
- Techs take hundreds of photos and the office cannot find the right ones for the adjuster.
- Moisture readings and equipment logs are on paper or in separate spreadsheets.
- Insurance paperwork and estimates take longer than the work in the building.
- We win a job from a referral partner and never tell them how it went.
What we build
Each one is a working piece you can open and check when it's done.
After-hours intake and dispatch
Loss calls and web forms are logged with address, type of loss and insurer, and the on-call crew is alerted with the details.
n8n, Make and Zapier automation GoHighLevel setupPhotos filed to the job
Photos from the field filed by job and room, named the same way every time, with a shared folder for the adjuster.
API integrations and data sync Python scripts and utilitiesDaily moisture and equipment logs
Readings and equipment placed are entered once on a phone and added to a log the office can print as a report.
Google Sheets and Apps Script automation Web apps and MVPsClaim documents
Work authorizations, scope notes and invoices collected into one packet per claim, with the status of each item visible.
PDF and document data extraction n8n, Make and Zapier automationReferral partner updates
Agents, plumbers and property managers who send work get a short status when the job starts and finishes.
CRM setup and lead pipelinesJobs and revenue view
Open jobs, days in progress and money outstanding by insurer, on one page.
Dashboards and reportingRestoration software we work with: DryBook, Xactimate, Encircle, Albi, CompanyCam.
And the general tools around it: QuickBooks, Google Sheets, Google Drive, Twilio, Zapier, Make.
Example projects
Illustrations of the shape of the work, not past clients. Yours gets its own written scope.
Example project
Night call to dispatched crew
Example: a restoration company wants a burst-pipe call at midnight logged with address and insurer, the on-call lead alerted, and the customer sent a text confirming that someone is on the way.
Phone system, Twilio, GoHighLevelExample project
Daily photo and reading report
Example: a water mitigation crew enters moisture readings on a phone form and uploads photos. A daily PDF for the job is built and filed in the claim folder.
Apps Script, Google Drive, formExample project
Referral partner status
Example: a company that gets work from property managers wants each manager to receive a short update when the job starts, when drying finishes and when it is closed.
CRM, email, SMSQuestions people ask first
Do we have to switch software?
No. Most of the work is connecting your job and documentation software to the tools around it. If something can't do what you need, we say so in the scope and lay out the options before anything changes.
Can this work with the restoration software we already have?
Often, yes. It depends on what that product lets other tools do, such as its integrations, exports or notifications. We check this first and tell you in the scope what can be connected.
Who owns what you build?
You do. It is built in your own accounts, and you get notes on how it works so your office can change it without us.
How do we start?
Tell us which tools you use and the one thing that wastes the most time each week. We reply with questions or a written scope.
Tell us what you need built.
Email a few lines about what you want and which tools you use, or call. We reply with questions or a written scope.
hello@pushbuild.com