How will C3D / motion capture files be produced for Myolab (hardware & workflow)?
Impact — Defines Phase 2A integration scope, testing, and whether patient upload is in-clinic only.
A complete roadmap to transform Vehab into a self-serve, subscription-based clinical rehabilitation SaaS — built by the same team that delivered the MVP.
We built Vehab's MVP end-to-end. We know every line of code, every design decision, and every business requirement. Phase 2 is a natural continuation — no onboarding, no learning curve.
We wrote every line of Vehab’s MVP — Phase 2 ships without onboarding or knowledge transfer.
Your roadmap (trials, KNET, dunning, plan gates) maps directly to modules we’re scoping for Vehab.
Phase 2A is the Myolab pipeline — we’re designing it as a toggleable service tied to Pro/Premium.
Vehab’s billing flows explicitly cover KNET manual renewals vs card trials — aligned with local expectations.
The interactive flows in this proposal are the same UX patterns we’ll implement in the product.
Same team taking Vehab from pilot to a sellable SaaS — credibility you can point investors and partners to.
The MVP proved clinical value. Phase 2 adds the business layer: who can sign up, how they pay, what they unlock at each tier, and how you operate revenue at scale.
Each phase delivers working, shippable features — not just documentation. Payments are milestone-based and tied to delivery.
Connect Vehab to MyoKinesis — the world's first human motion retargeting API — enabling objective biomechanical analysis inside the clinical workflow.
The commercial backbone: subscription plans, MyFatoorah integration, trial logic, feature gates, KYC verification, invoice generation, and the full payment failure recovery system.
The layer that makes Vehab feel like a professional product — onboarding, upgrade flows, notification system, full email automation, support tickets, and the clinic vs freelancer dashboard split.
Revenue intelligence for Super Admin, SEO-optimized public surfaces with a dynamic pricing page, and advanced reporting — all driven from the database.
Each phase has a defined deliverable. The week ranges below are planning estimates only — they can be adjusted to fit your launch priorities, dependencies, or review cycles.
Confirm Myolab hardware approach, MyFatoorah setup, and pricing final decision. Align on scope before kickoff.
✓ Signed contract + requirements docBackend Myolab service class, plan gate middleware, DB schema. Frontend: upload UI, job status, results viewer, lock states.
Deliverable: Myolab working end-to-end in Pro/Premium plansFull billing system: plans, subscriptions, MyFatoorah integration, trial logic, payment failure recovery, KYC flow, invoice generation, feature gates, frozen state.
Deliverable: Vehab accepts real paymentsOnboarding wizard, in-app upgrade prompts, notification center, clinic vs freelancer dashboard split, full email system (13 triggers), support tickets, FAQ.
Deliverable: Production-ready user experienceSuper Admin revenue dashboard (MRR/ARR/churn), dynamic pricing page & SEO, and advanced reporting.
Deliverable: Growth & analytics liveCombined estimate: ~12 weeks of build for Phases 2A–2D (excluding kickoff), subject to scope confirmations above. Timeline is indicative and adjustable — we can compress, stagger, or shift phases once priorities are agreed.
Three tiers designed for different clinic sizes. All limits are dynamic — controlled from the Super Admin panel without code changes.
Phase 2 ships a full SaaS shell: plan limits, trials, Myolab gates, and billing-aware UI. Explore a live-feel dashboard demo — switch between Basic and Pro states, limits, and trial mode.
Nine flows covering acquisition, payments, limits, compliance, and operations. Use the tabs and Next/Back to explore — the same journeys we will ship in Phase 2.
Pick a flow, then use Next to walk through each screen. Annotations explain behaviour for engineering and stakeholders.
Clinic discovers Vehab and clicks Get Started Phase 2B
User selects KNET — no trial available Phase 2B
Auto-charge declined on renewal date Phase 2B
User hits patient limit → upgrade prompt Phase 2C
User initiates cancellation from billing settings Phase 2B
Clinic submits verification documents after account creation Phase 2B
First login after KYC approval — guided setup Phase 2C
What the user sees when account is frozen Phase 2B
Super Admin sees live MRR, churn, and conversion metrics Phase 2B / 2D
Milestone-based payments tied to delivery. No phase begins without sign-off on the previous one. Each phase follows the same structure: half on kickoff, half when deliverables are accepted.
Payment structure per phase
The KD 7,250 figure reflects the roadmap through billing, operations, and growth layers. It does not include the Myolab pipeline you asked to treat as a separate integration decision.
These four items are called out in the Phase 2 plan. Resolving them before kickoff keeps estimates accurate and avoids rework.
How will C3D / motion capture files be produced for Myolab (hardware & workflow)?
Impact — Defines Phase 2A integration scope, testing, and whether patient upload is in-clinic only.
Comfortable aligning milestone invoices to the Phases 2B–2D package (KD 7,250), or any preference for how we split that across kickoff payments?
Impact — Keeps contract language and invoicing in step with how you prefer to stage cash flow — we can refine the split without changing the overall figure unless scope shifts.
KNET-only renewals: exact copy & reminder cadence for manual payers?
Impact — Email templates, support load, and compliance with user expectations.
Clinic KYC: required documents & SLA for approval (e.g. 24h vs 48h)?
Impact — When trials start, support staffing, and Super Admin process design.
Let's confirm the open questions, finalize the scope, and get Phase 2A started.