.png&w=3840&q=75)
Every few years, finance teams find themselves back in selection mode. Tenders are issued, demonstrations are booked, scorecards come out, and vendors line up to explain why their platform is the answer.
Most of the process focuses on the software. Can it support complex budgeting? Will it integrate with the ERP? Can it handle multiple entities, detailed forecasting and management reporting? How much will it cost?
Those questions matter. But they do not tell you what it will be like to work with the vendor once the selection process is over.
Finance teams do not replace budgeting and forecasting systems for the sake of it. They do it because spreadsheets have become unmanageable, reporting takes too long, planning lacks visibility, or existing systems can no longer support the complexity of the organisation.
The software needs to solve those problems. If it becomes part of your finance operation for the next ten or twenty years, however, there is another question worth asking:
What happens after the contract is signed?
What should you look for in an FP&A software partner?
When choosing an FP&A software partner, look beyond functionality and price. Evaluate the vendor's implementation experience, understanding of finance processes, long-term customer support, retention of customer knowledge, responsiveness to changing requirements and track record with organisations similar to yours.
I lead the Consulting & Projects team at IDU, so I work at the point in the relationship where the sales conversation ends and the real work begins.
After more than two decades of doing this, I have found that the quality of a vendor relationship has very little to do with what appears in the proposal. You see its real value much later, when your business has changed, your business requirements have shifted, and the people involved in the original implementation have moved on.
That is when you discover whether you bought software from a supplier or chose a partner.
What an FP&A Software Tender Can and Cannot Tell You
Procurement processes are designed to compare functionality, pricing, technical fit and compliance. That is necessary, but it is not the whole decision.
An RFP can confirm whether a platform supports multi-entity consolidation or employee-level budgeting. It cannot tell you whether the team behind it will still answer your calls in five years. It cannot show whether they will understand your organisation well enough to help with a problem you have not encountered yet.
That difference may barely register during a polished demonstration. Ten years later, it matters a great deal.
We see this with some of our longest-standing customers.
The University of the Witwatersrand, or Wits, is required by policy to put its major supplier contracts out to tender every five years. IDU's contract is therefore regularly opened to the market and evaluated against competing options.
For sixteen years, the outcome has remained the same.
As Rakhee Maharajh, Divisional Financial Manager at Wits, explains:
"Every five years we have to go out to tender. Up until now, we haven't found another budgeting partner we can actually work with. We always put in a motivation to extend IDU's contract."
This is not a customer that has stayed because it has never considered the alternatives. Wits has formally tested the market several times and repeatedly chosen to continue the relationship.
UNISA tells a similar story from a different perspective. The university implemented IDU in 2005. Willem Du Plessis, then Executive Director of Finance at UNISA, spoke of looking forward to "many more years of partnership with IDU, even after my retirement."
That is not how people usually talk about a software supplier. It is how they talk about a team they have come to rely on.
The same pattern appears outside higher education. Hirt & Carter has used IDU for its budgeting and management information requirements since 2005. Its finance team attributes its ability to deliver timely, effective management reporting not only to the system, but to the relationship behind it.
That distinction matters because software can be replicated.
Relationships cannot.
Why Long-Term Partnership Matters When Choosing FP&A Software
Most finance teams think they are selecting software. In reality, they are also choosing who they will rely on when the business inevitably changes.
Over the life of a financial planning system, organisations restructure, reporting lines change, entities are added, regulations evolve and new leaders arrive with different expectations. The people who understood the original implementation may no longer be there.
A good partner helps the organisation absorb that change without having to start again each time.
They retain knowledge of how the system was configured and why particular decisions were made. They understand the finance processes around the technology. When a new requirement arises, they do not need the entire history explained from the beginning.
That continuity reduces risk, disruption and dependence on individual employees. It is difficult to capture in an RFP score, but it becomes increasingly valuable over the life of the system.
What Does a Good FP&A Software Partnership Look Like?
"Partnership" is used so often in business that it can mean almost anything. In practice, it tends to show up in a few very ordinary but important ways.
You can speak to someone who knows your environment
Not just a ticket number or an anonymous support queue. An actual person who understands your setup and has enough context to get to the problem quickly.
Customers notice the difference. They also notice when each call begins with another explanation of who they are, what they use and how their business works.
The team understands finance, not only the software
A product expert can explain where to click. A consultant who understands finance can help you decide whether the process itself makes sense.
That matters when the obvious configuration is not necessarily the best one, or when a short-term fix may create a bigger problem later. Experience across different finance environments allows a good consultant to challenge an approach, suggest an alternative, or identify a risk before it reaches the reporting cycle.
The knowledge survives changes in people
Over a ten- or twenty-year relationship, people leave, teams change and organisations reorganise themselves.
A strong partner keeps enough institutional knowledge for the relationship to continue without starting from scratch whenever a key person moves on. That takes proper handovers, shared understanding and a team that sees the customer relationship as more than one person's account.
The relationship continues after go-live
Most vendors put enormous effort into getting a customer live. The more revealing test comes afterwards, when the project is no longer receiving executive attention and the system simply needs to keep delivering value.
That work is less visible. It includes resolving support issues, training new users, reviewing changing requirements and adapting the solution as the organisation develops.
It is also where long-term trust is built.
Strong Customer Relationships Improve the Software
A close relationship with customers does more than improve support. It also affects the way the product develops.
In a large software organisation, customer feedback can have a long journey. A request becomes a ticket, enters a backlog and competes with thousands of other priorities.
When consultants know the finance teams they work with, feedback tends to arrive differently. A customer may raise a recurring problem during a support call, mention an awkward process in a workshop, or point out an opportunity while working through a budget.
A surprising amount of functionality in IDU started in exactly that way. A customer phoned, emailed or raised something during a workshop, and someone listened.
Not every request should become a feature, of course. But staying close to customers makes it easier to distinguish between an isolated preference and a problem shared by many finance teams. It keeps product development connected to the realities of the people using the software.
What to Look for in an FP&A Software Vendor
If you want to understand what a vendor relationship will really be like, move beyond the sales presentation.
Ask to speak to customers who have used the platform for more than ten years. Do not ask only whether they are happy with the software. Ask what support has looked like in practice and whether the quality of the relationship has held up over time.
Find out whether customers have named contacts or work through a general queue. Ask what happens when the customer's main consultant leaves the vendor. Does the knowledge transfer cleanly, or does the customer have to rebuild the relationship?
Ask for an example of functionality that was introduced because customers identified a real need. The answer will show how closely feedback and product development are connected.
Most importantly, ask existing customers about the last serious problem they experienced. How quickly did someone respond? Did they have to chase for answers? Did the vendor treat it as a shared problem, or as something for the customer to manage?
The answers may not fit neatly into a scoring matrix. They will tell you a great deal about what happens after go-live.
Key considerations when choosing an FP&A software partner
Before choosing an FP&A software vendor, consider:
- Software capability: Can it support your budgeting, forecasting and reporting requirements?
- Finance expertise: Does the vendor understand finance processes as well as the technology?
- Implementation: Will the team help you configure the system around your organisation?
- Long-term support: Who will you deal with after go-live?
- Continuity: Does the vendor retain knowledge when people change?
- Customer feedback: Does customer experience influence product development?
- Track record: Can the vendor provide references from long-standing customers?
The Cost of Choosing the Wrong Relationship
Changing financial planning software is expensive in ways that do not always appear in the business case.
There is the direct cost of implementation, but also the time spent retraining users, rebuilding processes and reproducing knowledge that existed in the previous system. While that is happening, the finance team is pulled away from the analysis and decision support it is meant to provide.
Organisations do not always replace a system because the technology has failed. Sometimes the relationship around it simply never became valuable enough to keep.
Twenty years after a software purchase, nobody remembers the demonstration that won the RFP.
They remember whether support answered the phone.
They remember whether the vendor understood their business.
They remember whether the relationship became stronger as the organisation grew more complex, or whether they had to explain everything again each time something changed.
Software can be bought.
Partnership has to be earned.
That is the thing worth evaluating before you sign the contract, and the standard every vendor should be expected to meet in the years that follow.
Frequently Asked Questions About Choosing an FP&A Software Partner
What should you look for when choosing FP&A software?
When choosing FP&A software, consider more than functionality and price. Evaluate how well the system supports your budgeting, forecasting and reporting requirements, how it integrates with your existing environment, and the quality of implementation, consulting and ongoing customer support.
What is the difference between an FP&A software vendor and an FP&A partner?
An FP&A software vendor primarily provides the technology. An FP&A partner provides technology alongside implementation expertise, finance knowledge, ongoing support and an understanding of the organisation's changing requirements.
Why is long-term support important when choosing FP&A software?
FP&A systems often remain part of an organisation's finance processes for many years. Organisations change during that time, with new reporting requirements, structures, users and processes. A long-term support relationship helps the organisation adapt the system without having to start again.
What questions should you ask an FP&A software vendor before buying?
Ask about implementation, ongoing support, named contacts, consultant expertise, knowledge transfer, product development and how customer feedback influences the software. It is also useful to speak to long-standing customers about their experience after implementation.
How important is implementation when choosing budgeting and forecasting software?
Implementation is important because the quality of the initial configuration, processes and knowledge transfer can affect how effectively the organisation uses the system. The relationship with the vendor also needs to continue after go-live as requirements and users change.
Should you speak to existing customers before choosing FP&A software?
Yes. Customer references can provide information that is difficult to assess during a sales demonstration, including the quality of support, responsiveness, continuity of knowledge and how the vendor handles problems after implementation.