This answer applies 3 methods from the guide, led by one.
Start with the repeated problem
Measure the task before selecting a tool, then choose the smallest intervention that could help.
- 1Describe the repeated task and who owns it.
- 2Measure time, missed work, errors and useful outcomes.
- 3Check fit, total effort, exportability, permissions and support.
- 4Prefer a reminder or template before a larger automation.
Hold when: Do not buy complexity to solve an undefined problem. Do not assume a tool is connected because it can chat.
Read it in Broker Brain →Keep one trustworthy working record
Use the CRM for confirmed identifiers, permission, needs, source dates and next actions.
Read it in Broker Brain →Test with a human checkpoint
Use permitted data, verify the output and keep every external action behind an accountable person.
Read it in Broker Brain →Start from three repeated jobs, and measure them first
Agents use what saves them time this week. A rollout that starts with a licence and a login gets a burst of curiosity and then silence; one that starts with a job they already dislike doing gets used. The guide's method, Start with the repeated problem, puts the job and its owner before the tool.
Ask the team where their hours go, then pick three jobs that repeat every week, have a clear idea of a good result and are checked before a client sees them. Follow-up after a viewing, rewriting listing descriptions and preparing for an appraisal are common first choices. Leave jobs where a wrong figure goes straight to a client until the checking habit is in place.
- 01Name each job and the person who owns it.
- 02For the week before you start, note how long each job takes, what gets missed and what goes wrong.
- 03Ask whether a template or a reminder would fix it before you buy anything larger.
- 04For any tool you consider, check the fit, the total effort including review, whether the agency can export the work, who can see what, and who supports it.
Agree the data rules and one working record before anyone logs in
Keep one trustworthy working record: client identifiers, permission, needs and next actions live in the agency's CRM, not in anyone's chat history. Then write the rules on one page an agent can read in five minutes, and have the finished page checked locally, because privacy law and advertising rules differ by market.
- 01What may go in: listings, published market data, agency templates and past marketing.
- 02What may not: identity documents, bank details and anything your privacy law treats as sensitive.
- 03Where client details may live: in systems the agency controls and has approved, never in personal accounts.
- 04Figures: every figure sent to a client has a source and a date, and the agent checks it.
- 05Approvals: nothing AI-drafted reaches a client until the agent who owns that client has read it, and public adverts or anything quoting a price or yield also go to a manager.
- 06Voice: how the agency writes, including the words you use and the ones you never use.
- 07Ownership: one named person owns the rollout, the rules and the quality of the record, answers “can I put this in?” and reviews the policy monthly.
- 08Mistakes: when AI gets something wrong, who is told and how it is corrected.
One workspace the agency controls, not one account per agent
When each agent signs up alone, client details end up in personal accounts the agency can't see, every agent pastes the same background into a blank chat, and when someone leaves, their history leaves with them. That is the second CRM the guide warns against.
A shared workspace fixes the structure: the agency's voice and rules loaded once, the records it answers from, approvals, and a record of what went where. Whether that is a team plan of a general assistant or a workspace built for real estate, the test is the same. Can you see where client details go, does it start from your records rather than a blank page, and does the agency keep the work when an agent moves on? A chat window on its own doesn't prove it can reach your CRM or send anything.
Test each job with a human checkpoint, on real work
Treat each job as a small test. Try it first on low-risk material, decide what a good output looks like and what counts as a failure, and make sure nothing reaches a client, a portal or a social account without the owning agent's approval. A prompt workshop is forgotten by Friday; an hour on a real listing is remembered because it saved them time the same day.
- 01Run each of the three jobs live on one of the agent's own listings.
- 02Show them a draft with an unsourced figure in it, and have them find and fix it.
- 03Have each agent complete one real job before they leave the session.
- 04Make mistakes visible: one place to report a wrong output, and a check that the same message can't go out twice.
- 05At day five and again at a month, compare against the baseline: time per job after corrections, errors caught, work missed and what clients noticed.
- 06Decide for each job: keep, change or stop. Sit with anyone who isn't using it, find which job it isn't helping with, and replace that job rather than repeating the training.
What gets in the way
Announcing a tool and expecting agents to adopt it.
Start with the three jobs that cost them most, measure them first, run each on their own listings, and check at day five who is doing them in it.
Letting everyone use personal AI accounts with no rules on client data.
Agree in writing what may go in and where it may live before anyone starts, and move client work into one workspace the agency controls.
Buying everyone a ChatGPT licence and calling it an AI strategy.
A blank account doesn't know your listings, clients or rules. Decide the jobs, the record and the approvals first, then judge any tool against them.
Letting drafts reach clients in a generic AI voice.
Load the agency's voice once from your best past listings and messages, and make the owning agent read and correct every client draft.
Questions agents ask next
Should I just give my team ChatGPT Team or Claude for work?
It is better than personal accounts, because the agency holds the accounts. It still starts blank on your listings, clients and voice, and a chat window doesn't prove it can reach your CRM. Decide the jobs, the record and the rules first, then judge any tool against them.
How do I stop agents putting client data into AI?
Give them a better place to do the job, and a written rule. A ban with no alternative pushes use into personal accounts you can't see.
How long does an AI rollout take?
Setting up a focused one takes about a week: rules agreed, records loaded, three jobs tested, then each agent trained on real work. Take the baseline in the week before, so you can tell whether it helped, and check use again at a month, because habits take longer.
Who should own AI in the agency?
One named person, often an operations lead or a senior agent the team respects. They own the rules and the quality of the record, answer questions about what may go in and review what is actually being used each month.
Will AI replace my agents?
No. It takes preparation off them: drafts, summaries, call lists and first versions. The conversations, the judgement and the relationship stay with the agent, and so does the approval.