No. VProGo is specifically built to work alongside Kipu — not replace it. The bidirectional integration means your clinical team stays in Kipu for documentation, utilization review, and group notes. VProGo handles everything Kipu wasn't designed for: referral lifecycle, payment prediction, billing operations, patient engagement, marketing, and multi-facility dashboards. No EMR migration. No data cleanup. No disruption to clinical workflow.

VProGo connects to Kipu via its native API with bidirectional sync for admissions, demographics, census, level-of-care transitions, insurance policies, utilization reviews, group sessions, and discharges. Setup is handled as part of VProGo onboarding. Clinical notes stay in Kipu and are never copied out — only the operational data needed to coordinate admissions, billing, and engagement flows between the two platforms.

Kipu does not have payment prediction. The 8-tier confidence-scoring engine in VProGo sits between VOB and admission decisions, trained on millions of historical claims with dynamic weighting across policy match, rate source, data quality, match quality, VOB quality, plan intelligence, industry alignment, and a composite confidence score. No EMR offers anything comparable — because it requires the intersection of real-time VOB data, historical billing outcomes, and operational context that only an integrated operations platform can provide.

Kipu's CRM is designed as a lightweight intake-tracking module, not a business-development platform. VProGo's CRM is purpose-built for behavioral health admissions workflow: multidirectional referral lifecycle (step-up, step-down, transfer, re-refer), working referrals with VOB status and clinical screening in a Kanban admissions view, referral source attribution with gamification, and full BD team management. Most facilities running Kipu end up using spreadsheets or generic CRMs alongside it; VProGo replaces both.

Kipu Billing (via the Avea acquisition) is designed primarily for residential programs. VProGo's full RCM supports the complete admissions-to-collections lifecycle with ClaimMD clearinghouse integration, Waystar in development, and a clearinghouse abstraction layer that lets facilities switch vendors without data loss. VProGo also has a separate VProBilling portal purpose-built for third-party billing companies managing multi-facility portfolios — functionality Kipu does not offer.

Yes. VProGo is deployed as an operations layer on top of Kipu, not a replacement. Your PE-standardized EMR stays in place. The question for portfolio operators is typically: can we layer consistent operations, prediction, billing, and marketing on top of our facilities without disturbing the clinical stack? VProGo is specifically designed for that architecture. Multi-facility dashboards, portfolio-level benchmarking via VProSEO, and consolidated revenue reporting all work across Kipu-native facilities.