AI Assistants for General Contractors: What Sequoia's "Sell the Work" Thesis Means for Your Back Office

Short answer: AI assistants for general contractors should hand you finished paperwork to review (a drafted pay app, an updated submittal log, a flagged change order, a first-pass estimate) instead of another piece of software your team has to learn and feed. That is the construction version of Sequoia's "sell the work, not software" thesis. The part that makes it safe for a GC is simple: a person on your team approves every change before it goes out.

By Adam Hicks, CooperBuild AI · October 31, 2026

---

#What is Sequoia's "sell the work, not software" thesis?

In early 2026, Sequoia partner Julien Bek published an essay called "Services: The New Software" (opens in a new tab). His core line: "A copilot sells the tool. An autopilot sells the work."

He illustrates it with an example every contractor will recognize: "A company might spend $10K a year for QuickBooks and $120K on an accountant to close the books. The next legendary company will just close the books."

His reasoning is about where the money goes. Bek writes that "for every dollar spent on software, six are spent on services," and Fortune repeated that figure (opens in a new tab) from an interview with him in April 2026. That ratio is an investor's estimate across all industries, not a construction statistic, so read it as direction, not a number to put in your budget.

One detail gets lost in the reposts. Bek told Fortune that "autopilot" does not mean a machine doing the job alone. He meant it the way it works in aviation: a lot of the process is automated, and a human is still monitoring and ready to step in.

#Why does this matter to a small or mid-size GC?

Because most GCs with 10 to 80 people already live the problem Bek describes. You pay for software, and then you pay people to operate it.

Look at a typical month:

• A PM or bookkeeper rebuilds the pay app from a schedule of values that lives in a different spreadsheet than the estimate.
• Someone updates the submittal log by hand from emails and transmittals.
• A change in the field shows up in a daily report or a text thread, and nobody prices it until the owner's rep asks.
• The estimator copies last job's workbook and re-keys cost codes for the next bid.

Contractors say this out loud. One owner on r/Contractor wrote in April 2026 that they felt like they were "spending 80% of my time chasing paper and 20% actually running the business." In r/ConstructionManagers, a thread asking what still runs on spreadsheets and group chats drew answers like sub insurance tracking, lien waivers, and copying "the same info into three different places."

More software has not fixed that, because software is the $1. The paper chasing is the $6.

#What should "finished work" look like in a GC back office?

If you take Bek's idea seriously, the test for any back-office tool changes. Don't ask what features it has. Ask what it hands you at the end of the day. A few concrete examples:

#Pay applications

The useful output is a draft pay app built from the scope you sold, with this period's percent complete filled in from the job, and retainage and previous billings carried forward, waiting for your review. Not a blank form and a training video. (We covered why the SOV should come from the estimate in Bill from the scope you won.)

#Submittals

The useful output is a submittal log that is already updated when a transmittal or approval comes in, with the items that are late or missing called out, so your PM reviews a list instead of building one.

#Change orders

The useful output is a flag. Something in a daily report, an RFI or a meeting looks like a change, and it's put in front of the PM with the related scope before the work is buried in the job. The PM decides whether it's a change and what it's worth.

#Estimates

The useful output is a first-pass estimate structured like your last winning bid, ready for your estimator to check quantities, apply judgment and price. Your estimator still owns the number. (See Sunday-night estimating for why that workload breaks small teams.)

In every one of these, the deliverable is a draft of real work. The person reviewing it is still yours.

#Why does "you approve every change" matter so much in construction?

Because in construction, the paperwork is the contract. A pay app is a sworn statement of work in place. A submittal is your representation of what goes into the building. A change order moves money and schedule. If something goes wrong, the owner, the lender and the surety look to the GC, not to a software vendor.

So the model that fits construction is not "the software does it for you." It's assistants that do the paperwork, and a person who approves every change. In practice that means:

• Drafts, not decisions. The assistant prepares the pay app, log update or change-order flag. A named person on your team approves it before it goes to the owner, a sub or your books.
• A visible trail. You can see what was changed, from what source, and who approved it.
• Easy correction. When the draft is wrong, your PM fixes it in the same place, not in a side spreadsheet.

That is also what Bek means by autopilot: automated process, with a human watching and ready to step in.

#How should a GC evaluate assistants without getting burned?

A few practical rules, whether you look at CooperBuild AI or anything else:

1. Start where you already pay for the work. Bek's own playbook says to start with work that's already outsourced or already has a budget line. For a GC that's often pay-app prep, bookkeeping help or a submittal coordinator's time.
2. Measure today first. Write down how many hours last month's pay apps or submittal log actually took. Without that, you can't tell if anything improved.
3. Run one job, not the company. Commenters on r/Contractor gave the same advice about any new system: pilot on one project and don't migrate history on day one.
4. Review everything for the first month. If the drafts need heavy rework, it isn't saving time yet.
5. Refuse anything that won't show its work. If you can't see where a number came from, you can't sign the pay app.

#Where CooperBuild AI fits

CooperBuild AI is built around this idea: assistants that do the paperwork, and you approve every change. Each assistant has a job title, such as Tony · Estimating, and works inside the same workspace where your estimate becomes the job and the job becomes the bill. That way the drafts start from the scope you actually sold, not a fourth copy of it. If you want the background on that approach, start with The estimate is the company and Stop stacking.

If your team is spending more time chasing paper than running work, start a free trial of CooperBuild AI and bring one live job. You'll see quickly whether the drafts are worth approving.

---

#FAQ

#What does "sell the work, not software" mean for a general contractor?

It means judging back-office tools by the work they hand you (a drafted pay app, an updated submittal log, a flagged change order) rather than by features you have to learn and operate yourself. The idea comes from Sequoia partner Julien Bek's essay "Services: The New Software."

#Is it true companies spend $6 on services for every $1 on software?

That ratio is Sequoia's claim. Julien Bek writes that "for every dollar spent on software, six are spent on services," and Fortune reported the same figure from him in April 2026. Treat it as an investor's market estimate, not a construction-specific statistic.

#Do AI assistants replace my project manager or bookkeeper?

No. Good assistants take the copy-paste and first drafts off your people's plates. Your PM, estimator and bookkeeper still review, correct and approve the work before anything goes to an owner, a sub or your books.

#Why does "you approve every change" matter?

Because a GC carries the liability for what it bills, submits and signs. An assistant that drafts work and waits for your approval keeps a person accountable for every number, which is how owners, lenders and sureties expect a contractor to operate.

#Where should a small GC start with assistants?

Start with one paperwork job you already pay someone to do, such as monthly pay apps or the submittal log. Measure the hours it takes today, let an assistant draft it for a month while you review everything, and expand only if it actually saves time.