top of page

Healthcare Tech MVP: AI Care Coordination Platform

  • Mar 17
  • 3 min read

Developed an MVP connecting formal and informal caregivers, validated with users and ready for pilot launch. Healthcare tech MVP for a startup tackling care coordination for elderly people, combining deep user research, product strategy and AI‑enabled features.


THE SITUATION

Client: Healthcare and social care services focusing on elderly care.​

Challenge:

  • Aging population and caregiver shortage

  • Poor coordination between formal care (nurses, primary care, social care) and informal care (family, friends)

  • Elderly people falling through the cracks​

The brief:

“We know there’s a problem. Formal and informal caregivers don’t communicate. Elderly people fall through cracks. We need a platform connecting them. Can you help us figure out what that should look like?”​

My role: Product strategist and researcher leading MVP development


THE APPROACH

1 THE RESEARCH PHASE (Weeks 1-4)

What I did:

  • Stakeholder interviews (15+):

    • Formal caregivers (nurses, facility managers, doctors)

    • Informal caregivers (family, friends)

    • Care recipients (elderly people, patients)

    • Technology gatekeepers (hospital IT, data privacy)​

  • User needs assessment:

    • Real problems they are trying to solve

    • Information they need to feel confident

    • Communication gaps and pain points

    • Constraints in daily work​

  • Competitive analysis:

    • Existing platforms and tools

    • Gaps and unmet needs

    • Market opportunity​

  • Data privacy & regulation:

    • GDPR requirements for health data

    • Local healthcare regulatory requirements

    • Security needs and risk areas


THE STRATEGY PHASE (Weeks 5-8)

What I developed:

  • Product strategy:

    • Core features (care plan, communication, medication tracking, fall detection)

    • User personas (formal caregiver, family member, elderly person, doctor)

    • Technical architecture (cloud‑based, mobile‑first, secure)​

  • MVP scope:

    • What to include (must‑have core features)

    • What to exclude (nice‑to‑haves)

    • Rationale for each decision (research‑backed)​

  • Business model:

    • Revenue streams (SaaS, per‑facility, per‑patient)

    • Pricing options

    • First target segments​

  • Go‑to‑market strategy:

    • Pilot locations

    • Launch strategy

    • 2‑year growth roadmap


THE MVP DEVELOPMENT PHASE (Weeks 9-16)

What I built:

  • High‑fidelity Figma prototypes:

    • Caregiver dashboard

    • Family member app

    • Simple interface for elderly users

    • Doctor integration view​

  • Technical roadmap:

    • Architecture design

    • Technology stack recommendation

    • Development timeline

    • Budget estimates​

  • Feature prioritization:

    • MVP features (must‑have)

    • Phase 2 features (important)

    • Future features (nice‑to‑have)


THE RESULTS

MVP Completed
  • Product strategy document
  • High‑fidelity UX designs
  • Comprehensive user research findings
  • Cloud‑ready technical architecture
  • Go‑to‑market plan and 2‑year roadmap​
User Verification
  • 90% of users said the platform would solve a real problem
  • 87% said they would use the platform​
Market Validation
  • Confirmed market need and addressable market
  • 5+ potential customers identified
  • Pilot feasibility confirmed​
Strategic Clarity
  • Clear path to MVP development
  • Defined success metrics
  • Risk mitigation strategies
  • Funding strategy with clear requirements

BUSINESS OUTCOMES

Funding:
  • Clear MVP requirements → stronger funding conversations
  • Market validation → increased investor confidence
  • Go‑to‑market strategy → clear use of funds​
Partnerships:
  • 3 pilot healthcare facilities committed
  • 2 potential distribution partners identified
  • 1 integration partner (major health platform) interested​
Next phase:
  • MVP development timeline: 6 months
  • Beta testing: 3 pilot facilities
  • Commercial launch: Month 9

KEY INSIGHTS FROM RESEARCH

What the market needs:
  1. Simple communication (elderly people cannot use complex tech)
  2. Medication tracking (prevent dangerous errors)
  3. Fall alerts (fast emergency response)
  4. Care plan visibility (everyone on the same page)
  5. Strong data privacy (regulated environment, trust is critical)​
What doesn’t matter yet:
  • AI diagnosis features (too early for this market)
  • Integration with all health systems (focus on solving the core problem first)
  • Comprehensive analytics (pilot needs are simpler)

Why this MVP process worked

The Process That Worked
Why this MVP succeeded:
  • Deep user research (understood real problems)
  • Strategic thinking (product aligned with market)
  • Business model clarity (clear path to revenue)
  • Phased approach (MVP focused, not bloated)
  • Continuous validation (tested assumptions with users)​
What made the difference:
  • Talking to real users, not just stakeholders
  • Making hard choices about what not to build
  • Focusing on the core problem: care coordination
  • Building feedback loops into the process

"It is brilliant and excellent solutions. It's also good for the relatives to see, even though they don't provide care. I have presented your material to the head of the administration and she finds your material interesting." — Activity Manager, Municipality


MY ROLE IN THIS PROJECT

I wasn't a developer.

My role:
  • Strategic designer on product direction
  • Researcher conducting user interviews
  • Facilitator of design thinking
  • Market analyst identifying opportunity
  • Business strategist developing go‑to‑market
  • Project leader coordinating everything

This shows the range of strategic advisory I can provide for healthcare tech and complex MVPs.


bottom of page