A convincing selection explains how a platform will meet your requirements, what achieving that fit involves and whether your organisation can operate it.
Two suppliers can answer “yes” to the same requirement and propose very different solutions. One may use standard configuration. Another may need an additional product, custom logic or continuing specialist support.
A requirements spreadsheet can conceal those differences. An effective Enterprise Performance Management (EPM) selection brings them into the open before they become delivery costs or operational dependencies.
The objective is a decision your organisation can explain and implement with confidence.
Start with the business problem
A group struggling with complex consolidation and ownership changes has a different starting point from one trying to connect sales, workforce and financial planning.
Identify the outcomes the investment must support, the controls it must preserve and the weaknesses it should address. Agree which requirements are essential and which are preferences.
Challenge inherited processes too. Replicating every existing spreadsheet may preserve the complexity that prompted the investment.
Build a shortlist around fit
Consider the market against your requirements, architecture and operating model. Explain why candidates are included or excluded.
Whether you are weighing OneStream, Anaplan, Board, Pigment, Workday Adaptive, Oracle or SAP's own stack, the discipline is the same: judge each against your requirements, not its marketing.
The incumbent should be assessed fairly. A familiar platform may be the right choice, but familiarity alone is insufficient evidence. Equally, independence does not require choosing an unfamiliar supplier.
Vendor information, analyst research and partner experience can inform the shortlist. The final decision needs evidence relevant to your organisation.
Test the requirements that matter most
Agree evaluation criteria before demonstrations. Separate mandatory conditions from weighted preferences, and avoid counting the same strength repeatedly under overlapping categories.
Ask suppliers to work through demanding scenarios.
Illustrative exampleA consolidation demonstration could include a late submission, an ownership change, a group adjustment and an investigation back to supporting detail. A planning demonstration could show a finance user changing a business assumption and updating the forecast without developer intervention.
For each important requirement, establish:
- Whether the capability is available today and included in the proposal.
- Whether it requires configuration, an extension or another product.
- Who will implement and maintain it.
- What happens when the business requirement changes.
Record the strength of the evidence alongside the score. A demonstrated capability and an untested assurance should not carry the same confidence.
Assess delivery and ownership
The platform is only part of the commitment. Assess the proposed implementation team, its availability and the demands the programme will place on your own people.
Finance specialists may need to support design, reconcile data, test results and continue their normal responsibilities. A delivery plan that overlooks this effort creates a risk regardless of the software selected.
Look beyond go-live. Establish who will maintain models, change hierarchies, investigate failed interfaces and support users. Understand which changes finance can manage and which require IT or specialist assistance.
Compare costs over a consistent period, including implementation, internal effort, integrations, environments, training, support and likely changes. Examine commercial assumptions that could affect future cost, such as additional modules, usage limits and renewal terms.
Our recommendation
Select the platform and its proposed delivery approach together. A product may meet the requirements while the proposed team, budget or operating model makes the overall proposal unsuitable.
Where two options remain close, investigate the assumptions that separate them. Small differences in a weighted score are a weak basis for commitment when the underlying evidence is uncertain.
Make commercial interests visible, including any opportunity for the adviser to deliver the implementation. The recommendation should explain the preferred option, its compromises and the conditions that must be satisfied before proceeding.
Before you approve an EPM platform
| Question | Evidence to request |
|---|---|
| Does it handle our most demanding requirements? | Demonstrations using your scenarios, including exceptions and adjustments. |
| What does each “yes” involve? | A distinction between configuration, additional products, extensions and custom development. |
| Can the proposed team deliver it? | Relevant experience, named responsibilities, availability and a credible approach. |
| What must our people contribute? | Explicit finance and IT effort for design, data, testing, decisions and adoption. |
| Can we operate and change it afterwards? | A walkthrough of routine administration, business changes and support dependencies. |
| What could change our decision? | Analysis showing how different cost, scope or delivery assumptions affect the preferred option. |
An unanswered question identifies an uncertainty to resolve, price or explicitly accept before commitment.