BuildOps, a Los Angeles software company that sells service, project and financial software to commercial specialty contractors, announced three AI agents on November 5, 2026, at Forge 2026, its customer conference. The agents work on the service side of the business. They read technician visit notes, quotes, open jobs and customer contracts, then draft quotes, follow-up messages and invoices for office staff to approve. The Revenue Agent is in early access now, and BuildOps says the full set reaches customers in January 2027.
What it does
In a mechanical or electrical service shop today, a technician writes up a failing compressor in the visit notes, and someone in the office has to notice it, price it and send a quote. A service coordinator chases open jobs that are missing a timesheet or waiting on parts. A billing clerk applies each customer’s contract rates before the invoice goes out. BuildOps assigns an agent to each of those desks. An agent here means software that watches the records in BuildOps, finds a gap, and drafts the next step for a person to approve.
The release describes the agents in the order a job moves:
- The Revenue Agent reads visit notes and watches quotes, service agreements and equipment records. It flags repairs that were written up but never quoted, equipment on a serviced property that sits outside the service agreement, quotes drafted but never sent, and approved work with nothing on the schedule. For each one it drafts a quote, a follow-up email or a new job. The BuildOps website says quotes idle for 14 days or more get flagged.
- The Service Coordinator Agent checks every open job each day against more than 20 reasons work stalls, including a missed visit, parts not received, or a passed not-to-exceed limit. It drafts the message to whoever has to act, and it finds billable parts, fees and time in visit notes that never reached the job.
- The Billing Agent applies each customer’s billing rules, reads the contract and builds the invoice. It flags low markups and negative margins before the invoice is sent, and catches completed jobs that were never invoiced.
The approval step sits with a person. BuildOps says nothing an agent writes reaches a customer until someone approves it, each finding shows the evidence behind it, and each declined suggestion records a reason. The agents draw on the jobs, equipment, agreements and pricing a contractor keeps in BuildOps, so a shop that runs quoting or dispatch in another system would give them less to read.
Evidence so far
The evidence is BuildOps’ announcement, which includes comments from two customers, and the company’s website. These claims come from BuildOps:
- In early access, one contractor used the Revenue Agent to act on $2 million of quotes that had gone cold within a single 30-day period.
- About 16,000 people use OpsAI, the AI layer inside BuildOps, each month.
- Its 2026 benchmark report, built from a year of jobs, invoices and work orders across more than 1,500 contractors, found that BuildOps shops average about five field technicians per back-office employee, and the top 20% support nearly seven.
Collin Drovdahl, operations manager at Jolma Electric, said in the release, “The Revenue Agent picks up things the guys mentioned in our daily reports that the PM might miss.” Jonathan Clark of Omnia Mechanical Group said the agent’s follow-ups get customers to approve proposals they had set aside.
The $2 million figure counts quotes the contractor acted on. How many of those quotes were approved, and how often a flagged item turned out to be a real miss, are not yet public.
How to measure it on your projects
The cleanest pilot metric for the Revenue Agent is unquoted recommendations: repairs a technician wrote up in visit notes that have no quote 14 days after the visit. Count them, and total their dollar value at your price book rates.
To capture the baseline, export the last 90 days of visit notes and quotes, match each recommendation to a quote by job and asset, and list the ones with no match. A pivot table in Excel by technician and by customer will show where the misses cluster. During the pilot, also log how many agent drafts the office sent unchanged, edited or discarded, since edited drafts still take review time.
| Agent | Metric | Definition | Baseline to capture |
|---|---|---|---|
| Revenue Agent | Unquoted recommendations | Repairs a technician wrote up in visit notes with no quote 14 days after the visit | Count and dollar value from the last 90 days of visit notes |
| Revenue Agent | Quote approval rate | Share of quotes sent that the customer approved within 30 days | Last 90 days of sent quotes |
| Service Coordinator Agent | Days from job complete to invoice | Calendar days from the last field visit to the invoice going out | Median and slowest 10% of service jobs closed last quarter |
| Billing Agent | Invoices corrected after sending | Invoices credited or reissued because of a rate or line-item error | Count from the last three months |
For the Billing Agent, track calendar days from the last field visit to the invoice going out. Our post on adjusting DSO for retainage and billing cycles shows how that delay feeds into days sales outstanding. The same baseline works for comparing BuildOps with the invoice agent in ServiceTitan’s Max pilot.
A first step on one service line: pull last quarter’s visit notes for your busiest technician and count the written-up repairs that never got a quote.
Availability and cost
The Revenue Agent is in early access, and the Service Coordinator and Billing agents join it in January 2027 for BuildOps customers. BuildOps also previewed a Collections Agent for past-due invoices and unapplied payments, and AP Automation, which matches vendor bills to purchase orders and codes them to jobs. Both are expected in early 2027.
BuildOps prices by quote, based on the number of field and office users on the account. Its pricing page lists integrations with Viewpoint Vista, Viewpoint Spectrum, Sage Intacct, NetSuite and QuickBooks. Contractors can sign up for the agents at buildops.com/platform/opsai.