Agree on scope before configuration
Write down the workflows that must work on the first day: quotations, sales, purchases, inventory, customer and supplier balances, accounts and owner reports. Identify which processes are standard and which need an industry-specific demonstration.
For each process, name the responsible team member and the acceptance result. For example, an invoice should reduce stock in the agreed warehouse, update the customer balance and appear in the required report.
Choose deployment and migration deliberately
Compare online access and locally deployed options against connectivity, remote access, backup responsibilities and support arrangements. Deployment labels alone do not define who manages updates or recovery.
Prepare products, customers, suppliers and opening balances in an agreed format. Run a trial import, reconcile totals and confirm the cutover process. Keep data cleanup, historical transactions and external integrations explicit in the proposal.
Price the implementation, then the ongoing operation
Use published ERP pricing to explore the baseline. Ask for configuration, migration, training, hosting, backups, ongoing support and optional development to be itemised where applicable.
If your workflow is unusually complex, the Enterprise enquiry brief helps document integrations, acceptance criteria and rollout expectations. A quotation is specific to those requirements; it is not proof that an integration is already available.
Common questions
What should we prepare for an ERP demonstration?
Prepare your business type, branches, warehouses, current documents and a short example of an order from quotation to payment. List the reports and controls your team needs.
Is implementation included in every ERP price?
Check the published package scope and your written proposal. Setup, training, migration, hosting and custom development must be confirmed separately rather than assumed.
Can the rollout happen in stages?
A phased rollout can be discussed after the team understands your workflow and data dependencies. Each stage should have an agreed scope and acceptance checks.