Signed solution design
The document that defines the build — processes, structure, accounts, roles and the agreed list of extensions.
Implementation
A rollout method built around your go-live date
Our professional implementation team helps you employ the full power of the platform. Discovery, solution design, configuration, data migration, testing and go-live are sequenced backwards from the date the business needs to be live — so the plan serves the calendar instead of drifting past it.
Discovery, solution design, configuration, data migration, parallel run, go-live. Each stage has an owner, an exit test and a date.
The method
Six phases, each with something you can inspect.
Every phase closes on an artefact — a mapped process, a signed design, a reconciled migration, a passed test script. Nothing advances on a verbal understanding, because that is where go-live dates quietly slip.
01
Discovery & process mapping
Workshops with the people who run the process. We record how orders, stock, production, cash and approvals move today, where the workarounds live, and which reports the business genuinely relies on.
02
Solution design
The mapped processes become modules, roles, document flows, approval chains and a chart of accounts, written up as a design document that you review and sign before build begins.
03
Configuration
Your environment is built to that design — entities, locations, tax and costing rules, numbering, permissions and document templates — plus custom extensions wherever the standard product does not fit the way you trade.
04
Data migration
Customers, suppliers, items, bills of material, employees, open documents and opening balances are extracted, cleansed, mapped and loaded — then reconciled back to your existing trial balance and stock valuation.
05
Testing & parallel run
Scripted end-to-end tests against your own scenarios, user acceptance sign-off by the people who will own each process, and a parallel period where both systems are posted so the numbers can be compared line by line.
06
Go-live & handover
A dated cutover plan with our consultants alongside your team, hypercare while the first cycle of documents and the first close run through, and a documented handover into the continuous support desk.
The implementation team
Realize the benefits of a fully integrated application.
An integrated system only pays off when every module is posting to the same ledger with rules the business recognises. Getting there is a consulting problem before it is a software problem, so the team that arrives is a mix of process consultants and product engineers.
- Consultants who have configured this platform for retail, manufacturing, practice, campus, fleet and public sector operations
- Engineers who can build a custom extension or interface when the standard product stops short
- A single project lead accountable for the plan, the risks and the date
- Environments hosted on a company-owned exclusive cloud facility, so infrastructure never becomes a third-party queue
Deliverables
What you actually receive.
Not a status deck. Artefacts your team can read, test against and keep after the project closes.
Configured environment
A live environment built to that design, with a separate sandbox that training and future testing run against.
Reconciled migration
Masters and opening balances loaded, with a reconciliation pack tying the new ledger and stock valuation back to the old one.
Test scripts & UAT sign-off
Scenario-based scripts written from your processes, executed by your own process owners and formally accepted.
Trained users & materials
Role-based sessions run on your configuration, with course materials your team keeps for new joiners.
Cutover & handover plan
A dated, hour-by-hour cutover runbook, followed by a written handover into the continuous support desk.
Questions
Before the project starts.
It is driven by scope: how many entities and locations, how many modules, how much history you want migrated and how clean that data is. We size it in discovery and commit to a dated plan then, rather than quoting a typical duration that would not describe your project.
Masters, open documents and opening balances are extracted, cleansed, mapped to the new structure and loaded — then reconciled back to your existing trial balance and stock valuation. How much transaction history comes across is a scope decision taken in discovery, and it is agreed in writing before migration begins.
Configuration first, always — it is faster to deliver and simpler to support. Where a genuine business requirement falls outside the standard product, our own engineers build a custom extension, interface or configuration, and it is recorded in the design document rather than added quietly.
A named process owner per area who can make decisions, access to your current data and reports, and availability for the workshops, user acceptance testing and the parallel run. Those three things move an implementation date more than anything on our side of the plan.
Start with discovery
Bring us the date you need to be live.
We will walk the processes that matter, tell you honestly what fits the standard product and what needs building, and lay the phases out against your calendar.