The most common question IDD agencies ask before committing to a new platform is not about features. It is about implementation. What does the transition actually look like? How long does it take? How much of my team’s time does it require? What happens when something goes wrong?
These are the right questions. Implementation is where software vendor promises meet operational reality, and the experience agencies have during that period shapes how they feel about the platform for years afterward. Here is what Vertex customers consistently describe when they talk about implementation, in their own terms.
The Discovery Process Is More Thorough Than They Expected
Agencies that have been through implementations with other vendors often arrive at Vertex expecting a standard onboarding: pick a start date, get some login credentials, attend a few training webinars. What they find instead is a structured discovery process that asks detailed questions about how their agency actually operates before anything is configured.
What payers do you bill? How are authorizations managed across your waiver programs? How do you track credentials for your DSP workforce? What documentation workflows does your clinical team use? What does your production floor scheduling look like?
These questions are not standard intake forms. They are the foundation for configuring a platform that fits the agency’s actual operations rather than requiring the agency to adapt to a generic setup. Customers who have been through this process consistently describe it as more thorough than expected, and more valuable because of it.
Lark Enterprises, a Pennsylvania organization that operates both supported employment and production programs, described the Vertex relationship as one where customization and responsiveness were central from the beginning. When Pennsylvania changed its service definitions in ways that made their existing systems obsolete, the Vertex team went back in and made the necessary adjustments rather than leaving the agency to figure out the compliance change on its own.
Training Is Role-Specific, Not One-Size
One of the most consistent implementation frustrations agencies describe with other platforms is training that covers everything in a general way and prepares no one for their specific role. A billing coordinator who sat through a three-hour webinar covering case management, scheduling, EVV, and payroll alongside billing comes out knowing a little about everything and not enough about what they need to do their job.
Vertex’s implementation approach trains staff for their specific workflows. Billing coordinators learn the billing module with the authorizations, payer configurations, and billing codes specific to their agency. Case managers learn case management documentation in the context of their actual client population and service types. Program supervisors learn scheduling and time tracking for the way their programs actually run.
This role-specificity reduces the ramp-up time between training and productive use, and it reduces the early post-go-live support burden because staff are not trying to apply general knowledge to specific situations.
The Go-Live Period Has Responsive Support Behind It
The period immediately after go-live is when implementation quality shows up most clearly. Staff are using the system in real conditions for the first time. Scenarios arise that were not covered in training. Configuration choices that seemed right during setup turn out to need adjustment in practice. Questions come up that need answers quickly because billing deadlines do not pause for software transitions.
What Vertex customers describe about this period is that support is responsive and knowledgeable about IDD specifically. Not a generic help desk that routes tickets to a generalist. The Vertex support team understands what a DODD billing code is, what a commensurate wage calculation involves, and what an EVV exception looks like in the context of an Ohio Individual Options waiver claim. That specificity makes support interactions faster and more useful than agencies experienced with general healthcare software.
Diversified Opportunities Incorporated, whose 17-year Vertex relationship produced billing cycle reductions from three hours to under 30 minutes, describes the partnership as one where the Vertex team worked directly through multiple development cycles to build exactly the compliance documentation format their program required. Implementation was not a handoff. It was the beginning of an ongoing collaborative relationship.
Data Migration Is Professionally Managed
The part of implementation that agencies dread most is getting their historical data from the old system into the new one. Client records, billing history, authorization data, staff information: years of organizational knowledge that cannot be lost in a platform transition.
What Vertex customers describe is a migration process that is professionally managed rather than left to the agency to figure out. Vertex Billing Import handles billing data migration specifically, with the Vertex team managing extraction, mapping, and validation rather than requiring agency billing staff to become data migration experts alongside their day jobs.
This does not mean migration is effortless. Agencies that have the smoothest migrations are the ones that engage seriously in the data quality review process before go-live, identifying and cleaning up inconsistencies in their historical data before they get carried into the new system. But the professional management of the migration itself means the risk of data loss or corruption is substantially lower than in self-managed transitions.
The Relationship Continues After Implementation
What distinguishes the Vertex customer experience most clearly from the typical software vendor relationship is that implementation is not a handoff. Customers who have been on the platform for years describe a relationship with the Vertex team that includes proactive communication about compliance changes affecting their state, responsiveness to configuration needs as their programs evolve, and development work that addresses IDD-specific requirements as the regulatory environment changes.
Johnson County Industries, a nonprofit in North Carolina that has worked with Vertex since 1990, expanded its Vertex ecosystem from financial and payroll management to include production management as the organization grew. That kind of long-term platform evolution is only possible in a vendor relationship where the implementation was the beginning of the partnership rather than the conclusion of the sales process.
Connect with the Vertex Systems team to talk about what implementation looks like for an agency at your size and what the first 90 days typically involve for organizations with your program mix.
