NAP carries the same enterprise context from implementation into integration and production operations, so each stage starts with what the last one already learned.
Three pools of services work, converted into software.
Implementation work
Software
8020P
Integration projects
Software
NAP Connect
Production support
Software
Mira
01 — 8020P
Transform
Modernize ERP.
Turn implementation work into software.
8020P reads the legacy environment directly, understands what must move, what must change and what can disappear, then executes the modernization and proves the result before cutover.
Account framework resolved. to a dimensional model, derived from posted history rather than the setup screen.
Customizations classified— carried forward, rewritten as extensions, or retired because the target does it natively.
Dexterity and C/AL read, with behaviour preserved and verified against real payloads.
Cutover gated per entity. $0.00 variance or it does not go.
On a typical GP estate, 137 customizations classify as 31 carried forward, 44 rewritten and 62 retired.
Mira watches critical ERP workflows in production, finds the root cause of failures, resolves what it can and encodes what it learns so the same problem does not keep returning.
Root cause, not symptom — with the payload, the step and the system that returned it.
Resolved once. Recurrence after encoding is zero.
Applied everywhere, including deployments that have not started yet.
Headcount stays flat as transaction volume grows.
256K transactions a day with one human in the loop, across 40 live production environments.
8020N is the enterprise agent layer behind NAP. It gives agents identity, context, permissions and governed actions across systems of record — underneath all three products rather than beside them.
The secure connection, the API path, the field mappings and the business logic that moves a transaction from one system to another.
8020N asks
How does an AI agent safely understand and act inside those systems?
Identity and authentication. Credentials and permissions. ERP objects and custom fields. Which actions are allowed. Where a human must approve. What context travels with the action.
