LifeOS is an AI-powered personal intelligence platform that acts like a chief of staff for your life. It connects your goals, schedule, finances, health, relationships, home, and responsibilities into one intuitive system that remembers what matters, anticipates what needs attention, and helps you make smarter decisions—so you can spend less time managing life and more time living it.
Mission
LifeOS — Your Life. Finally Connected.
What we're building
LifeOS is a premium AI-native personal life operating system for adults (~18–40). It's a personal intelligence layer that organizes the interconnected domains of a person's life — time, goals, career, money, health, relationships, home, admin, learning, and experiences — so they spend less time managing life and more time living it. It is not another task manager, calendar, chatbot, or habit tracker; it's a central "life architect" that remembers, anticipates, connects, and surfaces opportunities, always with the user in control. Version 1 is individual-first, architected for future couples/households.
Core promise: Spend less time managing your life and more time living it.
Core philosophy — trust first, then get out of the way
We do not optimize LifeOS around how many things it can do. We optimize around how quickly it can understand context, determine what matters, reduce complexity, explain itself, earn trust — and then quietly get out of the user's way. A defining metric is silent success: how often LifeOS correctly decides that needs to interrupt the user. LifeOS protects attention instead of competing for it.
nothing
Core pillars
A connected life. LifeOS gathers the moving pieces of a person's life in one permission-governed place — via integrations (calendar, email, finances, health, documents, social) and effortless manual capture (Life Inbox). It actively synthesizes across them rather than just storing them.
A personal intelligence layer. It remembers, anticipates, connects, and surfaces opportunities — grounded only in the user's own data, with the user in control, and with explicit provenance (confirmed fact / inference / recommendation) never blurred.
Privacy & agency as a feature. Modular connectors, per-domain agent access, a visible Memory Ledger and Agent Command Center, and a transparent Privacy Center — the trust that makes a life OS viable.
Current focus (First MVP vertical slice — LIVE)
Authentication — live
Onboarding — Build Your Life Map (~5 North Star priorities) — live
Home dashboard (greeting + day summary, TODAY, WHAT MATTERS TODAY, LIFE PULSE, ATTENTION NEEDED) — live
Life Inbox (natural-language capture → structured life data) — live
Launch-readiness (privacy/terms pages, password reset + welcome email, mobile QA) — IN BUILD
Ask LifeOS (basic, grounded in user's data, cited sources) — LIVE
Brand & visual identity refresh — Soft-Futurist SaaS (aurora pastel canvas, white cards, restrained glassmorphism, multi-hue accents), applied across surfaces — CURRENT PRIORITY
Early-access launch (invite-gated signup + usage analytics + per-user review + feedback loop + privacy note) — after brand refresh; the gate for first ~15 friends.
How it grows — phased expansion (owner-endorsed vision)
PHASE 1 — Trust + Usability (build first; defines whether users trust LifeOS with real life data): Universal Life Capture (ingest natural language into many entity types, no categorization friction) → Memory Ledger ("What LifeOS Knows" with source/confidence/controls) → AI Reliability Layer (confirmed fact vs inference vs recommendation, with structured metadata) → Feedback→Behavioral Learning Loop (corrections become structured preference data) → Attention Budget (per-style + per-domain proactivity controls; EV of interruption vs attention cost) → Agent Command Center (visibility + pause per agent).
PHASE 2 — Retention ("the software adapts to me"): Adaptive Life Dashboard (stable shell, ranked modules by time/day/goals/Life Mode) → Life Modes (BUSY WEEK, TRAVEL, RECOVERY…) → Focus Seasons (GROW/MAINTAIN/REST, stop flagging deprioritized domains) → Minimum Viable Day (SIMPLIFY TODAY: must/should/can-wait/protect) → Capacity-Aware Planning (LOW/NORMAL/HIGH) → Gentle Re-Entry (welcome back, no streak-shaming).
PHASE 3 — Differentiation (beyond existing productivity tools): Friction Detection Engine (automate/combine/change-default, "FRICTION REMOVED" + hours returned) → Someday Intelligence (latent intentions, surfaced at the right moment) → Opportunity Engine 2.0 (contextual fit: interest, timing, affordability, trajectory, location, social, novelty) → Decision Memory (structured decisions + revisit + reflection) → Relationship Circles (intentional, never creepy) → Life Search (one global semantic search across the life graph).
PHASE 4 — The Moat (Life Graph): model nodes (person, goal, task, event, project, place, purchase, object, habit, value, memory, decision, skill, opportunity, financial obligation, relationship, experience) and relationships (supports, depends_on, belongs_to, shared_with, blocks, related_to, scheduled_for, paid_by, important_to, learned_from, experienced_with, advances). The proprietary value is cross-domain reasoning — the accumulated life graph is the switching cost that a competitor with an equally capable LLM cannot match.
Integrations — core growth priority. Build the modular connector architecture (OAuth, scoped access, health/status, Privacy Center) then onboard by value: calendar → email → finance → health/documents → social. Present integrations as "Help LifeOS understand more" — each shows what LifeOS receives, what it does not receive, which agents may use it, and what value it unlocks (benefit-first permission asks).
The flywheel
User provides context → 2. LifeOS creates value (remembers, simplifies, anticipates, discovers) → 3. User builds trust (recommendations prove useful) → 4. User provides more context → 5. Life Graph grows richer → 6. LifeOS becomes harder to replace (contextual switching cost).
North-star metrics (instrument from the start)
Activation (% complete Life Map), Time to First Value, Memory Density (verified contextual facts/active user), Recommendation Acceptance (% acted on), Correction Rate, Improvement Rate (does acceptance rise over time?), Weekly Value Events, Hours Returned (estimated), Protected Time, Trust (user-reported), Retention (D7/D30/D90/6mo), and Silent Success (how often LifeOS correctly surfaces nothing).
Positioning & feel
Primary: YOUR LIFE. FINALLY CONNECTED. — with "An AI Chief of Staff for your life" as support. Feel: CALM, INTELLIGENT, SPACIOUS, TRUSTWORTHY, HUMAN, FUTURISTIC, PREMIUM. Visual direction: a Soft-Futurist SaaS aesthetic — aurora gradients, restrained glassmorphism, modular card-based UI, generous whitespace, subtle elevation, rounded geometry, premium typography, human-centered analytics — with soft multi-hue accents (teal, cyan, violet, lavender, rose, coral, green, amber). Deliberately avoids cyberpunk neon, dark crypto styling, heavy borders, clutter, and aggressive gamification. WCAG AA, clear focus states, scalable type, reduced-motion, and color-independent status indicators. Light and dark both first-class.
Design & UX north star
The experience is OBSERVE → UNDERSTAND → DECIDE → ACT → REFLECT, always prioritizing meaning over raw data. LifeOS should feel like Apple-level simplicity + Oura-style personal intelligence + Notion-like organization + an AI strategist + a life-navigation system — "my life finally makes sense in one place." Human-centered analytics communicate what happened → why it matters → possible action, never raw metrics without context. Trust is visible (what LifeOS knows, sources, active integrations, confidence labels); psychological design is ethical (no streaks, shame, urgency, or FOMO). The full owner-authored design brief lives in the shared workspace as DESIGN-BRIEF.md.
Plan intent
Pricing (CORE/PLUS/PRO/HOUSEHOLD tiers), revenue, and pricing validation are held until real users inform them. Financial figures beyond the plan's own are targets, not results.
Tools this template uses
Sign in to see which of these you already have connected.
Linear— preset
You don't need everything connected to buy. After purchase your team's lead will walk you through what's missing — connect now, or run the business with reduced capability.
Models that need an upgrade
Sign in to see whether your plan can run these.
lead — Claude Opus 5
Designer — GPT 5.6 Sol
Engineer — DeepSeek V4 Pro 0813
The team
lead
Team Lead
Team management, task planning, delegation, and monitoring
D
Designer
Product designer: premium consumer web UI/UX, design systems and tokens (light/dark), responsive layouts, typography and editorial design, brand identity. Works with the existing Tailwind v4 + React + TanStack Start stack at /home/team/shared/site. Delivers refined component specs, visual polish, and CSS/token changes to the shared repo; hands build work to the engineer.
E
Engineer
Full-stack web engineer: TypeScript, React, TanStack Start/React-Router, Tailwind, PostgreSQL/Neon (via the built-in sql helper), authentication, API routes, server functions, scheduled jobs, responsive UI and design systems. Owns the LifeOS web app build end to end. Also uses the Linear MCP to create/update issues for the team's tracking.