​

Network Types and Use Cases

​

Core Thesis

CareSupport is network-specific infrastructure that equips each care network to manage its care team effectively—built for the whole network, with a Coordination Lead role (can be held by any member). Instead of universal protocols for everyone at once, we deliver specialized coordination tools tuned to family networks, independent caregiver networks, agency networks, and platform networks.

---

​

Network Types Overview

We focus on distinct care networks—how coordination is arranged and who benefits. The Coordination Lead is a role, not a fixed person; it can be held by the care recipient, a family member, a professional, or shared/rotating.

---

​

Family Networks

​

Who Coordinates + Who Benefits

Coordinated by: Care recipient or family member (e.g., Rob; Marta as backup)
Benefits: Entire family care team (15 caregivers + family)
Primary Coordination Need: Unified view of all caregivers regardless of source
Infrastructure: Family Platform (pro-integrated)

​

Real Example: Rob’s Network

Rob is quadriplegic and coordinates his own care team of ~15 people:

• 9 professional caregivers from 3 different home care agencies
• Family members (mother Marta, sister, others)

The Problem Before CareSupport: The three agencies don’t speak to each other. They all use Rob as the proxy for his own care. When someone texts “I can’t make it Saturday evening,” Rob has to manually search through 15 contacts to find who can backfill. He coordinates his own life-or-death care from a phone he operates with his nose.

How Family Platform Helps Rob

Coverage Visibility: Rob sees all caregivers from all three agencies in one unified scheduleGap Detection: System automatically detects when someone cancels and identifies available backfill candidatesCoordination Automation: Instead of manually texting 15 people, Rob confirms one AI-generated proposalHandoff Continuity: Each caregiver sees notes from the previous shift, regardless of which agency they’re fromBackup Coordinator: Marta can step in when Rob needs rest, with full context preservation

​

Family Platform Features

​

Policy Pack: Family.Pro-Integrated

• Who: Care recipient + family caregivers + professional caregivers
• Coordination Lead: Care recipient or designated family member + backup
• Rules: Handoff required at shift boundaries; PHI scoped by role
• Coverage: 24/7 monitoring with escalation chains

---

​

Independent Caregiver Networks

​

Who Coordinates + Who Benefits

Coordinated by: Independent caregiver (e.g., Sarah)
Benefits: All families they serve (multi-family practice)
Primary Coordination Need: Professional tools for managing multiple families
Infrastructure: CareGiver OS

​

The CareGiver OS Vision

CareGiver OS (capital “G”) elevates independent professionals to a professional identity with tools to manage multi-family networks.

​

Real Example: Sarah’s Multi-Family Practice

Sarah is an independent professional caregiver serving 4 families:

• The Rodriguez family (medication management, meals)
• The Chen family (mobility assistance, appointments)
• The Williams family (overnight care)
• The Johnson family (weekend respite)

How CareGiver OS Helps Sarah

Multi-Family Schedule: Sarah sees all her commitments across families in one unified viewSession Logging: Quick voice-based session summaries that automatically appear in each family’s timelineAvailability Management: Sarah sets her hours once; system prevents invalid assignments across all familiesCare Checklists: Templates for common care tasks (medication admin, mobility assist) with family-specific customizationsBusiness Operations: Invoicing, payouts, tax reports, compliance signatures—all built inProfessional Profile: Verified credentials, certifications, reputation vault that travels with Sarah across families

​

CareGiver OS Features

​

Policy Pack: Pro.Multi-Family

• Who: Independent professional as Coordination Lead across families
• Rules: Strict PHI scopes per family; no cross-family data leakage
• Boundaries: Clear work hours; availability propagates to all families
• Audit: Complete trail of which family data was accessed when

---

​

Agency Networks

​

Who Coordinates + Who Benefits

Coordinated by: Agency coordination lead/manager
Benefits: Agency workforce + Linked Circle families
Primary Coordination Need: Enterprise ops with family connectivity
Infrastructure: Agency Platform

​

The Agency Integration Challenge

Home care agencies already have their own scheduling, HR, payroll, and EVV systems. They don’t want to replace their entire stack. What they need is seamless family connectivity without heavy integration work.

