Custom ERP development.
When stock, invoices and dispatch live in different tools, the same work gets entered twice. Build a system around the records and decisions your operation depends on.
For businesses whose established workflows have outgrown disconnected spreadsheets or off-the-shelf tools.
- Workflow & data model
- Business modules & roles
- Integrations & migration
- Acceptance & handover
In the scope
Start with the flow of work.
We map how a record enters the business, who changes it and what must happen before it becomes an invoice, payment or report. The first deliverable is an agreed workflow and scope, including the exceptions.
- Choose a starting workflow: receiving to stock, dispatch to billing, or attendance to payroll.
- Define each record’s owner, approval points and cancellation or correction rules.
- Separate the first release from later modules so the delivery can be reviewed against a clear boundary.
Connect the records that belong together.
Modules are selected for the engagement. A logistics system and a manufacturing system need different records, permissions and reports; the scope follows the business process.
- Inventory, billing, fleet, trip operations, payroll or accounting workflows, as agreed in scope.
- Role-based access, approval states and an audit trail for the changes the business needs to trace.
- Reports tied to agreed definitions and source records, with corrections reflected consistently.
Define the boundary with other systems.
Before connecting an accounting tool, payment provider or messaging channel, we check its access model and available interface. An integration plan names the source of truth and what happens when an external service is unavailable.
- Specify the records exchanged, direction of sync and ownership of credentials.
- Agree duplicate handling, retry behaviour and a way to reconcile failed transfers.
- Keep posting and approval permissions explicit; an integration is not a reason to bypass them.
Reconcile the data before changing systems.
Migration begins with a representative export and a review of its quality. We agree field mappings and opening records, then use a trial import to find gaps before a cutover is approved.
- Identify missing fields, duplicates and records that need manual decisions.
- Compare imported samples and balances with the agreed source data.
- Document cutover responsibilities, backups and the route for correcting a failed import.
Test the business transaction, end to end.
Acceptance is based on named workflows and expected results. A useful test follows the record through its lifecycle, including rejection, cancellation and the report it affects.
- Review a representative transaction from creation through approval and reporting.
- Check that restricted actions are unavailable to the wrong role.
- Resolve exceptions and reconcile migrated data before agreeing the release.
Agree how the system will be run.
The handover scope covers the source, deployment configuration, operating notes and the people responsible for access and changes. Monitoring and ongoing support are agreed as part of the engagement.
- Document environments, access ownership and release steps.
- Review backup and recovery procedures for the agreed hosting setup.
- Define support responsibilities and the route for requesting changes.
One workflow. A clear starting point.
Bring one workflow, the tools it currently touches, and the point where records stop agreeing. That is enough to begin a scope discussion.
Start a project