No. We're saying AZZLY covers the EHR/CRM/RCM basics that a lot of facilities need, and VProGo covers the operational depth that AZZLY doesn't — payment prediction at scale, multi-facility operations dashboards, billing-company channel partnerships, patient engagement PWA, marketing intelligence. For facilities already on AZZLY who are hitting growth constraints, the honest answer is not "leave AZZLY for VProGo"; it's "AZZLY works, layer VProGo on top." For facilities evaluating both from scratch, the answer depends on which problems are most pressing.

Not natively at this time. VProGo ships with Kipu integration (live, bidirectional), with Sunwave and Alleva integrations in development. AZZLY is not currently on the public integration roadmap. For AZZLY-side facilities, running VProGo as a parallel operations layer with light manual data coordination is workable in the short term; a native integration is the cleanest long-term answer and is a reasonable conversation to open if there's interest.

In practical terms: pricing stability, contract flexibility, and roadmap accountability. Founder-led platforms can afford to make long-horizon commitments that PE-backed platforms structurally can't. When a customer asks "will your pricing double in year three?" a PE-backed vendor can't honestly answer; a founder-led vendor can. This is not a criticism of PE-backed vendors — it's a structural difference in incentive alignment. Both AZZLY and VProGo are on the founder-led side of that line.

Typically one of three patterns. First: multi-facility reporting and operations become hard once you're running more than 2–3 facilities on AZZLY's all-in-one architecture. Second: payment prediction becomes a priority — knowing what insurance will actually pay before admission, not just verifying that coverage exists. Third: a billing-company partnership or channel strategy becomes relevant, and AZZLY's architecture doesn't have a BC-facing portal comparable to VProBilling. Any of these three is a reasonable trigger for adding VProGo as an operations layer above AZZLY.

AZZLY handles basic RCM needs for its typical customer size. VProGo's RCM is built for more demanding scale — ClaimMD clearinghouse with Waystar in development, clearinghouse abstraction so facilities aren't locked into one vendor, a purpose-built VProBilling portal for third-party billing companies managing 10–50+ facility portfolios, and 8-tier payment prediction integrated into the billing workflow. For AZZLY customers whose billing is straightforward enough to stay inside AZZLY, that's fine. For those expanding into billing-company partnerships or operating at the scale where clearinghouse flexibility matters, VProGo's architecture is more permissive.