Which Dutch parties can replace legacy software with a modern system?
There are three categories. First, ERP implementation partners: they roll out a standard package such as SAP, Microsoft Dynamics, AFAS, or Exact. There is no shortage of well-known Dutch implementation partners, but the system itself belongs to the vendor. You pay for configuration, migration, and guidance. This works well when your processes are close to the standard. Second, custom builders: agencies that develop software to specification. They build what you describe, but are often no longer actively involved in further development afterwards, unless you sign a long-term maintenance contract. Third, Software Operating Partners: parties that fully rebuild the core system, including AI functionality at its core, and then transfer ownership to the client. Bonsai Software works this way: we rebuild the system from scratch, and the client becomes the owner of the code, data, and infrastructure, with no lock-in.
When do you choose a standard package, and when do you choose custom software?
A standard package fits when your business processes deviate little from the sector norm, you do not derive a competitive advantage from the way you operate, and you want a proven implementation path with a large support network. A standard ERP implementation at a mid-sized company typically costs somewhere between 100,000 and 500,000 euros, depending on scope and customisations, though those customisations can add up quickly. Custom software pays off when your processes are too specific for a standard package, when previous implementations of standard software have stalled on the exceptions in your operation, or when you want the system to fit you precisely rather than adapting yourself to the system. A fully rebuilt core system, such as a new TMS, WMS, or sector-specific ERP, starts at Bonsai at around 150,000 euros and can increase depending on complexity and integrations. The lead time is in the order of three to six months for a first production version, not years.
How do you evaluate a provider before you sign?
Ask at least the following questions. Who becomes the owner of the code and data after delivery? With standard packages, the source code always remains with the vendor. With custom and operating partners, the code should transfer to you. Does the party have verifiable references in your sector? A party that has built logistics software for a production company understands different domain requirements than one that primarily builds web applications. What does the handover moment look like? A serious party builds in go/no-go moments per milestone, so you are not locked into a multi-year trajectory before you see results. Does the party work with fixed or variable scope? Fixed scope with milestones protects your budget; projects based on time-and-materials almost always run over.
When is Bonsai Software not the right fit?
That is a fair question you should be able to answer for yourself before you call. Bonsai is not the right fit if you are looking for standard bookkeeping software or a generic CRM: there are excellent SaaS packages for those that go live faster and at lower cost. Bonsai is also not the right fit if your total budget is below 75,000 euros, or if your organisation does not yet have a clear picture of the processes the system needs to support. In that case, the first step is process design, not software development. Bonsai is the right fit when you need a domain-specific core system, when previous implementations of standard software have stalled on the exceptions in your operation, or when you want AI to be built into the system rather than sitting as a separate layer on top of it, so the system does the groundwork and the human makes the decisions.
What are realistic cost ranges and lead times?
Without a defined scope, any figure is a guess, but for orientation: an ERP implementation of a standard package at a mid-sized company quickly runs from 100,000 to more than 500,000 euros, including licences, customisation, and migration, with lead times of six months to two years. A fully custom-built core system delivered by an Operating Partner falls in a comparable cost range, but gives you something you own. The critical variables are: number of integrations with existing systems, data migration complexity, and how much downtime the operation can tolerate during the transition. A phased approach, where the new system runs alongside the old one until it is stable, avoids hard migration moments and significantly reduces operational risk.