Sunwave Health merged with Lightning Step under common BVP Forge ownership in October 2025. The combined entity now spans roughly 3,000 facilities across two distinct platforms with two distinct codebases. Public communications have not yet committed to a consolidation roadmap or pricing-stability terms, which has prompted multiple independent reviewers (EHR Source, others) to recommend that prospective buyers explicitly negotiate pricing caps or escalation limits before signing.

PE-backed software vendors operate on a different timeline than founder-owned ones. Capital partners typically expect revenue acceleration on a defined horizon, which historically translates into per-seat price increases, narrower contract terms, and reduced negotiation flexibility once an installed-base pricing position is established. None of this is unique to Sunwave or BVP Forge — it's the standard PE software playbook. The relevant question for facility operators is whether the platform has structural protections against that pattern. Sunwave's do not appear to be publicly committed.

No, but the answer is more nuanced than the Kipu version. Because Sunwave positions as an all-in-one (EMR + CRM + RCM), VProGo and Sunwave overlap on more surface area than VProGo and a pure EMR like Kipu. The question is whether you want VProGo to layer on top of Sunwave for the operational and marketing functions Sunwave doesn't cover (referral lifecycle, prediction, patient engagement, marketing intelligence) or whether you want VProGo to replace Sunwave outright while keeping your billing relationships intact. Both are workable. The Sunwave EMR integration is in development.

Yes. VProGo is 100% owned by founder Michael Wilson, who is also Co-Owner / Director of Family Services / President of East Point Behavioral Health (a Joint Commission-accredited multi-state behavioral health provider). The platform is operator-built, with the founder as the primary user. There is no PE clock running. The pricing architecture is published, the MSA is publishable on request, and contract terms are mutually fair (12-month mutual liability cap, 60-day termination notice, $0 self-service data export). The fundraise underway is seed-stage with deliberate dilution caps; it does not change the platform's operator-aligned trajectory.

Form customization in VProGo is self-service. Service Agreement and Order Form templates can be configured through the admin interface. Custom workflows, notification rules, and role-based permissions are administered without vendor tickets. Where vendor support is genuinely required — for example, custom EMR integration logic or new clearinghouse adapters — those engagements are scoped under a separate Statement of Work and priced transparently rather than charged per ticket inside the support relationship.

If your facility is on Kipu, Alleva, or another EMR, replacing it with Sunwave's all-in-one is a 6-12 month project with the associated workflow disruption, staff retraining, and clinical-data migration. VProGo's alternative architecture is to integrate with whatever EMR you're on and run as the operations layer above it. The operational benefit lands in weeks, not quarters, and the clinical workflow doesn't change. For facilities specifically interested in moving away from Kipu or Alleva at the same time as picking up an operations platform, that decision can be sequenced — VProGo first, EMR change later if needed.