How to Choose the Right CRM: A Practical Framework for Swiss Companies

Companies often start a CRM project by comparing Salesforce, InvestGlass, Microsoft Dynamics, Pipedrive, Zoho… It usually makes more sense to start with the business itself: how sales and Marketing work, what customer information employees need, which systems the CRM has to connect with and what management wants to see in reports. Swiss companies also need to check how customer data is stored, processed and transferred, especially now that AI features are becoming standard in CRM platforms.

A customer relationship management system can give sales, marketing and customer service teams one place to work with customer information. Salespeople can see previous conversations before calling a client, marketing teams can track what happens to the leads they generate and managers can check the sales pipeline without pulling information together from different spreadsheets.

CRM projects often go wrong before the software is even chosen. A company buys a platform before deciding how leads should be handled, what employees need to record or who will be responsible for keeping the data clean. The software may work perfectly well, but employees still end up using different processes, entering information in different ways or keeping notes outside the system.

CRM platforms also now cover much more than contacts and sales pipelines. Many include marketing automation, customer service, reporting and AI tools, so companies are often choosing software that will sit at the centre of several commercial processes for years.

For Swiss companies, the decision also involves data protection because most major CRM systems run in the cloud. Customer and prospect data may therefore be processed by the provider and by other companies it works with, sometimes outside Switzerland.

A good selection process should answer these questions before the company starts comparing product demonstrations.

Step 1: Write Down How Sales Actually Work

Start with what happens from the moment someone shows interest in the company until the deal is won or lost.

A prospect may come through a website form, an event, a referral, LinkedIn, an advertising campaign or a salesperson’s own network. Someone then needs to decide whether the lead is worth pursuing, assign it to the right person, arrange meetings, prepare an offer and follow the opportunity.

The details vary by business. A consulting company may work on one opportunity for several months and speak with several people at the same client. A property company may need to connect enquiries to individual developments. A manufacturer may work with direct customers and distributors at the same time. A wealth manager may need to connect one client relationship with family members, advisers, companies and trusts.

Writing down the process shows what the CRM has to support. It can also show where teams already work differently. Sales and marketing may not agree on what counts as a qualified lead, for example, or two salespeople may move opportunities through the pipeline in different ways.

The company should agree on these rules before asking software to enforce them.

Step 2: Decide What Information Employees Really Need

Once the sales process is clear, decide what information people need at each stage.

A sales team may need the company name, contact person, expected deal value, likely closing date, lead source, responsible salesperson and next step. A B2B company may also need to record several contacts at the same company and note who makes the final decision. Marketing may need information about campaign source and communication consent, while managers need enough structured data to track conversion rates and forecasts.

It is easy to add too many fields because somebody thinks the information could be useful later. That usually makes the CRM harder to maintain.

For every field, ask three simple questions: who will enter it, when will they know the answer and what will the company use the information for? If nobody has a clear answer, there is little reason to make the field mandatory.

Swiss data-protection rules also support a more selective approach. The Federal Data Protection and Information Commissioner says companies should build privacy into their systems and, by default, collect only the personal data needed for the stated purpose.

The CRM should therefore contain enough information for employees to do their jobs without collecting information simply because the system allows it.

Step 3: Decide What Management Wants to See

A CRM only produces useful reports when the company agrees on what it wants to measure and employees record the data consistently.

Management may want to know how much qualified business is currently in the pipeline, where leads come from, how long deals usually take, where opportunities are being lost or how accurate sales forecasts are. Marketing may want to know which campaigns generate meetings and sales rather than just clicks and form submissions.

Each report depends on specific information being entered correctly.

If managers want to compare lead sources but employees often leave the source field empty, the dashboard will be unreliable. If salespeople use pipeline stages differently, the revenue forecast will be unreliable as well.

Companies should therefore decide which reports they need before the CRM is configured, because those reports determine which fields, stages and rules have to be built into the system.

Step 4: Check Which Systems the CRM Needs to Connect With

Most companies already use several tools that contain customer information. The CRM may need to connect with email, calendars, website forms, marketing software, customer support, accounting software, an ERP system or specialist industry tools.

Take a simple website enquiry. Ideally, the enquiry should enter the CRM automatically, keep information about where it came from, go to the right salesperson and later show whether it turned into a sale.

If employees have to copy the same information from one system to another, they lose time and errors become more likely.

Existing technology should therefore influence the shortlist. A company that already uses Microsoft heavily may care much more about Outlook, Teams and Dynamics integrations. A business running most of its marketing through HubSpot will have different priorities.

Do not rely only on a vendor saying that an integration exists. Ask them to show how it works with the process your team actually uses.

Step 5: Decide Who Is Responsible for the CRM

