SolutionsPricingWorkshopsBlogNewsAboutLet's Talk

How to Choose a CRM: What to Check Before You Commit

How to choose a CRM system for your business without relying on brand recommendations. What to check in workflows, integrations, and support.

AutomushPublished 7 min read

How do you choose a CRM without relying on brand recommendations

A recommended CRM system is one that fits your workflows, not one someone else said was good. A business selling recurring services needs something different from a business selling one-off projects, and a business with three people needs something different from a business with thirty.

When we build a customer and lead management system for a business, the first question is always what happens now: how a lead comes in, who touches it, where it disappears, and what needs to happen after it becomes a customer. The system needs to support that process, not dictate it.

This guide describes what to check before you commit to a vendor, how to ensure the system will connect to what already works for you, and how to know if support will actually be there when something breaks.

What needs to happen in the system before you choose it

A CRM system needs to support three basic things: recording new inquiries, tracking progress, and generating reminders or tasks for whoever needs to handle them. If any of these doesn’t work without custom configuration, the system doesn’t fit.

When we set up a system, we first check how leads come in today: through a website form, through WhatsApp, through email, or through a phone call. The system needs to capture these inquiries automatically or at least with one click, not by manually copying fields.

After a lead comes in, it needs to be clear who owns it and what the next step is. If this doesn’t happen automatically, it needs to be simple to configure: “every lead from the website goes to Shay, every lead from WhatsApp goes to Tamar”. A system that requires code or external development for rules like these won’t last.

The third thing is reporting: who sees how many leads came in, how many were handled, and how many became customers. If you need to export an Excel file every week to know this, the system isn’t doing the job.

Does the system connect to what already works for you

A CRM system that doesn’t connect to your existing systems becomes an isolated island. People keep working in Google Sheets, WhatsApp, or email, and the new system stays empty.

We check three types of connections before recommending a system: connection to inquiry channels, connection to accounting systems, and connection to communication tools. Connection to inquiry channels means a lead that comes in through a website form, through WhatsApp, or through email enters the system automatically. If you need to copy manually, the process breaks within two weeks.

Connection to accounting systems means you can issue an invoice to a customer directly from the system, or at least send the details to the system that issues it. Businesses working with Green Invoice, Manager, or other invoicing platforms need to verify this connection exists or can be built through n8n or Make.

Connection to communication tools means you can send a WhatsApp message, email, or SMS to a customer directly from the system, and the conversation is logged. If you need to leave the system to send a message, logging won’t happen.

How long does it take to set this up

Setting up a basic CRM system takes between one week and three weeks, depending on the number of connections and the complexity of the workflows. A system that requires more than a month is usually more complex than what the business needs.

The first week is configuration: building the fields, defining the stages, and setting the basic rules. The second week is connections: linking to forms, WhatsApp, email, and external systems. The third week is testing and training: verifying the process works end-to-end and that the team knows how to use it.

We recommend starting with one process and expanding after it works. A business handling leads and existing customers will start with the lead process, and add existing customer management after a month. This works better than setting up everything at once and discovering half of it doesn’t fit.

A system that requires custom development or integration with large enterprise systems can take two to three months. This happens mainly in regulated businesses that need internal approvals or security checks before every connection.

What happens when something breaks

A CRM system will break. A field will fill incorrectly, a connection will stop working, or an automation rule will run on the wrong leads. The question isn’t whether this will happen, but how quickly someone will fix it.

We build systems with a monitoring layer: every critical process sends an alert if it fails. If a lead is supposed to enter automatically from a form and doesn’t, we know within minutes. If a connection to an external API stops working, the system sends a message to WhatsApp or email.

When choosing a vendor, you need to ask two questions: what is your response time when something breaks, and how do I know something broke before a customer complains. A vendor who can’t answer the second question didn’t build the system correctly.

