Health’s Spot

The problem

The product already existed as a working codebase spanning training, cardio, nutrition and recovery. The engagement started from that code rather than a blank page — establishing what was genuinely implemented, and what only looked implemented.

Define a production-ready version of the product with reliable core fitness workflows, secure handling of user data, and clear release criteria.

The challenges

• ●Separating genuinely implemented functionality from prototype, placeholder and incomplete surfaces, without overstating readiness.
• ●Tracing authentication, authorization, persistence and subscription behaviour across several frontend and backend integration points.
• ●Turning a broad existing feature set into a smaller, testable MVP with explicit technical and product boundaries.
• ●Reviewing a large structured workout-content library and identifying its consistency, delivery and maintainability requirements.

The solution

• ●Mapped the existing application architecture, routes, modules and external integrations to establish an evidence-based baseline.
• ●Audited the Strength, Cardio, Nutrition and Recovery workflows, separating calculators, deterministic rules and statistical features from generative AI.
• ●Defined production acceptance criteria covering identity, user isolation, subscriptions, module persistence, exports and operational quality.
• ●Sequenced the remediation work so security and data integrity are addressed before any further feature work.
• ●Established an MVP product model, and criteria for deciding when a feature can be called production-ready.