Someone needs to be responsible for the system after it goes live. That includes deciding who can create or change fields, who manages user permissions, who deals with duplicate records, who changes pipeline stages and who checks whether reports still use the right definitions.

In a small company, one person may handle most of this alongside another role. In a larger organisation, sales operations, marketing, IT and data-protection teams may share the work.

Without clear ownership, the CRM can quickly become inconsistent. One team creates new fields, another uses different naming conventions and old workflows stay in the system even though nobody needs them anymore.

The company does not need a complicated governance structure, but it does need clear responsibility.

Step 6: Test the Tasks Employees Do Every Day

Product demonstrations often focus on the most impressive features. The company should also test the basic tasks employees will use every day.

Ask a salesperson to create a contact, find an existing company, record a meeting, update an opportunity, add a follow-up and review the full history of an account.

Managers should check how easily they can see the current pipeline and understand why a forecast has changed. Marketing users should follow a lead from its original campaign into the sales process.

This type of test is usually more useful than comparing long feature lists because it shows how much work the CRM creates for the people using it.

If updating an opportunity takes too long, employees may start keeping notes in spreadsheets, email or personal documents. Once that happens, managers can no longer rely on the CRM as the full record of the customer relationship.

Step 7: Check the Swiss Data-Protection Requirements and Swiss Regulations

Swiss companies should review data protection before choosing a vendor, not after the contract has been signed. The Federal Data Protection and Information Commissioner treats cloud services as outsourced data processing. The company using the CRM still has responsibility for how personal data is handled, even when an outside provider processes it.

That means companies should check where data is stored and processed, which subcontractors may have access to it, what security measures are in place and whether customer data may be transferred to another country.

A provider saying that the main database is hosted in Switzerland or the EU does not answer all of these questions. Support, analytics, email delivery or other services may still involve companies in other locations.

The company should therefore ask for the provider’s subprocessor list, data-processing terms and information on international transfers before making a final decision.

For businesses handling sensitive personal data or using more complex profiling, legal or data-protection teams may also need to decide whether a data protection impact assessment is required.

Step 8: Ask What the AI Features Actually Do

AI is now built into many CRM products. The tools can summarise customer histories, draft emails, suggest next steps, analyse sales activity or help employees search through records.

The useful question is not whether the CRM includes AI, but what the AI can access and what happens to the data.

Companies should ask which customer information the AI reads, whether the data stays inside the CRM environment, whether another provider processes it, how long the information is kept and whether it can be used to train models.

These questions are especially important when the CRM contains years of client emails, meeting notes, contact details or sensitive information.

The Swiss Federal Data Protection and Information Commissioner has confirmed that the Federal Act on Data Protection also applies when AI systems process personal data. Companies still need to know why the data is being used, where it comes from and how the processing works.

AI features can save time, but they should be reviewed with the same care as any other function that has access to customer data.

Step 9: Work Out the Real Cost

The advertised monthly licence price rarely tells the full story.

A CRM project may also include implementation, data migration, customisation, integrations, training, support and higher subscription tiers for features the company later needs. Some providers charge mainly by user, while others add costs for contacts, storage, marketing activity or extra modules.

Companies should calculate what the system could cost in two or three years, not just what it costs with today’s team.

A platform may be inexpensive for six users and much more expensive once 30 employees need access. A low entry price may also become less attractive if the company later needs advanced permissions, marketing automation or paid connectors.

Data migration deserves attention as well. If the old database contains duplicates, outdated contacts and inconsistent categories, importing everything without cleaning it first simply moves those problems into the new system.

Step 10: Compare Vendors Against the Same Scenarios

Only after the company has worked through the previous steps does it make sense to compare vendors in detail.

Salesforce, InvestGlass, HubSpot, Microsoft Dynamics 365, Pipedrive, Zoho and specialist CRM providers all cover core CRM functions, but they differ in complexity, integrations, pricing and the type of company they suit best.

Ask every shortlisted provider to show the same real-life tasks. Show us what happens when a website enquiry arrives. Show us how three contacts from the same company are handled. Show us what a salesperson sees before a client meeting. Show us how marketing can trace a sale back to the original campaign. Show us how customer data can be exported if we decide to leave the platform.

The last point is easy to overlook. A CRM may contain years of customer history, activities, attachments, custom fields and links between people and companies. The company should know from the beginning how much of that information can be exported and in what format.

By this stage, the choice should be much clearer because the company is comparing each CRM against the way it actually works. The final decision can then focus on whether employees can use the platform easily, whether it connects with existing systems, whether the data setup supports useful reporting, whether the provider meets Swiss data-protection requirements and whether the cost still makes sense as the business grows.