Services How It Works About Blog Contact BOOK CALL

AI and Consumer Duty Compliance for UK Estate Agents

TL;DR

Consumer Duty (FCA PS22/9) applies to estate agencies carrying on regulated financial activities – mortgage introductions, insurance distribution, bridging-finance referrals – and it requires you to evidence four consumer outcomes, not just document that processes exist. A compliance folder is not compliance evidence; the FCA wants contemporaneous, timestamped records of what actually happened for each client. AI agents deployed inside your CRM produce that audit trail as a by-product of routine work – provided they are built on a UK GDPR-compliant data design from the start.

Consumer Duty has been in force for two years. Most estate agency directors know it exists. Far fewer have built the evidence infrastructure the FCA actually expects to see.

The regulation applies to firms carrying on regulated financial activities — which includes estate agencies offering mortgage introductions, insurance distribution, or bridging finance referrals. If your agency refers clients to financial products and earns a fee, Consumer Duty applies to you. The question is not whether you are in scope. It is whether you can prove compliance if the FCA asks.

This is where the AI Strategy Intensive starts for compliance-conscious agencies: not with AI, but with the data infrastructure question. What records do you have? What can you reconstruct? And what would an FCA reviewer actually find if they looked?

What Consumer Duty Actually Requires

Consumer Duty (FCA PS22/9) came into force 31 July 2023 for open products and services, and 31 July 2024 for closed products and services. It requires firms carrying on regulated financial activities to demonstrate four consumer outcomes: Products & Services are fit for purpose; Price & Value is fair; Consumer Understanding is enabled; Consumer Support is accessible. Firms must evidence these outcomes — not just document that they have processes in place.

That last sentence is where most agencies are exposed. The FCA has been explicit about this distinction: a compliance folder is not compliance evidence. A written policy saying "we ensure clients understand our services" is not evidence that any specific client understood anything. The regulator wants to see what actually happened — for individual clients, at specific points in time, with contemporaneous records.

The four outcomes are not abstract principles. They are measurable standards with direct implications for how agencies document their client relationships:

The FCA's supervisory approach is outcomes-based. Inspectors will not be satisfied by a policy document that says the right things. They will ask to see the data that proves the outcomes occurred. Agencies that cannot produce that data are at risk, regardless of whether their intentions were good.

Who Is Actually in Scope

Not every estate agency is directly regulated by the FCA. But the scope is broader than many directors realise. If your agency earns commission on mortgage referrals, recommends insurance products, or introduces clients to bridging or development finance, you are carrying on regulated activities. The Consumer Duty obligations flow from those activities — not from estate agency itself, but from the financial services layered on top of it.

HMRC, not the FCA, supervises estate agents for anti-money laundering compliance. But the FCA supervises the regulated financial activities that many agencies treat as a revenue stream. Understanding which regulator governs which activity is itself a Consumer Duty requirement — you cannot demonstrate adequate consumer outcomes if you do not know which framework applies to each part of your business.

Why Process Documentation Isn't Enough

The FCA's shift to outcomes-based regulation is explicit: a compliance folder is no longer evidence of compliance. The regulator expects firms to demonstrate that consumers actually received the intended outcomes — which requires systematic data collection, timestamped records of interactions, and measurable evidence of outcomes delivered. Retrospective documentation does not satisfy an FCA review.

This is the compliance gap that most agencies do not know they have. They have procedures. They have training records. They have a file that says "Consumer Duty policy — reviewed annually." What they do not have is an ongoing, contemporaneous record that client outcomes were actually delivered across their regulated activities.

Retrospective documentation is the specific problem the FCA is designed to catch. When a review is triggered — whether by a complaint, a thematic review, or a firm-specific supervision visit — the regulator will look at when records were created relative to when events occurred. Documentation created after the fact, in response to a review, carries significantly less weight than records created at the time of each client interaction.

