Back to Reference Scenarios
Manufacturing / IndustrialReference Scenario
How We'd Modernize a 15-Year-Old ERP Without Stopping Production
An engagement blueprint for incrementally modernizing a legacy custom ERP using the strangler fig pattern — because when downtime halts production lines, a big-bang rewrite is a bet-the-company move we'd refuse to make.
Type: Illustrative engagement blueprint — not a client claim
Timeline: 6–9 months (incremental)
6–9 months
Timeline
€45–80K
Budget Range
Founder-led
Staffing
These are example engagements — illustrative blueprints that show how we work, not client claims. Cloudrix launched in 2026 (KVK 97732699); we'd rather show you exactly how we approach real problems than invent testimonials. Your project could be our first named case study — early clients get featured placement and case-study pricing.
The Typical Situation
The typical situation: a manufacturing company runs critical operations on a 15-year-old custom ERP. The original developers are gone, documentation is sparse, and the codebase is nearly impossible to modify safely. Any downtime halts production, making a rewrite too risky — yet new customer EDI integration requirements are impossible to meet on the existing architecture.
How We'd Approach It
We'd apply the strangler fig pattern: put a clean API layer in front of the legacy system, build new capabilities as small services behind it, and extract legacy modules one at a time — each extraction independently shippable and independently reversible. Message queues (RabbitMQ) decouple new services from legacy timing assumptions. Crucially, the internal team pairs with us throughout, so the engagement ends with them able to maintain and extend the system without us. We measure our success by our own obsolescence.
What You'd Get
- Legacy system audit: dependency map, risk register, and extraction sequence
- Anti-corruption API layer isolating legacy modules from new services
- First extracted modules shipped as documented, tested microservices
- EDI integration layer designed for onboarding additional customer systems
- Hands-on training plan and pairing sessions for the internal team
- Modernization playbook the team can continue executing independently
Typical Stack
Node.jsReactPostgreSQLRabbitMQDockerAzurePower BI
Become our first named case study
No anonymous testimonials here — we don't have named clients to quote yet, and we won't invent them. If this scenario looks like your project, you'll get founder-level attention and case-study pricing; in exchange, if (and only if) you're happy with the result, your project becomes the first real case study on this site.
Book a Free Intro CallDoes This Look Like Your Project?
Let's have an honest conversation about your situation and whether we're the right fit — no invented numbers, no pressure.
Book a Free Consultation