Choosing a core platform is one of the most consequential decisions a growing company makes, and one of the easiest to get wrong. Vendors are skilled at presenting their products. Buyers are usually busy, under pressure to move quickly, and comparing options that all look capable in a scripted demo.
The result is familiar: a contract signed on the strength of a presentation, followed by an implementation that reveals gaps nobody tested for.
A better selection process is designed to surface the truth early, while you still have leverage and options.
Define the work before you meet the vendors
Start by documenting the real work the system must support. Avoid long feature checklists, which every vendor will answer “yes” to. Instead, write ten to fifteen scenarios drawn from your actual operations:
- a routine transaction from start to finish;
- the three or four exceptions your team handles most often;
- a month-end or reporting process;
- an audit or compliance request;
- something that went wrong last year, and how the team recovered.
These scenarios become the backbone of the evaluation.
Make vendors show, with your data
Ask shortlisted vendors to run your scenarios in their system, using a sample of your own anonymized data. Watch how they handle the exceptions, not just the happy path. Note how much configuration or custom work each scenario requires, and who would need to do it.
Include the people who will use the system every day in these sessions. Front-line staff notice things leaders miss, and their involvement builds early confidence in whichever option is chosen.
Check what the sales process will not tell you
Before deciding, spend time on the questions that rarely come up in a demo:
- Reference calls with similar companies. Ask specifically about implementation timelines, support quality and what they would do differently.
- The implementation team. Who will actually do the work, and how experienced are they?
- The roadmap and its track record. What has the vendor promised in the past, and what did they deliver?
- Data and exit terms. How do you get your data out, in what format, and at what cost?
- Pricing at scale. What does the contract cost at two and five times your current volume?
Score, decide and write it down
Score each option against the scenarios and the questions above, using weights the leadership team has agreed in advance. Agreeing the weights before seeing the results keeps the decision honest.
Then record the decision in a short memo: the options, the scores, the risks you accepted and the conditions you negotiated to manage them. That memo becomes the reference point for the implementation team, and a useful check if the project starts to drift from what was promised.
A disciplined selection takes a few weeks longer than a quick one. It routinely saves months during implementation, and it gives the people who will live with the system a reason to believe in it.