Enterprise software selection has become a discipline. Vendor evaluation matrices, analyst reports, structured demos, reference calls. The decision that follows it - who actually builds the thing - usually gets a fraction of that attention. It is also the decision that determines whether the platform delivers.
Anyone who has sat through an enterprise software selection recognises the process. A cross-functional team is assembled. Requirements are documented. Analyst reports are read, sometimes closely. Three or four vendors are shortlisted, each gets a scripted demo, and a scoring matrix produces a winner. Somewhere between four and eight months pass.
Then the implementation partner is chosen. Frequently in a single procurement round, frequently on price, and frequently from a shortlist supplied by the vendor whose software was just purchased.
The imbalance is striking once you notice it, because the second decision has at least as much bearing on the outcome as the first.
The platforms are not the differentiator they used to be
Twenty years ago, enterprise performance management platforms differed substantially in what they could do. Some handled multi-GAAP consolidation well and planning badly. Some could not manage intercompany elimination at scale. Choosing wrong meant discovering a hard limit halfway through implementation.
That gap has narrowed. The platforms that appear consistently in analyst evaluations - CCH Tagetik, OneStream, Oracle, Anaplan, SAP - are all capable of handling the core requirements of a large finance function. They differ in architecture, in the commercial model, in where their strengths lie. They do not differ in whether they can produce a consolidated set of accounts or a driver-based budget.
Which means the question has shifted. It is no longer whether the software can do the job. It is whether your instance of it will, once configured against your consolidation rules, your planning logic, your chart of accounts, and the exceptions nobody wrote down.
What actually goes wrong
Enterprise software implementations fail more often than vendor case studies suggest, and the failure modes are consistent.
The documented process is not the whole process
Every finance function has an accounting manual. Every finance function also has rules that never made it into one: an elimination treated differently for one legal entity because of an acquisition years ago, an allocation whose logic three people understand, a quarterly adjustment introduced for reasons nobody can now reconstruct. These surface during configuration, usually late, and each one forces a decision that should have been made during design.
Platform expertise is not accounting expertise
Configuring a consolidation engine requires understanding consolidation - minority interest, currency translation, multi-GAAP parallel reporting - not just the software's interface. A technically correct configuration built on a misunderstanding of the accounting produces a system that runs perfectly and gives the wrong answer.
Scope was set by ambition rather than sequence
Planning, consolidation, disclosure, regulatory reporting and ESG delivered simultaneously, in one programme, with one go-live. It is the pattern that most reliably produces a project that is late, over budget, and adopted by nobody.
Adoption was assumed rather than planned
Controllers who have maintained their own models for a decade do not abandon them because a new system exists. They abandon them when they trust the new numbers — which requires parallel running, training, and enough support during the first cycles that the system proves itself.
None of these are software problems. All of them are things an experienced partner anticipates.
Five questions worth asking
The evaluation of an implementation partner is rarely as structured as the evaluation of a platform. It could be. A few questions separate partners who deliver from those who configure.
Who exactly will work on this project?
Not the firm's headline credentials - the specific consultants, their certifications, their experience with implementations of comparable complexity. Pitch teams and delivery teams are not always the same people, and it is a fair question to ask directly.
How do you approach process design before configuration?
The answer reveals the methodology. A partner who moves quickly to system design is likely to discover your undocumented rules the expensive way.
What happens when we find something during configuration that changes the design?
Every implementation encounters this. What matters is whether the answer is a change request or a conversation.
How will the first live cycle run?
Parallel running with the existing process is slower and more expensive. It is also the difference between discovering a problem in a test environment and discovering it in a published set of accounts.
What does support look like after go-live?
The period immediately after go-live is when adoption is won or lost. A partner who disengages at go-live has optimised for the wrong milestone.
Certification is a signal, not a guarantee
Software vendors operate tiered partner programmes precisely because implementation quality varies and clients cannot easily assess it. The top tiers typically require a minimum number of certified consultants, a demonstrated track record of complex deployments, and adherence to delivery standards the vendor enforces.
It is an imperfect signal - certification measures capability, not necessarily fit - but it is not a meaningless one. A vendor granting its highest partner tier is putting its own reputation behind that partner's delivery.
In the CCH Tagetik ecosystem, this is the Platinum tier. Inulta, a Romanian-founded consultancy, holds that status as a certified CCH Tagetik implementation partner, with more than 100 certified consultants and over 250 enterprise performance management projects delivered across financial services, manufacturing, automotive and energy.
About Inulta
Inulta's client list includes Philip Morris International, Danone, Nissan, Renault and Raiffeisen Bank, with projects delivered alongside Big 4 firms including PwC and EY. In May 2026, CCH Tagetik named the company Best EPM Implementation Partner at its global InTouch26 conference - a recognition awarded on delivery quality across the vendor's international partner network.
For finance leaders selecting a partner, the practical implication is that the shortlist should be wider than it often is. The assumption that complex finance transformation requires a global consultancy is worth testing against what specialist firms can demonstrate.
Inulta is a CCH® Tagetik Platinum Implementation Partner specialising in finance transformation. More information about its implementation approach is available at inulta.com.
Comentează