Estate Agent Client Portals: Use Your CRM's, Buy One or Build Your Own

An estate agent client portal is a secure login where your vendors, buyers, landlords and tenants see their own sale or tenancy (viewings, feedback, offers, progress, statements, documents) without ringing the office. For most UK agencies the right first move is to switch on the portal your CRM already includes. A custom portal on your own website earns its cost only when the client experience is part of what you sell, as it is for prime agents, developers and agencies with international clients, or when the CRM's version cannot show what your clients need.
This guide sets out what each type of client wants to see, the three ways to give it to them, and how to tell which one fits your agency.
The short version
- A client portal is a private, logged-in window onto your CRM: each client sees their own sale or tenancy and nothing else.
- Sales take longer than they used to. Connells Group puts the average time from sale agreed to exchange at 120 days in 2026, up from 78 days in 2016 (Property Industry Eye, 18 November 2026). A portal does not shorten that wait, but it fills the silence.
- Street.co.uk, Alto and Reapit all ship a client portal, and Alto says its Keyflo portal is included in the Alto subscription (checked November 2026). Check what you already pay for before buying anything.
- Generic portal software is built for service businesses in general, not UK agencies. Without a live link to your UK CRM, somebody re-types every update.
- A custom portal on your own domain reads from your CRM's API (Reapit Foundations, the Street Open API), so the CRM stays the source of truth and you own the experience.
- Build only when brand, the data you need to show, or a second language matter more than speed. Otherwise switch on what you have.
What is an estate agent client portal?
An estate agent client portal is a password-protected area, on the web or in an app, where a client logs in to follow their own transaction with your agency. A vendor sees viewings, feedback and offers on their home. A landlord sees rent statements and maintenance jobs. Nobody sees anyone else's file.
In the UK the word "portal" usually means Rightmove, Zoopla or OnTheMarket, so the same thing goes by several names: vendor portal, landlord portal, client app, online tracker. They all describe a view of the data your team already keeps in the CRM, filtered to one person and presented so they can act on it.
That last point matters. A portal is only as good as the record behind it. If negotiators log feedback three days late, the portal shows it three days late, in writing, to the client.
Why client portals matter more in 2026
Client portals matter more now because the wait between sale agreed and exchange has grown by more than a month in ten years. Connells Group says the average went from 78 days in 2016 to 120 days in 2026, and its own sales average 110 days, as reported by Property Industry Eye on 18 November 2026.
| Measure | Days |
|---|---|
| Market average, 2026 | 120 |
| Connells Group, 2026 | 110 |
| Market average, 2016 | 78 |
The cost of that wait lands on your team as well as your clients. In research by Landmark Information Group, agents, conveyancers and lenders estimated they spend 34% of their working time chasing outstanding information and answering enquiries, and the share of agents frustrated by poor communication between parties rose from 19% to 36% since Landmark's 2025 research (Property Industry Eye, 23 October 2026, summarising Landmark's report). Landmark also surveyed 500 recent movers: 67% had faced uncertainty or delays after agreeing a sale.
The industry's bigger fix is shared data. The National Property Transaction Network, built by LMS with Connells, aims to collect property, identity and financial information once and share it securely between agents, lenders and conveyancers. Skipton expanded its role in November 2026 (Property Industry Eye, 10 November 2026) and Santander joined on 18 November (Property Industry Eye, 18 November 2026). As both reports note, the network has not yet published how much time it saves.
So be honest about what a portal does. It will not make a conveyancer reply faster. It will make the wait visible, put the answer to "where are we?" in the client's pocket, and give your progressors back some of the hours they spend repeating themselves.
What vendors, buyers, landlords and tenants want to see
Each type of client wants a different slice of the same record, and the best portals show each one only their slice. The grid below is built from what Street.co.uk's Client App and Alto's Keyflo describe on their own product pages (November 2026), which is a fair picture of what UK clients now expect.
| Feature | Vendor | Buyer | Landlord | Tenant |
|---|---|---|---|---|
| Book or track viewings | Yes | Yes | Yes | Yes |
| Viewing feedback | Yes | No | Yes | No |
| Offers and sale progress | Yes | Yes | No | No |
| Approve the listing | Yes | No | Yes | No |
| Documents, e-signing, ID checks | Yes | Yes | Yes | Yes |
| Rent statements and invoices | No | No | Yes | No |
| Maintenance requests | No | No | Yes | Yes |
| Certificates, tenancy documents | No | No | Yes | Yes |
Vendors
Vendors want proof that you are working for them. That means confirmed viewings, written feedback soon after each one, every offer as it arrives, and once the sale is agreed, the milestones: searches ordered, mortgage offer, survey, exchange date. Alto says Keyflo vendors see viewings, feedback and offers, and that you control what they can access. That control is the real design work: raw feedback from a viewer is not always something you want a seller to read word for word.
Buyers
Buyers want fewer emails and more certainty. Book and rearrange viewings, submit an offer at eleven at night, upload proof of funds and solicitor details, then follow the sale. Street describes a buyer flow that collects anti-money laundering (AML) checks, proof of funds and solicitor details straight after an offer.
Landlords
Landlords want their money and their obligations in one place: monthly statements, invoices, maintenance jobs waiting for approval, gas and electrical certificates, and the tenancy history. Portfolio landlords care most about seeing every property at once.
Tenants
Tenants want to report a problem with a photo and know it has been seen. After that, they want their tenancy agreement, certificates and inspection reports without asking for them again.
Option 1: switch on the portal your CRM already has
The portal built into your CRM is the quickest and cheapest route, because the data is already there and nobody has to build anything. The three CRMs you are most likely to run all offer one (checked November 2026):
- Street.co.uk. One Client App adapts to whoever signs in (vendor, buyer, landlord or tenant) and takes on your logo, colours and agency name with no Street branding.
- Alto. Keyflo gives vendors and landlords documents, e-signing, ID and AML checks, listing approval and progress tracking, and Alto states it is included in the subscription. Keyflo covers everything up to "let agreed"; Alto points landlords and tenants to its separate PropertyFile portal after move-in.
- Reapit. Reapit lists a Client Portal among the platform's client-facing features alongside its workflows and task plans.
What you give up is control. Your clients use the same app as every other agency on that CRM, with your logo on top. You get the features the CRM vendor decides to build, in the order it builds them. If you change CRM, the portal goes with it and your clients learn a new one.
For a one or two branch agency whose clients mainly want feedback and progress, that trade is usually worth making. Switch it on, test it as a vendor yourself, and train the team to keep the record current.
Option 2: buy standalone client portal software
Standalone portal software gives you a white-label client area that is not tied to any CRM, and for most UK estate agents it is the wrong tool. Much of what ranks for "estate agent client portal" is this category: general client portal tools such as Assembly and Moxo, built for service businesses of every kind rather than for UK agencies. SuiteDash is another.
The prices can look tempting. SuiteDash's pricing page lists a Start plan at $19 a month with unlimited portals and white labelling (US dollars, as of November 2026). The catch is the data. None of them is built around a UK property CRM, so unless you connect the two, it does not know what happened in your CRM this morning. Either someone re-types each viewing and offer, or you glue the two together with an automation tool and maintain that glue for ever.
There is one case where it fits: a service your CRM does not model at all. A buying agency, a relocation service, or a refurbishment project for an overseas owner has its own documents, tasks and invoices, and a general portal can hold those well.
Option 3: build a custom portal on your own website
A custom portal is a logged-in section of your own website that reads your clients' data from the CRM's API and presents it in your design, on your domain. The CRM remains the source of truth. The portal is a window onto it.
- Your CRM (Reapit, Street, Alto): the record your team updates.
- API and webhooks: read changes and hear events as they happen.
- Portal database: a synced copy, fast to read, every access logged.
- Your domain: the client logs in and sees only their own sale or tenancy.
- Return path: client actions (feedback replies, uploads, approvals) are written back to the CRM.
Whether this is practical depends on your CRM's API, and the picture differs by vendor:
- Street.co.uk. The Street Open API covers companies, branches, viewings, valuations, applicants, vendors, tenants and landlords, with webhooks for real-time events and a sandbox for testing. Street says agencies on its platform can use it to build their own tools.
- Reapit. Reapit Foundations is a REST API whose data model includes vendors, landlords, contacts, properties and enquiries. Reapit charges for API consumption and warns developers not to call the API on every page render, so a portal should sync into its own database rather than query Reapit live.
- Alto. The Alto feed most websites use is a property feed. For client-level data, ask your Alto account manager what partner access is available before anyone quotes you. We explain the property side of all three in our guide to property feeds for estate agent websites.
What a custom portal involves
A custom portal is a web application, not a page, and the work sits in the parts clients never see:
- Sign-in. Email links or passwords, with two-factor authentication for anything holding identity documents or bank details.
- Roles. One person can be a vendor on one property and a landlord on another. Each login must see exactly their records.
- Sync. A scheduled job plus webhooks keeps the portal's copy current without hammering the CRM.
- Documents. Encrypted storage, expiring download links, and a log of who opened what.
- Write-back. A vendor's reply or a tenant's maintenance photo goes back into the CRM against the right record.
- Notifications. Email or push when something changes, so clients do not have to keep checking.
- Upkeep. Hosting, monitoring, security updates, and changes when the CRM's API changes.
The reward is a portal that is entirely yours: your design, your domain, English and Italian if your buyers are in Milan, and data the CRM does not hold, such as development build updates or how the property's page on your own site is performing. And if you change CRM, you rewrite the connector, not the portal. Your clients keep the same login.
Use your CRM's portal, buy one or build: how they compare
The right route depends less on features than on how much the client experience is part of what you sell. This comparison sets the three side by side.
| CRM's own portal | Standalone software | Custom, on your site | |
|---|---|---|---|
| Set-up | Switch it on; often in the subscription | Monthly fee; you configure it | A build project, then hosting and upkeep |
| Data | Live from the CRM | Re-typed, or glued on with automation | Synced from the CRM API, plus your own data |
| Branding | Your logo and colours on the vendor's design | White label, generic layout | Your design, domain and language |
| Changes | What the CRM vendor puts on its roadmap | Within the tool's modules | Anything the API exposes |
| New CRM | Portal goes; clients learn a new one | Stays; reconnect the automations | Rewrite the connector; clients keep their login |
| Best for | Most agencies, as the first step | Services the CRM does not model | Prime agents, developers, international clients |
When a custom client portal is worth building
A custom portal is worth building when the portal itself is part of the service you are paid for. From the builder's side, that usually means one of these:
- Prime and luxury agencies. A seller instructing you on a prime family house judges you by every touchpoint. A generic app with your logo on it undoes the work your bespoke website did to win the instruction.
- Developers selling off-plan. Reservations, stage payments, build progress photos, upgrade choices and snagging lists are not things a resale CRM models well.
- International and bilingual clients. Overseas buyers and owners want the portal in their language and their time zone, with updates they can read without a phone call.
- More than one system. Sales on one CRM, lettings on another, property management somewhere else. A custom portal can put all three behind one login.
- Portal and website as one product. The client who searches your listings, books a valuation and later follows their sale should never feel they have left your brand.
It is not worth building when:
- your clients mainly want feedback and progress, and your CRM's portal already shows both;
- your team does not keep the CRM current, because a portal broadcasts the gaps;
- you are about to change CRM, because that decision comes first.
How to decide in an afternoon
One afternoon testing your CRM's portal as a client, and one week logging why clients ring, tell you whether to switch on, buy or build:
- Ask your CRM provider what is included. Then switch the portal on for a test property and log in as a vendor and as a landlord.
- Count the calls. For one week, have negotiators and progressors note why each client rang. The top five reasons are your portal's job description.
- Check the gap. Does the CRM portal answer those five reasons? If yes, roll it out and stop here.
- Check the API. If not, ask whether the missing information is available through the CRM's API, and whether there is a sandbox to test against (Street offers one).
- Start small if you build. One client type, usually vendors, and one job, usually feedback and sale progress. Add landlords and write-back once that works.
Security and data protection
A client portal holds personal data at its most sensitive: identity documents, AML checks, bank details and rent statements. Under the UK GDPR's security principle you must protect it with "appropriate technical and organisational measures", and the ICO's guide to data security points to encryption, risk analysis and regular testing (the ICO notes the guide is under review after the Data (Use and Access) Act, as of November 2026).
In practice: two-factor sign-in, encryption at rest and in transit, the least access each role needs, an audit trail, and a data processing agreement with whoever hosts it. A CRM-bundled portal handles most of this for you. A custom one makes it your developer's job, so ask how they will do it before you ask how it will look.
Your next step
Start with the portal you already pay for. If you have tested it as a client and it still does not show your vendors, landlords or buyers what they need, that gap is the brief for a custom build.
That is the kind of work we do at The Code Bottega in London: web apps and custom software for property businesses, built on top of the CRM you already run, alongside real estate website development in English and Italian. For an example of a property platform we built from listings to lead capture, see AFFITTO/VENDO.
