Do you serve manufacturing outside the UK?
Yes, when the constraint is the same: an overnight batch the plant still runs on rented iron. The pattern is written from UK mid-market plants.
Manufacturing
Manufacturing systems for UK mid-market plants.
The plant already has a core. The pain is the overnight loop finance cannot close. Start there.
In short
Velosius builds manufacturing systems for UK mid-market plants — and US plants with the same overnight-batch constraint. We strangler the painful loop into your cloud account. The core ERP stays until a later, boring decision. Samuel Okonkwo leads the work.
Who this is for
Operations and IT at plants where overnight planning, shop-floor confirmations, or inventory still run on rented iron, and Monday finance cannot reconcile them.
We will not rip out a working core in year one, and we will not sell a greenfield MES because a slide asked for a platform.
What plant work looks like here
A UK mid-market plant is not a greenfield software business. Planners, supervisors, and finance already have a system of record. The failure is usually one loop: a batch that still needs the datacentre, a confirmation that never reaches inventory, a close that waits until someone copies a file.
Manufacturing systems in this studio means that loop, in your account, with monitoring and rollback. It is not a five-year programme to replace the core. If the brief is “new ERP everywhere”, we will say so on the first call.
What stays on the core
Finance close, master data, and the parts of the plant that already run are left alone until the first pathway is live. The strangler sits beside the core: APIs, a managed database, a job the operators can see fail. When that loop is boring, you decide whether the next slice is worth it.
US plants with the same overnight constraint use the same cut. The UK-hours overlap is for the people who have to approve a cutover, not a night shift that replies the next day.
Who stays on the programme
Samuel Okonkwo leads manufacturing and integration. You speak to him on the brief, not an account layer that translates the plant back to Colombo. The 90-day first pathway is one loop — planning, confirmations, or inventory finance cannot reconcile — then handover so the next slice does not need us in the room.
What the first programme leaves you
- One overnight or shop-floor loop named with a business owner
- Strangler in your cloud account; the core ERP is not the project
- Monitoring, rollback, and a runbook plant IT can use
- A composite plant-to-cloud snapshot on /work — not a fake logo
Programme lead: Samuel Okonkwo.
Commercial page
Cloud manufacturing ERP
Cloud manufacturing ERP for UK mid-market plants. Strangler the overnight batch first — not a five-year core ERP replacement.
Work snapshot
Plant to cloud
A UK manufacturer was paying datacentre rent for batch jobs that ran overnight. We replatformed the pain first — managed databases, strangler APIs — not a heroic weekend cutover. Field note: cloud manufacturing ERP.
Seasonal demand without buying more iron
Longer field note: Cloud manufacturing ERP: replatform the pain, not the whole plant.
FAQ
Before you brief us
Is this a manufacturing ERP replacement?
No. The industry page is the plant and the operators. The service is a strangler of one painful loop. The core stays.
Who leads manufacturing programmes?
Samuel Okonkwo. A 15-minute call is enough to see if the loop is a fit.
Next step
Fifteen minutes is enough.
Send the loop that fails on Monday, the systems it must touch, and the constraint you cannot break. We will say build, connect, or stop.