How to Set Up Your Files So AI Can Actually Run Your Building Business

The difference between AI being a novelty and AI actually doing work in your building business comes down to something deeply unglamorous: how your files are set up. I ran a session with a group of builders this week on exactly this, and it is worth writing down, because the setup is what everything else stands on.

Get this right and you can point AI at your business and get real answers, real reports, and real jobs done. Get it wrong and you get generic guesses. Here is the order I do it in.

1. One Claude project per job, linked to its folder

The core move is to create one Claude project for each job, linked directly to that job’s folder in your Google Drive or OneDrive. Each job then has its own context, its own scheduled tasks, and its own reporting. Different jobs have different clients, contract types and complexity, so they need different things watched.

You need the Google Drive (or OneDrive) desktop app installed so your files sync locally, then you point the project straight at the job folder. Two things make this powerful:

• Anything Claude creates saves straight back into your Drive, not locked inside the AI. If you ever switch tools down the track, your work is already sitting in your own folders.
• You can also run a master project that sees every job plus your accounting, as a management and reporting view across the whole company, while giving a team member access to just their one job.

2. Match your job numbers, and name things properly

This is the boring rule that makes everything work: keep your job numbers identical between your project management system and your file storage. Wunderbuild auto-assigns a J-number, so carry that exact number into your Drive folder name. When the number matches, AI understands how your folder links to the job, and knows where to file things.

Naming matters just as much. A file called “download-3” tells you nothing, and it tells AI nothing either, so it has to open the file to find out what it is, which wastes time and burns through tokens. Name things so the AI (and you) can tell what they are without opening them. Two rules do the heavy lifting: put the date first in year-month-day form (2026-Jul-13, not 13/07/26) so the latest version always sorts to the top, and start every document with a type keyword (Plan, Quote, Variation, Permit, Report, Invoice, Meeting Notes) so it is instantly searchable.

What	Convention	Example
Construction job folder	J-number, site address, client first names	J-01009_122 Main Street _ Jack & Jill
Business project	Year-month, description	2501_New Website
Documents	Date, type keyword, description, job number	2026-Jul-13_Plan Engineering Set_J-01009.pdf
Business assets	Name, version	Employee Cost Spreadsheet_V1.0.xlsx

Date first means the latest version sorts to the top, so when there are four versions of a set of plans, AI goes straight to the current one.

3. Connect Wunderbuild

Once your folders are sorted, connect Claude to Wunderbuild through its connector. That is what lets you ask questions of your live job data instead of digging through it. I wrote the full plain-English guide to connectors, and what the Wunderbuild one unlocks, in Claude and connectors.

4. Skills are your SOPs

Here is the simplest way I know to explain an AI agent. It needs three things, just like a good employee: the right context (the job folder), the right tools (your connectors), and a skill, which is its standard operating procedure, telling it how to do the task. Add a routine to fire it on a schedule and you have covered who does what, when.

A few skills that earn their keep for builders:

• A filing skill that knows your rules: a tidy folder structure, sensible naming, and a firm habit of never deleting anything, only archiving it.
• A meeting-notes skill that reads a note and files it in the right place, project chat in the job folder, an HR chat somewhere private.
• A quote-sweep skill that scans your email, matches subbie quotes to the right quote request in Wunderbuild, and chases the late ones. This quietly solves the eternal problem of subbies emailing quotes instead of logging them. It no longer matters where the quote lands, as long as AI can read it.
• A version-control skill that keeps a register of plan versions and flags when something is out of date.

5. Scheduled tasks, used with restraint

Two tasks I would not run a job without: a daily site diary that gets emailed to the client weekly, and a weekly timesheet reminder into Wunderbuild. The site diary is cheap insurance and a weekly client touchpoint. The timesheet reminder keeps your labour data current.

One warning I gave the group, because it matters: do not over-automate your reminders. If everything becomes an automated message, your team tunes all of it out. Keep it to about once a week, and vary the wording so it does not become wallpaper. And use AI as a thinking partner on the actual management problem, not just a nag. If three of seven people still are not doing timesheets after a month of reminders, ask it what to change, do not just send a fifth reminder.

6. The headaches this kills

None of this is theory. In the session, builders were describing the exact pain this fixes:

• A plumber had priced off an old set of drawings that morning, because the plans had been updated in the system but nobody told him to look again.
• I have priced off the wrong plan version myself and lost days of work to it.
• One builder was still receiving scanned, handwritten quotes he had to retype. Now you photograph it, drop it on the computer, and have AI convert and log it.
• And the biggest one, universal in the room: time lost just hunting for information and the latest document.

A file system that AI can read makes every one of those problems smaller.

The order that matters

Structure first, then connect, then automate. Most people want to jump to the clever automation, but it only works on top of tidy folders, matched job numbers and clear names. Do the boring bit first and the clever bit takes care of itself.

This is the exact setup we walk builders through inside Future Builder.

Cheers Luke