Many companies start looking for a customer management system after noticing problems: quotes sent without follow-up, a customer who contacted them twice without a reply, or an employee who left with customer numbers on their phone. Buying a CRM system seems logical, but a system alone cannot fix an unclear way of working.
The system does what you define for it. If you do not know your sales stages, required data, or who owns each step, it will move the same disorganisation onto a new screen. Organise follow-up on paper first, then choose a system that fits.
Map your sales stages
From the first enquiry to closing the deal, what stages do your customers go through? Write them as they actually happen, rather than as they should happen. The aim is to describe reality, because any system you build needs to fit how your team works today, then improve it gradually.
Example sales stages
For a company providing finishing services, for example, the stages might be:
- New enquiry through the website, WhatsApp, or a phone call.
- First contact to understand the request, project type, and location.
- Site visit.
- Sending a quote.
- Follow-up and negotiation.
- Decision: deal won or closed without agreement.
You may have fewer or more stages. Each should be clear and distinct, and the team should know when a customer moves to the next one.
Questions to help map the stages
- Where do enquiries come from: the website, WhatsApp, sales representatives, or referrals?
- What happens immediately after an enquiry arrives, and who replies?
- Where do customers usually stop without continuing?
- When do you consider an opportunity lost, and do you record why?
- What happens after closing the deal? Does it move to the implementation team?
Write the stages with the team handling customers daily, rather than alone. You will discover steps you did not know existed and differences in how employees work.
Bring all sources into one process
If enquiries arrive from several places, define how they all enter the same first stage. A website form submission, WhatsApp message, and call to the company number should all end up in a single record the team knows how to find, with the source recorded.
This step alone solves a large part of the lost-enquiry problem by preventing customers from remaining on an employee’s phone or in an unchecked inbox.
Only essential fields
Define the information you need at each stage: name, service, quote value, and person responsible. Too many fields cause the team to ignore the system because data entry becomes a burden employees postpone until they forget.
A simple rule: do not collect information you will not use for a decision, report, or follow-up. If you cannot answer “When will we need this information?”, remove it.
Fields for each stage
- At enquiry: Name, contact number, enquiry source, and requested service.
- After first contact: Request details, city or region, and the date of the next step.
- When sending the quote: Quote value, date sent, and person responsible for follow-up.
- At the decision: Outcome and reason for loss if the deal was not completed.
Fields are added gradually as customers move through stages, rather than requesting everything at first contact. This makes entry easier and ensures important data is available at the right time.
Standardise data entry
Define fixed lists for recurring fields, such as enquiry source, service type, and reason for loss, instead of letting each employee write them differently. Fixed lists make later reports useful, showing which source brings the most customers and where opportunities are lost.
If you have customer data in old spreadsheets or employees’ phones, decide now what to migrate. The article on migrating data to a new business management system explains how to select and clean data before migration.
Remember that fields can be added later when a real need arises. Starting with a few important fields and expanding once the team gets used to data entry is much better than starting with a long form everyone ignores, fills differently, or leaves blank.
Who follows up on what?
Define each team member’s responsibilities and when customers should move to the next stage. Clear responsibility matters more than the system itself. A simple system with clear responsibilities works better than an advanced one where nobody knows what is expected.
Questions to define responsibilities
- Who receives and assigns new enquiries?
- Does the customer stay with one employee until closing, or move between several people?
- Who can change the quote value or close an opportunity?
- Who reviews overdue opportunities that were not followed up on time?
- Who sees all customer data, and who sees only their own customers?
Always have a next task
The most important customer follow-up habit is giving every open opportunity a next task with an owner and date. “Call on a specific day”, “Send the revised quote”, or “Follow up after the site visit”. An opportunity with no next step will be forgotten.
What do you want reports to tell you?
Before choosing a system, write down the questions it should answer regularly. For example: how many new enquiries arrived, and from which sources? How many quotes were sent without follow-up? Where do most opportunities stall? Who has overdue tasks?
These questions reveal whether your fields and stages are sufficient. If you want a report on reasons for lost opportunities, for example, the reason for loss needs a fixed-list field rather than a free-text note each employee writes differently.
Try this approach for a while using a simple shared spreadsheet before choosing a system. You will learn what works and what needs changing, making your system requirements much clearer.
Then comes the question of the right tool. If you need customer and sales follow-up, this is the role of Customer and sales management system. If your needs extend to inventory and purchasing, read do you need CRM or ERP? before deciding.
Frequently asked questions
Can I start with a spreadsheet instead of a CRM system?
Yes, it is a good way to test stages and fields. As customer and employee numbers grow, spreadsheet limits appear: task reminders, permissions, and tracking changes become difficult. A system then becomes a logical next step.
How many stages should I have?
There is no fixed number. Each stage should be a real step where something changes, and the team should distinguish between them without hesitation. Too many similar stages create more confusion than value.
Can the website and WhatsApp connect to the system?
This can be assessed based on the chosen solution and the tools you use. Required integrations are defined in the scope of work before implementation, as explained on the page for Business management systems.
Where do I start if I need help?
Send us a short description of your current customer follow-up process through contact page, and we will discuss suitable stages and fields before suggesting a system.