01 / THE STORYThe answers lived in fields, notes and spreadsheets.
Results Roofing runs its claims work through JobNimbus. Getting a clear read on carrier behavior or supplement results meant pulling from job fields, notes and separate spreadsheet trackers, then reconciling them by hand.
When the company joined the XBuild Operator beta, the goal was direct: ask a plain question about the business and get an answer the team could check against what they already knew.
02 / THE STORYA 90-day carrier view, checked by the people who know the claims.
In the first session, the XBuild team asked the Operator which carriers had produced the highest scopes over the previous 90 days. It returned a table in 37 seconds, broken down by carrier with counts, averages, medians, largest scopes and totals.
The claims team recognized the pattern right away. One carrier group stood out as the source of the fortified claims they discuss most often, and they could name the single large supplement that had lifted another carrier's average. When asked to verify the figures, they confirmed them.
A second prompt looked at supplement increases approved over the last 30 days. The team compared the result with their internal tracker and said it closely matched, with the small gap explained by a different date range.
03 / THE STORYA follow-up session turned a mismatch into an audit.
The next day, the team ran their own queries on supplement performance, asked the Operator to read job field data instead of status changes, and had it add roof square counts so years with different house sizes could be compared fairly.
While reviewing a State Farm query, they noticed the count was short. In JobNimbus, the insurance carrier is a free-text field, and the same carrier had been entered several different ways. The first pass missed four records. Once the team supplied the alternate spellings, the count came back correctly, and the finding prompted an audit of carrier names so later reports start from consistent data.
04 / THE STORYWhat the team can do with it now.
The Operator gives Results a fast way to question its own claims history and a clear reason to keep that history clean. The beta asks the team to check answers against what they already know and keep a log of accuracy as they go, so every spelling fix and corrected field makes the next report more reliable.
