Product Roadmap

This roadmap separates the current repository state from future product work.

Phase 0: App foundation#

Goal: make the base app, auth, API, docs, and account flows coherent.

Current build:

• marketing and documentation routes
• signup, login, email verification, account page, and session handling
• Better Auth database schema
• Hono and oRPC API
• generated OpenAPI docs
• status and authenticated user endpoints

Proof:

• users can create and verify accounts
• authenticated account state works
• API docs match the implemented contract
• docs do not claim nonexistent product capabilities

Phase 1: Implementation operations#

Goal: prove that Arn can create a trusted, source-backed implementation record from communication.

Build:

• first communication connector
• first account-system import
• event store and relationship timeline
• implementation relationship record
• workstreams
• blocker, decision, task, file, owner, risk, deadline, and commitment extraction
• source-backed implementation brief
• internal approval before customer-visible publishing
• first customer-facing status projection
• approved sync for status, risks, and next steps

Avoid:

• generic project management
• full ticketing
• full CLM
• source-to-pay procurement
• broad workflow builders
• unsupported connector breadth

Phase 2: Relationship operations#

Goal: make the relationship record useful beyond initial implementation.

Build:

• account and vendor briefs
• renewal and escalation workstreams
• decision logs and commitment tracking
• relationship-aware file inventory
• contract and obligation summaries
• support and customer-success context sync
• portfolio views across customers and vendors
• stronger external participant management

Phase 3: Vendor and partner coordination#

Goal: extend the same model to vendor and partner dependencies without becoming a procurement suite.

Build:

• vendor onboarding workstreams
• compliance document collection
• vendor communication timelines
• portal sync for delivery and status changes
• PO, invoice, and payment question context
• vendor risk and performance summaries
• multi-vendor dependencies tied to customer delivery
• procurement and finance sync where approved

Phase 4: B2B OS foundations#

Goal: make Arn the operating layer for multi-organization work.

Build:

• connector SDK
• organization and identity graph
• cross-channel thread stitching
• relationship-scoped RBAC
• field-level and document-level policies
• permission-aware search and retrieval
• source confidence model
• summary approval workflows
• sync rule engine
• audit, retention, and export controls
• workflow orchestration for high-touch relationship work

Product bets#

• Communication first: the product is only valuable if it captures channels where work already happens.
• Evidence over vibes: summaries, health, risks, and decisions need source links.
• Permissioning as product: external collaboration is only useful when visibility is precise.
• Approve before sync: downstream systems should be updated deliberately.
• Wedge before platform: implementation operations should work before the broader B2B OS is claimed.