What is a CRM system? A plain English guide for small businesses

The broker who handled the biggest deal of the month has gone on holiday. The buyer messages you: “Weren’t we meeting on Thursday?” You can find their number in the phone, an email in the inbox, and a few messages in a chat. What you cannot see is the important part: what was promised, who is preparing the documents, and whether the viewing is confirmed. “Let me check” buys you a little time. Tomorrow, the same conversation will happen with another client.

What is a CRM system? It is a shared place for information about customers, enquiries, deals, and next steps. It helps a team answer four questions: who contacted us, what do they need, what have we agreed, and who will do what next and when? The software gives people a place to record information and set reminders. The value comes when the team agrees what to record and who owns each task.

Here is one hypothetical story in two versions. Five brokers work at a real estate agency. Enquiries come from the website, property portals, and phone calls. A buyer is looking for an apartment for their family and wants to view one on Thursday. This is a fictional example, not a GrandMa case with measured results.

Names vary between products, but the logic is familiar. A contact answers “who is this person, and how can we reach them?” An enquiry or lead records the initial interest. A deal brings work together around a possible sale. A stage shows what is happening now. A task names the next action, its owner, and a due date. The history keeps important conversations and changes.

For example, in Microsoft Dynamics 365 documentation, a lead can have contact details, enquiries, activities, and notes attached to it. A deal record can include a stage, an owner, and related activities. This shows one way a system can organize data. Another CRM may use different field names or let you create your own stages.

The buyer’s record should not turn into a form with thirty required fields. A colleague opening it in the broker’s absence should be able to understand: “Looking for a two-room apartment in this area; viewed property A; asked about payment terms; waiting for Thursday viewing confirmation. Olena is responsible and must confirm the time by Wednesday at 4 pm.” That is enough to hand over the work without a detective story.

One person can have several enquiries over time. The buyer first looked for an apartment for themselves and six months later contacted the agency about a home for their parents. The contact is the same, but the needs and possible deals are different. If everything goes into one long note beside a phone number, the second story will soon bury the first. Keeping contacts and deals separate avoids mixing the context without creating a new person in the database after every call.

The record should also make sense without a broker’s private shorthand. “Warm client” tells a colleague nothing about what to do next. “Viewed property B; waiting for an answer about payment terms by Friday” says what to check and when to follow up. That small change in wording makes a handover much clearer.

The buyer leaves a phone number on the website. A broker calls, asks about the budget, and sends a shortlist in a messenger. The buyer chooses two apartments but rejects one because of the floor. The broker asks the owner of the second apartment about a possible Thursday viewing and tells the buyer they will come back with the exact time.

Three separate traces now exist. The enquiry is in the inbox or the website spreadsheet. The broker remembers the budget and why the first apartment was rejected. The Thursday arrangement is in the broker’s personal chat. No one has been assigned the next action because the broker has already planned to do it mentally.

When that broker goes on holiday, a colleague sees only the phone number. They offer the buyer an apartment they have already rejected. The buyer asks about Thursday, and the colleague does not know whether the owner agreed to a time at all. The main problem is not that the company failed to buy CRM software. It is that no one created a record the team could use to continue the work.

Another detail can slip through: the colleague calls the apartment owner without knowing that the first broker has already discussed the possibility of negotiating the price. Two people from the agency ask different questions and make it seem as though no one is handling the deal. To the buyer, it looks like a trust problem. For the team, it is a gap in shared history, with the same costly result.

A well-kept spreadsheet and a working team chat could also have prevented this. The tool’s name is not the issue. When five people manage dozens of conversations at once, assigning tasks, tracking changes, and keeping ownership clear becomes harder in a spreadsheet. That is where CRM starts to make a practical difference.

The buyer gets a record after the enquiry arrives. The broker enters the budget, area, two-room requirement, enquiry source, and contact details. After the call, they add a short note: property A did not work because of the floor; property B is of interest; a Thursday viewing may be possible, but the exact time is not confirmed. They create the task “Confirm time with owner and update buyer by Wednesday at 4 pm” and assign someone to cover it while they are away.

When the buyer writes on Thursday, the colleague opens the record and sees what has been confirmed and what is still only a plan. If the owner has not replied, the colleague can say honestly: “We have discussed a possible viewing; we are confirming the exact time.” If the owner has replied, the colleague sends the address and time. They do not ask again about the floor because the previous reason for rejecting a property is already recorded.

After the viewing, the deal stage changes, for example from “Viewing scheduled” to “Terms under discussion.” The next task may be about documents or an answer to the buyer’s question. If the buyer changes their mind, the team closes the record with a short reason. A month later, the agency can see where deals most often stop, provided the team records reasons consistently.

