The Rolodex was invented in 1956 by Danish engineer Hildaur Neilsen. It was a rotating card file, a physical device that stored contact information on index cards that could be spun and flipped to find a name.
It was, in essence, the first CRM. Not because it managed relationships, but because it organised the information that made managing relationships possible. Names. Numbers. Notes. The mechanical predecessor of every contact database that followed.
By the 1980s, personal computers had arrived in offices and the Rolodex began its transition into software. The first commercial contact management application, ACT!, built by Pat Sullivan and Mike Muhney, launched in 1986. It was described at the time as a digital Rolodex. It stored names, phone numbers, and notes. It let salespeople search for clients by region, by purchase history, by last contact date. It saved time. It reduced the risk of losing information when someone left the company.
It was built for people the business already knew.
What a CRM actually does
Through the 1990s, contact management evolved into Sales Force Automation. Tom Siebel left Oracle in 1993 and founded Siebel Systems, which became the dominant enterprise CRM vendor of the decade. The term “Customer Relationship Management” was formally adopted by the industry in 1995. Salesforce launched in 1999, delivering CRM through a browser for the first time and eventually becoming the world’s largest CRM provider.
Through all of this evolution, from Rolodex to ACT! to Siebel to Salesforce, the core function remained consistent. A CRM organises information about contacts who already exist in a business’s world. It records interactions. It tracks history. It manages pipelines. It automates follow-up sequences. It generates reports on activity and conversion.
Every feature in every CRM built across seventy years of development assumes one thing: the contact record already exists.
The CRM begins its work after the person has been entered into the system. Everything before that moment, every interaction, every signal, every piece of context about where the person is in their decision, is outside the CRM’s field of vision.
The word that matters
Customer Relationship Management. Not creation. Not identification. Management. The word implies something that already exists and needs to be organised and maintained. You manage a relationship that has already formed. The moment before that, when an unknown person sends their first message, is not a CRM problem. It never was.
How CRM entered estate agency
Property CRMs arrived in UK estate agency during the 1990s and early 2000s as the sector began to modernise its operations. The case for adoption was straightforward: agencies were managing large numbers of buyer and seller contacts across multiple branches, and paper-based systems were becoming inadequate.
The CRM solved real problems. It centralised contact records. It tracked applicant requirements. It recorded viewing histories. It managed vendor relationships across the instruction and marketing process. It gave branch managers visibility into pipeline and activity that had previously existed only in individual negotiators’ heads or notebooks.
Property-specific CRMs, built for the workflows, terminology, and transaction types of estate agency, became the operational backbone of most UK agencies. They remain so today. The majority of agencies run their entire business through a property CRM.
But the CRM entered estate agency to solve the same problem it was originally built for everywhere else: managing relationships with people the business already knew.
Registered applicants. Vendors on the market. Contacts in the pipeline. Landlords in the managed portfolio. People with existing records. People whose history with the agency could be tracked, reviewed, and acted upon.
The inbound enquiry, the message from the unknown seller who has never contacted the agency before, sits outside that world until someone creates a record for them.
What it was never designed for
There is a specific moment in the estate agency workflow that the CRM does not address and was never designed to address.
A seller sends an enquiry. It arrives in the inbox. Before anyone responds. Before a record is created. Before the CRM has any knowledge that this person exists.
In that moment, between the enquiry arriving and the first response going out, a decision is made about how seriously to take the enquiry. Whether to call immediately or reply by template. Whether this seller is choosing between agents this week or curious about prices this year.
The CRM offers nothing to inform that decision. Not because the CRM is poorly implemented, or because the agency has chosen the wrong system, or because the software needs updating. But because the CRM was built to begin after that moment has passed.
The contact does not exist in the CRM yet. There is no record to pull. There is no history to review. There is no prior interaction to reference. The CRM’s entire capability, every field, every workflow, every automation, requires data that has not yet been created.
This is not a gap in the CRM. It is the boundary of what the CRM was built for. The CRM ends where it was always designed to end: at the edge of the known.
The implication
Most agencies treat the CRM as their primary intake tool because it is the system they open first. An enquiry arrives, someone creates a record, and the CRM takes over. The assessment of who sent the enquiry and what they represent happens informally, in the seconds between the message being read and the record being created.
That is where instruction opportunities are won or lost. The CRM cannot help with it. The data it would need does not exist until after the moment has passed.
This is not an argument against CRMs. Record-keeping, pipeline visibility, workflow management — all of it is irreplaceable once a contact exists. It is an argument for what needs to happen before the CRM begins. The intake moment needs its own layer. Not a replacement for the CRM. A predecessor to it.