ChatGPT, set up for a trade business.
Most teams already have someone using ChatGPT. We set it up properly for the whole team: your documents, your weekly jobs, safe connections to your systems, and rules everyone can follow.
Your documents. Your jobs. Your rules.
The right plan
ChatGPT Business for the team, so your conversations stay out of model training and you control who has access. You hold the subscription.
Projects for your documents
Price lists, procedures, warranty terms and templates in one place, so answers come from your business, not the internet.
Apps connected carefully
ChatGPT apps linked to the tools you use, read-only first, with write actions left off until you decide otherwise.
Rules for the team
No customer data in personal accounts, an AI policy everyone has read, and a list of the AI tools in use.
The first prompts for each role.
Training on your own work: the office, estimators, techs and owners each get the handful of requests worth typing on day one.
Office
Turn a long customer email into a reply draft, and a phone note into a tidy job note.
Estimators
Draft a quote description from your templates, then price the risk yourself.
Owners
Ask plain-English questions of an exported report, and check the answer against the source.
You approve. AI earns its way in.
Every build starts small and read-only, and gets write access one step at a time.
Dry run first
Every tool shows what it would change, and changes nothing until a person says yes.
You approve what matters
Quotes, refunds, anything sent under your name: a person signs off before it goes.
Customers know it's AI
Chat and voice agents say they are AI, offer a person, and announce recording before a call is recorded.
Your data stays yours
It lives in your own Simpro, ServiceM8, CRM and AI accounts. Nothing is copied into a system we own.
Built to local rules
Call-recording consent, the Spam Act for texts and email, the Do Not Call Register for AI voices, and no AI-written reviews.
Handed over properly
Every build ends with an AI policy and a register of the AI tools you use, with one named owner.
General information, not legal advice.
One job first. Measured.
We don't start with a platform. We start with the task that eats the most hours, and prove it.
- 01
A fifteen-minute call
Which job eats your week? Which system holds it? We tell you straight if AI is the wrong tool.
- 02
We time it
Minutes per task, on your own jobs, before anything changes. That number is what we have to beat.
- 03
We build one thing
It runs as a dry run first. You see every change it would make, and you approve it.
- 04
We train the people who use it
Role by role, on your own system, with your own jobs. The go-to person in the office first.
- 05
A month later, we check
Is the task faster? Who still uses it? What needs changing? Then we pick the next job.
Every build is quoted before it starts. No platform plans, no lock-in.
ChatGPT questions.
ChatGPT or Claude?+
Both are good. Our own tools run on Claude, and we're happy to set up whichever your team already uses. If you're starting fresh, we'll recommend one on the call.
Is our data used to train the model?+
On ChatGPT Business it isn't by default. We check the settings with you at set-up.
Can ChatGPT connect to our job system?+
It depends on the system. We'll tell you what yours allows, and start read-only.
Find the hours first.
Fifteen minutes, no pitch deck. Tell us which job eats your week and we'll tell you whether AI is the answer yet.
Hayden Nosatti · Leadout · Sydney