Technology AI

Piloting AI in one branch: a 30-day plan

A 30-day plan for trialling an AI tool in one agency branch: choosing the task, preparing data protection and staff, daily checks, stop rules and go/no-go.

Ava research teamPublished 7 min read

On this page
  1. Why one branch, one task and thirty days
  2. Where most firms are starting from
  3. Choosing the task
  4. Groundwork before day one
  5. Get pilot-friendly contract terms
  6. The 30-day plan
  7. Daily and weekly checks
  8. Bring the team with you
  9. Stop rules
  10. The go/no-go scorecard
  11. Worked example: out-of-hours calls in one branch
  12. Write it up
  13. Frequently asked questions
  14. References

Key takeaways

  • Only 21% of UK businesses had adopted some AI tools in 2025/26, while 45% said AI was not relevant to them, so a careful pilot puts you ahead without betting the business[1].
  • Pick one task in one branch with high volume, low legal risk and an easy measure, such as out-of-hours calls or inspection write-ups.
  • Do the groundwork first: a named owner, a data protection screening, supplier terms, a staff briefing and wording for clients[2].
  • Decide go or no-go on day 30 against thresholds you wrote down before day 1, and listen to the people who used the tool.

Why one branch, one task and thirty days

AI projects in agencies usually fail in one of two ways. Either the owner buys a tool, switches it on everywhere and spends months dealing with the fallout, or the tool sits half-configured because nobody owns it. A tightly scoped pilot avoids both. One branch keeps the impact contained and makes the results easy to compare with others. One task keeps the measures clear. Thirty days is long enough to get past the novelty and short enough to keep attention.

The aim is a decision, not a demonstration. At the end you should know whether the tool does the job well enough to extend, needs adjusting, or should be stopped, and you should be able to explain why with numbers and with the team's experience.

Where most firms are starting from

The government's 2025/26 cyber security breaches survey found that 21% of UK businesses had adopted some AI tools, while 45% said AI was not relevant to their organisation[1]. The ONS reports that 41% of businesses with ten or more staff saw no barriers to adoption in mid-2026, and that the most common barriers were difficulty identifying use cases, cost and lack of expertise[3]. A pilot deals with all three: it names the use case, limits the cost and builds expertise inside the team.

UK businesses and AI tools, 2025/26Share of all UK businesses.
UK businesses and AI tools, 2025/26Comparison. Adopted some AI tools: 21%; Said AI was not relevant: 45%.21%Adopted some AI toolsAdopted some AI tools: 21%45%Said AI was not relevantSaid AI was not relevant: 45%UK businesses and AI tools, 2025/26Comparison. Adopted some AI tools: 21%; Said AI was not relevant: 45%.21%Adopted some AI toolsAdopted some AI tools: 21%45%Said AI was not relevantSaid AI was not relevant: 45%

Source: Department for Science, Innovation and Technology (GOV.UK), 2026[1]

Show the data
ItemValue
Adopted some AI tools21%
Said AI was not relevant45%

Choosing the task

Comparing candidate tasks for a first AI pilot.
Candidate taskVolumeLegal riskEasy to measure?Pilot verdict
Out-of-hours call answering and loggingHighLow to mediumYes: answered calls, bookings, callbacksGood first pilot
Inspection and valuation write-ups from voice notesMediumLowYes: time per report, correctionsGood first pilot
Listing copy from verified fact sheetsMediumMediumPartly: time saved, correctionsGood with strict checks
Applicant enquiry repliesHighMediumYes: response time, viewings bookedGood with approved facts
Maintenance triage for managed letsMediumMedium to highYes: response times, re-tieringSecond pilot, after experience
Tenant scoring or selectionMediumHighHard: fairness needs long testingNot a pilot task

Choose the task that causes the most visible pain today and scores well on the other columns. If the branch manager cannot describe the problem in one sentence, such as 'we miss most calls after half past five', the task is not ready for a pilot.

Groundwork before day one

  • Name a pilot owner in the branch with time set aside each day, and a sponsor who will make the final decision.
  • Screen the processing for a data protection impact assessment; UK GDPR requires one before new technology processing that is likely to result in a high risk to people[2].
  • Get processor terms from the supplier, confirm where data is held and switch off any use of your data for training if you can.
  • Prepare the approved facts the tool will use: property sheets, office hours, fees page links and escalation contacts.
  • Brief the branch team on what will change, what will not, and how to report a problem.
  • Write the client-facing wording, such as a call greeting or a line in the email footer.

Get pilot-friendly contract terms

A pilot is only a pilot if you can walk away. Before signing, check that the agreement matches a 30-day decision rather than locking you into a year.

  • A monthly or pilot-length term, with no automatic roll into an annual contract.
  • Set-up help and a named contact included for the pilot period.
  • The right to export your data in a usable format and have the rest deleted if you stop.
  • Clear limits on any usage-based charges, so a busy week does not produce a surprise bill.
  • Agreement that pilot results, including errors, can be shared inside your business.

