Can we start with a single module and grow into it?
Yes. Most clients begin with Accounting + Sales — the two modules where ERPNext's Dutch localisation is strongest: native BTW codes, the RGS chart of accounts, PEPPOL BIS 3.0 e-invoicing and SEPA payments all work out of the box. We design the data model assuming you'll bolt on Manufacturing, Stock, CRM or HR later, so the second migration costs less because the master data, users and integrations are already in place. You're never forced to buy modules you don't use — ERPNext ships every module at €0 licence cost, so starting small is a sequencing decision, not a pricing one. A typical first-module go-live lands in 8–16 weeks, and we map the phased roadmap with you before the first invoice.
What does 'fixed fee, fixed scope' mean when scope always changes?
Scope changes are tracked, costed and signed off in writing — not absorbed silently and sprung on you in the final invoice. Before we quote, we run a short discovery to fix the scope: the processes, the modules (Accounting, Sales, Manufacturing and so on) and the integrations. That becomes the fixed-fee baseline, typically €15K–€50K for an SME project delivered in 8–16 weeks. Want to add a module mid-flight, or wire in PEPPOL e-invoicing you hadn't planned for? We quote it as a separate change order, you approve it, then we build it — no surprises at sign-off. And if we miss the date because we got discovery wrong rather than because you moved the goalposts, that's on us, not on your budget.
Can you work with our in-house developers?
Yes. Roughly a third of our engagements are co-build, pairing with your developers rather than working around them. We don't hoard the codebase — every line ships to your own GitHub from day one, with pull-request reviews and pairing sessions on a fixed weekly cadence, so your team can read, extend and maintain it without us. Because ERPNext and the Frappe framework are fully open source (Python and JavaScript, €0 licence), there's no proprietary layer your developers are locked out of. We also set up the local bench, CI and deployment pipeline so your team can ship changes themselves. The goal is that by go-live your developers can run the system unaided, with our certified consultants on call for the Dutch-specific pieces like BTW, RGS and PEPPOL.
What if we want to leave?
You take the code, the data and the operating manual — no exit fee, no hostage situation. ERPNext is fully open source, so any other certified Frappe partner, or your own team, can pick up exactly where we left off; you're not tied to us by a proprietary platform or a per-user licence. At the end of every engagement we hand over a written transition document: the architecture, every customisation, the integrations (PEPPOL, SEPA, bank feeds) and the deployment setup. Your data exports in standard formats, and because we host inside the EU — the Netherlands and Germany, under GDPR — you can take a full backup whenever you want. We'd rather earn the next phase than trap you into it, which is exactly why we ship to your GitHub from day one.
Do you support SAP customers?
Yes — but rarely as a rip-and-replace. Most SAP work we do is integration: ERPNext running one subsidiary or business unit, SAP at HQ, the two kept in sync via Workato or SAP Integration Suite. That lets a Dutch entity get native BTW, RGS and PEPPOL BIS 3.0 e-invoicing on ERPNext while group reporting stays in SAP. A pure SAP-to-ERPNext migration is a multi-year programme, not a single fixed-scope project, and we'll say so up front rather than sell you a timeline we can't hit. Where it makes sense we phase it: integrate first, prove ERPNext on one entity in 8–16 weeks, then expand entity by entity. You keep SAP for as long as it's earning its licence fee, and drop it only when ERPNext has genuinely replaced what it did.