The platform gets chosen first, and the operating question comes after. We start at the other end — with the decision in front of you, the trade-off inside it, and an honest answer about whether to act at all.
Not one of these has a single right answer. Each has an answer that fits how you operate — and a case for doing nothing.
Complaints about reporting, manual re-entry, and a finance team closing the month out of a spreadsheet.
Replacement buys one coherent system and costs you the longest programme your organisation has run. Fixing the edges is faster and leaves the seams in place.
If the ledger is sound and the pain is all at the boundaries, that is an integration problem wearing an ERP costume — and it costs a fraction to solve.
Growth. A system that ran one business well is asked to report across six, and nobody agrees which version of the number is true.
One standard gives you a single view and one thing to train against. It also removes the local freedom that made your strongest unit distinctive — and that freedom is sometimes the product.
If your units genuinely serve different customers, a group standard solves a problem you do not have. The reporting layer is usually the cheaper answer.
A board question about dependency, usually after an implementation went sideways.
Building keeps the knowledge inside and takes two hiring cycles to be real. Buying moves faster and leaves you owning the relationship rather than the skill.
If the team that will own this on day four hundred does not exist yet, that is the first decision — not the last. Everything else waits.
We deliver these systems. Here is when we will tell you not to buy one from us.
Your operation as it runs, including the exceptions nobody documented.
The trade-off resolved in writing, with the case against it kept in.
We implement what the decision called for, sequenced so the business keeps running.
We run it after go-live and stay accountable for how it performs.
We are vendor-neutral, so this list is not a menu. It is the delivery capability that lets a recommendation be honest: we can name what fits, then be held to running it. Six business units, built and governed regionally.
Answering that first is what made the rest straightforward. We delivered Shiji's hotel management and point-of-sale platform, connected to e-invoicing through Reachware — the integration was the project; the platforms were the consequence of it.
Not a quiz, and not a score. Three questions locate the decision actually in front of you. What comes back is written in plain terms — and on several paths it says the honest thing is to do nothing yet.
Five situations account for most of what senior teams bring us — from systems that do not talk to a compliance date that is coming.
Where the numbers diverge, where data is re-keyed, what is actually growing. The detail that decides whether the edge or the core is the problem.
The question that changes the answer more than either of the others. If there is no answer yet, that is the first decision — not the platform.
A decision agenda, in three parts: what is already known, what is exposed, and what still has to be tested. No readiness score, no maturity rank, no percentage — we have not earned those and neither has a form with three questions in it.
Nothing is gated. You get the reading without leaving an email address. If it is useful and you want the full version — your entity structure, your close, where the exceptions actually live — that is a paid diagnostic, and its fee is credited against the engagement if you go ahead.
Thirty minutes with an advisor to work out which of the three questions above is actually in front of you — and whether it is worth acting on this year. If the answer is no, you will hear that.