Implementation

One priority workflow, live in weeks

Enterprise FP&A means three to six months and a six-figure engagement. Planir targets one priority workflow live in weeks, at a scoped fee in the tens of thousands. Four stages, a written success definition, validation against your own data.

Priority workflow
Monthly board pack
7 entities · 3 ERPs · 4 currencies
01 · Align on the scope
Success criteria signed off
Complete
02 · Connect systems
7 of 7 entities synced
In progress
Trusted by CFOs and finance teams at multi-entity groups across APAC

How does a Planir implementation work?

Four stages. Align on scope: the workflow, the success criteria, the entities, the users, the integrations. Connect and configure the source systems and the chart-of-accounts mapping. Validate with Finance until the numbers tie. Then go live. Stage 3 cannot be compressed.

Four stages, scoped around one workflow rather than a platform migration.

01
Align on the scope

Confirm the priority workflow, the success criteria, the entities, the users and the required integrations, in writing, before configuration begins. A vague scope produces an implementation that cannot be declared successful.

02
Connect and configure

Connect the source systems, map the chart of accounts across entities with agent assistance, and configure the reports or planning model the agreed workflow needs.

03
Validate with Finance

Reconcile the numbers, test the business rules, confirm the output meets the agreed requirements. Non-negotiable, and the moment trust is actually established.

04
Go live and expand

Train users, support the first live cycle, and add further workflows when the team is ready, not before.

Why start with one workflow rather than the platform?

Because platform breadth is a poor entry claim. It invites comparison against every incumbent on every axis, and asks you to commit to the transformation programme we promise you will not need. So the entry point is narrower: one priority workflow.

One workflow, one success definition, one cycle.

Select the workflow

Usually the monthly multi-entity consolidation and group reporting pack: painful, recurring, measurable within one cycle, and the place where cross-ERP consolidation is unambiguous. The board pack is the next strongest candidate.

Define success

Written before anything is built: what has to be true at the end, which entities and systems are in scope, and who signs it off. A validation that cannot be declared successful is not a validation.

Validate with your data

Your entities, your chart of accounts, your currencies, your last closed period. Finance confirms the numbers tie before anyone discusses a wider rollout.

What about running it in parallel first?

That is stage 3, and it is offered rather than conceded. “I would need to run it in parallel” and “you would have to replace my model” are risk statements, not capability statements. The right answer is a bounded exercise with a defined end.

A parallel run is not an obstacle to the sale. It is the sale.

Reconcile Planir's output against your existing process until Finance confirms the numbers tie

A written success definition agreed before configuration, so the result can be judged rather than debated

A scoped, priced, time-boxed validation with a defined decision point at the end, not an open-ended proof of concept

Complete audit trail and data lineage from the final report back to source, so every difference can be explained

Who is delivering it?

ITLink Business Solutions, 30+ years delivering planning and analytics for Finance teams. The same team builds the platform and delivers the implementation. There is no reseller, no referral partner and no third-party consultancy in between, so the people configuring your consolidation are the people who can change the product when your group needs something it does not do yet. At a scoped implementation fee you are not only assessing software. You are assessing whether the vendor can deliver. Three decades is a different risk profile from a two-year-old startup.

Enterprise planning heritage, delivered in weeks not quarters.

Enterprise EPM background

The team behind Planir has delivered planning and analytics programmes for Finance teams for over thirty years, across the enterprise tools these teams are usually quoted.

APAC presence

Singapore-built for Singapore, Australia and Malaysia finance teams, with regional ERP combinations, the regional currency mix, and support that answers during your working day.

Governance from the start

SOC 2 Type II certified, with role-based access, Security by Measure and a complete audit trail. ISO 27001 certification is in progress.

Common questions about implementation

How long does a Planir implementation take?
Weeks for one priority workflow, against three to six months for an enterprise EPM programme. The scope is deliberately narrow: one workflow, one written success definition, one cycle. Breadth comes afterwards, once the first workflow is live and running.
What does it cost?
The scoping session is free. Everything after it is priced against the agreed workflow, driven by entity count, ERP estate complexity, the number of source systems and chart-of-accounts effort. Implementation is quoted separately from the licence, after the scoping session.
We would want to run it in parallel for a quarter first. Is that a problem?
No, it is stage 3 and the recommended path. Objections like “I would need to run it in parallel” are risk statements, not capability statements. The honest answer is a bounded reconciliation with a defined end.
Which workflow should we start with?
Usually the monthly multi-entity consolidation and group reporting pack: painful, recurring, measurable inside one cycle, and where cross-ERP consolidation is unambiguous. The board pack is next strongest. The budget cycle is tied to your calendar.
Why not just implement everything at once?
Because a validation that expands mid-flight into “and also cash, and also the budget” is how a six-week proof becomes a six-month unpaid implementation, for both sides. One workflow, one success definition, one cycle.
Who does the work?
A joint team. Planir handles connection, configuration and chart-of-accounts mapping, with agent assistance. Your Finance team owns the success criteria and the validation. Stage 3 cannot be delegated, because Finance signing off that the numbers tie is the point.
What happens if the validation fails?
There is a defined decision point at the end of the scoped validation, and that is what it is for. A validation with a written success definition can be failed honestly, which beats a proof of concept that never ends.

Scope your first workflow

The scoping session is free. Bring the workflow that costs you the most every cycle, and we will define what success on it would look like and what it would take to get there.

Book a working session Talk to Sales