Development Timeline

Altored Health has progressed across two semesters, from initial planning and infrastructure decisions through active development, a working prototype, and ongoing refinement toward a commercial-ready product.

Phase 1: Planning and Infrastructure (August to October 2024)

The project kicked off in August 2024 with team formation, sponsor onboarding, and early scoping work. The first several weeks were primarily dedicated to planning: understanding the problem space, defining requirements, and evaluating technical options. By October we had committed to Microsoft Azure as our cloud platform and finalized our core tech stack.

Phase 2: Architecture and Core Development (October to December 2024)

With the stack locked in, the team moved into active development. We designed the system architecture, built the data ingestion pipeline, stood up the PostgreSQL database, and delivered a functional prototype by the end of the fall semester in December 2024. Core features including search, data display, and user authentication were all in place at that milestone.

Phase 3: Refinement and Feature Expansion (February to May 2025)

Spring semester focused on iterative improvement through two-week sprints. Each sprint addressed specific issues and added new capabilities. Key additions this phase include recommended plan suggestions, location services, self-pay vs. insurance comparison, a feedback and contact system, and a full UI overhaul. Beta testing with partners and performance optimization were also completed during this phase, following the roadmap below.

Project Roadmap to Market Readiness

Our spring semester roadmap laid out a structured path from core MVP through commercial readiness, organized across four timeframes.

February to March

  • Core MVP Development
  • Architecture Refinement
  • Feasibility Checks

March to April

  • Beta Testing with Partners
  • Performance Optimization
  • Short Feedback Cycles

April to May

  • Iterate Based on Feedback
  • Reliability and Scalability Testing
  • Commercial-Ready MVP

May

  • Commercial-Ready MVP (End of Spring)
  • Full Market Readiness (End of Academic Year)

Current Status

The platform is fully functional and commercially ready at the capstone level. All core features are live, the UI has been overhauled, and the system is deployed on Azure running end-to-end. A beta release for broader use is expected sometime this summer as the team continues refining the platform beyond the academic year.

Resources and Budget

Team Allocation

Work was divided on a flexible, weekly basis with tasks assigned dynamically based on project needs and team availability. Separate branches for cloud infrastructure and frontend development enabled parallel workstreams without conflicts. The team met weekly to sync on progress and address blockers, with Discord as the primary day-to-day collaboration tool.

Budget

We minimized costs throughout by using Azure free tier and student credits wherever possible, keeping cloud services lean and avoiding unnecessary resource consumption. Database queries are optimized to reduce compute time and storage is managed efficiently. This approach kept our budget minimal while still delivering a robust, deployed platform.