How long does an implementation take?

Business Central engagements for mid-market companies typically run three to nine months end to end, depending on entity count, data quality and integration scope. EPM implementations are faster — often weeks rather than months, particularly where a rapid-deploy platform fits. We give you a phase plan with dates after the assessment, not before.

Do we need an ERP before we can do EPM?

You need a reliable source of actuals. For most companies that means an ERP. If your accounting system is clean and well structured, a planning layer can sit on top of it directly — the assessment tells us which situation you are in.

Can you work with our existing implementation partner?

Yes. We are often brought in specifically to own the finance design workstream alongside a technical implementation team.

What happens after go-live?

Hypercare is included with defined exit criteria. Beyond that, ongoing optimisation is available through our Performance service, or we hand over entirely to your team. Both are legitimate outcomes.

We deliver globally from India. Engagements run remotely, with on-site phases where the project warrants it.

Implementation

Your planning system is only as good as the structure underneath it.

Most finance system projects are run by technologists who understand the software but not the close. We run them the other way round. Twenty years in finance, applied to the decisions that determine whether your reporting works three years from now — chart of accounts, dimension design, entity structure, and the data model your planning layer will sit on.

Book a systems assessment See how we work

Architecture layers

Reporting
Board packs, dashboards, statutory
Planning
Budgets, forecasts, consolidation
Integration
Mapping, reconciliation, data flow
ERP
Ledger, dimensions, entity structure

Each layer only works if the one beneath it was designed for it.

The expensive mistakes are made in week two.

By the time a finance system goes live, the costly decisions are already locked in. A chart of accounts built for statutory filing rather than management reporting. Dimensions that can't answer the questions the board actually asks. An entity structure that makes consolidation a manual exercise forever.

None of these show up at go-live. They show up eighteen months later, when you try to add a planning layer and discover the data won't support it — and the fix is a re-implementation.

Software vendors don't catch this, because it isn't a software problem. It's a finance design problem, and it needs someone who has closed books, built budgets, and sat through the audit.

We design the finance architecture first, then implement against it.

Design

Chart of accounts, dimension strategy, entity and currency structure, cost allocation logic, and the management reporting model. Documented before a single system is configured.

Implement

Configuration, data migration, reconciliation, testing, training and cutover — run to a defined phase plan with go/no-go gates, not an open-ended engagement.

Hand over

Your team owns the system when we leave. We build in-house capability deliberately, because a finance system you can't change yourself is a liability.

Where you begin depends on what you already have.

Path A — No ERP in place

Spreadsheets, or accounting software you've outgrown.

You're running finance out of Tally, QuickBooks, Zoho, or Excel. Month-end takes two weeks. Every report is rebuilt by hand. You know you need a proper system but every quote you've received is either enterprise-scale overkill or a licence reseller with no finance depth.

We implement Microsoft Dynamics 365 Business Central as the finance foundation — sized for mid-market, deployed in months not years, and structured from day one so a planning layer can sit on top of it later without rework.

What you get: General ledger and dimension design, AP/AR, banking and reconciliation, fixed assets, multi-entity and multi-currency where needed, statutory and management reporting, data migration from your existing system, and user training.

Talk about an ERP foundation

Path B — ERP in place, no planning layer

The system records what happened. It can't tell you what should happen next.

Your ERP is doing its job. But budgeting still runs on emailed spreadsheets, forecasts are a quarterly fire drill, and consolidation is a manual assembly job that only one person understands.

We select and implement the right EPM platform for your size, stack and planning maturity — and we do it vendor-neutral. We are not incentivised to sell you the largest licence. The selection is part of the engagement, and we will tell you if the answer is a smaller tool than you expected.

What you get: Requirements definition, structured vendor evaluation, planning model design, ERP integration and data mapping, model build, user enablement, and a first live planning cycle run alongside your team.

Talk about a planning layer

We work with the platforms that fit the mid-market.

Microsoft Dynamics 365 Business Central

ERP foundation.

Full finance and operations for mid-market companies. The right answer when there is no real system in place, and the natural fit if you already run Microsoft 365.

Solver

Rapid-deploy xFP&A.

Pre-built reports, dashboards and budget forms mapped to your existing financial system. Connects to Dynamics 365, Sage, Acumatica, SAP Business One and QuickBooks. The fastest route from ERP to a working planning cycle.

Vena

Excel-native planning.

Structure, workflow and a central database without asking your finance team to abandon Excel. Strongest fit for Microsoft 365 and Power BI estates, and for teams with mature models they don't want to rebuild.

Jirav

Driver-based planning for smaller teams.

Forecasts P&L, balance sheet and cash flow from operational drivers. Right-sized where a full EPM platform would be over-engineered.

No platform suits every company. If none of these fit, we will say so.

Phases, gates and a fixed scope.

1
Assessment (2–3 weeks)
Current systems inventory, process mapping across record-to-report, gap analysis, and a written recommendation. Deliverable is a decision document. You can stop here and take it elsewhere.
2
Architecture (2–4 weeks)
Chart of accounts and dimension design, entity and currency structure, reporting model, integration architecture, and the data migration plan. Signed off before build begins.
3
Build and configure
System configuration, model build, integrations, and iterative review with your finance team throughout — not a black box you see at the end.
4
Migrate and test
Data migration with reconciliation evidence, user acceptance testing, and role-based training.
5
Cutover and hypercare
Cutover runbook, parallel run where appropriate, and defined post-go-live support with exit criteria.
6
Handover
Documentation, admin enablement, and a capability review. Ongoing support is optional, never assumed.

Finance people, doing systems work.

Twenty years in finance

The engagement is led by someone who has run closes, built budgets, defended forecasts and handled auditors. Design decisions get made by a practitioner, not translated through one.

Vendor-neutral by design

Selection is an advisory service, not a sales process. We are paid for the outcome, not the licence.

Built for what comes next

Every implementation is designed so the next layer — planning, integration, analytics — attaches without rework. That is the whole point of doing the architecture first.

India-based delivery

Senior finance-systems expertise at a cost structure that makes proper design affordable for mid-market companies, not just enterprises.

Questions we get asked

Start with an assessment, not a demo.

Two to three weeks, a fixed fee, and a written recommendation you own — including the recommendation not to buy anything. It is the cheapest way to find out what you actually need.

Book a systems assessment