We work with businesses that need high availability, such as businesses receiving inquiries 24/7 or businesses where the process is critical to revenue. In these cases, we configure a backup process: if the primary system isn’t available, inquiries enter a temporary backup until the issue is fixed.

Should you build yourself or buy off the shelf

An off-the-shelf system fits businesses whose process is standard: receive lead, make phone call, send quote, close. If this describes your business, an off-the-shelf system will work.

A custom system fits businesses whose process is different: non-standard stages, connections to internal systems, or complex business rules. We build custom systems around n8n when the business needs full control over the process or when off-the-shelf systems don’t support the connections the business needs.

Criterion Off-the-shelf system Custom system (n8n)
Setup time One to two weeks Two weeks to one month
Monthly cost Per user (typically $15-60 per user) Fixed maintenance (typically $400-1,000)
Process flexibility Limited to existing templates Full, any process possible
System connections What the vendor supports Any system with API or webhook
Vendor dependency High, can’t move easily Low, can transfer or change

Businesses just starting should start with an off-the-shelf system and move to custom only if the process doesn’t fit. Businesses that already know their process is different save time if they build custom from the start.

How do you know the system actually works

A CRM system works if three things happen: leads don’t disappear, people know what to do next, and there’s data for decision-making. If any of these doesn’t happen, the system doesn’t work.

Leads don’t disappear means every inquiry that comes in is recorded, assigned to someone, and handled in reasonable time. We check this by tracking average response time: how much time passes from when a lead enters until someone contacts them. If it’s more than one business day, something isn’t working.

People know what to do next means the system displays clear tasks: “call this customer”, “send quote”, “follow up on meeting”. If people need to ask what to do now, the system isn’t clear enough.

There’s data for decision-making means you can see how many leads came in this week, how many were handled, how many became customers, and what the average handling time is. If you need to ask the team to know this, the system isn’t doing the job.

What do you do with the old system

Moving from an old system to a new one needs to be planned. Data migration is the most critical part: if existing customers don’t transfer, the new system isn’t useful.

We recommend a three-stage transition: data import, parallel run, and full migration. Data import means transferring active customers and leads to the new system. You don’t need to transfer everything, only what’s relevant to current work.

Parallel run means working with both systems in parallel for one to two weeks: new leads enter both, and the team works in both. This gives time to verify the new system works before leaving the old one.

Full migration means closing the old system and working only with the new one. We recommend keeping a backup of the old system for at least three months, in case you need to look up old information.

Businesses working with spreadsheets instead of a CRM system can move directly: the data is already in table structure, and it’s easy to import. Businesses working with an old system that doesn’t allow export need to check if there’s an API or option to access the data through an external tool.

Frequently asked questions

Can you start with a free system and upgrade later

Yes, but only if the free system supports the connections you need. Many free systems limit API connections or automations, which means you'll need to work manually. If you're planning to upgrade within six months, it's better to start with the paid plan from the beginning and save the migration.

What happens if the system vendor closes or stops supporting it

If your system is based on a closed vendor (off-the-shelf system), you're completely dependent on them. If they close, you'll need to move to another system and import the data again. Systems built on n8n or open infrastructure are less dependent: you can move the workflows to another vendor or run them yourself.

Do you need to train the entire team before starting to use the system

Yes, but the training shouldn't take more than an hour per person. If the system requires a full day of training, it's too complex. We recommend training first the people who will work with the system every day, and giving them a week to work with it before training the rest. This way you can fix issues before everyone moves over.

How do you know if the system will hold up when the business grows

Check two things: does the system charge by number of users or by number of leads, and how does it behave when there are many records. A system that charges by users typically fits growth, because you can add leads without paying more. A system that slows down when there are thousands of records won't hold up long-term.

Interested?custom CRM development for business

From the newsroom

All news

Which of your processes could run on its own?

A free 30-minute discovery call, no commitment. We map your processes together and tell you honestly whether and how automation can help.

Try a call with agent now