Contact Info
What can a CRM consultant do for a German Mittelstand company?
For a German Mittelstand company, a CRM consultant decides first whether a separate CRM is needed beside the ERP's own sales functions, then designs project opportunities, order intake reporting, installed base and service sales around how the firm really sells. I prepare plain material on activity logging for the Betriebsrat, put hosting and data processing questions to every vendor, and compare options without commissions. The engagement is remote and in English.
Last reviewed by Vikas Saroj
Many German manufacturers and technical wholesalers sell in long arcs. An inquiry from a plant engineer turns into a specification, several revised offers, a negotiation with purchasing and finally an order that the ERP configures and schedules. Years later the same installation produces spare parts orders, service contracts and a retrofit project. A CRM designed for quick transactional deals captures little of this, and the sales team notices immediately.
As an independent CRM consultant, I support German companies remotely. The first question is often whether you need a separate CRM at all, since many ERPs used in Germany already carry offers, contacts and some sales tracking. If you do, I design the opportunity model, the reporting management relies on and the boundary with the ERP before any product is chosen.
The engagement runs in English. German field labels, templates and the wording of any works agreement come from your own team or advisors. No vendor or system house pays me anything.
Every result is a document German management can review, challenge and keep, whatever product follows.
A test of your ERP's existing sales and contact functions against the sales process, ending in a written view on whether to extend them, add a CRM or combine both.
Opportunities that follow a technical sale: inquiry, specification, offer revisions, purchasing negotiation and award, with buying center roles and the offer version history kept together.
A reporting model that separates weighted pipeline, order intake and revenue, so the monthly management meeting compares figures that mean the same thing in sales and in controlling.
Records of delivered machines or systems per customer site, linked to service contracts, spare parts and retrofit opportunities, so after-sales revenue is managed rather than waiting for the phone to ring.
A neutral description of each candidate's user logging, individual reports and switch-off options, written for management and HR to use in talks with the Betriebsrat and in any works agreement.
Scripted demos with your project and service scenarios, plus identical hosting and data processing questions to each vendor, scored without any commission or referral interest.
Decide what the CRM must add
Model projects, service and limits
Choose on evidence, then roll out
The question sounds simple, but in Germany it often has a surprising answer. ERPs common in the Mittelstand, from German suites to Business Central and Sage, usually include contacts, offers, order history and some form of sales tracking. Where configurable products are involved, the offer itself has to come from the ERP, because only the ERP knows the variants, prices and lead times.
I start by testing what you already own. Sales and inside sales walk through real situations in the current ERP: logging a visit, following up an offer, seeing all open offers for a customer group, preparing a key account review. The gaps are written down and weighed:
The outcome is a short written recommendation with the reasoning management can check. Only then does any product comparison begin. The broader ERP picture for German companies is on my ERP consultant page for Germany.
Technical sales in Germany often run through a buying center: the plant or project engineer who writes the specification, purchasing who negotiates, management who approves and sometimes an external planner. Offers are revised several times as the specification changes. A CRM that stores one contact and one amount per opportunity misrepresents almost all of this.
I design the opportunity around the real sequence. It records the roles involved and who has been engaged, links each offer version from the ERP with its date and value, and uses stages tied to customer actions such as specification received, technical clarification complete or purchasing negotiation opened. Loss reasons are fixed categories: price, technical fit, delivery time, competitor relationship, project cancelled.
Reporting is where German management usually looks hardest. I keep apart figures that are often blended:
Definitions are agreed with controlling before configuration, so the monthly meeting no longer debates whose number is right. The same model drives forecasting by product group, region and sales representative.
For machine builders, plant suppliers and technical wholesalers, the customer relationship continues long after delivery. Each installation generates spare parts, maintenance, inspections and eventually modernization. In many companies that knowledge sits in the service department's own tools or in the heads of a few technicians, while sales only sees new-business opportunities.
The CRM design can bring these together. I model the installed base as records per customer site: what was delivered, when, under which order, with which configuration and under which service contract. Service and sales then share a view of each site. Practical uses include:
The ERP usually remains the owner of serial numbers, configurations and orders; the CRM receives a summary view. Where a field service tool is involved, the integration rules are written down once for every system involved. The technical link is designed on my system integration consultant page for Germany, and field service considerations on ERP for field service.
A CRM records who called whom, which visits were logged, how fast leads were followed up and how each person's pipeline develops. Where a Betriebsrat exists, the introduction of technical systems capable of monitoring employee behavior or performance generally falls under its co-determination rights, and many companies conclude a works agreement covering the CRM. How those rights apply to you is a matter for HR and your employment lawyer.
What speeds up that process is accurate information early. For each product on the shortlist I document which activities are logged automatically, which reports show individual figures, what an administrator can limit by role or turn off, and how long activity history is retained. Management can then propose purposes and limits, for example team-level reporting only, before configuration is fixed and before the project timeline depends on a quick agreement.
Data protection and hosting run in parallel. Each vendor receives one identical questionnaire: the countries holding live data and backups, the subcontracted processors, the scope of the data processing agreement and the exit procedure for getting records back. Some German buyers require hosting in Germany or the EU; others accept a global cloud under EU terms. Your data protection officer judges the answers. Marketing consent rules for German contacts are covered in product terms on my Zoho CRM page for Germany.
With the design written, the comparison becomes concrete. Depending on the outcome of the need assessment, the shortlist may include the CRM functions of your existing ERP, Dynamics 365 Sales where the company is deep in the Microsoft world, Salesforce for larger and more complex sales organizations, HubSpot for marketing-led businesses, Odoo CRM where Odoo already runs operations, or Zoho CRM where a broad suite appeals. German CRM publishers can belong on the list too.
Every shortlisted product walks through one shared script built on your data: a project opportunity with several offer revisions linked from the ERP, a monthly order intake report, an installed base record with an expiring service contract, and the controls that limit individual activity reporting. Your sales and service users score usability; management scores reporting, administration effort, the ERP connection and cost drivers such as license model, implementation and integration work.
Comparisons like Dynamics 365 vs Salesforce show the kind of trade-offs involved. I take no commission from vendors or system houses, so extending the ERP remains a real option to the end. Delivery is remote, and visits happen by arrangement. My CRM consulting page explains the method in general terms, while the Germany overview collects the rest of my German work.
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.
Perhaps you do not. I test the ERP's sales and contact functions with real scenarios from your sales and service teams. If the gaps are about configuration or habits, extending the ERP is usually the better choice. A separate CRM is justified when mobile visit reports, buying center tracking, campaigns or multi-country pipeline go beyond what the ERP handles well.
Where a works council exists, systems capable of monitoring staff generally involve it, and many companies agree a works agreement for the CRM. Your HR team and employment lawyer determine the exact obligations. I supply a factual description of logging, reports and restriction options for each candidate, so that conversation starts early and with accurate facts.
Yes, if the definitions are agreed first. I separate weighted pipeline, order intake confirmed in the ERP and invoiced revenue, and agree the rules with controlling before configuration. Order intake then flows from the ERP into CRM reports rather than being typed in by sales, which keeps both views consistent.
That is a policy decision for management and your data protection officer. Some companies insist on German or EU hosting, others accept a global provider under EU contractual terms. I put identical questions on data location, subprocessors, data processing terms and exit to every vendor, so the decision rests on complete answers.
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.