Business Central, implemented by the engineers who run it after go-live
Fixed-scope implementations, migrations and integrations for mid-market finance and operations teams. Phased in 12–16 weeks, with a cutover weekend rehearsed twice before it happens.
You don’t need more software. You need the close to stop hurting.
Every stalled implementation we’ve rescued had the same three symptoms. If two of them sound familiar, the fix is scoping, not licences.
Spreadsheets are the real system of record
Intercompany balances, stock valuation and commissions get rebuilt by hand every month, and no two versions agree.
Nobody owns the migration data
Opening balances have been “nearly reconciled” for weeks, and there is no named person in finance who can sign them off.
The cutover plan is a slide, not a runbook
No hour-by-hour sequence, no rollback point, no rehearsal, so the go-live weekend becomes the first test.
Four engagements, each with a fixed deliverable
Start anywhere. Most clients begin with an assessment and stop there if the numbers don’t work.
Assessment & roadmap
Process mapping, licence sizing and a costed roadmap you can take to anyone.
Implementation
Phased configuration of finance, purchasing, inventory and reporting with scripted test packs.
ERP migration
Legacy or on-prem NAV to cloud BC, with reconciled balances and a rehearsed cutover.
Integrations & AL extensions
Shopify, Salesforce, payments, WMS and payroll, event-driven, monitored, documented.
Thirty minutes with a senior engineer. You leave with a written summary and a rough scope, no deck.
Book the callFour phases, one owner, a working deliverable at every gate
Discover — map what actually happens
We sit with the people doing the work, document the real process rather than the documented one, and size licences honestly.
Moving off Dynamics GP, NAV or Navision
Dynamics GP has a published end-of-life date, and NAV stopped being a version-to-version upgrade a long time ago, so both are migrations now rather than upgrades. We run the same rehearsed cutover either way: source system assessment, mapped and cleansed data, a trial migration into a sandbox, reconciled opening balances signed off by your finance team, and a second timed rehearsal before the live weekend.
What a Business Central implementation actually costs
Fixed scope, phase by phase, with the number agreed before the phase starts. A mid-market single-entity rollout typically lands between the assessment estimate and about 15% above it; multi-entity, multi-currency and heavily integrated projects are scoped after discovery rather than guessed at. Licences are quoted separately and sized honestly — most distributors and professional services firms do not need Premium. If the numbers do not work, the assessment is where you find that out, and stopping there is a normal outcome.
Get a scoped estimate →Month-end close cut from nine days to two
Three entities, one chart of accounts with dimensions, six integrations, and a cutover weekend rehearsed twice. Finance signed the opening balances before go-live, not after.
“They integrated four systems that had never spoken to each other, then trained our team to own it.” — Daniel Okoro, Head of IT, Meridian Manufacturing
Straight answers before you spend anything
If the honest answer is that Business Central is the wrong fit, we’ll say so in the first call.
Fixed-scope, phase by phase. A mid-market single-entity rollout typically lands between the assessment estimate and 15% above it; multi-entity is scoped after discovery. You see the number before phase two starts.
Premium only if you need manufacturing or service management. Most distributors and professional-services firms run Essentials plus a couple of extensions, we will tell you which seats you do not need.
Yes, and it is a large share of our work. We start with a two-week assessment of what is configured, what the data looks like, and what can be salvaged before quoting anything.
Senior engineers who joined the first call. No offshore handoff after signature, no rotating junior teams.
Four weeks of hypercare, runbooks written during the build, and knowledge transfer to your team. A retainer is optional, not a dependency.
Bring the system you’re stuck on.
Thirty minutes with a senior engineer, not a salesperson. You’ll leave with a written summary of your options and a rough scope.