Adoption after 90 days
The share of intended users actively using the tool is the best test of whether the choice was right.
Protect margin
Technology vendor selection based on your workflows, not the demo
Buying software looks simple until you have done it a few times. The demo is polished, the salesperson promises it does everything, and the contract is signed before anyone checks whether it handles your actual workflow, connects to QuickBooks Online or exports your data if you leave. Six months later, half the team still uses the old spreadsheet.
Signs you need this
- You are about to replace a core system like your CRM, practice or field service software.
- Past software purchases were barely adopted or quietly abandoned.
- Several vendors are pitching you and their claims are hard to compare.
- Nobody has checked how your data would move to a new system or out of it.
- Renewal notices arrive and you are unsure whether to stay or switch.
A structured selection process starts with the problem and the people who will use the tool, not the vendor list. It turns your needs into written requirements, scores a short list against them, tests with your own data and real users, and checks the contract before signing. It takes a few weeks longer than buying from the first good demo, and it usually saves far more than that later.
How it works
Define the problem and users
Write down what is not working, who is affected and what success would look like in numbers. Include the people who will use the tool daily, such as dispatchers, paralegals or bookkeepers, not just managers.
Write requirements and a scorecard
List must-haves, nice-to-haves and deal-breakers: workflows, integrations, security, data export, support, total cost. Weight them before talking to vendors so the demo does not set the agenda.
Shortlist and run scripted demos
Pick three or four vendors. Give each the same scenarios from your business and ask them to show those, not their standard tour. Score each against the same sheet.
Test with real data and users
Run a trial or sandbox with a sample of your data and two or three staff doing real tasks. Call references from businesses of a similar size and type.
Check the contract and plan the move
Review term length, renewal and price increase terms, data ownership, export rights, security commitments and support levels. Plan data migration, training and the cutover date before signing.
Ways to do it
| Approach | Best fit | Notes |
|---|---|---|
| Stay and reconfigure | When the current tool is underused rather than unsuitable. | Often the best answer. A review of settings, training and integrations in the system you own can fix the problem without migration costs or disruption. |
| Run the process internally | Firms with an organized operations lead and time to manage it. | Use a written scorecard, scripted demos and a trial. The main risk is that the loudest voice or the best salesperson wins anyway. |
| Independent adviser or fractional technology lead | Larger or riskier decisions, such as replacing a core system. | A vendor-neutral adviser runs the process, asks the technical questions and checks contracts. Ask whether they receive referral fees from any vendor. |
| Reseller or implementation partner | When you have already chosen a platform and need help setting it up. | Useful for implementation. Their recommendations will naturally favor the products they sell and support. |
How we deliver this: AI automation for small business or fractional CTO leadership, scoped in writing and run over 90 days. See pricing or the sample scope.
What we would measure
Total cost of ownership
Include licenses, implementation, integrations, training and staff time, not just the subscription price.
The workflow measure that justified the purchase
If you bought it to speed up invoicing or scheduling, measure that against your baseline.
Tools retired as a result
A good purchase often replaces one or more older tools. Track the savings.
Risks and how we handle them
| Risk | Mitigation |
|---|---|
| Choosing on demo polish rather than fit. | Use scripted demos built from your own scenarios and score every vendor on the same weighted sheet. |
| Lock-in through long contracts or hard data export. | Confirm export formats, data ownership, termination terms and price caps in writing before signing. |
| Poor adoption after purchase. | Involve daily users in the trial, budget time for training and name an internal owner for the rollout. |
When not to do this
Do not run a full selection process for a low-cost tool used by one or two people. Try it on a monthly plan and cancel if it does not help. And do not start a search just because a contract is renewing. Often the honest answer is to stay, fix the configuration and negotiate the renewal. Switching core systems is disruptive and should solve a real, measured problem.
Common questions
How long should software selection take?
For a core system such as a CRM, practice management or field service platform, four to eight weeks is common: two to define needs, two to three for demos and trials, and one or two for references and contract review. Smaller tools can be decided much faster.
What questions should we ask vendors?
Ask them to show your specific scenarios, how data gets in and out, which integrations are native, what support looks like, how prices change at renewal, what security certifications they hold and how other businesses your size use it. Ask for references you can call directly.
Should we buy an all-in-one platform or best-of-breed tools?
It depends on how well each option fits your core workflow and how much integration work you can support. All-in-one platforms reduce connections but may be weak in some areas. Separate tools can fit better but need integrations to keep data consistent. Score both against your requirements.
How do we handle data migration?
Plan it before signing. Find out which records can be imported, in what format, and who does the work. Clean the data first, test a sample import and decide what history you really need to move. Migration is often where projects run late.
Is a fractional technology lead useful for this?
For larger decisions, often yes. A vendor-neutral lead writes requirements, runs demos, asks the technical and security questions and checks contract terms, then helps plan rollout. The value is clearest when replacing a system your whole business depends on.
By industry
Technology vendor selection for your industry
Guides
How to hire an AI consultantHow to hire a fractional CTOIs a fractional CTO worth it for a small business?Questions to ask a fractional CTOHow much does a fractional CTO cost?AI consultant red flags
Questions
How much does a fractional CIO cost?vCIO vs CIO?How much does an AI consultant cost?Should I build or buy AI?Copilot vs ChatGPT: which is better for business?
Glossary
Fractional CTOFractional CIOFractional executivevCIOTechnology roadmapSaaS sprawlAcceptance criteriaTotal cost of ownership
Other solutions
KPI and pipeline dashboardsSoftware stack auditDocument intake and data extractionInvoicing and collections follow-upInternal knowledge assistantJob scheduling and dispatchHiring and staff onboardingAI usage policy and governanceSystems integrationContract and document review supportCompliance documentation
Next step
Bring one expensive workflow. Leave with a clear next step.
In 30 minutes we look at one recurring workflow, what it costs you today and whether there is a credible case to improve it. If there is not, we will say so.
Book a 30-minute workflow review
Not ready to talk? Take the 3-minute check
30 minutes with Phil or Martin. No technical brief, no pitch deck. Phil or Martin replies personally, usually within one business day.