Calnorm works with mid-size groups on strategy, implementation and project management, across infrastructure and business applications.
Start a conversationMid-size groups get sold a platform sized for scale they don't have, then carry licence and support costs that outweigh what the system returns. The same pattern is repeating with AI — licences bought before anyone decides what they are for, who may use them, or on which data. It bites harder in markets where turnover does not justify pricing written for economies ten times the size. There is almost always a cheaper route to the same result. Finding it is the work.
ERP or any core business system, chosen against how the business actually runs — or a finding that the current one does not need replacing. Total cost counted through the years after go-live, not just at purchase.
Modules bought and never switched on, processes still run in parallel on paper, reports rebuilt by hand every month. Usually the fastest return available, and it needs no new licence.
What to license, what to govern, what to train people on — a defensible licensing position, a use policy people can follow, and awareness training that changes behaviour before the first serious mistake.
Custom web platforms, mobile applications, internal tools and portals — built when no product on the market fits the problem closely enough to be worth its licence.
Removing the manual steps between systems that people quietly absorb: workflows, integrations, scheduled reporting, data moving without anyone re-keying it.
Consolidated figures a board can trust, drawn from whatever the business runs today — not from a platform everyone has to migrate to first.
Networks, servers, cloud and hybrid architecture, end-user computing, backup and continuity — sized for the business rather than for the brochure.
Where the real exposure sits, what to fix in what order, and the human layer that most reviews skip.
Steering an implementation from kickoff to handover — managing vendors and implementation partners, and holding a programme to its scope, budget and timeline.
The shape matches how well-defined the question already is.
Short, fixed scope, ends in a written position that can be acted on or shelved.
Scoped, priced, finished — a decision, a design, a migration plan, an implementation managed to close.
A technology opinion in the room, or hands-on management of a programme, without carrying it on headcount.
Engagements are scoped from how the business actually runs, not from a vendor's reference architecture. The starting point is always the same question: what does this organisation need to run reliably, and what is it being asked to carry that it does not need?
Recommendations are made and tested against total cost of ownership, not list price — licensing, support, integration and the people needed to keep a system running, counted across the years it will actually be in use.
Work spans infrastructure, business applications, data and AI adoption, because these problems rarely stay inside one lane — a reporting gap is often an integration problem, and a licensing decision is often a governance one.