On process complexity, scale, regulatory load and how much of your operating model is genuinely distinctive. Multi-entity finance, regulated reporting and deep customer or field-service process usually point to Microsoft. Broad functional coverage at speed points to Zoho. Specific, hard-to-standardise operational process — particularly in manufacturing and inventory — often points to Odoo.

The selection is an output of the discovery work, not an input to it. If a platform is already chosen and it is defensible, we will implement it and say so.

Platform selection · Discovery · Fit-gap

A single-entity finance and operations core on Business Central or Odoo is typically a matter of months rather than weeks. Multi-entity, multi-country or manufacturing-heavy scopes run longer, and the difference is almost never configuration — it is data readiness, process decisions and the availability of the people who know how the business really works.

We phase deliberately: a core that goes live and is trusted, then the extensions. A programme that tries to deliver everything at once usually delivers the reconciliation problems first.

Phasing · Data readiness · Cutover

Yes, and it is a meaningful part of our work. We start with an independent assessment of the solution design, the data position, the integration inventory and the decisions that were never actually closed — then give you a recovery plan with a costed route to a usable go-live.

The assessment stands on its own. If you would rather your incumbent partner delivered the recovery plan, that is a legitimate outcome.

Project rescue · Independent assessment

Most estates keep something — a payroll engine, a trading platform, a customer portal, an industry-specific tool. Those interfaces are designed alongside the core rather than discovered in testing, and each one gets an owner, an error path and a reconciliation.

Replacing a system that works is rarely the cheapest way to fix a reporting problem.

Integration · Coexistence · Reconciliation

Hypercare while the first period closes, then a managed service with a release cadence. The point of the cadence is that improvements have somewhere to go: without one, the backlog turns into a second project eighteen months later.

Support covers the applications, the integrations and the reporting layer — the same team that built them.

Hypercare · Managed service · Release cadence

Yes. VAT treatment, WPS payroll files, multi-currency, multi-entity consolidation and free-zone versus mainland entity structures are treated as core scope from solution design onward, not as a localisation task bolted on before go-live.

VAT · WPS · Multi-entity

With a release cadence and a visible backlog. Improvements need somewhere to go, or they accumulate until somebody proposes a second project eighteen months later to clear them.

A small standing capacity delivered every quarter beats an occasional large one: it keeps the backlog credible and stops the platform falling behind the business.

Release cadence · Managed service · Backlog