Customer Relationship Management

For a long time, what a company knew about a customer lived in one person's head and one person's inbox. Whoever handled the account knew what had been promised and when; everyone else had to ask. The records existed, more or less — in a notes app, a personal calendar, a long email thread — but seeing the whole picture for a single customer meant searching four places.

The problem showed up the same way every time. A salesperson left, and the state of the thirty accounts they carried left with them. The handover document listed company names and phone numbers, not which account was waiting on budget approval and which one was comparing the product against a competitor. The person taking over would call the customer and ask where the conversation had left off, and the customer would explain, again, what they had already explained three months earlier.

Collisions were just as common. A customer who had already signed would receive a marketing email pitching them the product. Two people would contact the same company in the same week and quote different discounts. Nobody had made a mistake. There was simply nowhere to look up what the other person had done. Customer relationship management (CRM) exists to lift that record out of individual memory and turn it into something the organization owns.

CRM addresses four problems, and all four come apart once the record sits in one place.

1. It fixes where the history lives. Calls, meetings, emails and proposals attach to a single customer account in chronological order. When the owner changes, the new person reads one screen and catches up on six months.
2. It makes the stage visible. A lead — a prospective customer who has handed over contact details — sits at first meeting, proposal, negotiation or closed, and the tool shows which. Laying every open deal out by stage that way is a sales pipeline, and CRM is the container that pipeline lives in.
3. It attaches dates to next actions. Every record carries a follow-up and a due date. A note that says "call them again next week" gets forgotten; an item that surfaces on October 2 does not.
4. It produces numbers as a by-product. How many new customers arrived this month, and which stage most deals stall at, fall out of the records without anyone compiling them. Not having to compile them is the real gain here.

Which of the four matters most depends on headcount. With two salespeople, items 1 and 3 carry the whole job. Past ten, without 2 and 4 nobody in the room can say what the quarter will bring in.

With few enough customers, a spreadsheet is a real alternative. One sheet with columns for company, contact, last touch and next action holds up surprisingly well to around thirty accounts. It costs nothing, the columns bend to whatever the team wants, and nobody has to learn anything.

That approach breaks in three places.

1. Email and calls don't attach themselves. Someone has to copy the substance across by hand, and in a busy week that is the first task to slip.
2. Two people editing the same file lose track of which row is current. Copies appear, and the copies disagree.
3. There are no reminders. A date typed into a next-action column is visible only to whoever happens to open the sheet.

There is a middle ground too: labels in a shared inbox paired with calendar invites, or a sales stack — the set of tools a sales team runs on — assembled with the CRM slot left empty and covered by something else. Both work, but the record still belongs to an individual, so the handover problem survives intact.

Past a hundred customers or five salespeople, the alternatives run out. At that size, the time spent keeping a sheet accurate costs more than the software does. The tipping point is easy to spot in practice: it arrives the week someone asks how many deals are sitting in negotiation and three people produce three different answers from three versions of the same file.

"Did you check that account in the CRM? Sofia already spoke to them last month."

Look at the record before contacting a customer somebody else has already contacted.

"A meeting that isn't in the CRM didn't happen."

If it isn't logged, it doesn't reach the team's numbers either — the line that gets used to push for data entry.

"The quarterly forecast came straight out of the CRM stage amounts."

The projection rests on deal stages recorded in the tool rather than on anyone's gut feel.

At Pagedeck, Sofia starts the day in the CRM. Accounts with a follow-up due today come up as a list, and inquiries that arrived overnight are waiting as new leads. When a call ends she writes three lines of summary and the date of the next conversation, and that entry attaches to the account history.

The record gets read outside sales as well. Ravi opens it to see which channel produced inquiries that turned into signed contracts. Grace checks the totals by stage before the quarterly review. Three people looking for three different things, all reading the same records.

The most common reading is that a CRM is there to monitor sales activity. Who logged how many entries is visible to everyone, so the interpretation comes easily. The actual purpose is different: the history accumulates so that a customer never has to repeat themselves when the person handling their account is away or replaced. Used as a monitoring tool, the team optimizes for entry count — one-line records multiply while the context that matters stays in private notes.

The other expectation is that installing a CRM tidies customer data by itself. The tool is an empty box and returns what goes in. Without agreed input rules, one company accumulates as three entries under slightly different spellings, and stage definitions drift until the totals stop adding up. A deal one person marks as negotiation is still a proposal to someone else, and the forecast built on top of those labels inherits the disagreement. The time a rollout actually consumes isn't the setup; it's the few days the team spends agreeing on what belongs in which field.