Prospa Billing — Implementation Playbook (DSO)

Executive Summary

Prospa Billing is a cloud-based revenue-cycle management platform designed to automate billing workflows, reduce Days Sales Outstanding (DSO), and accelerate cash collection across multi-location dental practices. It integrates with existing practice management systems (PMS), automatically generates insurance claims, manages patient statements, and provides real-time revenue visibility through centralized dashboards.

DSOs benefit uniquely from Prospa because they operate across decentralized locations with inconsistent billing protocols. Prospa creates standardized revenue processes at scale, enabling corporate billing teams to enforce compliance, reduce billing errors by 40-60%, and compress DSO metrics across the entire portfolio. For DSOs managing 10-100+ practices, this translates directly to improved cash flow and enterprise valuation.

Expected Timeline: 12-16 weeks from contract signature to full network deployment (assuming 20-50 locations).

Pre-Implementation Checklist (Weeks 1-2)

Technical Requirements

• PMS Integration Audit: Confirm Prospa supports your primary PMS (Dentrix, Eaglesoft, Open Dental, Softdent). Request system compatibility reports for legacy versions.
• Network Infrastructure: Verify bandwidth capacity at each location (minimum 10 Mbps; 50+ Mbps recommended for high-volume claims submission).
• Data Migration Readiness: Export sample patient and claim data from 2-3 pilot locations to identify data quality issues early (missing insurance details, duplicate patient records, incomplete EOB history).
• User Licensing Model: Confirm you have adequate concurrent user licenses. DSO model typically requires: 1-2 dedicated billing staff per location + 2-3 centralized revenue analysts.
• Single Sign-On (SSO): If required by corporate policy, request setup of SAML/Active Directory integration before pilot launch.

Stakeholder Alignment

• Clinical Leadership Buy-In: Schedule 30-minute calls with each pilot location's dentist/practice manager to explain that Prospa reduces administrative burden (not increases it) by automating claim submission. Address resistance early.
• Billing Staff Interviews: Conduct 1:1 interviews with existing billing staff at pilot locations to understand current workflows, pain points, and concerns about automation. Position them as future RCM analysts, not as redundant.
• Finance/CFO Alignment: Secure commitment to DSO-wide DSO reduction target (e.g., "reduce DSO from 48 days to 35 days within 12 months"). Tie implementation budget to this outcome.
• IT Stakeholder Mapping: Identify primary IT contact at each location and designate a central IT champion at DSO level for escalations.

Baseline Metrics to Capture

Before any implementation work begins, establish a pre-implementation baseline:

Capture these from your PMS reporting and accounting system. This baseline is non-negotiable for ROI validation.

Pilot Wave (Weeks 3-6)

Location Selection Criteria

Select 2-4 pilot locations based on:

1. Billing Volume: Pick high-volume practices (10+ claims/day) so results are statistically meaningful.
2. Motivation: Prioritize practices with engaged managers or urgent DSO problems—avoid locations with apathetic leadership.
3. Data Quality: Select locations with cleaner data entry patterns (fewer missing insurance fields, lower duplicate patient rates).
4. PMS Diversity: If your DSO uses multiple PMS platforms, include at least one location on each major system to validate integration.
5. Geographic Clustering: Choose 1-2 locations close to your billing operations center (if you have one) for frequent in-person support.

Avoid: Selecting your smallest, lowest-complexity locations. You need meaningful volume to validate ROI.

Configuration and Setup

Week 3: Discovery & Configuration

• Conduct 2-hour configuration workshop with Prospa solutions architect and pilot location managers.
• Map current claim submission workflows (e.g., "claims submitted Tuesday/Thursday" → move to daily automated submission).
• Define insurance verification triggers (auto-verify 10 days before appointment; escalate unverified to staff).
• Set patient statement rules (send 14 days after claim adjudication; resend at 45/60 days).
• Configure claim scrubbing rules (deny reasons, auto-resubmission logic).

Week 4: Data Migration & Testing

• Migrate patient demographics, insurance, claim history from pilot locations' PMS.
• Run 100+ test claims through Prospa in sandbox mode. Verify claim formatting matches each insurance carrier's EDI requirements.
• Audit for data anomalies: missing NPI numbers, invalid date-of-births, mismatched provider credentials.
• Correct data issues before going live (don't push bad data into production).

Week 5: Go-Live Prep

• Schedule 2-3 hour on-site training session at each pilot location for:
  • Front desk (insurance verification workflow changes)
  • Billing staff (exception handling, dashboard navigation)
  • Clinical staff (if they touch claim forms)
• Distribute 1-page quick-reference guides (what changed, who to call for support).
• Establish daily standup calls (15 min) between Prospa CSM and pilot billing staff for first 2 weeks post-launch.

Week 6: Go-Live + Monitoring

• Go live on a Monday (avoid Fridays for support chaos).
• Monitor claim submission volumes, error rates, and carrier acceptance rates hourly for first 3 days.
• Create Slack channel for pilot locations to post questions/blockers in real-time.
• Track: # of claims processed, # of errors, # of manual interventions required, staff time spent troubleshooting.

Scaled Rollout (Weeks 7-16)

Wave Planning

Wave 2 (Weeks 7-10): Deploy to 5-10 locations. Use pilot learnings to refine configuration templates.

Wave 3 (Weeks 11-13): Deploy to 10-20 locations. Increase speed by using pre-built configuration templates from Waves 1-2.

Wave 4 (Weeks 14-16): Deploy remaining locations. Target 5-10 locations/week once you have standardized playbook.

Stagger go-lives by 3-5 days to prevent support overload. Don't deploy all locations in a single week.

Change Management

• Assign DSO-Level Billing Lead: One person owns Prospa rollout accountability across all locations.
• Location Champions Program: Identify power-user at each location who becomes internal expert; compensate them (bonus, title change) to create buy-in.
• Monthly Town Halls: Host 30-minute all-hands webinar for all billing staff. Share wins (e.g., "Practice A reduced DSO by 8 days"), answer questions, celebrate early adopters.
• Resistance Handling: If a location's practice manager resists, arrange call between Prospa CSM, DSO leadership, and local PM to address concerns directly. Common objection: "This will cost us staff hours." Counter: Show pilot data proving hours decrease after 6-week ramp.

Support Infrastructure

• Tier 1 (Location Level): Each practice has 1 designated Prospa power-user who first-responders to questions.
• Tier 2 (DSO Billing Team): 1-2 dedicated analysts at DSO HQ manage cross-location issues, exception escalations, and weekly performance reviews.
• Tier 3 (Prospa Support): Your dedicated Prospa CSM handles PMS integration issues, carrier connectivity problems, and feature requests.
• Knowledge Base: Create internal Confluence/wiki with: FAQ, workflow diagrams, screenshot guides, video tutorials (2-3 min each). Update weekly based on support tickets.

ROI Tracking

Key Metrics to Measure

| Metric