ERP implementation
We implement SAP Business One, Dynamics 365 Business Central, NetSuite, and our own suite — against a go-live date fixed in week two and a scope written down before configuration starts.
30 minutes · no obligation · We reply within 1 business day.
14wk
Median rollout
Last 22 engagements
22
Deployments delivered
0
Failed go-lives
Overview
An ERP implementation replaces the spreadsheets, the ageing finance system, and the three databases nobody owns with one record of what the business actually did. We run the whole programme: selection, blueprint, configuration, migration, cutover, and the four weeks after go-live when it matters most.
It is for organisations between 50 and 2,000 people where finance closes late, inventory is guessed at, or a plant runs on knowledge held by one person. It is not for you if you want a system administrator for an ERP you already run well — that is our managed service, and it costs a fraction of this.
You get a working system, a reconciled migration, and documentation good enough that your team can run the next site rollout without us. Two of our manufacturing clients have done exactly that.
What we actually fix
Written in the words the finance director used, not the words we would prefer.
The problem
“Month-end takes eleven days and I still do not trust the consolidated number.”
What we do
One chart of accounts across all sites, automated intercompany elimination, and reconciliation built into the close checklist rather than bolted on afterwards.
Result
3 days
The problem
“We find out we are short of a component when the line stops.”
What we do
MRP driven by live stock and confirmed orders, with plant-floor scanning so the system knows what was actually consumed rather than what should have been.
Result
−62% stockouts
The problem
“The last implementation partner went live and disappeared.”
What we do
Four weeks of hypercare with daily triage, then a documented handover to your team or to our managed service. Both paths are written down before hypercare ends.
Result
0 failed go-lives
Benefits
Fixed in week two against a written scope. Twenty-two deployments, no failed go-lives in seven years.
Runbooks and configuration rationale good enough that clients run their next site rollout without us.
Three rehearsals and a reconciliation report your finance team signs before production cutover.
Plant floor, CRM, and banking connections mapped during blueprint, built during the same programme.
Training completion and transaction volume tracked per role for the first two months after go-live.
Segregation of duties, approval matrices, and audit logging configured before go-live, not after a finding.
Process
Durations are the median across our last 22 deployments. Your fit-gap analysis in stage one is what turns these into your dates.
We walk your current processes with the people who run them and record where the standard product will and will not fit.
Target process design, chart of accounts, and the integration map, signed off before a line of configuration is written.
Configuration in two-week increments, each one demonstrated to your process owners rather than reported on.
Three full migration rehearsals with reconciliation reports your finance team signs before we go near production.
A rehearsed, hour-by-hour cutover plan with a rollback point at every stage and your team in the room.
Daily triage falling to weekly, then handover to your team or to our managed service — your choice, documented either way.
Scope
Written into the contract, not implied by it.
Technology
ERP does not sit alone. These are the platforms we connect it to and support in production.
Proof
Four plants ran four different systems. Consolidated reporting took a fortnight and finance had stopped trusting it.
They gave us a fixed go-live date in week two and hit it. What I actually valued was that the handover documentation was good enough that my team ran the second plant rollout themselves.
Nguyen Thi Lan
Chief Financial Officer, Trakhon Industrial
3days
Month-end close, down from 11
How we contract
Fixed-scope is the usual choice for an implementation. We publish a range rather than a number because data migration effort is the largest variable and it is not knowable until we have seen your data.
A defined rollout with a known end state
Fixed price against a signed blueprint, with a change-control process that is written down before we start.
Continuous delivery against a shifting roadmap
Named engineers embedded with your team, billed monthly, with the same delivery discipline and no minimum term after month six.
Running the system after it is live
24/7 operations against a written SLA with published metrics and a quarterly service review you can hold us to.
By capability
A pipeline your sales team updates without being chased.
Make the systems you already own talk to each other.
Named engineers against a written SLA, not a ticket queue.
FAQ
Including the questions that are awkward for us.
Our median across the last 22 engagements is 14 weeks from kickoff to go-live for a single-site rollout, and 22 weeks for multi-site. We fix the date in week two once fit-gap analysis is complete — before that, any date either of us names is a guess.
Single-site implementations typically fall between USD 90,000 and 180,000 depending on module count, integration complexity, and data quality. We publish a range rather than a fixed number because data migration effort is the largest variable and it is not knowable until we have seen your data.
SAP Business One, Microsoft Dynamics 365 Business Central, Oracle NetSuite, and our own Aureus ERP Suite. We run a vendor-selection review first if you have not chosen — the recommendation is written and includes the case against our own product where that is the honest answer.
It usually is. We run three full migration rehearsals with reconciliation reports, and we will tell you in week three if cleansing effort is going to move the date. We would rather move the date once, early, than miss it.
No. Across 18 migrations we have not caused a day of production downtime. Cutover is rehearsed hour by hour with a rollback point at every stage, and we schedule around your production calendar, not ours.
Four weeks of hypercare with daily triage falling to weekly. Then you choose: full handover to your team with runbooks and training, or transition to our managed service against a written SLA. Both paths are documented before hypercare ends.
That is the intended outcome. Configuration rationale is documented, not just configuration. Two of our manufacturing clients have run subsequent site rollouts entirely with their own teams.
Regularly. We have delivered as a subcontractor, as a delivery-assurance reviewer, and as a replacement for a stalled programme. We will say plainly which of those we think fits your situation.
Next step
Thirty minutes with the engineer who would run it. You leave with a written view of scope, sequence, and the two things most likely to move your date.
30 minutes · no obligation · you receive a written scope estimate