How to Automate JobNimbus

JobNimbus tracks a roof from the knock to the final inspection

Roofing is a sales business that happens to involve ladders. A job starts with a door knock or a storm lead, survives an estimate, waits on a carrier, and only then becomes a tear-off and an install.

JobNimbus is the CRM and project management platform exterior contractors run that whole sequence in: roofers first, and alongside them siding, gutters, fencing, decks and windows.

Boards are the heart of it, drag-and-drop production boards where a job card moves across the stages a company actually uses, from lead to estimate to tear off to install to final inspection to invoice. Contacts, jobs, documents and photos hang off the card. Estimates are built in the same place, and Material Ordering sends the order straight out of the estimate.

A crew chief opens it to see today. An owner opens it to see whether next month exists. Same board.

The claim moves slower than the crew does

The install takes a day. The claim takes four months.

Somewhere in that gap a person is refreshing an insurance carrier's contractor portal to see whether the adjuster has uploaded a revised scope. Somebody is submitting a supplement with photographs and waiting on a partial approval. Somebody is watching for the depreciation to be released after the final inspection, because until it is, the last cheque does not come. Somebody is ordering a measurement report from an aerial imagery vendor and waiting for the PDF. Somebody is checking whether the county has issued the permit yet.

Add the supply side. Material prices moved again. A delivery date slipped and nobody told the crew. A credit for returned bundles has not appeared on the statement.

None of it shows up as a missed job. It shows up as cash arriving eight weeks later than it should have, and as one person in the office whose entire role is refreshing other companies' websites.

JobNimbus

Claims watched daily Every open carrier claim checked each morning, with new documents pulled down and attached to the job the day they appear.

Supplements that do not stall Submitted, approved and paid tracked as a list, so the ones that went quiet are visible rather than half remembered.

Permits before the crew rolls City and county status checked each morning, so nobody is scheduled onto a job that legally cannot start yet.

Boards and Automations already move a job through its stages

Inside its own walls JobNimbus automates a great deal, and a contractor who has not set this up properly should do that before adding anything else.

Automations run on When/If/Then logic and come in two kinds. Event-based automations fire when something changes: a status moves, a document is signed, a contact is created. Time-based automations fire once an interval has passed. The actions cover creating a task with the right person assigned, sending a notification, sending an email, sending a text, changing a job or contact status and creating an appointment, and one trigger can set several of them off at once.

Workflows define the stages each job type moves through, so an insurance job and a retail job follow different paths. Engage puts texting inside the platform, so the conversation with a homeowner sits on the job record instead of on somebody's personal phone, and it can be automated too.

Material Ordering is the exception worth noticing. JobNimbus built real bridges to Beacon PRO+ and Roof Hub by SRS, with live pricing and ordering straight from an estimate, and where that bridge exists the problem is solved. No insurance carrier ever built one.

The carrier portal is where the money actually sits

The carrier decides when a claim changes state. The office finds out when something next looks, which can be every morning.

Every open claim checked each morning across whichever carriers the company deals with, new documents pulled down and attached to the JobNimbus job, and a status change surfaced the day it happens rather than the week somebody remembers to look. Supplements tracked from submitted to approved to paid, so the ones that stalled are a list rather than a suspicion. Depreciation release watched after the final inspection, because that is the payment most likely to be simply forgotten.

Permit status checked against the city or county site each morning, so a crew is not scheduled onto a job that legally cannot start. Measurement reports ordered and the finished PDF filed against the estimate. Supplier statements collected, delivery dates confirmed against the install calendar, and price changes on the materials you quote most often written somewhere a salesperson will see them before the next estimate goes out.

Keep the boundary at the homeowner. Reading a portal and filing a document is safe to run unattended. A message to a customer in the middle of an insurance claim is a message about their house and their money, and a clumsy one becomes a review that sits under the company name for years.

Somebody still has to open the carrier portal every morning

That is the whole job, and right now it belongs to a person who could be selling.

WebRun is an agent that works a real Chrome browser, signed in as you. It opens the carrier portal, the permit search, the imagery vendor or the supplier account, reads what changed, and updates the JobNimbus job so the board reflects reality.

It runs on your schedule in your own private environment, and a run can be watched and stopped. Anything going to a homeowner is drafted and left for a person to send.

The workflows below are already built, and each one says which sites it opens.