Product

What Ready Practice does, across four surfaces and one shared backend.

The four surfaces

Surface	Public name	Audience	Stack	Hosting
Basis Flow Web	Ready Practice Platform	Clinic staff	Next.js	platform.basishealth.io
Basis Hybrid	Ready Practice App	Patients	Flutter	App Stores (white-label)
Basis Web	Client Portal	Patients	Next.js	web.basishealth.io (Netlify)
basis-functions	—	—	Python Cloud Functions	Firebase

Capability map

• Scheduling — availability, slots, memberships, waitlist, cross-booking, reschedule. → scheduling, booking audit
• Labs — ordering (LabCorp/Quest/BioReference, home kits), upload, analysis, results, benchmarks. → labs
• Programs & Protocols — care programs, biomarkers, activities, recurrence. → programs-protocols
• Payments — Stripe, subscriptions, multi-account, platform fee. → stripe-payments
• Insurance / RCM — claims, eligibility, ERA, superbills, Stedi. → insurance-rcm
• Chat & Notifications — messaging, push, email, Atlas draft-assist. → chat-notifications
• Onboarding — client onboarding, intake forms, invitations, signup flow. → onboarding, signup flow
• White-label app — per-clinic branding, section toggles, onboarding welcome.
• Atlas AI — copilot, consumer Health Assistant, operator. → Atlas & AI
• Marketplace / Shop — catalog, vendors, clinic-owned products, fulfillment. → shop status (see repo BASIS_SHOP_STATUS_AND_PLAN.md)

Live feature status

The authoritative, actively-maintained matrix (with app versions, last-changed dates, and known issues) is FEATURES.md. The unannounced queue that feeds the growth content loop is growth-content-backlog.

Design system

The Basis Flow Web design system (--rp-* tokens + UI primitives) is documented at hybrid/basisflow-web/DESIGN_SYSTEM.md. It is honest about adoption gaps (~9k hex values still un-migrated).

Gap

No public feature-comparison / competitive positioning or ROI / case-study pages exist yet. These are needed for the customer-facing site — tracked as growth work, not product docs.