OPERATING ROADMAP

Build the health
command center for
every wearable stack.

This roadmap turns Pulsara's value proposition into an execution plan: first unify the data, then drive daily decisions, then scale into coach, team, and partnership workflows. Assumes roadmap kickoff on May 1, 2026.

See pricing alignmentReview integration stack

Roadmap principles

Unify before optimizing

Pulsara wins when users can trust one canonical view of readiness, sleep, activity, and recovery across every device they own.

Package by moment of value

Free proves aggregation, Pro proves better decisions, and Coach proves business ROI for every client session.

Sequence integrations by platform risk

Ship the fastest cloud connectors first, while companion-app rails for Apple Health and Health Connect mature in parallel.

Activation target

65%

New users who connect at least 2 data sources within 7 days.

Retention target

40%

Week-8 retention for Pro-ready athletes and health-conscious users.

Coach wedge

25%

Share of paid revenue driven by coaches and coach-referred clients by month 12.

Phase roadmap

Three phases, one throughline: trust, action, scale.

Each phase expands the surface area only after the previous one creates a reliable user habit and a monetizable value loop.

Phase 1

MVP

May-July 2026

Launch the core aggregation loop for athletes and health-conscious individuals: connect devices, normalize daily metrics, and surface a single readiness story.

Success metrics

  • 100 beta users with at least 2 connected sources.
  • 65% onboarding completion from signup to first dashboard.
  • 70% week-4 retention among users who connect 2 or more sources.
  • Median dashboard API latency under 2.5 seconds.

Core product

  • Unified daily dashboard with metric provenance and source confidence tags.
  • Daily summary card, 7-day trend strip, and device health/status surface.
  • Account onboarding that drives multi-device connection before first-session drop-off.

Data platform

  • Canonical metrics schema for sleep, recovery, activity, and cardio signals.
  • Connector service with OAuth token vault, polling jobs, retry queues, and backfill pipeline.
  • Deduplication and normalization rules to reconcile overlapping metrics from multiple devices.

Commercial fit

  • Free tier: 1 device, 30-day history, daily dashboard lite.
  • Pro early-access promise: up to 5 devices, 12-month history, basic insights.
  • Closed beta with 100 athletes and 25 health-conscious professionals from the existing waitlist.

Key milestones

  • May 2026: canonical schema, auth vault, connector worker architecture finalized.
  • June 2026: Garmin, Fitbit, and WHOOP beta connectors live with internal QA.
  • July 2026: Apple Health and Health Connect companion sync beta; unified dashboard and daily insight cards launch.

Pricing fit

Phase 1 proves Free-to-Pro conversion: free users feel the benefit of a unified dashboard, while Pro unlocks multi-device history and daily decision support.

GTM fit

Use a closed-beta motion focused on athletes who already own multiple wearables, plus a smaller health-conscious cohort that values clarity over raw metrics.

Phase objectives

  • Support Garmin, Fitbit, and WHOOP cloud connectors with OAuth-based ingestion.
  • Ship iOS and Android companion sync rails for Apple Health and Health Connect.
  • Deliver a unified dashboard for sleep, recovery, strain/activity, resting heart rate, and HRV where available.
  • Generate basic insights: readiness status, sleep debt alert, and trend deltas versus the user's trailing baseline.
Phase 2

Growth

August-October 2026

Turn aggregation into habit and monetization: personalized recommendations, better mobile loops, and the first coach/client workflows.

Success metrics

  • 12% Free-to-Pro conversion inside 30 days.
  • 30% increase in week-8 retention for users receiving personalized recommendations.
  • 10 paid coach accounts managing at least 5 clients each.
  • 40% of active users open Pulsara on mobile 4 or more days per week.

Personalization

  • Recommendation engine built on user baselines, recent variance, and goal type.
  • Smart alerts for overreaching risk, poor sleep streaks, and recovery rebounds.
  • Goal tracker for consistency, sleep, readiness, and training load targets.

Coach product

  • Coach dashboard with up to 20 client slots, status filters, and daily readiness overview.
  • Client invitation flow, permissions model, and weekly exportable reports.
  • Session prep view that translates wearable data into coaching decisions.

Mobile & growth

  • Native sync status surface for Apple Health and Android Health Connect.
  • Mobile home refresh with notification hooks and faster re-entry into today's insight stack.
  • Free trial to Pro upsell paths triggered by second-device intent or recommendation clicks.

