The demo is designed to go well.
- Best for
- Owners holding vendor quotes with nobody in-house to judge them
- Independence
- Preferred partners named up front, on the page, before you decide
- Often ends in
- Do not buy this year — and that is a real answer
- What it costs
- Free discovery, then a fixed fee in writing before you decide
Every demo you have sat through looked good. They are built to. What none of them covered is what the thing costs to run once the implementation team goes home, whether it talks to the EMR you already pay for, and which of your people will actually open it on a Tuesday.
A larger agency hands that question to a CTO. You do not have one.
What an evaluation covers
- The real cost of ownership — licence, implementation, training time, and the staff hours it quietly consumes every month
- Whether it integrates with what you run today, verified rather than promised
- What happens to your data if you leave, and how hard leaving actually is
- Adoption risk — who has to change how they work, and whether they will
- The questions to ask that a vendor is not expecting, and what a good answer sounds like
Where I sit on vendors
I have preferred partners. I did not get them from a vendor dinner — I got them by evaluating and working with several and keeping the ones that held up. You should know that before you weigh anything I say, and you can ask me which ones and why.
You always have four real options: work across what you already own, evaluate independently and buy from whoever wins, build a roadmap with no lock-in, or walk the process through with one of my partners while I help you get the best price rather than handing you off.
The most common finding in this work is that you should not buy anything this year. That is a real answer and you get it plainly.
Small agency reality
Enterprise software is priced and scoped for organizations with a project manager to spare. You do not have one, which means the implementation risk is not the software — it is that nobody inside has the hours to land it.
Any recommendation that ignores that is a recommendation to waste your money.
How it runs
Five steps, in this order.
- 01
Start with the problem
Not the product. What were you trying to fix when you started looking?
- 02
Read the demo backwards
What the script skipped is the part that matters.
- 03
Price the second year
Implementation ends. The bill does not.
- 04
Ask your people
Whoever will not open it on a Tuesday decides whether this works.
- 05
Write the finding
Buy, wait, or fix something else first — in writing, with the reasons.
Where you probably are
If one of these is true, this is the right page.
- Four demos all looked good and you cannot tell them apart.
- Nobody has told you what year two costs.
- The reference calls were all arranged by the vendor.
- You bought something last year that nobody uses.
- You cannot tell whether it talks to the EMR you already pay for.
- The pressure to decide is coming from the person selling it.
Where this stops
- Implementation. I help you choose and sequence it; someone else installs it.
- Custom development. Not mine.
What you walk away with
A written evaluation with a recommendation, the reasoning behind it, the total cost of running it, and the questions to ask before you sign. You own it, and you can hand it to a board.
Every engagement. Yours to keep.
Also under AI Roadmap Architect
Free discovery. Then a number.
Tell me what you have been pitched and what problem you were solving when you started looking.
If there is work worth doing you get a written scope and a fixed fee before you decide — not a range, and not an hourly rate that grows.
Book a conversationYou are not in this alone. I see you. I am in this with ya.
Founder & CEO