​

Real Example: Rob’s Three Agencies

Rob receives care from three different home care agencies. Each agency:

• Schedules their own caregivers in their own system
• Has their own HR, payroll, and compliance processes
• Communicates with Rob independently

Before CareSupport, the agencies never spoke to each other. Rob was the integration layer.

How Agency Platform Helps Rob's Agencies

Shared Timeline: All three agencies see the same unified family timeline (with scoped access)Minimal Integration: CSV export or ICS feed from agency system → auto-sync to family viewIncident Routing: When something goes wrong during a shift, it routes to the right agency coordinator automaticallyReduced Support Load: Family can see shift status directly instead of calling agency officeNetwork Health Metrics: Agency sees measurable reduction in coordinator calls, improved coverage %, higher NPS

​

Agency Platform Features

​

Policy Pack: Agency.Family-Linked

• Who: Agency coordinator + workforce + linked family members
• Access: Read/write per policy; agency sees only their shifts unless broader access granted
• Adapter: Minimal (CSV/ICS/API-lite) with path to deeper integrations
• Audit: Complete trail of agency actions in family context
• ROI: Measurable reduction in calls/emails, improved coverage %, higher retention

---

​

Platform Networks

​

Who Coordinates + Who Benefits

Coordinated by: Platform operations or shared leads
Benefits: Matched families + caregivers post-match
Primary Coordination Need: Post-match coordination infrastructure
Infrastructure: Platform Integration (APIs + tools)

​

The Platform Use Case

Marketplaces like Care.com, Papa, Honor excel at matching families with caregivers. But post-match coordination—scheduling, handoffs, incident management—is where relationships often fail.

​

Real Example: Care.com Match → CareSupport Handoff

Family finds Sarah on Care.com. Match happens. Now what? Before CareSupport:

• Family and Sarah coordinate via text messages and phone calls
• No shared schedule, no handoff notes, no incident tracking
• High churn—many matches fail within first 30 days

With CareSupport Integration:

Post-Match Coordination Flow

1. Match Completion: Care.com match confirmed
2. CareSupport Handoff: “Powered by CareSupport” prompt appears
3. Shared Timeline Creation: Family + Sarah onboard into shared coordination space
4. Immediate Value: First session logged, handoff captured, schedule visible
5. Higher Retention: Measurable reduction in 30-day churn

​

Platform Integration Features

​

Policy Pack: Platform.Post-Match

• Who: Matched family + matched caregiver(s)
• Initialization: Shared timeline created at match time
• Coordination Lead: Family member (default) or caregiver (optional)
• Retention: 30-day retention metrics enabled
• Billing: Connect to platform payment flow or standalone

---

​

The Circle + Policy Pack Model

​

Circle Definition

Circle: Care Network as graph container with a Coordination Lead role (can be held by any member)

​

Policy Pack Templates

---

​

Network Health Score

North Star Metric: Network Health Score (NHS) per network

​

NHS Inputs

​

Quick Wins by Network Type

Family Network (≤7 days)

• Baseline NHS auto-generated
• First gap alert detected and resolved
• Handoff summary captured at least once
• Coverage % +10pp vs. baseline OR gap minutes/week −20%

Independent Caregiver (≤7 days)

• First session logged & summarized; family sees it in Timeline
• Time-to-fill for next gap < 24h
• Adherence improvement for at least one med/appointment
• Pro issues first invoice/payout

Agency Network (≤14 days)

• Coordinator calls/emails reduced for that family
• Coverage % up; support tickets down
• Agency sees NHS lift and handoff quality metrics

---

​

Differentiation

​

What Makes CareSupport Different

One-liner: We equip each care network with network-specific infrastructure.

​

Why Incumbents Can’t Replicate This

• Agency systems store shift state, not coordination reasoning—that happens in the coordinator’s head or on phone calls
• Family apps store tasks and calendars, not why tasks were assigned to whom
• Marketplaces store matches, not post-match coordination context

To capture decision traces, incumbents would need to rebuild their architecture from the ground up and insert themselves into coordination workflows they currently don’t touch. This is a multi-year structural disadvantage.

​

Our Moats