Operational records and workflows
Connected records for the agreed process: orders, projects, purchasing, inventory or work orders. Each stage has clear ownership, required information and a defined next action.
Operations / Connected business systems
Kerning / IntelligenceCustom ERP development
Build an ERP around the records, responsibilities and decisions that make your operation work. We connect the process from the first request to fulfilment and review, with a manageable path into everyday use.
When the handoffs become the work.
An order can move through sales, purchasing, stock, delivery and accounts while its context remains scattered across spreadsheets and messages. Teams spend time checking which record is current, who approved a change and what needs to happen next.
Custom ERP development starts by mapping those dependencies. We identify where a shared system would help, which existing tools should remain authoritative and whether a focused extension is more useful than replacing an entire platform.
01Scope / Shaped around your process
What we can build.
Roles, approvals and exceptions
Workspaces shaped around job responsibilities, with permission rules, review gates and exception queues. A manager can see what needs attention without giving every user the same access.
Reporting with traceable context
Operational views and reports tied to the records behind them. We agree definitions with the team so a status, stock figure or financial handoff has an understandable basis.
Migration and operating guidance
A plan for importing agreed records, checking completeness and resolving mismatches, alongside documentation and practical walkthroughs for the people responsible for running the system.
02Delivery / From context to working software
How the work takes shape.
Map a complete business cycle
Use representative transactions, including exceptions, to define the data model and acceptance criteria. Prioritise one coherent workflow for the first release rather than a disconnected collection of screens.
Connect the sources of truth
Review the APIs, exports, ownership and update frequency of existing systems. Define how failed imports, duplicate records and conflicting updates are handled before integration becomes an operational dependency.
Introduce the system in stages
Validate the workflow with its users, rehearse migration and agree a cutover plan. Subsequent releases can extend the same foundations as the business identifies its next priority.
Context / Relevant work
Connected operations in the Hemco workspace.
The Hemco application brings sales, projects, purchasing, inventory and accounting workflows into role-specific workspaces. The case study explains the project lifecycle and the handoffs between teams, alongside a complementary bank-reconciliation application.
The published workflow is illustrative. No measured customer outcomes or production performance figures are claimed.
03Before you begin
Useful questions.
Do we need to replace our existing ERP?
Not necessarily. Discovery may identify a missing workflow, portal or integration that can sit alongside it. We compare that option with a wider replacement using the constraints, ownership and maintenance needs of your operation.
Can you migrate spreadsheet and legacy data?
Migration can be included after reviewing the available exports, record quality and business definitions. The plan should specify what moves, how it is checked, how exceptions are resolved and which historic records remain in the original system.
How are integrations scoped?
We first confirm the other system’s supported interfaces, access permissions and commercial restrictions. The proposal then identifies the records exchanged, sync direction, frequency, error handling and responsibilities on each side.
What determines the delivery plan and cost?
Workflow breadth, user roles, migration complexity and integration dependencies shape the estimate. We define a first release and acceptance criteria before agreeing the delivery plan; pricing and ongoing support are set out in the proposal.
Next / Your first conversation
Bring us one complete workflow.
An example order, the teams it passes through and the points where it slows down make a useful starting point. We can work from there to define the first release.
Discuss your ERP project