Scenarios, not slideshows
Vendors are asked to run your transactions. Demos that avoid the hard path are scored as avoidance.
Choose
System Selection
We do not sell software. Selection is a comparison against your scenarios — the close, the order, the project, the clinic, the store — not against a feature matrix the vendors wrote. The output is a decision record your board can revisit in two years and still understand.
What changes
Total cost, said plainly
Licenses, integration, data, change, and the internal team. The cheap license is rarely the cheap program.
A decision you can defend
Criteria, weights, dissent, and the conditions under which you would reopen the choice.
Method
How the engagement runs
- 01
Criteria from the operation
Weighted with the people who will live with the choice, not only the steering committee.
- 02
Longlist to shortlist
A disciplined cut. Three vendors is a conversation. Seven is a delay.
- 03
Scripted scenarios
The same hard paths, the same data shape, the same questions for each finalist.
- 04
Decision record
Recommendation, commercial shape, and the risks we are accepting on purpose.
What you receive
- Weighted criteria
- Scenario scripts
- Scoring book
- Commercial comparison
- Decision record
When to call
- You are choosing a first ERP or replacing one that the business has outgrown.
- A vendor is already favored and you want the choice tested before it hardens.
- Procurement needs a record that will survive an audit.
Related work
Vesper Goods
A multi-banner retailer chose an ERP against its own peak week, not against a feature checklist.
Read the engagementOther practices
Consultation
Bring us the number that is wrong.
A partner will spend forty-five minutes on it. If we are not the right firm, we will say so before anyone writes a proposal.