Skip to content
Metalique

Custom ops

Template ERP is not the floor.

A template is a bet that your exceptions are someone else’s average. Most growing operations lose that bet on the floor, not in the demo.

16 September 2026

What a template is good at

Packaged ERP and vertical SaaS are fast to buy. They have a diary, an inventory tab, an invoice screen. If the week already looks like the demo, a packaged product is the right answer. We will say so.

The problem is not that templates are empty. It is that they model the happy path, then leave the rest to a spreadsheet, a WhatsApp group, and the person who “just knows.”

Where the exceptions live

The floor does not fail on the average job. It fails on the hold that cannot block a pick. The courtesy car promised twice. The snag that should stop practical completion. The failed direct debit that should block the door.

Those are not feature requests. They are the operation. If the software cannot hold them, people will — in their heads, then in a sheet, then in a fight at close. Event hire booking that is not the warehouse. Workshop job cards that are not the keys. Same split, different floor.

It shows up across UK hire, workshops, and field teams the same way: different trade, same gap between the branded login and the week.

The hidden second system

When a template cannot model the exception, a second system appears. It is usually Excel. Sometimes it is a chat. Always it is the real operations software — the one people trust when the licence disagrees with the floor.

You then pay twice: once for the seat, and again for the reconstruction every Monday. Integrations do not fix a missing object. They move the reconstruction into a queue.

Custom ops as the alternative

Custom operations software starts from the week, not from a module list. We watch how work, stock, and money move — including the workarounds people are ashamed of — then build the object the floor already uses.

That is the approach: discovery, a written scope, then a system for the people running the day. Not a demo deck with an inventory tab bolted on. History migrated, not discarded. Care with a named contact after launch.

It is slower to buy than a template. It is faster than running two systems forever.

How we start

A twenty-minute call. Cal.com, email, phone, or WhatsApp. We map the exceptions a template never modelled. Then a written scope — what is in, what is out, what depends on an integration. Pricing is not a public list; it depends on the operation.

UK studio, based in Chigwell, Essex. Custom systems for UK hire, workshops, and field teams — in the language those floors already use. If the tools still don’t talk to the floor, book a discovery call.

If the licence still disagrees with the floor, book a twenty-minute call. We start with the exceptions.