Key milestones

  • August 2026: recommendation engine v1 and personalized daily brief ship to Pro users.
  • September 2026: coach/client pilot begins with 10 design-partner coaches.
  • October 2026: mobile refresh, monthly reports, and Coach tier public launch.

Pricing fit

Phase 2 is where Pro becomes the default paid tier and Coach becomes a deliberate upsell for practitioners who need client-level leverage.

GTM fit

Pair self-serve athlete conversion with coach design partnerships, creator demos, and case studies built around 'coach smarter with readiness data.'

Phase objectives

  • Launch personalized daily recommendations for sleep, training, stress load, and recovery windows.
  • Introduce coach workspace, client roster, client invitations, and pre-session readiness snapshots.
  • Improve the mobile experience with push-ready summaries, habit loops, and faster sync diagnostics.
  • Expand reporting depth with monthly trends, goal tracking, and exportable summaries.
Phase 3

Scale

November 2026-April 2027

Build durable differentiation with advanced analytics, AI-driven insight layers, multi-user workflows, and partnership-ready APIs.

Success metrics

  • $45K MRR run rate with Pro and Coach as the core monetization engine.
  • 25% of paid accounts using at least one AI-generated insight each week.
  • 20 coach organizations with monthly active client monitoring.
  • 3 signed pilot partnerships using exported or embedded Pulsara data.

Advanced analytics

  • Multivariate trend views combining recovery, load, sleep quality, and adherence.
  • Benchmarking against user archetypes such as endurance athlete, shift worker, or coach-managed client.
  • Root-cause drilldowns showing which signals contributed most to a readiness change.

AI & automation

  • AI daily briefing with explanation, recommendation, and confidence score.
  • Auto-generated weekly coach recap and client-specific intervention suggestions.
  • Support tools for support and success teams: account health flags, sync anomaly detection, and churn-risk scoring.

Teams & ecosystem

  • Coach portfolio analytics, team rollups, and role-based access control.
  • Partner API for wellness studios, training platforms, and employer wellness pilots.
  • Enterprise packaging exploration: Coach Pro / enterprise-light extension after product-market proof.

Key milestones

  • December 2026: advanced analytics suite and benchmark views launch for Pro and Coach.
  • February 2027: AI briefing v1 and coach recap automation ship.
  • April 2027: team dashboards, partner API beta, and enterprise-light sales motion begin.

Pricing fit

Phase 3 deepens Pro stickiness, expands Coach ARPU, and creates the conditions for a Coach Pro or enterprise-light extension without bloating the initial price grid.

GTM fit

Lean into coach referrals, studio partnerships, and API-led distribution while content and creator channels continue to feed the top of funnel.

Phase objectives

  • Deliver advanced analytics: cohort benchmarking, longitudinal pattern detection, and confidence-scored insight trails.
  • Launch AI-generated briefings that explain why readiness moved and what to change next.
  • Expand to team, studio, and enterprise workflows with role-based access and portfolio reporting.
  • Open partnership rails through export APIs and selective data-sharing integrations.

RICE prioritization

Prioritize the compounding systems first.

RICE scoring is used here to protect the roadmap from chasing flashy AI work before ingestion quality, dashboards, and monetizable workflows are in place.

FeaturePhaseReachImpactConfidenceEffortRICEWhy now

Unified daily dashboard

Phase 1170030.856722.5Fastest path from connected devices to visible user value.

Mobile sync diagnostics + summaries

Phase 2150020.854637.5Reduces trust erosion caused by stale or confusing sync states.

Unified metrics schema + normalization pipeline

Phase 1180030.98607.5Foundational dependency for every dashboard, recommendation, and coach feature.

Personalized recommendation engine

Phase 2140030.87480.0Primary Pro conversion and retention lever once baseline data quality is stable.

Apple Health sync rail

Phase 1120030.78315.0Large addressable audience, but requires a mobile ingestion path instead of pure server-to-server sync.

Garmin connector

Phase 19502.50.657220.5Critical for athlete credibility, but partner friction makes it harder than Fitbit or WHOOP.

AI daily briefing

Phase 39002.50.657208.9Important differentiator, but only after the recommendation engine and data provenance are mature.

Coach dashboard + client roster

Phase 232030.85153.6Smaller reach than consumer features, but high monetization and referral leverage.

Partner API + team rollups

Phase 31802.50.7652.5Lower reach early on, but essential for enterprise-light expansion and partner-led distribution.

Platform dependencies

