'Infinitely customizable' is a bill, not a feature
Endless configurability sounds like power. It is a transfer of work, from the vendor's product team to your staff, and the research on choice is brutal. When a study offered shoppers 24 options instead of 6, purchases collapsed. Software that ships as a blank canvas ships an adoption problem with it.

"Fully customizable" is one of the most effective phrases in enterprise software sales. For most buyers it is also a warning label in disguise.
More options, fewer decisions
The research on choice is unusually clean. In a famous field experiment, shoppers offered a display of 24 jams were far less likely to buy than shoppers offered just 6. Thirty percent of shoppers who saw the 6-jam display made a purchase, compared with only 3% of those who saw the 24-jam display, even though the larger display drew more foot traffic, about 60% of passersby stopped versus 40% at the smaller one (Iyengar & Lepper, Journal of Personality and Social Psychology, 2000). More choice pulled people in. It also stopped them from deciding.
The principle behind this, formalized as Hick's Law, is that the time and difficulty of a decision rise with the number and complexity of the options in front of you. Later research has qualified the original finding: a 2010 meta-analysis found that choice overload depends on how hard the decision is, how sure people are of their own preferences, and how complex the options look (Journal of Consumer Research). That qualification matters more for a treatment center than it does for a jam aisle. Admissions decisions and clinical workflow decisions are exactly the kind of high-stakes, high-ambiguity choices where overload is worst. A prospective family choosing a program, or an admissions coordinator choosing which of a dozen intake paths to follow, is not comparison shopping. They need a small number of clear pathways, not a catalog of every possible combination of level of care, schedule, and payment arrangement.
Most users never change a default at all, which is why good products lead with sensible defaults and hide complexity behind progressive disclosure (Nielsen Norman Group). A platform that instead hands you a blank canvas is betting that your staff will do the design work the vendor chose not to do.
Configurability is a transfer of work
When a platform ships as a blank canvas, "flexible" really means "unfinished on arrival." The configuration that should have happened in the vendor's product studio gets handed to you instead: months of setup, a consultant's invoice, and a system only two or three people at your facility fully understand. General-purpose enterprise customer-relationship platforms, built for any industry and then bent toward behavioral health, are the clearest example. They are powerful and genuinely capable, and they routinely require significant implementation investment before they do anything useful for a treatment center's admissions or utilization review workflow. You buy potential and then pay, in staff hours and outside help, to assemble it into something that works on a Monday morning.
Your staff doesn't have the slack to absorb it
This would be a manageable tradeoff if behavioral health had spare clinical and administrative capacity lying around. It does not. As of December 2025, 137 million Americans, 40% of the U.S. population, lived in a designated Mental Health Professional Shortage Area (HRSA). In 2024, about 62 million U.S. adults, 23% of adults, had a mental illness, and 48% of those adults received no treatment at all (SAMHSA data cited by HRSA).
Set against that backdrop, every hour a clinician or admissions coordinator spends building custom fields, maintaining templates, or working around a system that was never finished is an hour not spent getting someone into care. The real cost of "infinitely customizable" software is implementation hours, training time, governance meetings, template maintenance, data cleanup, exception handling, and the opportunity cost of pulling scarce staff off patient access to do product design instead. The license fee is the smallest number on the invoice.
Regulatory complexity is rising, which makes standardization more valuable, not less
Telehealth and payer rules for behavioral health keep shifting, and each shift is another reason to build one repeatable workflow rather than let every site or department invent its own. CMS delayed the in-person visit requirement for behavioral health telehealth furnished by rural health clinics and federally qualified health centers to patients at home until January 1, 2026 (CMS), and later confirmed that Medicare beneficiaries in both rural and urban areas can receive behavioral health telehealth at home, with payment permanently set at the nonfacility rate (CMS; APA Services). CMS's 2026 changes also simplified how services get added to the Medicare telehealth list and moved more services toward permanent status (APA Services).
On the payer side, CMS added clinical psychology and clinical social work as Medicare Advantage network-adequacy specialty types starting January 1, 2024, and added outpatient behavioral health as a facility-specialty type in the 2025 rule, while also letting plans earn a 10-percentage-point credit toward network standards for contracting with telehealth providers (Kearny Street). The 2024 federal parity rule, with core provisions applying to plan years beginning in 2025, raises the evidentiary bar on plans to show real parity between behavioral health and medical benefits.
None of this is optional reading for an operations leader. Eligibility checks, consent, licensure verification, place-of-service coding, and payer-specific billing rules need to be built into a repeatable procedure once, not rebuilt by every clinician or every site every time a rule changes. A configurable platform is only as good as the staff and governance you have available to keep it current, and that staff is already stretched thin.
Opinionated beats infinite
A rigid product with no flexibility is not the alternative here, and neither is a blank canvas. What works is an opinionated system: one that ships a working default for the behavioral health workflow and lets you tailor the things that genuinely vary, such as roles, bed configuration, rates, and preferred referral providers, without a configuration project standing between you and value.
In practice that looks like a short list of operating habits:
- Standardize the core. One approved intake sequence, one level-of-care assessment workflow, one authorization checklist, one referral handoff, one revenue-cycle escalation path.
- Offer bounded choices. Present admissions staff and families with a few clinically appropriate pathways, not a catalog of every combination.
- Separate policy from preference. Make regulatory, clinical-safety, documentation, and billing rules non-configurable wherever possible. Allow local variation only where there is a documented reason.
- Give every configuration an owner. Each custom field, rule, form, and report should have a named owner, a review date, and retirement criteria, or it becomes permanent clutter.
- Measure completion, not customization. Track inquiry-to-assessment conversion, authorization turnaround, clean-claim rate, and staff training time, not how many settings your team has touched.
If a platform can do anything, it does nothing until someone spends three months telling it what to be. "Infinitely customizable" is a bill, not a feature, and in a field this short-staffed, it is a bill your clinical team ends up paying.
Keep reading
The best software is the one your staff actually opens
A feature list is worthless if the team quietly goes back to the whiteboard. In behavioral health, adoption is a design decision the vendor already made before you bought it, not something a training session or a stricter policy can fix after the fact.
Change is hard. So is the slow bleed of a tool your team won't use.
Switching systems is a real project, and "it's too hard to change" keeps a lot of operators on software everyone quietly hates. But staying is a decision too, and it has a price you are already paying in labor, denied claims, and turnover.
Software is a partnership. It should not cost a C-suite salary every year.
The software line item looks like an executive's salary, and it climbs every renewal as features you thought you bought get unbundled. A good partner grows with you and shows its pricing. A lock-in sends an invoice and dares you to leave.
Is your software working, or are you just a hostage to a contract?
Plenty of operators know their software is not working and stay anyway, because the migration and the exit fees feel scarier than the daily pain. Before you accept that fear as a fixed cost, measure it: track intake, authorization, revenue leakage, and staff hours, then compare that number to what leaving would actually cost.
Behavioral Health Updates is an independent industry publication published by vProGo.



