Fractional CTO for Estate & Letting Agents
You are running an agency on software you did not choose, cannot change, and pay for per branch per month. Or you are building a proptech product, the MVP works, and the person who built it has moved on. Either way the question is the same: who owns the technology decisions, and what happens to the business when they are made badly? I do that job one or two days a week — for agencies from eight staff to two hundred, and for the founders selling into them.
- Who I work with
- Managing Director / OwnerOperations DirectorHead of LettingsFounder / CEO (proptech)Group Finance Director
- Company size
- 8–250 staff, typically 0–12 in anything resembling a tech team
- Typical range
- £1m–£40m turnover, or pre-seed to Series A for proptech
You have a product, some agency customers, and an integration layer holding it all together with duct tape. You need architecture that survives the next hundred customers, and someone credible in the room when a portal, an investor or an enterprise agency group starts asking technical questions.
Twenty years of trading, four acquired branches, three CRMs, and nobody who can say what the technology should cost or do. You need someone to inventory it, cut what is dead, integrate what is not, and stop the next six-figure software decision from being made in a sales meeting.
What actually goes wrong in property businesses
None of these are hypothetical. They are what turns up in the first fortnight of nearly every property engagement I take.
Your CRM and your portal feed quietly disagree
A price reduction goes into the CRM, the negotiator sees it, the branch window shows it — and Rightmove is still showing last month's number because the feed silently failed on a malformed field three days ago. Nobody is monitoring the feed. You find out when a vendor calls, angry, or when a lead arrives quoting a price you no longer accept.
One stale listing on a portal for a week costs more in vendor trust than a year of feed monitoring.
Your data is hostage to your CRM contract
Reapit, Alto, Jupix and the rest hold your applicants, your vendors, your tenancy history and your entire trading record. Getting it out means a support ticket, an export fee, or a CSV that drops the fields you actually need. So you stay — not because the software is good, but because leaving costs more than the annoyance of staying.
Exit clauses are the single most expensive line most agency owners have never read.
Every new tool is another login and another re-key
Referencing in Goodlord, repairs in Fixflo, AML checks in Thirdfort or Credas, deposits with the TDS or DPS, rent in PayProp, accounts in Xero. Six systems, six logins, and a property manager typing the same tenant name into all of them. The integration you were promised turns out to be a nightly CSV, or nothing at all.
Typically 20–40 minutes of re-keying per tenancy, every tenancy, forever.
Compliance dates live in a spreadsheet somebody maintains by hand
Gas safety certificates, EICRs, EPCs, licensing, right-to-rent checks — all with expiry dates, all attached to a property, and all tracked in a shared spreadsheet that one person owns and nobody has tested. When that person is on holiday and a certificate lapses, the exposure is not a bad review. It is a criminal offence and an unenforceable section 21.
A single lapsed gas certificate can invalidate a possession claim entirely.
Material information rules changed and your data model did not
National Trading Standards now expects tenure, council tax band, rights and restrictions, flood risk and more to be on the listing up front. Most agency CRMs bolted these on as free-text fields. So the information exists, sort of, in a text box, unvalidated, and nobody can report on which listings are actually complete before they go live.
Client money reconciliation is a monthly act of faith
Rent in, commission out, landlord statements, contractor invoices, deposits held. Under Client Money Protection rules this has to reconcile exactly, every month, and be auditable. In a lot of agencies it reconciles because one experienced person knows where the bodies are buried — not because the system makes it impossible to get wrong.
Your AI pilot is three people pasting into ChatGPT
Someone started writing listing descriptions with AI, it was good, and now it is unofficial company policy. No prompt standards, no review step, no record of what went out, and property details being pasted into a consumer tool. The upside is real. The governance is nil, and the first bad description with an invented feature is a misdescription problem.
Nobody owns technology, so the loudest supplier decides it
The ops director does IT on top of a full job, an outsourced agency does the website, the CRM vendor does everything else, and each of them tells you a different story. There is no roadmap, no budget line that tracks against outcomes, and no one whose job it is to say no to a bad three-year contract.
The stack you are probably stuck with
UK property runs on a small number of incumbent systems and a long tail of point solutions bolted to their edges. I have no allegiance to any of the vendors below — the goal is to make the stack you already own work, and only replace what genuinely cannot.
Sales & lettings CRM
This is the system of record and the source of most pain. API access ranges from a genuine modern REST API to a paid add-on to nothing at all. Before anything else gets built, we establish exactly what your contract permits, what the API can read and write, and what your data extraction rights are on exit.
Portals & listing distribution
Feeds fail quietly. Nothing in a standard setup tells you a property did not update, or that a branch is publishing incomplete material information. A reconciliation job that compares what the CRM believes is live against what the portals actually show is a few days of work and ends an entire category of complaint.
Property management & maintenance
Repairs, contractor jobs, rent and accounts each live in their own system with their own view of a property. The same address exists four times with four different identifiers and no shared key, which is why nobody can answer 'what did this property cost us last year' without a manual afternoon.
Compliance, AML & referencing
Bought individually as regulation demanded them, integrated with nothing. Each holds a fragment of the truth about a person or a tenancy, and the audit trail an HMRC AML inspection or a redress complaint needs has to be assembled by hand from several screens.
Marketing, prospecting & data
Prospecting tools generate leads that arrive by email and get typed into the CRM. Attribution stops at the form, so nobody can say which channel produced instructions rather than enquiries — which means the marketing budget is allocated on anecdote.
Almost nothing here needs replacing. What is missing is a layer above it: one place where a property, a person and a tenancy have a single identity, one job that checks the feeds and the certificate dates every night, and one person who reads the contracts before they renew. That is a few months of focused work, not a platform rebuild.
What good looks like in a property business
Not a rebuild. A short list of things that should be boringly true and usually are not.
Listings are provably in sync, and you know within an hour when they are not
A nightly reconciliation compares the CRM against every portal and your own site, and anything that disagrees lands in a channel a human watches. Feed failures stop being discovered by vendors. New properties cannot go live missing the material information fields that Trading Standards expects.
Compliance dates are a system, not a spreadsheet
Every certificate, licence and check hangs off the property record with an expiry date, an escalating reminder, and a report anyone can pull. The question 'which of our managed properties has a gas certificate expiring in the next 60 days' takes four seconds, and the answer is trustworthy enough to act on.
A property, a landlord and a tenant have one identity across every system
The same property in the CRM, the maintenance system and the accounts package shares a key. That single decision is what makes portfolio reporting, landlord statements and profitability analysis possible — and its absence is why those things currently take days.
You know what your technology costs per branch and what it returns
One page: every system, its renewal date, its per-seat and per-branch cost, its notice period, and what would break without it. Most agencies find between eight and fifteen percent of that spend is duplicated or dead within the first month of looking properly.
AI is in the workflow, with a review step and a record
Listing copy, enquiry triage and inbound call summarisation are genuinely good uses of a language model in this business. Done properly they run inside your systems, on your data, with a human approving anything that reaches a consumer and a log of what was generated. Done badly they are a misdescription risk with a monthly subscription.
Someone senior says no to bad contracts before you sign them
Three-year terms with automatic renewal, per-branch pricing that punishes growth, and no data extraction clause are all normal in this market and all negotiable. Having someone technical read the schedule before the ink dries routinely saves more than the engagement costs.
Find out what your stack is actually costing you
A 30-minute call, no pitch deck. Tell me which CRM you are on, how many branches you run, and what broke most recently. Most conversations end in one of two fixed-fee starts: The Second Opinion, five days and a written verdict on the software you are paying for, or Cyber Essentials in Three Weeks when a client contract is waiting on the certificate.
The first 90 days
Deliberately unglamorous. The first month is almost entirely finding out what is true, because in property the gap between what the business believes about its systems and what is actually happening is unusually wide.
- Days 1–14
Find out what is actually true
- Full system inventory — every platform, its per-branch cost, renewal date, notice period and contract owner, on one page
- Read the CRM contract properly: API terms, data extraction rights, exit clauses, price escalators
- Map the listing lifecycle end to end, from instruction to live on every portal, and count the manual touches
- Sit with a negotiator for half a day and a property manager for half a day, and watch what they actually do
- Check the portal feeds against the CRM for the last 30 days and quantify the drift
- Establish where compliance expiry dates live and who, by name, maintains them
- Days 15–45
Stop the bleeding
- Automated nightly reconciliation of CRM against Rightmove, Zoopla, OnTheMarket and your own site, alerting to a channel people watch
- Compliance certificate tracking moved off the spreadsheet onto the property record with escalating reminders
- Material information completeness check that blocks or flags an incomplete listing before it publishes
- Kill duplicated and unused subscriptions found in the inventory; renegotiate anything renewing within 90 days
- One documented AI usage standard for listing copy and enquiry handling, with a mandatory human review step
- Days 46–90
Decide what to build, buy and bin
- A shared property and contact identity across CRM, maintenance and accounts — the foundation everything later depends on
- A costed, dated build-versus-buy recommendation on the two or three biggest gaps, with the ten-year cost of each option
- For proptech: an architecture review of the integration layer and a scaling plan for the next hundred customers
- A twelve-month technology roadmap tied to branch count, headcount and revenue rather than to vendor release notes
- A hiring or partner recommendation — whether you need a permanent technical hire, an agency, or neither yet
At day 90 you have one page showing every system and what it costs, feeds and compliance dates that monitor themselves, a single identity for a property across your stack, and a written roadmap with prices attached. Whether I stay on beyond that becomes a straightforward commercial decision rather than a dependency.

