Digital Transformation, Netherlands

Agree how the business should work before choosing tools

In many Dutch organizations decisions are reached through discussion, and people expect a say in changes that affect their work. That habit is an asset in transformation, provided the discussion happens at the right moment. If it begins only when a new system is already configured, it turns into resistance. If it begins with how the business should work, it produces better requirements.

So the first phase is about processes, data and people, not products. In remote workshops I follow real transactions end to end: an order from the webshop or an EDI message to the warehouse, the delivery, the invoice and the payment match; a supplier invoice from receipt to approval and posting; the steps from period end to the figures your accountant needs. Each team describes its part, and the gaps between teams become visible.

Alongside the process view I look at data. Article masters with inconsistent units, customers recorded twice with different payment terms and price lists kept in a spreadsheet beside the system all undermine later automation and reporting. Agreeing who owns each type of record is often the most valuable decision of the whole program.

The outcome is a short document set: flow diagrams per process, a landscape of systems and spreadsheets, an owner for every record type and a list of bottlenecks ranked by their effect on customers, cash and control. My business process consulting in the Netherlands goes deeper into the process layer when that turns out to be the main issue.

A roadmap connecting order flow, finance and the customer front end

With the bottlenecks agreed, I build the roadmap. Its purpose is to fix the order of work, because most initiatives depend on another being finished first. For a Dutch trading or service company the sequence often looks like this, adjusted to what the diagnosis found:

1. Process and data foundations: agreed flows, clean article and customer masters and a chart of accounts your accountant recognizes.
2. Operational core: an ERP or a stronger accounting and inventory setup, with links to the warehouse partner, webshop and bank designed as part of the choice rather than afterward.
3. Customer side: a CRM that hands accepted quotes to order processing without retyping, and a customer service view of orders and deliveries.
4. Automation: invoice capture, approvals, payment reminders and status messages, built on steps that are already stable.
5. Reporting: margin, stock turnover, overdue receivables and service levels from one source, with agreed definitions.
6. Lead engine: the website, search and campaigns feeding the same CRM, so marketing and sales argue about tactics rather than numbers.

Each phase lists owners, dependencies and the cost drivers that matter: subscriptions or licenses, partner effort, interfaces, data cleansing, training and internal time. Management can approve one phase while keeping the next in view. If the core system choice is the first big decision, my ERP selection work in the Netherlands runs that comparison.

Peppol, online filings and the labor market as drivers

Outside pressures help set priorities, as long as they are read accurately. Three matter for most Dutch companies.

Structured invoicing. Dutch public bodies receive electronic invoices, and Peppol is an established network for sending them. The EU is moving toward structured invoices and digital reporting more broadly, so a roadmap should make sure the core system can send and receive them through an access point. Which obligations apply to your company, and when, is for your tax advisor to confirm.

Digital dealings with government. Tax returns and many registrations already run online. Many government portals for businesses use eHerkenning as the login, and accountants often file on a company's behalf. The practical lesson is that figures should come straight from posted transactions, so a filing never depends on someone rebuilding totals in a spreadsheet.

Scarce people. When warehouse staff, bookkeepers and planners are hard to recruit, removing manual re-entry protects the team you have. Automation becomes a capacity decision rather than a cost-cutting exercise, and it should be presented to staff that way.

None of these points requires a particular platform, and none should trigger a rushed purchase. They shift the order of work: get structured invoicing and reliable ledger data in place early, and spend automation effort where people are most stretched.

Consultation, the ondernemingsraad and adoption

Change in a Dutch company works best when people understand why it is happening and have had a chance to shape it. I build that into the roadmap rather than treating training as the final step.

Where a company has an ondernemingsraad, its involvement may be required for systems that can monitor staff or that change how work is organized, and most ERP, CRM and automation tools log user activity. I do not advise on employment law. What I prepare is a factual description for management and HR: which user data each planned system records, which reports could show individual performance, how roles limit access and what can be switched off. Management and its advisors then decide how and when to involve the council, ideally early enough that its input improves the design.

For everyone else, each phase gets an adoption plan:

• A change note per team describing what will be different in their daily work.
• Key users who join design sessions and test the system before go-live.
• Training based on real tasks and real data, given in Dutch by your key users or a local partner where staff prefer it, using English material I prepare.
• A check some weeks after go-live on whether people work in the new way or have drifted back to spreadsheets.

Governance stays light: a business owner per initiative, a small steering group, a decision log and an agreed route for scope changes.

My role beside vendors, implementers and AI promises

Dutch implementation partners and software vendors deliver the configuration, integrations and support, and a good partner is worth a lot. Their offers, however, naturally favor their own products and scope. I sit on your side of the table. I hold the roadmap, translate it into requirements for each phase, compare options without preference, review statements of work and check that each delivered phase actually removes the bottleneck it was meant to address. Nobody in the supply chain pays me a commission or referral fee.

The same independence applies to AI. Practical uses exist: reading supplier invoices, suggesting matches between payments and invoices, drafting customer replies or searching internal documents. Each one depends on agreed processes and decent data, so I place AI initiatives later in the sequence and define who reviews the output, what data the tool may use and how errors are caught. GDPR questions about those tools belong with your privacy advisor. I do not attach savings figures to AI proposals.

You can engage me for the diagnosis and roadmap only, or as a fractional lead while partners deliver. The work is remote, with visits by arrangement. For the broader method see digital transformation consulting; for platform context see the ERP consultant page for the Netherlands; for the search side see SEO consulting in the Netherlands. The Netherlands overview lists the rest.