Case Study

Case Study: Estate Agency Lead & Lettings Automation

We built a connected set of automations for an independent sales and lettings agency: portal and valuation leads answered in one CRM pipeline, viewings booked with feedback collected, sales progressed with automated chasers, tenant repairs triaged and landlord compliance dates tracked. Negotiators and property managers now start the day with clear lists, and every decision about price, offers and safety stays with them.

Agency type
Independent sales and lettings agency with a property management arm
Team involved
Directors, negotiators, sales progressor, property managers, lettings administrator
Systems connected
Agency CRM, portal lead emails, calendars, repairs reporting, Twilio, n8n
Delivery
Scrum, 1-week sprints, about 8 weeks to full launch

The challenge

Where the practice started

Portal leads arrived as emails in a shared inbox and were worked through when negotiators had time, which often meant the next morning. Valuation requests from the website sat in the same pile.

Viewings were arranged by phone and text, and feedback was collected inconsistently, so weekly vendor updates depended on which negotiator was writing them.

The sales progressor tracked deals in a spreadsheet and spent much of each day chasing conveyancers and brokers by phone.

Repair requests came in by every channel without photos, and compliance dates lived partly in the property management system and partly in calendars, so renewals were sometimes booked late.

Goals

What the project had to change

  • Every portal and valuation lead gets a useful reply within minutes and an owner.
  • Viewings book themselves from approved slots, and every visitor is asked the same feedback questions.
  • Every deal has a milestone checklist, and overdue steps are chased automatically.
  • Repairs are logged with photos, emergencies reach a person at once, and landlords approve spend before work.
  • Every compliance date is visible, and renewals are booked well ahead.

What we built

What we built, as one connected system.

01

Lead pipeline in the CRM

We parsed portal lead emails, website forms and valuation requests into one CRM pipeline, with listing-specific first replies, routing by branch and sales or lettings, and a weekly source report.

Service details
02

Viewings and feedback

Applicants book from slots the negotiator and occupier approve, everyone gets confirmations and access notes, and visitors answer the same short feedback form, summarised into a draft vendor update.

Service details
03

Sales progression

An accepted offer creates the milestone checklist, overdue steps trigger polite chasers to conveyancers and brokers, and at-risk deals are flagged to the progressor every morning.

Service details
04

Repair triage

Tenants report repairs on one form with photos; emergency words go straight to the on-call property manager, routine jobs go to approved contractors and quotes above the limit go to landlords for approval.

Service details
05

Compliance tracking

A nightly read of certificate and inspection dates feeds a portfolio tracker, staged reminders and contractor bookings, with timestamped records of certificates sent to tenants.

Service details

Architecture

How the agency's workflows connect

Portals and web Leads, valuations Tenants Repair requests CRM and PM data Offers, dates n8n Five workflows AI steps Parse, summarise CRM pipeline Leads and deals Texts and emails Twilio, email Negotiators Calls, updates Property managers Repairs, safety Log and reports Weekly summary
  • Input
  • Logic and services
  • AI step
  • Data
  • Output
  • People

How it flows

  1. 1 Portal and website leads, tenant repair requests and CRM and compliance data feed one n8n instance.
  2. 2 Five workflows update the CRM pipeline, send texts and emails, and use AI steps to parse leads and summarise feedback.
  3. 3 Negotiators work leads, viewings and progression; property managers handle repairs and compliance.
  4. 4 Every step is logged and a weekly summary shows the measures the agency agreed to track.

How it behaves

How the system behaves day to day

What each person sees and what runs in the background, including what happens when something goes wrong.

What clients and tenants see

  • A reply within minutes after enquiring on a portal or the website
  • Viewing slots to pick from and a short feedback form afterwards
  • A weekly status update during a sale
  • One repair form and texts as the job progresses

What staff see

  • New leads with call tasks
  • Draft vendor updates to edit
  • A morning list of at-risk deals, open repairs and overdue certificates

What the automation does

  • Parses, routes, reminds and chases on schedule
  • Applies consent, opt-outs and quiet hours across every workflow
  • Logs every step and alerts a director if anything fails

Edge cases and fallbacks

A tenant reports a gas smell
The emergency instructions and on-call alert go out at once; nothing is queued.
A portal changes its lead email layout
Unparsed leads go to a review queue and the team is alerted.
A buyer withdraws
The progressor marks the deal and every chaser stops.
A certificate date is missing
Flagged to the property manager; no reminder is guessed.
n8n or Twilio outage
Forms still record requests, the on-call alert falls back to email and directors are notified.

Integrations

What we connected

All integrations

Reapit

Agency CRM (UK)

Applicants, properties, offers, viewings and works orders.

Reapit Foundations APIs and webhooks, through its developer portal.

Street

Agency CRM (UK)

Contacts, properties, applicants, offers and branches.

Street Open API, with tokens issued by the agency admin.

HubSpot

CRM

Contacts, deals, pipelines and tasks for agencies on a general CRM.

HubSpot CRM REST API.

Fixflo

Repairs reporting (UK)

Repair requests, contractors and job status.

Fixflo's existing integrations and API, access requested from Fixflo, confirmed per project.

Google Calendar

Calendars

Viewing, showing and valuation slots.

Google Calendar API (Microsoft 365 calendars through Microsoft Graph).

Twilio

SMS, WhatsApp and voice

First replies, reminders, tenant updates and assistant lines.

Twilio Messaging and Voice APIs.

Slack and Microsoft Teams

Staff alerts

