CRM Consultant, Netherlands

When most revenue comes from customers you already have

Standard CRM setups assume a funnel: leads come in, some become opportunities, a few close. A Dutch wholesaler or technical distributor often looks different. The bulk of revenue arrives as repeat orders through a trade webshop, EDI or the inside sales desk, and the commercial question is whether each account is growing, stable or quietly moving volume to a competitor.

For that kind of business I design the CRM around accounts first. Each customer gets a segment based on potential and buying pattern, an owner and a review rhythm. Order data from the ERP or webshop is brought into the account view as summaries: frequency, product groups bought, average order and trend against last period. An account manager opening the record before a visit sees the drop in one product line without asking finance for a report.

New business still matters, so a separate pipeline tracks prospects and expansion deals with stages that suit them. The two are kept apart in reporting, because mixing recurring volume with speculative opportunities makes both unreadable. I also define what triggers an action: an account that has not ordered within its usual cycle creates a task rather than waiting for someone to notice. The wider ERP picture for Dutch traders sits on the ERP consultant page for the Netherlands.

Logistics providers: rate requests, tenders and onboarding

Dutch logistics and warehousing companies sell services that take weeks to price and months to start. A shipper asks for rates on a set of lanes or a warehousing proposal for a new product range; the provider gathers volumes, designs a solution, prices it and often goes through several rounds before an award. After that comes onboarding: systems connected, stock moved, staff trained. A generic sales pipeline captures almost none of this.

I usually split the work into linked records:

• The request. Customer, scope, volumes received, deadline and the people involved in solution design and pricing.
• The proposal rounds. Each version with its assumptions, so a later price change can be traced to a change in scope.
• The onboarding project. Started automatically on award, with milestones that operations and IT own.

Reports then answer questions management actually asks: how many requests are in solution design, which proposals are waiting on the customer, what new volume starts next quarter in each warehouse. Win and loss reasons are recorded in fixed categories rather than free text, so patterns become visible. The same approach suits freight forwarders and contract logistics firms; city-level context for port businesses is on the Rotterdam ERP consultant page.

The works council and what a CRM records about staff

A CRM logs a great deal about the people using it: calls made, emails sent, visits recorded, deals moved and, in some products, location or time spent. Where a Dutch company has an ondernemingsraad, introducing or changing a system that can be used to monitor employees is generally a matter the council has a say in. The exact rights and the right moment are questions for your HR team and employment lawyer, not for me.

What I contribute is clarity. During selection each product on the shortlist gets a neutral note covering:

• Which user activities are logged automatically and which are entered by the user.
• Which standard reports or dashboards could show individual performance.
• Which of those can be restricted by role or switched off.
• How long activity history is kept and who can see it.

Management can then explain the purpose of the CRM, for example account coverage and response times rather than individual surveillance, and agree boundaries with the council before configuration is fixed. That tends to be easier than revisiting the design after go-live. It also feeds the privacy documentation your data protection officer keeps, since employee data in the CRM falls under GDPR just as customer contacts do.

CRM, ERP or both: drawing the line for a Dutch company

Many Dutch businesses already run an ERP or accounting package with some relationship features: contact persons, activities, quotes, sometimes a simple pipeline. The first question is whether a separate CRM adds enough to justify a second system. I answer it by testing the existing tool against the account management design. If it covers the needs with better configuration, extending it is usually cheaper and avoids a sync.

When a separate CRM is justified, the boundary has to be explicit. Typical decisions include:

• Which system creates a new customer and which only receives it.
• Whether quotes are written in the CRM or in the ERP where prices, stock and delivery dates sit.
• Which order, invoice and payment details flow back so account managers are not blind to overdue balances.
• How the KvK and VAT numbers are captured once and reused everywhere.

Outreach rules are part of the same design. Dutch companies process contact data under GDPR, and email and phone marketing is also subject to Dutch telecommunications rules. Your privacy officer decides the policy; the CRM records consent, objections and source so campaigns follow it. The technical connection to the ERP is specified on my system integration consultant page for the Netherlands.

Comparing CRM options without a favorite

The comparison starts from the design document, not from a feature grid. I script demos around your own situations: an account review for a declining customer, a rate request that goes through repeated proposal rounds, a quote that must reach the ERP with the right price agreement, and a manager's weekly pipeline meeting. Each vendor or implementer shows those cases with your sample data, and your account managers score them.

Scoring covers fit with the account structure, ease of daily use, the effort needed to administer the system, the realistic connection to your ERP and the cost drivers: license model, add-ons, implementation and integration work. Products differ in where their strength lies. Some are stronger in marketing automation, some in complex sales organizations, some sit inside a wider suite next to inventory and invoicing. The comparisons Zoho vs HubSpot and Zoho CRM vs Salesforce illustrate the trade-offs, and Odoo CRM is relevant where the ERP is already Odoo.

Because no vendor pays me, extending your current system is weighed as seriously as a new purchase. Work runs remotely in English, with sessions scheduled in the Dutch morning and visits by arrangement. If Zoho is already your choice, see the Zoho CRM page for the Netherlands; the general method is under CRM consulting, and other work is listed on the Netherlands overview.