Field NotesOctober 1, 20264 min readby Kol Dorney

Every builder software says AI now.

We looked at every AI-first platform selling to residential builders. Each one put its AI on a single job. Five jobs, one blind spot, and six questions for any demo.

This fall we went through every construction platform we could find that sells to residential builders and remodelers. There are dozens. Nearly all of the newer ones lead with the same two letters. AI-first. AI-native. An AI copilot with a first name.

Read past the homepage and a pattern shows up. Each vendor put its AI on one job. Not the same job, and almost never more than one.

The five jobs AI is doing for builders

The job	What the AI does
Drafting paperwork	Writes change orders, RFIs, scopes, daily logs and client emails from a short prompt or your project data.
Estimating	Builds an estimate from a job description, photos or plans, using your price book.
Paying bills	Reads sub and supplier invoices, assigns each to a job and cost code, and posts it.
Answering the phone	An AI receptionist that answers leads after hours, qualifies them and books the call.
Scheduling subs	Texts subs, reads their replies and updates the schedule.

All five are real work that eats a PM’s or an office manager’s day. None of them is a gimmick. The question is not whether AI helps. It is which job you need it on, and whether it can see enough of your firm to do that job well.

AI can only see what is in the system

This is the part the demos skip. An AI assistant reads the data in the platform it lives in. Nothing else.

If your website, CRM, job management and books are four systems, an AI inside the job tool sees the jobs. It does not see which ad produced the lead, what the homeowner said on the first call, or whether the last draw cleared. Ask it “which of my jobs is losing money” and it answers from half the numbers, with full confidence.

The more of the firm lives in one system, the more the AI can actually answer. That is not a feature you can buy separately. It comes from how the stack is put together. We laid out the typical stack in your firm runs on six rented systems.

Six questions for any AI demo

Which job does the AI do? Get one sentence. If the answer is “everything,” ask to see it do the one you care about, on a real job.
What data can it read? Jobs only? The CRM? The books? If it cannot see the books, it cannot tell you about margin.
Does it draft, or does it act? A drafted change order you approve is safe. An AI that sends one to a homeowner on its own is a different decision. Know which you are buying.
Is it in the plan you were quoted? Some vendors keep the AI in the top tier. Check the price with the AI turned on, not the starting price.
Whose accounts does it run on? Your price book, your cost history, your homeowner messages. That is what makes the AI useful to you. Find out where it is stored and whether it is yours.
What leaves with you? If you cancel, do you keep the data the AI was working from? Ask the same export questions you would ask about any software.

How we think about it at Yglu

We did not start from the AI. We started from putting the whole firm in one system: the website and lead capture, the pipeline, the job, and the books of record. All of it on the firm’s own accounts. That is what lets automation see the whole job, from the ad that produced the lead to the draw that paid for it.

Auto-quoting is the next piece, and it is in build now. When it ships, it will quote from the same price book and cost history the books already hold, not from a copy.

If you are sitting through AI demos this quarter, take the six questions with you. Ask them of us too.

Your job costs and your books should be one system.

Most builders keep job numbers in one tool and the books in another, joined by a sync. Where the two drift, what it costs, and why one ledger beats two.

Read the note →

Field Notes← All notes

Written by Kol Dorney, founder of Yglu. Field Notes drops when there is something worth putting on the record, not on a publishing schedule.