Most of the conversation about IDD software happens before the contract is signed. Demos, proposals, reference calls, budget conversations, board approvals. Once the contract is executed, many agencies enter a period of uncertainty: what happens now? Who do I talk to? When does implementation start? What is my team supposed to be doing?
The transition from prospect to customer is where the vendor relationship either builds trust or starts to erode it. Here is what the post-signature period typically looks like, what you should expect from your vendor, and what your team needs to do to make implementation go smoothly.
Week One: Introductions and Kickoff
Within the first week after signing, you should hear from your implementation team. This introduction establishes who your primary contacts are, confirms the scope of what is being implemented, and typically schedules a formal kickoff meeting within the first two weeks.
The kickoff meeting is your opportunity to align on timeline, communicate your agency’s priorities, and identify any known constraints on your team’s availability. Bring your billing coordinator, your lead case manager, your operations director, and any IT staff to the kickoff. These are the people who will be most directly involved in implementation decisions, and their attendance signals organizational commitment to moving forward.
If your vendor cannot introduce an implementation team within the first week or cannot schedule a kickoff within two weeks, that is an early signal about how the relationship will go. Responsive onboarding reflects organizational capacity and customer prioritization.
The Discovery Phase
Before your system can be configured, the implementation team needs to understand how your agency actually operates. Discovery typically involves structured conversations with your billing team to document your payer mix, billing codes, authorization structures, and state-specific requirements. It also covers case management workflows, service types, documentation standards, and program structure.
This is not the time to describe how you wish things worked. Describe how they actually work. The system will be configured around your real workflows, not an idealized version of them. If your billing process has a workaround you are not proud of, mention it. The implementation team needs to know about it to either replicate it in the new system or help you replace it with a better process.
Discovery also covers data migration. You will be asked about your current system, what data exists in it, and what you want to bring forward. Billing history, client records, authorization data, and employee records are the most common migration priorities. Start pulling an export from your current system early in the discovery phase, because data quality issues discovered late in the process delay go-live.
Configuration
Based on discovery, the implementation team configures the platform to match your environment. This includes setting up your service types, payer configurations, billing codes, state-specific rules, authorization structures, user roles, and any custom workflows your agency requires.
You will be asked to review and approve configuration decisions during this phase. Do not rubber-stamp these reviews. Work through them carefully with your billing coordinator and case management lead. Configuration errors that are not caught before go-live create billing problems that are harder to fix in production than in setup.
For Vertex Billing Manager, configuration includes payer-specific claim formats, authorization tracking rules, error notification settings, and the state-specific billing logic for each payer your agency uses. For Vertex Case Manager, configuration covers service types, goal tracking structures, documentation templates, and compliance reminder timing.
Data Migration
Moving your historical data from your current system to the new platform is one of the most operationally consequential phases of implementation. If it goes well, your team starts using the new system with full access to client history, billing records, and authorization data. If it goes poorly, your team starts go-live without critical historical context, or with corrupted data that creates billing problems from day one.
Vertex Billing Import handles billing data migration professionally. The Vertex team manages the extraction, mapping, and validation process, reducing the risk of data loss and the burden on your internal staff. Your role during migration is primarily data quality review: confirming that the migrated data looks correct and that key records are present and accurate before signaling readiness to go live.
Training
Role-specific training is how your team learns to use the system. Billing coordinators, case managers, DSPs, program supervisors, and administrators each need training relevant to their actual workflows, not a generic overview of the whole platform.
Protect your team’s time for training. Agencies that try to complete training in stolen hours between other responsibilities end up with staff who go live unsure of basic workflows, which creates errors and support tickets. Schedule training as a dedicated activity, hold attendance accountable, and build in time for practice in a test environment before go-live.
For DSPs and field staff using mobile EVV tools, training needs to be hands-on with the actual device and app they will use in the field. A 20-minute walkthrough in a conference room is not sufficient preparation for a DSP who needs to complete an EVV check-in at a client’s home for the first time.
Go-Live and the Stabilization Period
Go-live is not the end of the implementation. It is the beginning of the stabilization period. In the first two to four weeks after going live, your team will encounter scenarios they did not think to test, edge cases that were not covered in training, and operational questions that only arise when the system is in real use.
Your vendor should be available during this period with responsive support. The implementation team should be reachable for issues that arise in the first billing cycle, and there should be clear escalation paths for urgent problems.
Use this period actively. Track every question your team has, every error that surfaces, and every workflow that feels awkward. These are the inputs for a post-implementation review at the 30-day mark, where you and your vendor can assess what is working, what needs adjustment, and what training gaps should be addressed.
What a Smooth Post-Signature Experience Looks Like
The agencies that have the smoothest implementations share a few consistent patterns: they designate an empowered internal lead who can make decisions, they protect staff time for the process, they engage seriously in discovery and configuration review, and they treat go-live as a milestone rather than a finish line.
Vertex Systems provides dedicated implementation support with role-specific training and data migration assistance designed for IDD agencies. Connect with the team to discuss what implementation looks like for your agency’s specific scope and timeline needs.
