The CollectHive Roadmap
How to Read This
This isn’t a product roadmap in the traditional sense. CollectHive is a co-operative, not a SaaS company. The roadmap reflects what the community needs next, not what a product team decided in a quarterly planning session.
Every item has a status: done, in progress, next, or future. We don’t attach dates to “next” and “future” items because we’ve learned — ten weeks of learning, specifically — that timelines shift. What matters is the sequence and the reasoning. Items move based on what we discover, not what we predicted.
The Shared Brain
The infrastructure that makes CollectHive a co-operative, not just a platform. Everything else depends on this.
| Item | Status | Notes |
|---|---|---|
| Memory MCP server (store, recall, compound) | Done | Running in production |
| Three-environment pipeline (local, staging, prod) | Done | Automated deploys |
| Cross-user knowledge promotion | Done | Human-gated — you approve what’s shared |
| Heartbeat system (autonomous agent execution) | Done | Per-user, scoped, budgeted |
| Amber Monitor (cross-environment dashboard) | In Progress | Health visibility across all environments |
| Self-healing Convex restarts | Next | Auto-recovery with data integrity checks |
| Canary deploys with auto-rollback | Next | Deploy, health-check, auto-rollback if failing |
| Server-based monitoring | Next | Prerequisite for reliable alerting |
Idea-to-App Pipeline
| Item | Status | Notes |
|---|---|---|
| Phase 1: Idea to Preview | Done | Conversation to live prototype in minutes |
| Phase 2: Preview to Plan (gap analysis) | In Progress | Structure exists, end-to-end validation pending |
| Phase 3: Plan to App (commit-per-step) | Next | Container orchestration works, full loop untested |
| App type catalog (community-facing) | Next | Template library from patterns graduated by members |
| One-click deploy from catalog | Future | Pick a pattern, describe your app, get a live URL |
Strategic Agents
Building the app is only the first part. What about marketing? Business model? Exit? Strategic agents handle the stuff that isn’t code.
| Item | Status | Notes |
|---|---|---|
| Memory-backed decision context | Done | Agents recall prior decisions and reasoning |
| Marketing Growth Agent | Next | Visibility, conversion, acquisition |
| Ideation Algorithm Agent | Next | Product-market fit analysis for SMBs |
| Exits Agent | Future | Valuation, buyer identification, deal structure |
| Consulting delivery framework | Future | How members deliver strategic services |
Beyond the Members
When the pattern catalog matures, there are options: open it to a wider community, use it as the backbone for B2B consulting, or package it as a SaaS product. None of these are commitments — they are paths that become available once the foundation is strong enough.
| Item | Status | Notes |
|---|---|---|
| Members building new patterns | Done | Testing new app types, expanding the catalog |
| Pattern graduation process | In Progress | How a member’s app becomes a reusable template |
| Community onboarding flow | Future | Sign up, pick a pattern, start building |
| Community launch | Future | Depends on catalog having 5+ proven patterns |
| B2B consulting / SaaS path | Future | Patterns as the basis for external delivery |
Privacy and Governance
| Item | Status | Notes |
|---|---|---|
| Project-scoped memory isolation | Done | Your data stays in your scope |
| Human-gated promotion (user to hive) | Done | No automatic cross-user sharing |
| Personal project privacy | In Progress | Use platform for personal work without team visibility |
| Granular sharing controls | Future | Share specific learnings, not entire project history |
| Data export and portability | Future | Download everything, migrate anywhere |
What’s Deliberately Not on the Roadmap
Not everything belongs here. Some things are conscious choices to say “not now.”
Mobile app: the platform works in mobile browsers. A native app adds complexity without clear value.
Public API: CollectHive’s interface is conversation, not code. We’re not building for developers who want to integrate programmatically.
Enterprise features: SSO, audit logs, compliance certifications. We’re a co-operative of small teams and individual founders. If we need these later, we’ll build them later.
How Priorities Are Decided
Three questions, in order. Does it unblock the next builder? If a member can’t build their app because something is missing, that gets fixed first. Does it make the shared brain more reliable? Infrastructure improvements that prevent incidents and protect the knowledge base outrank new features. Does it expand what’s possible? New capabilities come after foundation and reliability.
We don’t build features because they’re exciting. We build them because someone in the co-operative needs them next.