Integration complexity is a product decision, not just an engineering task.

These notes reflect current platform requirements and should drive sequencing, staffing, and commercial expectations before the roadmap is committed.

Shared technical dependencies

  • Connector service with OAuth token storage, refresh, retries, and rate-limit awareness.
  • Canonical metric model with provenance, deduplication, unit conversion, and source confidence.
  • Backfill + scheduling layer for historical imports, missing-day replays, and mobile-delayed sync windows.
  • Insight rules engine that can graduate from static thresholds to personalized baselines and AI narration.
  • Permissions and sharing model for coach access, exports, team rollups, and future partner API scopes.

Garmin

Garmin Connect Developer Program / Health API partnership.

High

Technical dependencies

Partner approval, commercial/API agreement, OAuth or token exchange, ingestion worker, and backfill safeguards.

Initial scope

Start with activity, wellness, sleep, and HR metrics for athlete credibility.

Sequencing note

Begin approval process immediately because commercial and review steps can outlast the coding work.

Fitbit

Fitbit Web API with OAuth 2.0 and user-granted scopes.

Medium

Technical dependencies

App registration, consent flows, token refresh, quota handling, and explicit approval for intraday depth where needed.

Initial scope

Daily dashboard, sleep, resting heart rate, activity, and enough intraday support to power trend insights.

Sequencing note

Ship early because the cloud-based model is fast to validate and covers a mainstream health audience.

WHOOP

WHOOP developer app with OAuth, scoped data access, and production review.

Medium-High

Technical dependencies

Developer app setup, membership-aware testing, scope design, approval workflow, and event/backfill orchestration.

Initial scope

Recovery, sleep, strain, and journal-linked context for high-value athlete and coach users.

Sequencing note

Prioritize alongside Garmin to validate the athlete segment and premium willingness to pay.

Apple Watch

iOS companion app using HealthKit / Apple Health as the data bridge.

High

Technical dependencies

Native iOS app, HealthKit capability, permission messaging, background sync strategy, and App Store privacy compliance.

Initial scope

Sleep, heart metrics, workouts, activity rings, and data provenance surfaced as Apple Health-derived.

Sequencing note

Build in parallel during Phase 1, then harden the sync experience during Phase 2 mobile work.

Android smartwatches

Android companion app using Health Connect as the aggregation layer.

Medium-High

Technical dependencies

Android app, Health Connect SDK, runtime permissions, OEM compatibility QA, and local-to-cloud sync logic.

Initial scope

Sleep, activity, workouts, heart rate, and body metrics exposed through Health Connect-compatible devices.

Sequencing note

Treat as a mobile platform rail rather than a single vendor integration; quality depends on device fragmentation management.

Pricing and GTM

Tie every major feature to a tier and a go-to-market motion.

Free

Acquisition engine for waitlist, SEO, creator traffic, and product-led referrals.

  • Phase 1: one device, 30-day history, dashboard lite, weekly summary.
  • Phase 2: upgrade prompts tied to second-device intent, deeper history, and personalized recommendations.
  • Phase 3: remains the top-of-funnel product, not the innovation layer.

Pro

Default monetization tier for athletes and health-conscious individuals.

  • Phase 1: multi-device aggregation and basic insight layer justify the first paid conversion.
  • Phase 2: recommendations, exports, and mobile habit loops drive retention and annual-plan adoption.
  • Phase 3: advanced analytics and AI briefings make Pro the sticky everyday operating system.

Coach

B2B wedge and distribution channel via coach-referred clients.

  • Phase 2: client roster, readiness view, and reports create the first credible business workflow.
  • Phase 3: team rollups, automation, and partner exports expand ARPU and reduce churn.
  • Coach Pro / enterprise-light should only emerge after Coach usage proves real multi-client depth.

GTM motions by phase

Phase 1

Closed beta and customer discovery

Existing waitlist, Reddit/creator outreach, and hand-selected multi-device athletes.

Phase 2

Public Pro conversion + coach pilots

Creator demos, case studies, onboarding email flows, and coach design-partner referrals.

Phase 3

Partnership and studio expansion

Coach referrals, studio pilots, embedded/API partners, and long-tail content acquisition.

Recommended operating rule

Do not ship AI before trust.

If data quality, sync transparency, and source normalization are not visibly reliable by the end of Phase 1, delay Phase 2 recommendation ambition rather than adding a brittle insight layer that erodes trust.

Return to landing pageRevisit milestones