A property firm: 340 paper viewing cards replaced in a fortnight
A regional estate agency in Hampshire was still booking viewings on carbon-copy cards in 2024. The partners knew it was absurd; the staff knew it worked.
The reading
Four branches, eleven negotiators, two partners who remembered the fax machine fondly. The agency took around 340 viewing bookings a week across the branches. Each one was written on a two-part carbon card: top copy to the vendor's file, bottom copy to the negotiator's clipboard.
The system worked, after a fashion. Viewings happened, offers were made, properties sold. But the partners had noticed that negotiators spent an hour at the start and end of each day reconciling cards against the diary, and that cancellations frequently did not reach the vendor.
More quietly, they had noticed that no one could answer the question "how many viewings did we do on this property before it sold?" without going through a filing cabinet.
Paper that travels
The carbon cards travelled. They went out with the negotiator, were sometimes handed to the vendor, sometimes stuffed into a glovebox, occasionally lost. The branch admin reconstructed the week every Friday from whatever cards had returned, cross-referenced against the diary and the SMS log on the shared mobile.
The partners' concern was not efficiency. It was that the firm had no reliable record of what it had actually done. In a dispute with a vendor, the firm's position rested on the branch admin's weekly reconstruction.
- 340 viewings per week across four branches
- Carbon cards reconciled manually every Friday
- Approximately 8% of viewings not recorded against the correct property
- Cancellations reached the vendor on time in roughly 70% of cases
- No queryable record of viewing-to-offer ratios
What we built
We built a web application that the negotiators used on their own phones. A viewing was booked in under thirty seconds: property, prospective buyer, time, negotiator. Vendor notification went out automatically. Cancellations were a single tap.
The technical choice worth noting: we built the booking form to work offline. Negotiators in rural Hampshire frequently had no signal, and the previous attempt by another firm to digitise this process had failed because the app required connectivity at the point of booking. Our version queued bookings locally and synced when a signal returned. The partners noticed within a week that the Friday reconciliation had simply stopped happening, because there was nothing to reconcile.
The backend was a straightforward Rails application on a managed Postgres. Vendor notifications used the firm's existing SMS gateway.
The numbers at ninety days
| What | Before | After |
|---|---|---|
| Viewings recorded against wrong property | 8% | 0.3% |
| Cancellations reaching vendor on time | 70% | 99% |
| Admin hours on Friday reconciliation | 14/week | 0/week |
| Time to book a viewing | 2-3 min | 25 sec |
| Viewings-to-offer ratio queryable | No | Yes |
The record is the asset
The partners' instinct that the problem was not efficiency but record-keeping was correct. The firm now has, for the first time in forty years of trading, a defensible account of what it has done for each vendor.
That is what we mean by system-first: the system exists so that the firm can answer questions about itself. Everything else, including the thirty seconds instead of three minutes, is a consequence.