The 30-day plan

  1. Days minus 14 to 0: baseline

    Record the measures for two normal weeks: for call answering, calls by hour, answered, missed and returned, plus valuations and viewings booked by phone.

  2. Days 1 to 3: set-up and shadow mode

    Configure the tool and run it alongside the current process without clients relying on it, or on test calls only. Fix obvious errors.

  3. Days 4 to 10: live with full review

    Switch on for real clients in the agreed hours. The owner reviews every output or call record daily and logs every error.

  4. Days 11 to 20: spot checks

    If the error log is short, move to reviewing a daily sample. Adjust scripts and approved facts weekly.

  5. Days 21 to 28: steady state

    Run as you would after rollout. Keep the daily sample and record time spent on review.

  6. Days 29 and 30: decide

    Compare results with the baseline and thresholds, gather the team's views and make the go, adjust or stop decision.

Daily and weekly checks

  • Daily: read the overnight records, confirm anything urgent was handed to a person, and log errors by type.
  • Daily: check that records reached the CRM against the right contact and property.
  • Weekly: update the measures against the baseline and share them with the branch team.
  • Weekly: listen to or read five complete interactions start to finish, including at least one the tool handled badly.
  • Weekly: review client feedback and any complaint that mentions the new process.

Bring the team with you

Expect mixed feelings. In the government's public attitudes survey, around four in ten UK adults expected AI to have a positive impact and three in ten a negative one[4]. Your team is likely to split in a similar way. Involve sceptics in writing the scripts and reviewing outputs; they find problems faster than enthusiasts. Make clear that the pilot is about removing the work people dislike, not about cutting jobs, and keep that promise in how results are used.

Ask for a two-minute note from each person at the end of each week: what helped, what went wrong and what they would change. Those notes often explain the numbers better than the numbers explain themselves.

Stop rules

Write down in advance what would pause the pilot immediately. That protects clients and gives the owner permission to act without a debate.

  • Any safety-related failure, such as an emergency repair or gas report not passed to a person.
  • A data protection incident, such as client data sent to the wrong person.
  • A pattern of wrong information given to clients about properties, prices or rents.
  • A complaint that the tool refused or obstructed a request to speak to a person.
  • Review time rising instead of falling after the first fortnight.

The go/no-go scorecard

A sample scorecard; every figure in the result column is a fictional example.
CriterionThreshold set before day 1Example result
Out-of-hours calls answeredAt least 90%, from a baseline of 35%Example: 97%
Valuations booked from those callsAt least 4 more a month than baselineExample: 6 more
Urgent issues passed to a person100% within 15 minutesExample: 100%
Errors needing correctionUnder 1 in 20 records by week 4Example: 1 in 32
Daily review timeUnder 30 minutes by week 4Example: 20 minutes
Team viewMajority want to keep itExample: 5 of 6

If every threshold is met, extend to a second branch with the same measures. If most are met, adjust and run another 30 days. If the safety or error thresholds fail, stop and record why. For turning results into money, see measuring AI return in an agency.

Worked example: out-of-hours calls in one branch

Example: a fictional branch finds in its baseline that 41% of calls arrive after half past five or at weekends and that only about a third of those are answered or returned the same day. It pilots AI call answering for evenings and Sundays, with valuations booked into the valuer's diary, viewing requests passed to negotiators and repairs logged with urgent flags to the out-of-hours contact.

Example, continued: in week one the owner corrects several call notes where property names were misheard, and adds missing parking details to three property sheets. By week four the error rate is low, review takes twenty minutes a day and the branch has booked noticeably more valuations from evening calls. The team votes to keep it. The sponsor extends the pilot to the second branch, keeping the same scorecard. Before switching on, both branches work through an AI call answering checklist.

Write it up

Whatever the decision, write a one-page summary: the task, the baseline, the results against each threshold, the main errors and fixes, the team's view and the decision. Store it with the data protection assessment. When the next tool comes along, the summary is the template, and the agency gets better at piloting each time. The same discipline helps when you review bigger systems, such as an estate agent CRM.

Frequently asked questions

How long should an AI pilot in an estate agency last?

About 30 days of live use after two weeks of baseline measurement. That is long enough to get past early teething problems and short enough to keep the team focused on the decision.

Which task should we pilot first?

A high-volume, low-risk task that is easy to measure, such as out-of-hours call answering or inspection write-ups. Avoid tenant selection or anything that makes significant decisions about people.

Do we need a DPIA for a pilot?

Screen the processing before you start. If it is likely to result in a high risk to people, for example recording every call, complete an impact assessment before going live, even for a pilot.

What if the results are mixed?

Adjust the set-up, such as scripts, approved facts or hours, and run a second 30 days with the same scorecard. Stop if safety or error thresholds fail.

References

  1. Department for Science, Innovation and Technology (GOV.UK) (2026). Cyber security breaches survey 2025/2026 (opens in a new tab) ↑

  2. legislation.gov.uk (The National Archives) (2026). UK GDPR, Article 35: Data protection impact assessment (opens in a new tab) ↑

  3. Office for National Statistics (2026). Artificial intelligence in UK businesses: 2023 to 2026 (opens in a new tab) ↑

  4. Department for Science, Innovation and Technology (GOV.UK) (2024). Public attitudes to data and AI: Tracker survey (Wave 4) report (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo