Modular ERP platforms that scale with your operating model.
We build custom ERP systems for enterprises that have outgrown their legacy stack. Finance, supply chain, manufacturing and HR, wired together through clean APIs so you can replace one module at a time without rebuilding the rest. This is how manufacturing ERP solutions should have been built in the first place.
What we deliver
Custom ERP architecture
Domain-driven, modular cores with clean boundaries between finance, SCM, MES and HR. Each module has its own data model, team and deployment path.
Legacy ERP migration
Strangler-fig migrations from SAP, Oracle EBS, Dynamics or in-house monoliths. Parallel-run validation means zero data loss and zero operational downtime.
Finance and SCM modules
GL, AP, AR, inventory, procurement and WMS modules tuned to multi-entity, multi-currency operations with local tax and statutory reporting.
Manufacturing ERP
Shop floor to finance in one platform. MES integration, cost accounting, production planning, quality and maintenance tightly coupled to the general ledger.
Workflow and approvals
Configurable approvals, SLAs, escalations and full audit trails. Extend through APIs and webhooks without touching core modules.
Embedded analytics
Operational BI, KPI dashboards and write-back planning baked into the ERP user experience. No separate BI tool to chase.
Why teams choose FictiveBox
How we work
Discover
Process mapping with finance, operations and IT. Capability gaps, migration risks and the one-page success definition.
Architect
Reference architecture, module boundaries, data model and integration map. Nothing vague.
Build
Iterative module delivery with parallel-run validation against your legacy system. You see production telemetry from sprint one.
Operate
Hypercare, SRE handover, continuous optimization and FinOps. We stay on if you want us to, and hand off cleanly if you do not.
ERP Modules We Build
Composable ERP modules engineered to drop into existing landscapes or anchor a green-field platform.
Manufacturing ERP Suite
Shop-floor to finance ERP with MES integration, cost accounting and production planning in one platform.
View DetailsFinance & Close Suite
GL, AP, AR and consolidation modules engineered for multi-entity, multi-currency global operators.
View DetailsSupply Chain & WMS Suite
Procurement, inventory and warehouse modules with EDI and carrier integration baked in.
View DetailsLegacy ERP Migration Accelerator
Strangler-fig migration tooling for SAP, Oracle EBS and Dynamics with parallel-run validation.
View DetailsTools & technologies
Common questions
- What does FictiveBox's ERP development service include?
- Custom, modular ERP architecture with clean boundaries between finance, supply chain, manufacturing and HR; legacy ERP migration from systems such as SAP, Oracle EBS, Dynamics or an in-house monolith; finance and SCM modules covering GL, AP, AR, inventory, procurement and warehousing; manufacturing ERP with MES integration and cost accounting; a configurable workflow and approvals engine; and embedded operational analytics inside the ERP itself.
- When should a company replace or modernise its ERP?
- The usual signals are a month-end close that takes weeks, finance reconciling in spreadsheets outside the system, and every customisation adding months to the next upgrade. Those are symptoms of a monolith that can no longer be changed safely. The answer is usually a modular system you can replace one piece at a time, not another single large platform.
- How do you migrate off a legacy ERP without stopping operations?
- We use strangler-fig migrations with parallel-run validation: the new module runs alongside the legacy system and the two are reconciled against each other until the results agree, then traffic moves across. Modules are delivered iteratively rather than as one cutover, which is what keeps the operational risk contained.
- How is an ERP engagement delivered?
- Four phases. Discover maps processes with finance, operations and IT and produces a one-page success definition. Architect produces the reference architecture, module boundaries, data model and integration map. Build delivers modules iteratively with parallel-run validation. Operate covers hypercare, SRE handover, continuous optimisation and FinOps. Engagements run as outcome-based pods rather than staff augmentation. Every pod has an architect who writes code and an engineering lead who works inside your standups, and the engineer who designs the system is the engineer who stays with it.
- What should a customer prepare before an ERP project starts?
- Access to the people who actually run the processes in finance, operations and IT; a view of the current system landscape and its integrations; and the business outcome you want the programme judged on. The discovery session is a working session, so the more directly we can talk to process owners, the more accurate the architecture and plan.
- What technologies are used for ERP builds?
- Postgres, Kafka, Temporal, .NET, Java Spring, Node.js, React, Snowflake, dbt and Kubernetes. The exact selection depends on the estate we are integrating with rather than a fixed stack. You own the source code, the infrastructure definitions, the runbooks and the documentation. There is no black box and no lock-in, and we hand over cleanly whenever you ask.
Ready to engineer your next platform?
Book a 30-minute consultation with a senior solutions architect. No slide deck. Just answers.