Stop digging through five systems to answer one question.

It means an AI assistant like ChatGPT or Claude that can read your own systems, so you stop copying and pasting into it.

Example questions you could ask:

• “What did we do at this address last time, and what parts went in?”
• “Which customers haven’t booked since spring?”
• “What did we spend on produce last month?”
• “Draft a quote for this repeat job from our current price list.”

What’s involved:

• A connection between the assistant and the systems you choose, like your job software, QuickBooks or a shared drive.
• Permissions by role. A crew lead sees jobs and schedules, not payroll.
• Read-only first. Actions like adding a job note or drafting an invoice are added only if you approve them. It never moves money.
• A log of everything it reads and does.

You review anything it drafts before it goes to a customer. It’s built on an open standard that several AI assistants support, so you’re not tied to one AI company.

Partly, and you should know exactly how. When an AI assistant answers a question, the records it looks up are sent to the AI company’s servers to work out the answer. That’s how these tools work.

What we control is how much, and on what terms:

• Only what’s needed. The assistant can read only the systems and fields you approve. Payroll, bank details or anything else you rule out stays out of the connection entirely.
• Training turned off. Wherever the vendor allows it, we turn off training on your data. Business plans often exclude it by default, and we check the current terms for yours.
• Every vendor named. Your proposal lists each company that will process your data, before you sign.
• Your accounts. The connection runs in accounts you own, and our access is removed at handoff or when you end support.
• A log. You can see what the assistant read and when.

See how we handle data and system access on every project, and how custom AI integrations work.

The same rules apply on every project:

• Least access that works. We ask only for the permissions a job needs. Read-only comes first.
• Your accounts, in your name. Tools and automations live in accounts you own. Where a tool allows it, we get our own login that you can remove, instead of sharing yours.
• Every vendor named up front. Your written quote or proposal lists each company that will process your data, before you sign.
• AI training turned off. Wherever a vendor lets you turn off training on your data, we turn it off.
• Access removed at the end. Our access is removed at handoff, or when you end support.

The AI tools we set up only say and do what you’ve approved in writing. They never move money. Anything outside the rules goes to a person on your team.

Connecting an AI assistant to your records? See what data goes to AI companies and how custom AI integrations handle permissions.

You do. Some things are yours from day one, and the code is yours once you own the build:

• Accounts and phone numbers are set up in your name, with you as the owner.
• Data stays in your accounts.
• Code and automations become yours when you own the build. Pay for it up front, or buy out a managed plan at the price written in your proposal.
• Documentation comes with it, so anyone you choose can maintain the work.

Two things work differently:

• Our reusable templates. Some building blocks, like a standard reminder flow, get reused across projects. Those stay ours. You get a permanent, free license to use them, so nothing stops working if you stop working with us.
• Third-party software. Tools like QuickBooks or Jobber stay under their vendor’s terms. The accounts are still in your name.

There’s no lock-in to us either. Support is month-to-month, a managed plan’s buyout price is written in your proposal, and we flag any vendor contract longer than month-to-month before you sign. These commitments are part of the principles we work by.