The Demo Was Impressive. The Practice Feels the Same.
An owner sits through a demo, and it’s genuinely impressive. Dashboards, automations, integrations, a rep who knows the pain points cold. The owner signs, the thing gets installed, the team gets trained. Six months later the practice runs about the way it always did, there’s a new monthly charge on the books, and the tool has settled into that graveyard every practice keeps: software paid for and barely used, bought because it was impressive and abandoned because impressive was never the question.
The graveyard isn’t a buyer competence problem. It’s a filter problem. A demo is built to look impressive, and impressive and useful are different tests that happen to look alike in a conference room. Here’s a filter that tells them apart before the contract, built from the questions that actually predict whether a tool changes anything.
Question One: What Behavior Does This Change on Monday?
Not what it displays. What people do differently. A dashboard that shows denials more beautifully changes nobody’s Monday if the denials still get worked the same way in the same order by the same overwhelmed person. The tools that earn their keep close a loop: they change what happens, where a mirror only changes what’s visible. If the honest answer to “what will someone do differently” is “look at a nicer screen,” the tool is a mirror, and mirrors don’t move numbers. Process intelligence is the difference between seeing the process and changing it.
Question Two: Does It Remove Work, or Relocate It?
Real improvement deletes steps. A lot of practice software moves the work somewhere else and calls it progress: now someone maintains the tool, reconciles what it exports, handles the exceptions it kicks out, and the total human hours are flat or up. Ask where the eliminated work went. If it moved to a new screen instead of disappearing, you bought relocation, and relocation shows up on no report as the cost it actually is. The standard worth holding is 80% of the repeatable work gone, with people on the exceptions, not a fresh queue to babysit.
Question Three: Who Owns the Number It’s Supposed to Move?
Every tool is bought to move something: denials down, collections up, days in A/R lower. Name the number before you buy, name the person who owns it, and put a date on where it should be. Tools bought against a named number with a named owner get used, because someone’s accountable for the outcome. Tools bought against a vague hope of improvement get installed and forgotten, because nobody was ever on the hook for whether they worked. This is also the cheapest way to hold a vendor honest: agree on the number first, and the demo has to earn it.
Question Four: What Does It Cost After the Discount Ends?
The real price isn’t the subscription. It’s the subscription plus the setup, the training, the person-hours to run it, the integration work, and the switching cost when you want to leave, minus the introductory rate that expires in year two. Most tools are sold on the first number and lived with on the full one. Run the full one before signing, over three years, and a surprising share of impressive tools stop being worth it the moment the discount lapses.
Run the Filter on What You Already Own
Before the next demo, point these four questions at the software already on your books. Most practices find one line item that fails all four, still charging monthly, changing nothing, owned by no one. That’s the exercise working: the filter is as good at retiring dead weight as it is at screening new buys, and canceling one dead tool often pays for a year of a live one.
Where to Start
List your practice software, run the four questions down the list, and flag anything that fails more than two. Then grab 30 minutes with us. Prep nothing. We’ll walk the filter against real operations with you, and you’ll see the gap between software that demos well and software that changes what Monday looks like.