Roadmap

Current Quarter Q1 2026: Jan--Mar

Theme: Launch ready

Big Bet: Full platform live with first paying customer -- web + iOS + browser extensions all working, App Store approved, and real users validating willingness to pay $99/month.

Milestones

• CI/CD green (Completed: 2026-02-06)
  All CI jobs passing: lint, security scans, unit tests, system tests. 63 runs, 0 failures, 0 errors.
• iOS App Store submission (Target: 2026-02-15)
  iOS v24 tested on device, screenshots captured, submitted to App Store Connect with test account.
• First paying customer (Target: 2026-02-28)
  At least one workspace on a paid Solo or Team plan creating real content through the pipeline.
• Browser extension beta (Target: 2026-03-15)
  Chrome + Firefox extensions shipped to 3--5 beta testers with testing materials.
• Platform stable at v1.0 (Target: 2026-03-31)
  Web (authexis.app), iOS (App Store), and extensions all working reliably for daily use. Un-skip remaining system tests as features land.

Why this quarter

Launch ready is about crossing the finish line on a product that's been in active development since Q4 2025. The core content pipeline works -- AI characters research, interview, and generate thought leadership content through a 7-stage approval workflow. Now it needs to reach real users.

This aligns with PRODUCT.md principles:

• Principle #3 (Control at every stage): The pipeline is battle-tested with config-driven architecture
• Principle #5 (Multi-platform from day one): Web + iOS + extensions deliver on the multi-platform promise
• Success metric: First active workspace creating content validates the core value proposition

The through-line: CI green proves the code works, App Store proves the product is real, first customer proves the market exists.

Next Quarter Q2 2026: Apr--Jun

Theme: User acquisition

Big Bet: Content marketing and partner program activation drive first 50 active workspaces.

Output-mode sequencing

• Use Phase 1 export telemetry to decide whether branded outputs are worth the build.
• If usage is real, prioritize branded PDF first, branded DOCX second, and Google Slides partnership before any native deck work.
• Defer EPUB until long-form/institutional demand is visible.

Free/Pro launch infrastructure

• Ship workspace monthly content quota, centralized tier gates, inline upgrade prompts, and free-tier engine cost controls before enabling a public free tier.
• Keep pricing/landing copy updates separate from the infrastructure build, but reconcile any "no usage limits" copy before launch.

Public API and MCP

• Stabilize /api/v1 as the documented public REST contract for content, ideas, publishing, exports, workspace context, and integrations.
• Rework the MCP server so public MCP behavior wraps /api/v1 instead of duplicating database mutations.

Open questions

• Which acquisition channel produces highest-quality leads (LinkedIn, partner referrals, content marketing)?
• Is $99/month the right price point or does it need adjustment based on conversion data?
• After free-tier infrastructure ships, does capped free convert better than the 14-day full-access trial?
• Should we prioritize partner program (35--40% commission) or direct acquisition?

Past Quarters

Q4 2025 Oct--Dec

Theme: Foundation

Outcome: Built the complete Authexis platform from Rails 8 scaffold to working product. Shipped: multi-stage content pipeline, AI character system (Maya, Igor, Sydney, Trina), config-driven architecture, iOS native app (SwiftUI), email-first workflow, workspace/team management, Stripe billing, personal access tokens, browser extension (Chrome/Firefox), feature flags, RSS feeds, content export (Hugo/Jekyll/11ty/markdown).

Learnings

• Config-driven architecture (JSONB content types) was the right call -- new content types without code changes
• Email-first workflow resonated in early testing (3hr response vs 2-day dashboard check)
• Monorepo structure works well for cross-platform development
• Production database in dev eliminates schema drift but requires extra care

Roadmap principles

This roadmap is:

• Quarterly themes, not rigid project plans
• Big bets, not comprehensive feature lists
• Strategic direction, not tactical execution
• Living document, updated as you learn

How to use this:

Review quarterly

What theme for next 3 months?

Plan weekly

Which milestones are active?

Reference daily

Does this TODO align with current theme?

Learn continuously

Update "Learnings" when quarter ends.