| ERP consulting | Which system, which plan and which hosting, and what each vendor's limits mean for how you work. | A written advice note |
| Discovery | How many orders, bills, users and sites each team handles, and every system the ERP must talk to. | A scope with counts and a list of links |
| Process mapping | Each process drawn step by step: who does what, which record it touches and who approves it. | Process maps your team checks and signs |
Implementation The build | Settings, custom fields, approvals, reports and the links to your other systems, built in a test copy first. | A set-up system, tested with real orders |
| Data migration | Items, customers, suppliers, prices, opening balances and open orders, cleaned and checked. | Loaded data with counts and totals matched to the old system |
| ERP training | Key users first, then each role on its own tasks, on a copy loaded with your own data. | Sessions per role and short written guides |
| Ongoing support | Fixes, questions, small changes, and tests before each vendor update. | A support plan whose terms the contract sets |