The agencies most exposed under Consumer Duty are not necessarily the ones doing bad things. They are the ones that did the right things but did not document them systematically as they happened. Good intentions do not create compliance evidence. Consistent data infrastructure does.

The compliance question is not "did we treat clients fairly?" It is "can we prove, for each client, what happened and what outcome they received?"

The Audit Trail Standard

What the FCA is looking for in practice is an audit trail: a connected sequence of records showing that for a given client, at a given point in time, specific steps were taken and specific outcomes were achieved. This requires three things working together: timestamped records of client interactions, structured data that can be searched and aggregated, and records that were created contemporaneously — not reconstructed.

Manual systems can produce audit trails. The problem is that manual systems are inconsistent. A negotiator who is busy will defer record-keeping. A client interaction that happens over the phone may not get logged. A referral that generates commission may have a fee disclosure sent but no record of whether the client acknowledged or understood it. These gaps are invisible in a busy agency — and visible in an FCA review.

The Data Trail: How AI Creates Compliance Evidence

AI agents create structured, timestamped records of every client interaction — communications sent, advice given, decisions made, outcomes delivered. This ongoing data trail replaces ad hoc manual records with systematic, auditable evidence. When the FCA asks what happened for a given client, the answer is already in the data.

This is the point where AI and compliance intersect in a way that is genuinely useful — not as marketing language, but as a practical operational reality. When AI agents are deployed inside your CRM to handle client communications, they do not just send messages. They create records. Every output is logged, timestamped, and associated with a specific client record. The compliance evidence is a by-product of the operational workflow.

Consider the Vendor Update Agent as a concrete example. Deployed inside your CRM, it generates structured progress updates to vendors at defined intervals — after viewings, at weekly check-ins, following key milestones. Each update is logged in the client record with a timestamp. The content is consistent and on-brand. The frequency is systematic, not dependent on whether a negotiator is having a busy week.

From a Consumer Duty perspective, this single agent creates evidence across multiple outcomes simultaneously:

The Viewing Follow-Up Agent creates similar evidence. Each follow-up communication is logged, dated, and associated with both the applicant and the property. The record shows what information was provided, when, and what the client's response was. Over the course of a transaction, this builds the kind of granular, contemporaneous evidence trail that an FCA inspector would expect to see.

GDPR and AI: Getting the Design Right

AI agents that process personal data — and all client-facing agents do — must operate within a lawful basis under UK GDPR. This is not an optional consideration. It is the difference between a compliance advantage and a regulatory liability. The data infrastructure that powers AI agents must be designed with data minimisation, purpose limitation, and audit-ready records from the start — not retrofitted after deployment.

Agencies that deploy AI without a GDPR-compliant data design are trading one compliance risk for another. The AI Strategy Intensive addresses this directly: the Discovery stage (Weeks 1-2) audits existing CRM data quality, establishes the lawful basis for each data processing activity, and configures the data governance baseline that any agents you go on to deploy operate within. Compliance by design, not compliance by accident.

Where Does Your Compliance Data Trail Start?

The AI Strategy Intensive begins with a two-week Discovery: it maps your current data infrastructure against Consumer Duty requirements and identifies exactly where the gaps are — with a costed case for closing them, or Discovery is refunded in full.

BOOK A DISCOVERY CALL

Building Your Compliance Record Before the Next FCA Review

Forward-thinking agencies are building systematic compliance records now, before regulatory review. Deploy AI agents to log client interactions, track outcome evidence, and flag documentation gaps. When the FCA asks for evidence, the data already exists — it does not need reconstruction under time pressure.

The timeline matters. Consumer Duty is not a one-time compliance exercise — it is an ongoing obligation. The FCA expects firms to demonstrate outcomes across the full duration of client relationships, which for estate agencies can span months from first instruction to completion. Building the evidence infrastructure after a review is triggered is too late. The data that matters most is the data that was created at the time, not assembled afterwards.

