A dense block of rules beside a light open frame

Archived article, kept for reference.

Do you need a full ERP or a lightweight internal operating system?

Most operational pain is not an ERP-shaped problem. It is one or two broken processes sitting on tools that otherwise work. Here is how to tell the difference, and where to start.

Growing companies rarely arrive at a technology decision calmly. More often, a single bottleneck becomes the moment someone declares that the business needs a new system: an approval that takes a week, a report nobody trusts, a service request lost in an inbox. The instinct that follows is understandable but expensive: rip everything out and install a full enterprise resource planning (ERP) platform. For many Luxembourg SMEs and mid-market operators, that is the wrong reflex.

The reflex to replace everything

An ERP promises a single source of truth across finance, procurement, inventory, HR and operations. When it genuinely fits, it is powerful. But a full ERP programme is a structural commitment: months of implementation, significant licensing, external consultants, data migration, and a long period during which the organisation reshapes itself around the software rather than the other way round.

The uncomfortable truth is that most companies feeling operational pain do not have an ERP-shaped problem. They have one or two broken processes sitting on top of tools that otherwise work perfectly well.

Symptoms that do not require a full ERP

It is worth being precise about what you are actually experiencing before committing to a large replacement. The following are real problems, but they are rarely solved by an ERP:

  • Approvals stall because they live in email, and no one can see where a request has reached.
  • The same figures are re-keyed into several spreadsheets, and each version quietly disagrees.
  • Service or maintenance requests arrive through five channels and get lost between them.
  • Documents are routed by hand, with no record of who saw what and when.
  • Management asks for a simple dashboard and waits days for someone to assemble it.

None of these are failures of your accounting package or your core tools. They are gaps in the connective layer between people and process: the layer an ERP happens to include, but does not need to be bought wholesale to obtain.

Where a lightweight internal operating system wins

A lightweight internal operating system is a custom layer built around how your business actually works: the approvals, requests, reporting and document flows that are specific to you. Rather than bending the organisation to fit a product, it encodes existing practice and removes the friction around it.

Its advantages are practical. It is scoped to one or two processes, so it is smaller to specify, build and test than a full ERP programme. It covers the functions the process needs and no more. And because it uses your own words for cost centres, sites and roles, people recognise their own work in it.

Focused operational improvements can begin with a clear approval chain, a reliable request queue or consistent reporting. The useful first scope depends on the process, the quality of its records and the people responsible for it.

When a bespoke system should still integrate, not replace

Choosing a lighter path does not mean building an island. A well-designed internal layer should sit alongside the systems you already rely on and read from them, not duplicate them.

Your accounting software should remain the record of account, and your payroll tool the place where pay is calculated. The custom layer's job is to organise the work: capture the request, route it, apply the approval rules and log who did what and when, while each system of record keeps its own records. A bespoke system earns its place when it brings together records from tools that were never designed to talk to each other, and gives management visibility across the seam.

The test is simple: replace a process, not a product. If an existing tool does its job well, integrate with it. Only rebuild what is genuinely broken.

Phasing the work into one module

The safest way to begin is also the most disciplined: choose the single process causing the most pain and build only that. One module, such as a service-request flow, an expense-approval chain or a management dashboard, is small enough to specify precisely, build and measure honestly.

This phasing carries a further advantage. A tightly scoped first module is often the right size to align with available digitalisation support, keeping the initial commitment modest while you confirm the value before extending. Each subsequent module then builds on a proven foundation rather than a hopeful blueprint.

Eligibility and funding for any support scheme are decided by the competent authorities; companies should confirm their own situation.

The question, then, is not "ERP or nothing". It is whether you need to replace your operating environment or simply sharpen it. For most growing companies, the honest answer is the latter: a narrower, cleaner, better-fitting layer over the tools you already trust.

A note on how we work

Harrimont is an AI, data and systems engineering company, based in Kosovo and working internationally. It builds the applications operational teams use to plan, coordinate work and record decisions. Its platform, Ancilor, reads from the systems a business already runs, such as accounting, bank files and spreadsheets, and works alongside them rather than replacing them.

Start with one workflow.

Bring one process, the systems it already runs on and the decision your team needs to make.

Discuss your operation

Current articles

All insights