Runbook
Tasks tonight1,284
Result
Aldgate Estates
Portal leads answered in under a minute, viewings in the negotiator's diary.
- 3×viewings booked
- Lead routing
- 2024
Result
Aldgate Estates
Portal leads answered in under a minute, viewings in the negotiator's diary.
- 3×viewings booked
- Lead routing
- 2024
Result
Aldgate Estates
Portal leads answered in under a minute, viewings in the negotiator's diary.
- 3×viewings booked
- Lead routing
- 2024
The result · Result 06 / 06
3× viewings booked0123456789×
viewings bookedThe story
Portal leads answered in under a minute, viewings in the negotiator's diary.
Portal enquiries sat in a shared inbox until someone was free. Each lead is now matched to the property, answered with two viewing slots and booked straight into the negotiator's calendar, with a reminder to the applicant the morning of. Viewings booked per week tripled across the three branches, and the vendor gets a weekly summary without anyone writing it.
- Client
- Aldgate Estates
- Sector
- Real estate
- Workflow
- Lead routing
- Year
- 2024
What wewired.
- 01Week 1
Mapped the week
We sat with the people who do the work and drew every hand-off on one whiteboard: where a record is typed twice, where a reply waits, where a spreadsheet is rebuilt.
- 02Week 2
Wired the trigger
The workflow starts from the event the team already produces: a booking, a closed job, a form, a payment. Nobody has to remember to press anything.
- 03Week 3
Built the steps
Each step reads from the client's own systems and writes back to them under their own logins. Every run leaves a line in the log.
- 04Week 4
Ran it beside the team
Two weeks in parallel with the old way: the numbers were compared every morning, the edge cases added, and then the manual path was switched off.
Beforeand after.
- Admin hours a week
- Before: 38 h01234567890123456789 h
- After: 11 h01234567890123456789 h
- First reply
- Before: 2 days0123456789 days
- After: 4 min0123456789 min
- Records typed by hand
- Before: 100 %012345678901234567890123456789 %
- After: 0 %0123456789 %
The result · Result 06 / 06
3× viewings booked0123456789×
viewings bookedThe story
Portal leads answered in under a minute, viewings in the negotiator's diary.
Portal enquiries sat in a shared inbox until someone was free. Each lead is now matched to the property, answered with two viewing slots and booked straight into the negotiator's calendar, with a reminder to the applicant the morning of. Viewings booked per week tripled across the three branches, and the vendor gets a weekly summary without anyone writing it.
- Client
- Aldgate Estates
- Sector
- Real estate
- Workflow
- Lead routing
- Year
- 2024
What wewired.
- 01Week 1
Mapped the week
We sat with the people who do the work and drew every hand-off on one whiteboard: where a record is typed twice, where a reply waits, where a spreadsheet is rebuilt.
- 02Week 2
Wired the trigger
The workflow starts from the event the team already produces: a booking, a closed job, a form, a payment. Nobody has to remember to press anything.
- 03Week 3
Built the steps
Each step reads from the client's own systems and writes back to them under their own logins. Every run leaves a line in the log.
- 04Week 4
Ran it beside the team
Two weeks in parallel with the old way: the numbers were compared every morning, the edge cases added, and then the manual path was switched off.
Beforeand after.
- Admin hours a week
- Before: 38 h01234567890123456789 h
- After: 11 h01234567890123456789 h
- First reply
- Before: 2 days0123456789 days
- After: 4 min0123456789 min
- Records typed by hand
- Before: 100 %012345678901234567890123456789 %
- After: 0 %0123456789 %
The result · Result 06 / 06
3× viewings booked0123456789×
viewings bookedThe story
Portal leads answered in under a minute, viewings in the negotiator's diary.
Portal enquiries sat in a shared inbox until someone was free. Each lead is now matched to the property, answered with two viewing slots and booked straight into the negotiator's calendar, with a reminder to the applicant the morning of. Viewings booked per week tripled across the three branches, and the vendor gets a weekly summary without anyone writing it.
- Client
- Aldgate Estates
- Sector
- Real estate
- Workflow
- Lead routing
- Year
- 2024
What wewired.
- 01Week 1
Mapped the week
We sat with the people who do the work and drew every hand-off on one whiteboard: where a record is typed twice, where a reply waits, where a spreadsheet is rebuilt.
- 02Week 2
Wired the trigger
The workflow starts from the event the team already produces: a booking, a closed job, a form, a payment. Nobody has to remember to press anything.
- 03Week 3
Built the steps
Each step reads from the client's own systems and writes back to them under their own logins. Every run leaves a line in the log.
- 04Week 4
Ran it beside the team
Two weeks in parallel with the old way: the numbers were compared every morning, the edge cases added, and then the manual path was switched off.
Beforeand after.
- Admin hours a week
- Before: 38 h01234567890123456789 h
- After: 11 h01234567890123456789 h
- First reply
- Before: 2 days0123456789 days
- After: 4 min0123456789 min
- Records typed by hand
- Before: 100 %012345678901234567890123456789 %
- After: 0 %0123456789 %
Book a call
Tell us what eats your week. We'll automate it.
Pick what fits. On the call we map the first workflow, the tools it touches and the week it goes live.
Book a call
Tell us what eats your week. We'll automate it.
Pick what fits. On the call we map the first workflow, the tools it touches and the week it goes live.
Book a call
Tell us what eats your week. We'll automate it.
Pick what fits. On the call we map the first workflow, the tools it touches and the week it goes live.