Contact Info
How can a CRM consultant help a Swiss company?
For a Swiss company, the CRM consultant's first job is mapping how the business really wins customers, through key accounts, dealers, installers, specifiers and export distributors, then designing pipelines, account matching rules and the handoff to the ERP. The CRM platform is chosen afterward, on fit, hosting answers and group requirements. I do this remotely and independently, with local-language templates checked by your team.
Last reviewed by Vikas Saroj
Swiss sales rarely follow one straight line. A building technology supplier may win a project through an engineer who specifies the product, an installer who buys it and a building owner who pays for it. An exporter may sell directly in some markets and through dealers in others. A CRM that treats each of these as one generic deal produces a pipeline nobody believes.
As a CRM consultant working remotely for Swiss companies, I map how your business actually wins customers before any platform is chosen. I then design pipelines, account data, lead routing and the handoff into your ERP, and compare CRM options on that basis, whether the answer is Salesforce, Dynamics 365, HubSpot, Zoho CRM, Odoo CRM or the CRM module you already own.
I hold no commercial agreement with any CRM vendor, so the recommendation follows your sales process and your hosting requirements. The engagement runs in English; German, French or Italian templates and labels are drafted and proofread by your own staff or a language partner you appoint.
Each piece of work starts from the way your customers buy, then turns that into rules a CRM can enforce.
Workshops with sales, inside sales and management to record every route to revenue: key accounts, dealers, installers, specifiers, export distributors and web inquiries, with who owns each step today.
A deal model for projects that involve a planner, a contractor and an end client, so influence, purchase and delivery are tracked without counting the same project twice in the forecast.
Scripted comparison of the CRM options that fit your size and group setup, including staying with the CRM module of your current ERP, scored against your requirements rather than vendor feature lists.
Matching rules built on the Swiss business identification number, address standards and language variants of company names, so one customer does not appear three times under three spellings.
Written questions to each CRM vendor on storage location, support access from abroad and subprocessors, with the answers passed to your data protection advisor before a contract is signed.
Dashboards for regional managers and the board, a short training plan by role and usage reviews after launch, so the CRM replaces private spreadsheets instead of running beside them.
Record how revenue really arrives
Design first, then pick the platform
Launch, connect and measure use
Before any CRM discussion, I want to know where revenue comes from and who influences it. In Swiss companies the answer is often a mix that a single pipeline cannot hold:
For each route I record how a lead arrives, who qualifies it, how pricing is approved, where the order is placed and which system issues the invoice. I also note which information today lives only in a salesperson's notebook or mailbox, because that is what the CRM has to capture without adding admin.
The result is a short sales process map and a list of deal types, each with its own stages and owner. That document becomes the brief for platform choice and configuration. The broader method is described on my CRM consulting page.
Swiss suppliers to construction, building services and industrial projects face a forecasting problem. One project may appear as an influence opportunity with the planner, a quotation to two or three competing installers and finally an order from the one who wins. If each of those becomes a separate deal, the pipeline counts the same project several times and management stops trusting it.
I design a project record that sits above the commercial deals:
This structure also helps field sales plan visits: a planner with several live projects matters more than the size of any single quote suggests. Most mainstream CRM platforms can hold a model like this through custom objects or related records; the comparison checks how much effort each one needs. Companies in construction and engineering usually recognize the pattern immediately.
Two questions often settle a Swiss CRM decision before features are compared. First, does a parent group already run a CRM that the Swiss entity is expected to use? Second, do customer contracts or internal policy require data to stay in a particular location or to be accessible only from certain countries?
I put both to management early, then compare the remaining options with scripted demonstrations built from your own deal types:
| Situation | Options usually worth comparing |
|---|---|
| Swiss entity of a foreign group | The group CRM with a Swiss configuration, compared with a local CRM feeding group reporting |
| Owner-led manufacturer or distributor | The CRM module of the current ERP, Zoho CRM, HubSpot or Odoo CRM |
| Complex sales organization with an admin team | Salesforce or Dynamics 365, weighed against the skills needed to maintain them |
For hosting, I send each vendor the same written questions: where production and backup data are stored, from which countries support staff can access it and which subprocessors are involved. Swiss data protection law and, where EU contacts are involved, the GDPR shape how those answers should be judged, and your data protection advisor makes that judgment. My part is making sure the questions are asked before the shortlist is final, not after the contract is signed.
Duplicate accounts damage a Swiss CRM faster than almost anything else. The same company may be registered under a German and a French name, a dealer may appear once as a customer and once as a supplier, and a branch office may be created as a separate firm by a salesperson in another region.
I set matching rules before any import:
Marketing consent sits on the contact, not the account, together with its source and the date it was given. How the Swiss rules on data protection and advertising emails apply to your contacts is for your legal advisor; the CRM records what they decide and blocks campaigns to contacts without a valid basis.
Migration then follows the same rules: records from old systems and spreadsheets are matched, merged and assigned to current owners before the final load, with sales managers reviewing a trial import first.
A won deal only helps if the order reaches the ERP correctly. I specify the handoff with finance: which system creates the customer, at which stage the order is transferred, which fields are mandatory at that point and how invoice and payment status come back. The invoice itself, including the QR-bill payment part, comes out of the ERP or the accounting package; the CRM never issues it. Sales should see open balances and credit holds before quoting again, without needing access to the ledger.
Reporting is designed around a few decisions management actually makes: where to put field capacity, which dealers deserve more support, which specifiers bring projects and how reliable next quarter looks. I agree definitions first, such as when a project counts as specified and which exchange rate converts euro deals into the franc forecast, so regional figures add up.
Adoption comes from keeping data entry light and giving each role a view that helps them. After launch I review usage with managers and adjust what people ignore. Delivery is remote; a visit can be planned by arrangement. The integration side of this handoff is covered on my system integration consultant page for Switzerland, and the full set of Swiss services is on the Switzerland overview.
Tell me about your business and current systems. I’ll suggest the most sensible first step.
Book a Consultation
Not sure which ERP you need?
Share your business requirements with me and I will help you understand the right process, architecture and platform before implementation.
No single CRM is right for every Swiss company. I compare the options that fit your size, group setup and hosting requirements, including the CRM module you may already own, using demonstrations built from your own deal types. No vendor pays me a commission or referral fee, so the recommendation is based only on how well each option fits.
Yes, if it is designed for it. I model the project separately from the commercial quotations, record specification status and link each installer quote to the project. Only the expected winning quote counts toward the forecast, so the pipeline stops counting the same building several times.
That depends on the vendor, the edition and the hosting options available to you. I ask every shortlisted vendor in writing where data is stored, who can access it from abroad and which subprocessors are involved. Your data protection advisor then decides whether the answers meet your obligations and customer commitments.
Yes. Most CRM platforms let users work in their preferred interface language, while picklists and stage names are designed to report consistently. The engagement runs in English; customer-facing templates in each language are written or checked by your colleagues or a local partner and tested with real records.
No. The CRM manages leads, projects, quotations and accounts. Orders pass to the ERP or accounting system, which issues the invoice with its QR-bill payment part, handles VAT and records payments. Status information flows back so sales can see what has been invoiced and paid.
Every business is different. Share where you are today and what you want to fix, and I’ll tell you honestly whether and how I can help.
Book a Consultation
Book a consultation to talk through your processes, systems and goals. I’ll reply with practical next steps - no obligation.