The operational advantage of building this infrastructure now is compounding. Every client interaction logged today becomes part of a growing evidence base. Every AI-generated communication that enters the CRM creates a timestamped record. After six months of systematic operation, an agency has a compliance record that no retrospective documentation exercise could replicate — because it was created in real time, as the client relationships developed.

Example Agents, Distinct Evidence Streams

The AI Strategy Intensive builds the fix for the bottleneck Discovery surfaces. Where that fix involves client-facing AI agents, each one can create distinct compliance evidence alongside its primary operational function. Example deployments include:

None of these agents were designed primarily as compliance tools. They were designed to improve agency operations, reduce staff time on routine communications, and improve client experience. The compliance evidence is a structural consequence of how they work — which is exactly the right way to approach Consumer Duty. Compliance that emerges from good operations is sustainable. Compliance that requires separate manual effort is not.

What a Compliance-Ready CRM Looks Like

After an AI Strategy Intensive, an agency's CRM contains a searchable, structured record of client interactions that can be exported, audited, and presented in response to an FCA request. The records are timestamped, associated with specific clients and transactions, and created by a systematic process rather than dependent on individual staff behaviour. The compliance record exists as a side effect of running the business well.

Compare that to the typical starting state: notes in free-text fields, emails in individual inboxes, verbal communications with no record, and a compliance folder that documents what the agency intended to do rather than what it actually did. The gap between those two states is the gap between compliance risk and operational advantage.

Next Steps

The starting point is the AI Strategy Intensive — an eight-week engagement that audits current data infrastructure, identifies Consumer Duty evidence gaps, and builds the AI agents needed to create an ongoing compliance record on your existing CRM. The first two weeks are Discovery: you get a costed case for closing your single biggest gap, or Discovery is refunded in full.

The eight-week structure is deliberate. Weeks 1-2 are Discovery — auditing your existing CRM data against Consumer Duty requirements, establishing the lawful basis for AI data processing under UK GDPR, and identifying the gaps between your current records and what the FCA would expect to find. This stage surfaces the compliance risk you currently carry, often for the first time, and produces a costed case for the single biggest gap before you commit to the build.

Weeks three and four are Design: the fix is designed against the bottleneck Discovery surfaced, the context and data layer is specified, and the first working artifact is reviewed. Weeks five and six are Build: the fix is built and connected to your existing CRM — not in a test environment, not in a pilot, but in production — with data quality issues surfaced and handled along the way. Because you only commit to the build once you have seen the costed Discovery case, the work that follows is scoped to the gap that actually matters, not a fixed template.

Weeks seven and eight are Deploy and Measure: the system goes live across branches, your team is trained, and ROI is measured against the revenue-per-employee baseline established in Discovery. This stage reviews output quality against real data, refines the agents based on what they are actually producing, and sets the trajectory for the AI Transformation Partnership that can follow. The handover documentation means your team can manage the system without ongoing dependency on AGI Automations.

The question most directors ask at this point is: "Can we wait?" Consumer Duty is already in force. The FCA has been running thematic reviews of firms in scope since 2024. Every month without a systematic compliance record is a month where the evidence that matters most — contemporaneous, real-time records of client outcomes — is not being created. You cannot retroactively build a compliance trail. You can only start building it now.

Start Building Your Compliance Evidence Now

Our 8-week AI Strategy Intensive pinpoints the single biggest bottleneck holding back your revenue per employee, then designs, builds and deploys the fix on your existing CRM — measured against an RPE baseline. The first two weeks are Discovery: you get a costed case for the fix, or we refund Discovery in full.

EXPLORE THE AI STRATEGY INTENSIVE
About the author

Ben Van Dyke is the founder of AGI Automations and a CDMP-credentialled data professional and Anthropic system integrator. He specialises in AI and data architecture for UK multi-branch estate agencies, and created the Institutional Context Architecture (ICA) methodology and the Revenue Per Employee (RPE) arbitrage framework. Connect on LinkedIn.

← Back to Blog