Choose business software by starting with your own work, not the vendor's demo. Map how the work really happens, separate real requirements from habits, and make every finalist demonstrate your scenarios with your data. Check how data gets in and out, talk to references your size, and plan the migration and training before you sign. And make sure whoever is advising you isn't paid by the vendor.
Most small and mid-sized businesses buy an ERP or a CRM about once a decade. The vendors sell them every day. That's not a criticism of vendors. It's just an uneven match, and the process below is how you even it out.
Do you have a software problem, or a spreadsheet problem?
Before you buy software, look for the old spreadsheet.
Almost every business has one: the workbook that really runs scheduling, the export someone cleans up every Monday, the list that only lives in one person's inbox. When a team says "our system can't do this," the spreadsheet is usually where the real process lives, and it tells you more about your requirements than any feature list.
A lot of software problems turn out to be a data and process problem wearing a software problem's clothes. If customer records are inconsistent, a new CRM inherits the inconsistency. If nobody agrees on what counts as a "booked" order, a new ERP will report three different numbers just like the old one. Sometimes the fix is a cleaned-up process and a modest tool, not a new platform. Our post on replacing an Access database covers that case, when the "system" is really a database or spreadsheet someone built years ago.
Is it a requirement or a habit?
Ask that of every line on your wish list.
"We need to print the pick list in this exact layout" might be a requirement, because a customer or an auditor depends on it. Or it might be a habit from 2009. Habits aren't bad. But vendors will happily quote you custom work to reproduce them, and you'll pay to maintain that custom work for years.
The people who do the work are the right ones to answer this, not the person who wrote the original process document. Ask them why each step exists. You'll find some steps exist only to work around a limit in the current system.
What does a good software selection process look like?
Six steps, in this order:
- Map the work as it really happens. Walk through it with the people who do it. Quote to cash, order to ship, intake to close. Note every handoff, every spreadsheet and every place someone retypes something.
- Separate must-haves from habits. Keep the list short. A real must-have is something the business can't run without, or something a customer, regulator or auditor requires.
- Demo with your own data and scenarios, not the vendor's script. Give each finalist three or four real scenarios, including an awkward one, and a sample of your actual data. A scripted demo shows you the product at its best. Yours shows you the product doing your job.
- Check how data gets in and out. Ask about APIs, standard exports and existing connectors to the systems you're keeping. Ask how you'd get all of your data back if you left. If the answer is vague, treat that as the answer.
- Talk to references your size. A fifty-person company's experience is more useful to you than a case study from a global brand. Ask what took longer than promised and what they still do outside the system.
- Plan the migration and training before you sign. Who moves the data, how much history comes over, who trains your people and when. These costs are real, and they're easier to negotiate before the contract than after.
How do you compare finalists side by side?
A scorecard keeps the decision about your work instead of the best presentation. Score each finalist on the same criteria after the scripted-scenario demos.
| Criterion | What good looks like | Red flag |
|---|---|---|
| Fit to your real workflows | Handles your scenarios with configuration, not custom code | "We'd build that for you" on a core process |
| Your-data demo | Ran your scenarios with your sample data | Only shows its own demo environment |
| Data in and out | Documented API, full exports, connectors to systems you're keeping | Exports cost extra or come in an unusable format |
| Total cost | Licenses, implementation, add-ons and per-user growth in writing | Key features in a higher tier you learn about later |
| Implementation | Named team, clear plan, realistic timeline | Plan arrives only after you sign |
| References | Customers your size and industry, reachable directly | Only enterprise logos, or references they coach |
| Training and adoption | A plan for your people, not just a video library | "Users usually figure it out" |
Weight the rows to fit your business. For most of the companies we work with in Cedar Rapids and Iowa City, data in and out matters more than anything a sales deck will lead with.
What does an independent software selection consultant actually do?
An independent software selection consultant helps you choose an ERP, CRM or other core system without any financial stake in which product wins. The work starts before any vendor is involved: mapping how your business really runs, finding the spreadsheets and workarounds that hold the real requirements, and separating must-haves from habits. Then the consultant writes demo scenarios built from your actual work, so every finalist is tested the same way, and helps you score them. A good one also reads the contract for costs that show up later, checks how your data gets in and out, talks to references your size and plans the migration and training before you sign. The value is in the questions vendors won't raise and in having someone on your side of the table. The key word is independent: no referral fees, no reseller margin, no preferred-partner tier. Ask every adviser how they're paid.
Why does it matter who's paid by the vendor?
Many people who present themselves as software advisers are also resellers or implementation partners for a product. That can be a perfectly honest business. But referral fees, reseller margins and partner tiers shape a shortlist, even when nobody intends it.
So ask directly: "Do you receive any compensation from any vendor you might recommend?" A good adviser will answer plainly. If the answer is yes, you can still work with them. Just know that you're hearing from a seller, not a referee.
Mosaic is independent of any software vendor. We help businesses evaluate vendors and make technology decisions, and when the right answer is a modest tool plus a cleaner process, we say so. When the right answer is building the connections a new system needs, that's the software and integration work we do.
What happens after you choose?
The selection is half the project. The other half is getting your data in, connecting the new system to the ones you're keeping, and helping people work differently. Plan for that from the first conversation, and the software you choose will have a fair chance to deliver what it promised.
If you're starting a selection, or you've already bought something that isn't working the way you hoped, see how we approach selection, integration and custom builds.