Creating a CRM starts with drawing the path a enquiry takes to become a customer, and only then choosing a tool. A system built around the business’s real process stays in use, while a system built around a software’s menus empties out within a few weeks.
This guide walks through the steps in the order we work: mapping, fields, choosing a base, connecting lead sources, handling failures, migrating data and launching.
What do you need to decide before creating a CRM?
Before creating a CRM you need to decide four things: where enquiries come from, which stages they pass through until closing, who owns each stage, and what happens when an enquiry gets stuck. Without those four decisions, even a tidy system turns into a warehouse of names and phone numbers.
A simple example for a service business: enquiries arrive from WhatsApp, a website form and phone calls. The stages are new, contacted, quote sent, won and lost. Each stage has one owner and a clear exit condition, such as “quote sent”.
Draw this on a single page before touching any tool. If the process does not fit on one page, it is not ready for automation yet.
Which fields and stages should a CRM have?
Start with a small set of fields: name, phone in international format, enquiry source, stage, owner, last contact date, next-step date and loss reason. Add a further field only when someone uses it to make a decision.
Our rule: a field nobody reads is a field nobody will fill in. With twenty mandatory fields, salespeople fill in the first few and skip the rest, and the data stops being reliable.
The “next-step date” field matters most, because it shows which enquiry has been forgotten. An enquiry without that date is one nobody plans to follow up.
Should you build a CRM on a spreadsheet, a ready-made system or a custom build?
A CRM can be created in three ways: a Google Sheets file with automations, a ready-made CRM configured for the business, or a custom build. A small business with one simple process can start with a sheet. A business where several people work on the same customers needs a system with permissions and history.
| Approach | Fits when… | Main limitation |
|---|---|---|
| Google Sheets with n8n automations | A small team and one simple process | No row-level permissions and no organised conversation history |
| Ready-made CRM, configured for the business | Several people work on the same customers | Many systems charge per user, and the structure is limited to what the system offers |
| Custom build | A unique process that fits no ready-made structure | Needs maintenance and documentation over time |
In all three approaches, the connections between lead sources and the system decide whether it stays up to date. We build a CRM system tailored to the business around the process that was mapped, including the integrations, rather than starting from a fixed template.
How do you connect WhatsApp, forms and lead sources to a CRM?
You connect each lead source to the CRM with a workflow, for example in n8n, that receives the event through a webhook, normalises the phone number, checks whether the customer already exists, creates or updates a record and assigns an owner. Every source goes through the same path, so the data looks the same.
On WhatsApp, the WhatsApp Cloud API sends incoming messages to a webhook address you define. You can reply with a free-form message within 24 hours of the customer’s last message. After that window, an approved message template is required, so the process should be built to know which state the window is in.
Website forms follow the same principle: the form posts to the same webhook, and the workflow uses the phone number to recognise an existing customer. Someone who wrote once on WhatsApp and once through the form stays one record.
What breaks when the CRM connection is down?
In a well-built system, an enquiry is not lost when the CRM connection goes down. The failed run retries after a delay, and if it keeps failing it moves to an error queue and alerts a person. The original payload is kept, so it can be replayed.
In n8n you can define a separate error workflow that fires when another workflow fails, and that is where the alert is configured. It also helps to de-duplicate by phone number, so a replay does not create a second record for the same customer.
A simple check worth running regularly: compare the number of enquiries that arrived from each source with the number of records created in the CRM for the same period. A gap points to a connection that broke silently.
How do you move existing customers into a new CRM?
You move existing customers into a new CRM in four steps: export all lists to one file, clean it and merge duplicates, map each column to a field in the system, and load a small batch first. Only when that batch looks right do you load the rest.
The cleaning is most of the work. Phone numbers are written in many different ways, so they are converted to one international format. The same customer sometimes appears in two sheets under slightly different names, and the phone number is a safer key for merging than the name.
Leave the original file untouched. If something loads incorrectly, there is something to go back to.
How long does creating a CRM take, and what does it cost?
There is no fixed price or duration for creating a CRM, because both depend on how many lead sources there are, how many stages the process has, how many users, how much existing data must be migrated and which external systems connect, for example an invoicing system such as Morning. One process with one or two sources is far smaller than an organisation with several teams.
Cost has several components: the system licence (per user in many systems), the automation platform, setup work and ongoing maintenance. We break these down in a separate guide on CRM implementation cost.
To estimate reliably you first need the process map from the first step. Without it, any quote is a guess.
How do you know the CRM is actually used after launch?
Check that every open enquiry has an owner and a next-step date, and that no enquiries have gone too long without an update. If both hold, the CRM is being used for work and not just storage. A short weekly meeting goes through the stuck enquiries and decides what to do with each.
A good launch also covers permissions. Each employee gets a personal login, access only to what they need, and access is removed on the day they leave. We build with least-privilege access and action logging, as is customary in environments with strict security requirements.
For the first few weeks, keep the old spreadsheet read-only so nobody keeps working in it in parallel.
Frequently asked questions
Can you create a CRM without a developer?
For a simple process, yes. A Google Sheets file together with a visual automation platform such as n8n lets you build a basic system without writing code. Someone should own the logic and maintenance, and work with the WhatsApp Cloud API or with several systems at once usually benefits from a professional.
How many customers or users do you need before a CRM makes sense?
There is no minimum. The need appears the moment an enquiry is forgotten or two people contact the same customer without knowing about each other. Even an owner who works alone benefits from one place that lists every customer and the next step with each.
How do you protect customer data in a CRM?
Give each employee a personal login instead of a shared password, turn on two-step verification, limit access by role and remove access when someone leaves. It also helps to keep a record of who changed what. The legal obligations that apply to your business regarding databases are worth checking with legal counsel.
Can you switch CRM later without losing data?
Yes, when the data is clean and the fields are clearly mapped. You export the lists from the old system and load them into the new one, using the same cleaning and small-batch loading process. When connections run through one workflow, switching the destination means changing one node, not rebuilding every lead source.