A CRM record should not pretend to be a full copy of every chat. Keep what the team needs to continue the work and make decisions. If communication is integrated, check which messages actually appear in the record, who can access them, and whether the team can see the history after an employee leaves. A vendor’s use of the word “integration” does not prove that your particular channel is connected.

If one person handles customers, enquiries are few, and a simple list helps them reply on time, start with the list. A spreadsheet with the contact, request, status, owner, and next action will help you understand your own process. We compare a spreadsheet and a CRM for enquiries that arrive in chats here.

A CRM becomes more useful when several people work at once, a customer switches communication channels, a deal lasts for weeks, or a manager cannot reconstruct its status without calling the salesperson. Our hypothetical real estate agency has five brokers, several enquiry sources, and viewings to coordinate. A forgotten agreement has a visible cost. Even so, describe the stages of the work before buying software.

Use the same fair test for a spreadsheet and a CRM: can someone else open a record and understand, without asking its author, what was promised and what needs to happen next? If so, a spreadsheet may still be enough. If not, ask whether the problem is a limitation of the tool or that the team is not recording what it needs. A CRM will not fix the second problem by itself.

Lists of “the best CRMs this year” go out of date quickly. Start with how your team works.

1. How many people need to work with one customer? The broker needs their own task, a colleague covering for them needs the history, and a manager needs an overview without being able to change everything by accident.
2. Where do enquiries come from? Name every source: website, ad form, phone, property portal, messenger. Check how each specific record will enter the system and who will notice if something goes wrong.
3. Which integrations do you need now? Do not pay for a dozen “future” features. Choose the two routes you use most and test them from enquiry to assigned task.
4. Who will manage fields and access? If every broker creates their own statuses, such as “thinking,” “still thinking,” and “almost ready,” the report will become a work of fiction. Someone needs to maintain a short set of shared rules.
5. What happens to the data if you change providers? Ask about exporting contacts, history, and tasks, backups, and access after an employee leaves. Try it with sample records before moving the whole archive.

The last question is especially practical. CRM becomes shared memory only when the company controls access and can retrieve its records. One broker’s personal account as the only place for all contacts simply moves the old problem into a new interface.

Do not move everything over in the first few days. Start with active deals, check what information is needed for the next action, and configure six fields: contact, need or property, enquiry source, owner, stage, and next action with a due date. If the software lets you put the date in a separate field, do that. A short note about an agreement adds context to the record; it does not replace the next task.

The hypothetical agency can start with five stages: new enquiry, need clarified, viewing scheduled, terms under discussion, and closed. It is useful to distinguish outcomes within “closed”: the deal went ahead or the enquiry closed without a sale. If your business has a consultation or site measurement instead of a viewing, name the stage after the real action. Do not copy the labels from a demo account.

In the second week, run a short check. Ask a broker who did not manage a particular deal to open its record and explain what should happen tomorrow. If they cannot, do not immediately add another module. Find the missing field, unclear status, or rule nobody is following.

Check the process in the other direction too. Take one recently completed deal and try to reconstruct where it came from and which steps led to the decision. If the source is blank or the agreement date does not match the history, fix the recording rule now. It will be much harder to remember those details a quarter later.

Here is a message you can copy into the team chat:

After every customer conversation, update three things in the record: what we agreed, who owns the next action, and its due date. If we hand a deal to a colleague or go on holiday, assign a new owner and check that they can see the history. An agreement that exists only in a personal chat does not yet exist for the team.

That rule is more useful than telling everyone to “keep CRM up to date.” People know what to record and why. The manager also needs to open the system, ask questions based on its records, and avoid rewarding parallel private lists.

Often, the system asks too much of the team. To record a simple call, a broker has to fill in twenty fields and choose from seventeen statuses. They put the task off and return to their own chat. Reduce required fields to the information a colleague needs to continue the work.

Another reason is that no one maintains the shared rules. Half the team writes “customer thinking,” the other half selects “in progress,” and a third leaves the status unchanged from the first call. Agree on short definitions for each stage and review a few live records once a week. The goal is to find where a rule is awkward or unclear, not to punish people.

CRM can also become a reporting tool for the manager alone. The broker fills it in at the end of the day for the numbers but works from personal notes during the day. The next steps then do not help with the customer and quickly become stale. The system should save time for the people speaking with customers, not just produce a chart for Friday’s meeting.

If you lose not only enquiries but also agreements about delivery and payment, look at a broader way to organize work. If the problem is that a commitment stays in a chat, this article shows one way to record an order agreement. To connect forms, messages, and internal tasks in your process, see GrandMa’s approach to automation.