Implementation Process¶
We begin with your business workflow and agree the scope before configuring the system.
What happens at each stage?¶
| Stage | What we do together | What you prepare or confirm | Result |
|---|---|---|---|
| 1. Understand your business | Discuss your workflow, systems and main difficulties | Key users, a typical order or job, and your priorities | Shared understanding of the improvements you need |
| 2. Review the solution | Demonstrate relevant workflows and assess configuration, data and integrations | Confirm what fits and identify gaps | Proposed solution and initial scope |
| 3. Agree the proposal | Confirm modules, fees, responsibilities, timing and support | Review the proposal and service agreement | Written scope and agreed next steps |
| 4. Prepare data | Review agreed import files and resolve inconsistent records | Clean customer, supplier, product, stock and other agreed data | Data ready for agreed imports |
| 5. Configure and connect | Set up roles, workflows, templates and integrations | Approve settings and authorise third-party connections | System ready for testing |
| 6. Test and train | Walk through real examples with your users | Test routine work and exceptions; report issues | Confirmed workflows and trained key users |
| 7. Confirm go-live readiness | Agree the cutover plan, opening figures and unresolved items | Approve readiness and assign responsibilities | Agreed launch date and cutover plan |
| 8. Launch and review | Support live use and review follow-up needs | Record issues and nominate a contact | Live system with a follow-up plan |
How long will it take?¶
Timing depends on modules, data quality, integrations, custom work and your team's availability. We confirm an estimated schedule after reviewing these requirements.
Can we introduce the system in phases?¶
Yes. A first phase can focus on a core workflow, such as sales and stock, or jobs and time recording. Further modules can follow when your team is ready and the additional scope is agreed.
How is existing data handled?¶
We agree what needs to be imported, what can remain in an archive and how imported records will be checked. Full historical migration is assessed separately from master data and opening balances.
What does testing include?¶
Use realistic examples from your own business:
- A normal order or job from start to finish.
- A shortage, partial delivery, return or project variation where relevant.
- Staff permissions and approvals.
- Documents, pricing, costs and agreed integrations.
Record issues and confirm essential workflows before go-live.
What happens if requirements change?¶
We review the impact on configuration, development, fees and timing. Additional work is agreed before proceeding.