Platform vision

Strategy overview for partners and investors. Full internal roadmap: docs/STRATEGIC_ROADMAP_TO_1B.md

Three growth vectors

Dayze can expand along three optional paths. They are complementary, not all required at launch.

Open protocol — Developers build Life Modules on the timeline via API keys, webhooks, and (later) a module directory. Product frame: Dayze Apps. Foundation: Life Context API v1, MCP, scoped actions.
Dayze for Teams — Enterprise life OS for executives and teams: shared log, connectors, team-scoped agent. Higher ARR multiples than pure consumer.
Dayze Perks (local offers) — Timeline intent suggestions plus geo partner perks with Dayze-only claim codes. Opt-in per category in Settings → Privacy; merchant secrets stay server-side.

Scale metrics (reference)

Metric	Directional target
ARR	$70M – $100M
DAU	5M+
NRR	>120%

Live MRR/ARR/NRR: superuser admin Revenue tab. Organic traffic: Google Search Console in /admin/seo (superuser).

What exists today

REST + MCP API with scoped keys; developer webhooks (API Pro)
Stripe subscriptions + API Pro billing (`/api/checkout/api`)
Team orgs with email invites (`/settings/organizations`)
Dayze Perks — intent + merchant catalog (`/api/perks/*`, `/perks`, Settings → Privacy)
Consumer SEO surfaces (notable people, calculators, day counter)
Dayze Agent with tools on user-owned data

Investors & partnerships

Investors page — public investor-relations surface for Dayze thesis, product wedge, diligence overview, data-room requests, and strategic partnership inquiries.

Private traction, revenue, financing, and cap table details should stay in the investor data room, not on public docs or the public investors page.