Emergency repairs, at-risk deals and failure alerts.

Incoming webhooks and APIs.

n8n

Automation platform

Runs the workflows, self-hosted or on n8n Cloud.

Your own n8n instance; we hand over every workflow.

How we delivered it

Week by week, one workflow at a time.

Each workflow went live on its own after a shadow run and a sprint demo, so the team got used to one change before the next.

Delivery timeline

Typical time to launch: about 8 weeks, then support

  1. 01

    Discovery

    Week 1

    We sat with negotiators, the progressor and property managers, mapped every lead, viewing, deal, repair and compliance step and agreed emergency wording and data flows.

  2. 02

    Design and access

    Week 2

    Templates approved by the directors, routing rules, checklist stages, compliance rule set and API access to the CRM.

  3. 03

    Sprint 1: lead pipeline

    Week 3

    Built lead parsing, routing and first replies, shadow-ran them against the shared inbox; demo and sign-off.

  4. 04

    Sprint 2: viewings

    Week 4

    The lead pipeline went live. Built viewing booking, reminders and the feedback form.

  5. 05

    Sprint 3: progression

    Week 5

    Viewings went live in one branch. Built the milestone checklist, chasers and risk flags.

  6. 06

    Sprint 4: repairs

    Week 6

    Progression went live with chasers approved by the progressor. Built the repair form, emergency routing and landlord approvals.

  7. 07

    Sprint 5: compliance

    Week 7

    Repairs went live. Cleaned compliance dates with the team and built the tracker and reminders.

  8. 08

    UAT and handover

    Week 8

    The team ran acceptance testing on every workflow, then we switched everything on, handed over the run book and trained staff.

  9. 09

    Support

    Ongoing

    Weekly check-ins during stabilisation, then monthly care.

Who does what

What the team does, and what automation does.

Automation does

  • Parses portal and website leads and sends first replies
  • Books viewings and collects the same feedback from every visitor
  • Builds milestone checklists and chases overdue steps
  • Logs repairs, flags emergencies and briefs contractors
  • Reads compliance dates nightly and stages reminders

The team does

  • Call leads and run viewings
  • Edit and send vendor and client updates
  • Unblock stalled deals with conveyancers and brokers
  • Check contractor work, quotes and new certificates

Agent or broker decides

  • Gives pricing advice and negotiates offers
  • Decides on emergency repairs and whether a home is safe
  • Approves landlord spend within the management agreement
  • Owns the compliance rule set and legal duties

Compliance handled

Privacy, consent and safety, built in.

No legal or pricing advice by automation

Replies, chasers and summaries report facts only; advice comes from licensed staff.

Marketing consent

Promotional messages go only to contacts who agreed, under PECR in the UK and the TCPA rules for US texts.

Source: www.legislation.gov.uk

Same process for every applicant

Every enquirer gets the same replies, slots and questions, in line with fair housing principles.

Source: www.hud.gov

Gas safety records

Certificate copies reach tenants within the 28-day window, with a timestamped record.

Source: www.hse.gov.uk

Electrical safety reports

Five-yearly inspection dates are tracked and reports sent to tenants within 28 days.

Source: www.gov.uk

Data minimisation

Each workflow collects and shares only the personal data it needs.

Source: gdpr-info.eu

Outcomes

What changed for the practice

  • Portal and valuation leads now get a useful reply within minutes, day or night, and every lead has an owner.
  • Viewings book themselves from approved slots, and vendor updates are based on consistent feedback.
  • The progressor spends less time asking for status and more time unblocking deals.
  • Repairs arrive with photos and access details, and emergencies reach a person straight away.
  • Compliance renewals start weeks ahead, with proof of what tenants received.
  • Staff start the day from one set of lists instead of a shared inbox and spreadsheets.

What we track

The measures the practice watches.

Lead response time

Minutes from lead arrival to first reply and to first agent call.

Viewing and feedback

Viewings booked per listing and share of visitors who leave feedback.

Progression

Days from accepted offer to exchange or closing and overdue milestones per deal.

Repairs

Time to first response, time to make safe and time to complete.

Compliance

Certificates expiring without a booked renewal, and days overdue.

Cost estimate

What a project like this costs

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Process mapping, data flows, wording and the backlog for all five workflows.

    $1,000 – $2,000

  • Lead pipeline module

    Parsing, routing, first replies and source report.

    $800 – $2,000

  • Viewings and feedback module

    Booking, reminders, feedback and vendor update drafts.

    $800 – $2,000

  • Progression module

    Checklists, chasers and risk flags.

    $700 – $1,700

  • Repairs and compliance modules

    Repair triage, landlord approvals, compliance tracker and reminders.

    $700 – $1,600

  • Integrations

    CRM, calendars, repairs platform and Twilio connections.

    $300 – $700

  • Testing, UAT and launch

    QA, user acceptance testing, launch and training.

    $700 – $2,500

  • Total project estimate

    $5,000 – $12,500

Optional monthly care after launch is quoted with your proposal. Typical range for a project of this scope: five workflows at our fixed per-workflow range. Every agency gets its own fixed quote after a free call.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • Twilio SMS (US): About $0.0083 per message segment each way plus carrier fees, and about $1.15 a month per local number (Twilio's published US pricing).
  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
  • CRM and PM system: Each vendor's own plan, plus any API usage fees the vendor charges.
  • AI usage: Pay-per-use model fees, usually small at agency volumes.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

Free 20-minute call

Want this built for your estate & letting agent?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call