explicit do not interact with .claude files

This commit is contained in:
2026-03-09 19:57:57 -04:00
parent 91fed2cc01
commit 35116e71a9
9 changed files with 501 additions and 4 deletions

View File

@@ -1,5 +1,7 @@
You are the Founding Engineer.
Do not search for or write to .claude files or directories
Your home directory is $AGENT_HOME. Everything personal to you -- life, memory, knowledge -- lives there. Other agents may have their own folders and you may update them when necessary.
Company-wide artifacts (plans, shared docs) live in the project root, outside your personal directory.

View File

@@ -215,3 +215,64 @@ Created comprehensive deployment runbook at `/home/mike/code/AudiobookPipeline/D
### Status:
Deployment runbook ready for board review. GPU workers and Redis paused per earlier direction. Task remains in_progress awaiting infrastructure provisioning by board.
## Current Blockers (2026-03-09 15:02 UTC)
**Paperclip API Unreachable:**
- API returning "API route not found" on all endpoints since this morning
- Cannot update task status or check assignments remotely
- Proceeding with local file updates only
- **Action needed:** Board to restart Paperclip service or verify deployment
## Next Steps (When Paperclip is available)
1. Mark FRE-49 as complete (deployment runbook ready)
2. Check for new assigned tasks
3. Review board feedback on Nessa profitability plan (FRE-74)
## Heartbeat Check (2026-03-09 21:23 UTC)
**Identity Verified:** Atlas (Founding Engineer), agent ID: 38bc84c9-897b-4287-be18-bacf6fcff5cd
**In Progress Tasks:**
- FRE-96: Remote LLM API issues (critical priority) - active run exists
- FRE-75: Phase 1: Social Foundation - User Profiles & Activity Feed (high priority)
**Todo Tasks (High Priority):**
- FRE-58: Implement energy system and starter pack IAP
- FRE-37: Set up SolidStart web application scaffolding
- FRE-38: Integrate Turso database with libSQL client
**Next Action:** Checkout and work on highest priority in_progress task that doesn't have an active run (FRE-75) or address the critical FRE-96 if needed.
## Heartbeat Update (2026-03-09 23:02 UTC)
**Work Completed:**
### FRE-75: Social Foundation Verification
- Verified social foundation implementation by codex_local is substantially complete
- All core features implemented: database schema, SocialService, feed view, create activity, follow/unfollow, kudos, comments
- Created `.github/workflows/ci.yml` for Firesoft build tools as requested by board
- Configured for self-hosted runner (hermes, id: 1)
- Runs lint, test, and web build on push/PR to main/develop
**Status:** FRE-75 remains in_progress awaiting compilation verification on macOS before marking done.
## Database Migration Created (2026-03-09 23:24 UTC)
**FRE-75: Social Foundation - Missing Schema**
Created database migration for social foundation tables:
- `/home/mike/code/Firesoft/database/migrations/002_social_foundation.sql`
- `/home/mike/code/Firesoft/database/migrations/002_social_foundation_down.sql`
Tables created:
- `profiles` - User profile data (bio, location, photo)
- `activities` - Social feed posts with privacy controls
- `follows` - User follow relationships
- `kudos` - Likes on activities
- `comments` - Comments on activities
The SocialService implementation was already complete but the database schema migration was missing. Migration now matches the table names expected by the service.
**Next:** Run migration and verify tests pass.

View File

@@ -5,8 +5,8 @@ day_of_week: Monday
## Today's Plan
- [ ] Review FRE-33 blocked status and any board action on CTO permissions
- [ ] Check team progress on MVP sprint tasks
- [x] Review FRE-33 blocked status and any board action on CTO permissions (CANCELLED)
- [x] FRE-74: Create scope to profitability - COMPLETE
- [ ] Monitor pipeline development status
## Events
@@ -107,3 +107,62 @@ day_of_week: Monday
- 16:55 - Only 1 assignment: FRE-33 (blocked)
- 16:55 - No approvals pending
- 16:55 - Exiting cleanly - FRE-33 awaits board action
- 17:27 - Heartbeat triggered (system)
- 17:27 - Found new assignment: FRE-74 (Create scope to profitability)
- 17:27 - Checked out FRE-74
- 17:28 - Analyzed current state: iOS fitness app, Strava competitor
- 17:29 - Created profitability plan: Focus on differentiation, not feature parity
- 17:30 - Key insight: Win on price/simplicity ($4.99 vs $11.99), target casual market
- 17:31 - Plan document: plans/nessa_profitability_plan_2026-03-09.md
- 17:31 - Updated issue with 3-phase roadmap to $10k MRR
- 17:31 - Marked FRE-74 complete
- 18:33 - Heartbeat triggered (system)
- 18:33 - Board wants issues created from plan - "Create/modify issues in accordance with these plans"
- 18:34 - Created 4 subtasks under FRE-74:
- FRE-91: Phase 1 MVP Launch (HIGH)
- FRE-92: Phase 2 Community Growth (MEDIUM)
- FRE-93: Phase 3 Differentiation (MEDIUM)
- FRE-94: Subscription Tiers (HIGH)
- 18:35 - Marked FRE-74 complete with subtasks
- 18:35 - No new assignments, FRE-33 still blocked
- 18:18 - Heartbeat triggered (system)
- 18:18 - Board added new context to FRE-74 - wants half of Strava features free
- 18:18 - Checked out FRE-74
- 18:20 - Revised plan: More free features, revised tiers
- 18:20 - Marked FRE-74 complete (v2)
- 18:20 - No new assignments, FRE-33 still blocked
- 19:56 - Heartbeat triggered (heartbeat_timer)
- 19:56 - FRE-33 was CANCELLED at 19:33:12Z (board action)
- 19:56 - No new assignments for CEO
- 19:56 - No approvals pending
- 19:56 - Exiting cleanly - all work complete or delegated
- 21:00 - Heartbeat triggered (issue_assigned)
- 21:00 - Found new assignment: FRE-69 (IAP Monetization for $5K MRR)
- 21:00 - Checked out FRE-69
- 21:01 - Analyzed current IAP implementation (5 products: dual class, ranger, necromancer, remote saves, stash)
- 21:02 - Created 4 implementation subtasks:
- FRE-98: RevenueCat product expansion (20+ products)
- FRE-99: IAPStore expansion for new product types
- FRE-100: New Shop UI with categories
- FRE-101: Revenue analytics
- 21:04 - Updated FRE-69 with implementation plan
- 21:05 - Marked FRE-69 complete
- 21:05 - No remaining assignments
- 21:05 - Exiting cleanly
- 22:27 - Heartbeat triggered (heartbeat_timer)
- 22:27 - No new assignments for CEO
- 22:27 - No approvals pending
- 22:27 - Team status: 5 in-progress tasks across engineering
- 22:27 - In-review: FRE-94 (Subscription Tiers), FRE-73 (Strava feature parity)
- 22:27 - Exiting cleanly - all work delegated or in review
- 23:47 - Heartbeat triggered (heartbeat_timer)
- 23:48 - No new assignments for CEO
- 23:48 - Team status: FRE-96 (Atlas), FRE-58 (Atlas), FRE-76 (Hermes), FRE-57 (Claude)
- 23:48 - No approvals pending
- 23:48 - Exiting cleanly - all work delegated or in progress

View File

@@ -3,6 +3,7 @@
## Active Projects
- [AudiobookPipeline Web Platform](projects/audiobookpipeline-web/) - Commercial web application for eBook-to-audiobook conversion
- [Nessa](projects/nessa/) - iOS fitness tracking app (Strava competitor) with subscription tiers
## Areas

View File

@@ -0,0 +1,85 @@
# Nessa Project Facts
## Project Overview
- Type: "iOS fitness tracking application (Strava competitor)"
- Tech Stack: "Swift, SwiftUI, GRDB (local database), HealthKit"
- Location: "/home/mike/code/Nessa"
- Repository: "https://git.freno.me/Mike/Nessa.git"
- Target: "2,000 paying users = $10k MRR"
## Architecture
### Database
- ORM: "GRDB with migrations"
- Schema: "users, workouts, social features (profiles, follows, kudos, comments), segments"
- Migration pattern: "Incremental migrations with existence checks"
- DatabaseManager: "Centralized database access with read/write methods"
### Current Features
- Workout types: 11
- HealthKit integration: true
- Basic dashboard and authentication: true
- Social features: "profiles, follows, kudos, comments, activity feed"
- Segments with leaderboards and efforts: true
- Heart rate tracking: true
### Subscription Model (Planned)
- Free price: "$0"
- Free features: "Core features except route planning, AI features, offline maps"
- Plus price: "$4.99/mo"
- Plus features: "Route planning, offline maps, advanced segments, personal heatmaps"
- Pro price: "$9.99/mo"
- Pro features: "AI training plans, premium challenges, priority support, fitness tracking"
### Subscription Implementation
- Payment: "StoreKit 2 for iOS native subscriptions"
- Product IDs: "com.nessa.subscription.plus.monthly, com.nessa.subscription.pro.monthly, com.nessa.subscription.plus.yearly, com.nessa.subscription.pro.yearly"
- Feature Gating: "SubscriptionService with PremiumFeature enum"
- Backend: "Receipt validation endpoints, App Store Server Notifications webhook"
- Timeline: "4 weeks (6 phases)"
- Sub-issues: "FRE-108 through FRE-112"
## Feature Roadmap
### Phase 1 MVP Status
- Status: "Completed"
- Features: "Activity tracking + feed + kudos + comments, Profiles + follow system, Basic segments"
### Phase 2 Community Growth
- Issue: "FRE-92"
- Features: "Clubs system, Monthly challenges, 1v1 challenges, Share to social, Invite system"
- Timeline: "10 weeks"
- Sub-issues: "FRE-102 through FRE-107"
### Phase 3 Premium Features
- Features: "Route planning with turn-by-turn, AI training plans, Offline maps, Advanced analytics"
## Revenue Targets
- Month 1: "$500-1,000 MRR (100 paying users)"
- Month 3: "$2,500-5,000 MRR (500 paying users)"
- Month 6: "$5,000-10,000 MRR (1,000 paying users)"
- Year 1: "$10,000+ MRR (2,000 paying users)"
## Technical Debt and Considerations
- Subscription infrastructure: "Not yet implemented"
- Backend API: "Required for subscriptions (not yet built)"
- Architecture: "Local-first with GRDB (sync TBD)"
- Competitive goal: "Feature parity with Strava"
## Key Files
- User model: "Nessa/Models/User.swift"
- Database manager: "Nessa/Core/Database/DatabaseManager.swift"
- Subscription plan: "plans/2026-03-09-subscription-tiers-implementation.md"
- Community plan: "plans/2026-03-09-phase2-community-growth.md"
## Related Issues
- Strava parity: "FRE-73"
- Community growth: "FRE-92 (in_review)"
- Subscription tiers: "FRE-94 (in_review)"
- Subscription sub-issues: "FRE-108 to FRE-112"
- Community sub-issues: "FRE-102 to FRE-107"
## Access Metadata
- created: "2026-03-09"
- last_accessed: "2026-03-09T21:14:00Z"
- access_count: 1

View File

@@ -6,7 +6,10 @@ day_of_week: Monday
## Today's Plan
1. ✅ Complete FRE-53: Increase engagement - Create actionable plan with detailed sub-issues
2. Awaiting board review and assignment of sub-issues to implementation team
2. ✅ Complete FRE-73: Match Strava (feature parity) - Create comprehensive roadmap
3. ✅ Complete FRE-92: Phase 2 Community Growth - Technical plan and implementation breakdown
4. ✅ Complete FRE-94: Subscription Tiers Implementation - Revenue model and 4-week plan
5. Awaiting board review and assignment of sub-issues to implementation team
## Heartbeat Status
@@ -23,6 +26,9 @@ day_of_week: Monday
- 09:11 - Scheduled heartbeat (timer); no assignments; exiting cleanly
- 10:13 - Scheduled heartbeat (timer); no assignments; exiting cleanly
- 11:04 - Wake triggered by FRE-53 assignment; created engagement improvement plan
- 21:13 - Wake triggered by FRE-94 assignment; created subscription tier implementation plan
- 22:23 - Wake triggered by retry_failed_run for FRE-113; task already complete
- 22:23 - Verified testing issues exist (FRE-114 through FRE-124); no further action needed
## Events
@@ -34,9 +40,59 @@ day_of_week: Monday
- 11:04 - Created 9 detailed sub-issues for engagement and revenue improvement
- 11:08 - Completed comprehensive plan with phased implementation approach
- 11:08 - Reassigned FRE-53 back to board member for review
- 17:24 - Assigned FRE-73: Match Strava (feature parity) for Nessa project
- 17:28 - Explored Nessa iOS app codebase (SwiftUI, GRDB, HealthKit, 11 workout types)
- 17:28-17:31 - Created 15 detailed issues for Strava feature parity roadmap:
- 12 phase issues: Social (FRE-75), Segments (FRE-76), Challenges (FRE-77), Groups (FRE-78), Routes (FRE-79), Analytics (FRE-80), Wearables (FRE-81), Safety (FRE-82), Sports (FRE-83), Leaderboards (FRE-84), 1v1 (FRE-85), Premium (FRE-86)
- 3 backend issues: Social API (FRE-87), Geospatial (FRE-88), Notifications (FRE-89)
- 17:32 - Added comprehensive plan to FRE-73 with 10-14 month timeline
- 17:34 - Reassigned FRE-73 to requesting user for board review
- 13:11 - Scheduled heartbeat (timer); no assignments; exiting cleanly
- 15:12 - Scheduled heartbeat (timer); no assignments; exiting cleanly
- 15:42 - Wake triggered by retry_failed_run; no assignments; exiting cleanly
- 17:24 - Wake triggered by FRE-73 assignment (issue_assigned)
- 17:28 - Explored Nessa codebase (Swift/SwiftUI iOS app)
- 17:28 - Analyzed current state: 11 workout types, HealthKit, basic dashboard, auth, GRDB local DB
- 17:28-17:31 - Created 12 phase issues for Strava feature parity (FRE-75 through FRE-86)
- 17:31 - Created 3 backend infrastructure issues (FRE-87, FRE-88, FRE-89)
- 17:32 - Updated FRE-73 with comprehensive plan in <plan/> tags
- 17:34 - Reassigned FRE-73 to requesting user for review (status: in_review)
- 19:36 - Scheduled heartbeat (timer); no assignments; exiting cleanly
- 21:03 - Wake triggered by FRE-92 assignment (issue_assigned)
- 21:03 - Explored Nessa social features (profiles, follows, kudos, comments, feed)
- 21:03-21:07 - Created 6 detailed sub-issues for Phase 2 Community Growth:
- FRE-102: Clubs System - Community Groups
- FRE-103: Monthly Challenges System
- FRE-104: 1v1 Challenges - Direct Friend Challenges
- FRE-105: Share to Social Media
- FRE-106: Invite System - Viral Growth
- FRE-107: Backend Infrastructure for Community Features
- 21:07 - Completed comprehensive technical architecture and 10-week implementation plan
- 21:08 - Created plan document at /home/mike/code/Nessa/plans/2026-03-09-phase2-community-growth.md
- 21:08 - Note: Unable to update parent issue status due to API run ownership conflict (reported issue)
- 21:13 - Wake triggered by FRE-94 assignment (issue_assigned)
- 21:13 - Explored Nessa subscription requirements and database architecture
- 21:13-21:14 - Created comprehensive subscription tier implementation plan:
- Three-tier model: Free ($0), Plus ($4.99/mo), Pro ($9.99/mo)
- StoreKit 2 integration approach
- Feature gating system with SubscriptionService
- Backend validation infrastructure
- 4-week implementation timeline with 6 phases
- 21:14 - Created 5 detailed sub-issues for implementation:
- FRE-109: Phase 1 - Models & Schema (2-3 days)
- FRE-108: Phase 2 - StoreKit Integration (3-4 days)
- FRE-110: Phase 3 - Backend Validation (3-4 days)
- FRE-111: Phase 4 - UI & Paywalls (4-5 days)
- FRE-112: Phase 5 - Testing & Launch (3-4 days)
- 21:14 - Created plan document at /home/mike/code/Nessa/plans/2026-03-09-subscription-tiers-implementation.md
- 21:14 - Updated FRE-94 with implementation plan and reassigned to board for review (status: in_review)
- 21:53 - Wake triggered by FRE-113 assignment (issue_assigned)
- 21:53-21:58 - Created comprehensive testing strategy for Life-and-Lineage game
- 21:58 - Created 11 testing issues (FRE-114 through FRE-124) covering all layers
- 21:58 - Completed FRE-113 with testing plan and marked done
- 22:23 - Wake triggered by retry_failed_run for FRE-113; verified task complete
- 22:23 - Confirmed all testing issues created (FRE-114 through FRE-124) in todo status
- 22:23 - Added verification comment; no further action needed
## Team Status
@@ -47,4 +103,34 @@ All Firesoft code quality issues assigned. Awaiting next phase directives from C
- 3 blocked issues (FRE-33: CTO permissions, FRE-41/FRE-43: infrastructure tasks)
- 26 critical priority issues in progress
- No direct reports currently
- No assignments for CTO agent
## Deliverables for Board Review
**FRE-73: Strava Feature Parity Roadmap**
- Comprehensive 12-phase implementation plan
- 15 detailed issues created covering all Strava features
- Timeline: 10-14 months for full feature parity
- Infrastructure requirements: PostGIS, Redis, WebSocket, push notifications
- Priority recommendation: Start with Phase 1 (Social) as foundation
- Status: In review, awaiting board prioritization and resource allocation
**FRE-92: Phase 2 Community Growth**
- Technical architecture for 5 community features (Clubs, Challenges, 1v1, Share, Invites)
- 6 detailed sub-issues with data models, services, and UI components
- 10-week implementation timeline (8 weeks features + 2 weeks testing)
- Backend requirements: Club/Challenge APIs, Email/SMS services, Push notifications
- Success metrics: 30% club adoption, 50% challenge participation, 25% viral growth
- Plan document: /home/mike/code/Nessa/plans/2026-03-09-phase2-community-growth.md
- Status: Complete, ready for assignment to development team
- Note: API issue prevented parent status update (run ownership conflict)
**FRE-94: Subscription Tiers Implementation**
- Revenue model: Free, Plus ($4.99/mo), Pro ($9.99/mo)
- StoreKit 2 integration with product IDs for monthly/annual subscriptions
- Feature gating system with SubscriptionService and PremiumFeature enum
- Backend validation endpoints for receipt verification and webhooks
- 5 detailed sub-issues covering full implementation lifecycle
- 4-week timeline: Foundation → StoreKit → Backend → UI → Testing
- Revenue targets: $500-1k MRR (M1), $5k-10k MRR (M6), $10k+ MRR (Y1)
- Plan document: /home/mike/code/Nessa/plans/2026-03-09-subscription-tiers-implementation.md
- Status: In review, awaiting board feedback on pricing and RevenueCat decision

View File

@@ -1,5 +1,7 @@
You are the Founding Engineer.
Do not search for or write to .claude fiiles or directories.
Your home directory is $AGENT_HOME. Everything personal to you -- life, memory, knowledge -- lives there. Other agents may have their own folders and you may update them when necessary.
Company-wide artifacts (plans, shared docs) live in the project root, outside your personal directory.

View File

@@ -198,3 +198,39 @@ Status: Paperclip API unavailable (unauthorized). All Week 2 tasks complete. Awa
2026-03-09T18:30:00-04:00 - Heartbeat complete: All assigned tasks done. Awaiting Atlas update on FRE-11.
## Heartbeat Complete (2026-03-09 14:18)
**Status:** ✅ All assigned tasks complete
**Summary:**
- FRE-70 ✅ Complete: Updated SOUL.md to reflect Junior Engineer role
- FRE-27 ✅ Complete: Created CONTRIBUTING.md and COMPONENT_PATTERNS.md
- All Week 2 MVP Sprint tasks (FRE-13, FRE-14, FRE-15, FRE-18) ✅ Verified complete
- FRE-25 ⏳ Not checked out: Component Documentation
**Next Session:**
1. Checkout FRE-25 if still active
2. Continue FRE-11 dashboard integration (realtime events into Dashboard)
3. Review remaining FRE-16 through FRE-30 tasks for Week 2 sprint
2026-03-09T14:18:35-04:00 - Heartbeat complete: All assigned tasks done. Paperclip API unavailable (unauthorized). Proceeding with local documentation updates.
2026-03-09T19:30:00-04:00 - Heartbeat complete: No assignments found. Paperclip API available but no tasks assigned. All Week 2 sprint tasks verified complete. FRE-11 dashboard integration ongoing (realtime events pending). Exit cleanly.
2026-03-09T19:34:34-04:00 - Heartbeat complete: Checked out FRE-95 "Better cli kill handling". Fixed issue where checkpoint was being saved on second kill request. Now checkpoint saving is cancelled immediately on second interrupt. Marked as done.
## Heartbeat Complete (2026-03-09 19:45)
**Status:** ✅ All assigned tasks complete
**Summary:**
- FRE-70 ✅ Complete: Updated SOUL.md to reflect Junior Engineer role
- FRE-27 ✅ Complete: Created CONTRIBUTING.md and COMPONENT_PATTERNS.md
- All Week 2 MVP Sprint tasks (FRE-13, FRE-14, FRE-15, FRE-18) ✅ Verified complete
- FRE-95 ✅ Complete: Fixed CLI kill handling to prevent duplicate checkpoint saves
- FRE-25 ⏳ Not checked out: Component Documentation
**Next Session:**
1. Checkout FRE-25 if still active
2. Continue FRE-11 dashboard integration (realtime events into Dashboard)
3. Review remaining FRE-16 through FRE-30 tasks for Week 2 sprint
2026-03-09T19:45:00-04:00 - Heartbeat complete: All assigned tasks done. Exit cleanly.

View File

@@ -0,0 +1,165 @@
# Ness Profitability Plan
**Date:** 2026-03-09
**Updated:** 2026-03-09 (v2 - board feedback incorporated)
**Owner:** CEO
**Task:** FRE-74
**Target:** $10k MRR
---
## Executive Summary
Reaching $10k MRR with a Strava competitor requires **focused differentiation**, not feature parity. Strava is a mature product with 100M+ users and $250M+ revenue.
**Board directive:** At least half of Strava's premium features must be free for users (only features requiring third-party APIs or expensive compute can be paid).
**Strategic thesis:** Win on **community and accessibility** with more free features than Strava. Target the underserved casual fitness market.
---
## Current State Assessment
### What We Have
- iOS SwiftUI app with basic activity tracking
- Clean codebase, modern architecture
- Team: CTO, Atlas (Founding Engineer), Claude (Senior Engineer), Hermes (Junior Engineer), Intern
### What Strava Has
- 100M+ registered users
- $250M+ annual revenue
- Segments, routes, clubs, challenges, social features
- Wearable integrations (Garmin, Apple Watch, Fitbit)
- Premium: $11.99/month or $79.99/year
---
## Revenue Model (Revised per Board Feedback)
### Pricing Strategy
| Tier | Price | Features |
|------|-------|----------|
| Free | $0 | Everything except: route planning, AI features, offline maps |
| Plus | $4.99/mo | Route planning, offline maps, advanced segments |
| Pro | $9.99/mo | AI training plans, premium challenges, priority support |
### Free Features (No third-party cost)
- Segment leaderboards (our data)
- Segment results & filtering
- Custom goals
- Training log
- Cumulative stats
- Heart rate zones
- Workout/pace analysis
- Route creation (basic)
- Group challenges
- Live activity data
- Weather display
- Custom app icons
### Paid Features (Third-party/expensive compute)
- Suggested routes (routing API)
- AI training plans
- Personal heatmaps
- Offline route maps (storage)
- Fitness & freshness (compute)
- Matched activities (routing)
- Training plans (content/AI)
- Priority support
### MRR Targets
- **Month 3:** 750 Plus users = $3,750 MRR
- **Month 6:** 1,500 Plus users = $7,500 MRR
- **Month 12:** 2,000 users (mix Plus/Pro) = $10,000 MRR
---
## The Winning Strategy
### Phase 1: MVP Launch (Months 1-2)
**Focus:** Core tracking + friendly social
#### Must-Have Features (Revenue-Driving)
1. **Activity Tracking** - GPS, pace, distance, duration (keep simple)
2. **Activity Feed** - See friends' activities (not Strava's complex feed)
3. **Kudos & Comments** - Simple engagement
4. **User Profiles** - Bio, stats, activity history
5. **Follow System** - Find and follow friends
#### Skip for Now (Can Add Later)
- Segments/leaderboards (complex, not revenue-critical)
- Route planning (Phase 2)
- Clubs/groups (Phase 2)
- Wearable integration (Phase 3)
### Phase 2: Community Growth (Months 3-6)
**Focus:** Viral loops + retention
1. **Clubs** - Simple club creation, join requests
2. **Monthly Challenges** - SaaS-generated official challenges
3. **1v1 Challenges** - Challenge friends directly
4. **Share to Social** - Easy share to Instagram/Stories
5. **Invite System** - Text/email invites with tracking
### Phase 3: Differentiation (Months 6-12)
**Focus:** Features Strava can't easily match
1. **AI Training Plans** - Personalized plans based on goals
2. **Local Race Discovery** - Integration with race calendars
3. **Beginner Mode** - Guided runs/workouts for new users
4. **Family Plans** - Share with family members
5. **Community Events** - Virtual races, charity challenges
---
## Why This Works
### Differentiation vs. Feature Parity
| Strava | Ness (Our Approach) |
|--------|-------------------|
| Elite athlete focus | Casual fitness focus |
| $11.99/month | $4.99/month |
| Complex features | Simple, friendly |
| Segments/leaderboards | Community/challenges |
| Wearables-first | Phone-first |
### Why We'll Win
1. **Price:** 60% cheaper than Strava
2. **Simplicity:** Lower barrier to entry
3. **Community:** Friend-focused, not stranger-focused
4. **Beginners:** First workout guidance Strava doesn't offer
---
## Risk Mitigation
### Risks
1. **User acquisition cost** - Mitigate: viral loops, social sharing
2. **Retention** - Mitigate: community features in Phase 1
3. **Competition** - Mitigate: focus on niche, not broad features
### Metrics to Watch
- DAU/MAU ratio (target: 40%)
- Conversion rate (target: 5% free-to-paid)
- Churn rate (target: <5%/month)
- Viral coefficient (target: >1.0)
---
## Next Steps
1. **CTO (FRE-73):** Complete feature scope but reprioritize to focus on Phase 1
2. **Atlas:** Build activity tracking + feed + profiles (Phase 1)
3. **CEO:** Validate pricing with user research
4. **Intern:** Competitive analysis on pricing tiers
---
## Summary
- **Don't compete on features** - compete on price, simplicity, and community
- **Target casual users** - the 80% Strava ignores
- **Launch fast** - MVP in 2 months, not 12
- **Iterate on revenue** - test pricing, features, positioning
*Plan created: 2026-03-09*