How we work
Scope first. Price second. Software third.
Most ERP projects are lost before delivery starts, in a scoping conversation that never happened. This is the process we run instead, and the reason our timelines hold.
Discovery
The questionnaire comes before the quote. Always.
Every prospect goes through a structured requirements questionnaire before anyone quotes. It surfaces the things that quietly destroy ERP projects.
How many entities
One company or a group. Consolidation, intercompany trading and separate statutory reporting change the shape of an implementation entirely.
How many locations
Warehouses, outlets and whether they are colocated. Stock design follows from this and is expensive to change later.
Which bank accounts
Reconciliation scope drives a surprising amount of configuration and testing effort.
Payroll and statutory
Whether payroll carries statutory deductions, and which. This is frequently discovered late and always costs time.
Where the process diverges
The places your business does not work the way the software assumes. This is where the real project risk lives.
What data exists
What you have, in what condition, and how much of it needs to come across. Migration effort is proportional to mess, not volume.
Commercials
Quotes are built, not guessed.
You will always be able to see how a number was arrived at. The structure is the same for every client, whatever the size of the engagement.
Implementation, priced off a blended day rate
We estimate the work in days by workstream from the discovery output, and price those days at a blended rate. You can see the day count per workstream and challenge it.
Support, priced as a share of the project
Annual support is quoted as a defined proportion of the implementation rather than an arbitrary retainer, so it scales with the complexity of what we built.
Hosting, priced separately
Infrastructure is quoted as its own line so you can compare it, take it elsewhere, or run it yourself. We would rather lose the hosting than bundle it invisibly.
Change, priced before it happens
Scope changes are estimated and agreed in writing before work starts on them. Nobody discovers a variation on the final invoice.
Delivery
What the weeks actually look like.
Timelines vary with scope. The sequence does not.
Blueprint
We document how the business will run on the system, module by module, and you sign it off. Open questions are listed as open questions rather than assumed away.
Configuration
The system is built against the blueprint in an environment you can log into and poke at while it is being built.
Data migration
Masters and opening balances loaded, then reconciled against your existing records. We do not proceed on data you have not agreed is correct.
User acceptance testing
Your people run their own real scenarios. Issues are logged, fixed and retested before anyone talks about a go-live date.
Training
Role-based sessions in your process language, with a written runbook your team keeps.
Go-live and hypercare
We are present for the first close, because month one is where the questions actually surface.
Start with the questionnaire.
Thirty minutes of your time gets you a scope and a price that will hold, rather than a range that will not.