DR-2026-003: Project SaaS Renamed to Legionis (legionis.ai)

Context

The project began as a SaaS wrapper for the Product Org OS plugin — web/desktop client with cloud storage to make the 39-agent product organization accessible to non-CLI users.

The working title "OrgPro" was flagged by VP Product for category dilution concerns. The name positioned the product narrowly as a product-org-specific tool, which:

Created artificial ceiling on market size
Obscured the broader vision: giving anyone teams of agents to augment their work
Conflicted with the underlying architecture (the OS is one team module; the platform can support many team types)

Domain availability: legionis.ai acquired and ready for use.

Options Considered

Option A: Keep "OrgPro"

Pros: Clear positioning (product organization), strong connection to Product Org OS brand
Cons: Narrow market definition, category dilution with "OS", limits expansion potential
Rejected because: The product is architecturally general-purpose (39 agents is just one team, architecture supports multiple team modules), and market opportunity is broader than product orgs

Option B: "Legionis" [CHOSEN]

Etymology: From Latin "legio" (legion) — organized units of specialized agents working together
Positioning: AI workforce platform, not just product org tool
Domain: legionis.ai (acquired)
Tagline candidates: "Your AI Workforce" | "Teams of Agents, On Demand" | "The Legion You Need"
Market: Any knowledge worker who needs specialized teams (product, engineering, design, sales, marketing, finance, legal)

Option C: Generic descriptive name (e.g., "TeamFlow", "AgentForce")

Rejected because: Harder to own, weaker brand differentiation, doesn't convey the multi-team concept

Rationale

The core insight: The Product Org OS v3.0 is the first team module for Legionis, not the entire product.

Legionis is a general platform where users can:

Deploy teams of agents for different work domains

Product Org (39 agents) is the flagship team, fully implemented

Future teams: Engineering Org, Design Studio, Sales Legion, Marketing Brigade, Finance Team, Legal Counsel, etc.

Each team = specialized agents + skills + workflows + context layer

This positioning:

Opens addressable market from ~100K product leaders to millions of knowledge workers
Aligns with architectural reality (team modules are swappable/expandable)
Differentiates from "ChatGPT for X" single-agent tools and from workflow automation platforms
Creates expansion revenue path: start with one team (Product), add more teams as needs evolve

What Changed

Immediate

Project name: "Project SaaS" → Legionis

Domain: legionis.ai (production app: app.legionis.ai)

Repository naming: Update from "orgpro" to "legionis" when convenient (not P0)

Execution plan: References to "OrgPro" remain in V3.0 (already in progress), update in V4.0

Marketing & GTM

Positioning statement (to be created):

- FROM: "AI-powered product organization for product leaders" - TO: "AI workforce platform — deploy specialized agent teams for any knowledge work domain"

Value proposition:

- FROM: "39 product org agents + 61 skills" - TO: "Deploy your AI workforce: Product teams, engineering teams, design studios (more coming)"

Landing page messaging: Emphasize "teams of agents" concept, not single-tool focus

ICP expansion: Product leaders (first), then CTOs, design leaders, CMOs, CFOs

Product

First team module: Product Org OS v3.0 (39 agents, 61 skills, 8 gateways, V2V framework)

Future modules roadmap:

- Engineering Legion (architecture, backend, frontend, DevOps, QA agents) - Design Studio (already scaffolded in Extension Teams: 6 agents) - Marketing Brigade (already scaffolded: 14 agents) - Sales Legion (discovery, qualification, outreach, closing agents) - Finance Team (FP&A, accounting, compliance agents)

Pricing evolution: Teams sold as add-ons (e.g., $10/mo base + $5/team/mo), bundle discounts

Architecture

Team modules as pluggable units: each has teams/{team-name}/agents/, teams/{team-name}/skills/, teams/{team-name}/rules/
Shared core: L1 protocol, context layer, file operations, gateway orchestration
Per-team L2/L3 prompts compiled from team-specific source

Success Criteria

Brand recognition: "Legionis" becomes associated with "AI workforce platform" (not narrowly "product org tool")

Market expansion: Attract users beyond product org (engineering, design, marketing roles)

Product roadmap: 2nd team module shipped within 6 months of launch (likely Engineering or Design)

Revenue: Multi-team users account for >30% MRR within 12 months

Re-Decision Triggers

If brand confusion arises (users don't understand "what is a legion?"), reconsider simpler naming

If Product Org remains 90%+ of usage after 12 months, evaluate whether general positioning was premature

If domain name issues arise (trademark conflicts, pronunciation confusion), consider alternatives

Migration Path

Documentation

CLAUDE.md: Update project name in workspace table
business-portfolio.md: Update from "Project SaaS" to "Legionis"
Execution plan V4.0: Full "OrgPro" → "Legionis" replacement
PRD: Update branding, positioning, naming throughout

Code

Current repo: C:\dev\orgpro (can stay for now, local only)
Vercel project: Create new project legionis (or rename existing)
Environment variables: Update NEXT_PUBLIC_APP_URL to https://app.legionis.ai
Not urgent: Code references to "orgpro" are internal, can migrate gradually

External

Domain: Point legionis.ai to Vercel project
SSL: Configure for app.legionis.ai
Stripe: Update product names to "Legionis Individual", "Legionis Team"
Google OAuth: Update redirect URIs to legionis.ai domain
Landing page: Build at legionis.ai (not orgpro.ai — don't acquire)

Cross-References

Related to: DR-2026-001 (Full-Capability Day 1 Pivot) — both expand scope beyond MVP minimalism
Impacts: Product Org OS positioning (now "flagship team module" not "entire product")
Impacts: GTM strategy (broader ICP, multi-team revenue model)
Impacts: Roadmap prioritization (2nd team module becomes P1 after launch)

Documented: 2026-02-14 Domain acquired: legionis.ai Supersedes working title: "OrgPro"