Listed satellite-servicing operator
Space / satellite servicing & debris removal
A property business is, at its core, a content and integration problem: branch staff publishing structured records to multiple external channels, under rules where a wrong or stale field carries real consequences. That is exactly what this build was — a composable content system where the editorial team assembles and publishes pages with no engineering involvement, fed from a headless CMS through typed integrations, under a strict security posture. Swap sections for listings and locales for portals and the architecture is the same shape.
Built the entire ERP from zero for UK's largest 3D printing service — quotes, orders, production, dispatch across £2M of machines.
Engineered the Icon Payments Framework trusted by Citi, NatWest, BNP Paribas, JP Morgan.
Questions I get asked in this sector.
We are locked into Reapit (or Alto, or Jupix). Can you actually change anything?
Yes, and usually without leaving. Most of what frustrates agencies is not the CRM itself but the absence of anything around it — no feed monitoring, no shared identity with the maintenance and accounts systems, no reporting layer. Those are built alongside your CRM, not instead of it. The first thing I do is read your contract to establish exactly what the API permits and what your data rights are, because that determines what is possible. Migration is occasionally the right answer, but it is the last option I reach for, not the first.
Do I need a CTO, or do I just need a better software supplier?
Often the second, and I will tell you if that is the case. The test is whether your problems are delivery problems or decision problems. If you know what you want built and it is not getting built, you need a better supplier. If every supplier tells you something different, your systems do not talk to each other, and nobody can say what technology should cost you per branch, that is a decision problem and no supplier will fix it — they are the interested party. A fractional CTO is worth it when the decisions are the bottleneck.
We want to build our own portal or our own app. Is that a good idea?
Almost always no for a portal, and it depends for an app. Competing with Rightmove and Zoopla means competing on liquidity, not software, and no agency has ever won that. A tenant or landlord app is a different question: it can genuinely reduce inbound calls and improve retention, but only if it is connected to live data from your CRM and maintenance systems. An app showing stale information generates more calls than it prevents. I would want to see the call volume data before recommending it.
Is AI actually useful in an estate agency, or is it hype?
Genuinely useful in four places: drafting listing descriptions from property facts, triaging and routing inbound enquiries, summarising calls into the CRM, and extracting data from documents like EPCs, certificates and tenancy agreements. All four are established, unglamorous and save real hours. What does not work yet is anything where the model's output reaches a consumer unreviewed — descriptions especially, because an invented feature is a misdescription. The value is in wiring it into your systems with a review step, not in the subscription.
We are a proptech startup, not an agency. Is this page for you or for us?
Both, and the two halves inform each other. For proptech founders the work is different in emphasis: architecture that survives scale, an integration layer that does not break every time a CRM vendor changes something, security and diligence readiness before a raise or an enterprise agency deal, and a hiring plan for your first engineers. Knowing how agencies actually operate is the part most technical advisors lack — it is why integration roadmaps written without it consistently miss.
What does this cost and how quickly do we see something?
Engagements are typically one or two days a week on a monthly retainer, with no long tie-in. Something concrete lands inside the first fortnight: the system inventory with every renewal date and per-branch cost on one page has, on its own, paid for the first month more than once. The heavier work — feed reconciliation, compliance tracking, shared property identity — lands across the following two months. Book a call and I will tell you honestly whether the numbers make sense for your size of business.
You are the one who signs off the spend. This is the seat that shows you the working. Technical direction owned, the team unblocked, fundraising and hiring run as workstreams, and a technical voice that answers to your board rather than to a supplier.
Learn moreFrom a demo to software your customers actually use. Architecture, full-stack build, data and AI, infrastructure and delivery — owned end to end by one accountable engineer, on a fixed shape with a date attached.
Learn moreGet certified, not just "ready". Cyber Essentials, then Cyber Essentials Plus, then ISO 27001 with ISO 27701 in one combined audit, and ISO/IEC 42001 when AI is in scope — each rung a certificate in its own right, and each one the groundwork for the next.
Learn moreA build you can't evaluate, a demo that has to ship, or a certificate a contract is waiting on.
Book a 30-minute discovery call. Bring what you're building, the decision you need help with, and your timeframe. We will check fit and agree the next step before any paid work.