{"generatedAt":"2026-05-08T14:08:49.968Z","phases":[{"key":"now","phase":"Now (Q2 2026)","cadence":"Shipping in the next few revisions","items":[{"key":"stripe-checkout","title":"Stripe checkout + plan upgrade flow","status":"next","description":"Plan limits already bite (free=3 sources / 15-min loop floor; pro=25 / 5-min; team=100 / 1-min). The upgrade CTA is wired and the daily cost cap creates a clean 'upgrade for higher cap' upsell on top of the source cap. Stripe Checkout is the only remaining monetisation gate."},{"key":"mcp-server","title":"MCP (Model Context Protocol) server","status":"next","description":"Thin wrapper around /api/v1 — no design work left, only protocol-translation. Exposes signals, tasks, artifacts, memory, search, stats, focus tags, comment reactions, blockers, and bulk operations as MCP tools so Claude Desktop, Cursor, and any MCP-compatible host can drive a workspace. ~1 day of wrapping work."},{"key":"slack-interactive-approvals","title":"Slack interactive approvals","status":"soon","description":"Approve / archive / regenerate buttons inside the cycle-brief Slack post (Slack interactive components). Slack already carries 25+ push channels (briefs, scheduled pause, cost cap, cost spike, due reminders, comment @-mentions, memory promotions, mention acks, ad-hoc artifact pushes, task unblocked, stuck loop, stale tasks, task auto-archived, archive warnings, cost spikes per-task/per-source/per-tag/per-assignee, chronic warnings on 3 axes, source resumed, digest gating change) — interactive buttons in the brief block are the highest-leverage step before the loop becomes 'approve from chat without ever opening the dashboard'."},{"key":"mailgun-postmark-dns","title":"Mailgun / Postmark inbound email DNS config","status":"soon","description":"The /api/webhooks/email/[token] endpoint shipped rev 7 with HMAC verification (rev 13), but it still needs DNS configuration so every workspace can receive forwarded customer email at <token>@in.loopdesk.space. One-time infra setup; unlocks the same flow for every workspace."}]},{"key":"next","phase":"Next (Q3 2026)","cadence":"Designed; pending Now-phase completion","items":[{"key":"mcp-announcement-post","title":"MCP server announcement post","status":"next","description":"Once the MCP server lands, a dedicated marketing post explaining 'Loop Desk now speaks MCP' to the 18,000+ MCP-server community. The v1 surface is functionally complete — this is the natural Q3 launch moment."},{"key":"task-dependency-graph","title":"Task dependency graph (visual)","status":"soon","description":"Rev 36 made dependencies a real queue gate; rev 37 made unblocking push-loud; rev 38 added a list-view dependency surface. Workspaces with 20+ interrelated tasks across multi-step workflows would benefit from a real DAG render — natural extension of the rev-38 list view."},{"key":"shopify-etsy-webhooks","title":"Shopify + Etsy order webhooks","status":"considering","description":"Schema types exist (`shopify`, `etsy` source kinds) but the webhook receivers and signal generators aren't wired. Highest-leverage signal source for the e-commerce slice of our ICP after the existing RSS / review-site / LinkedIn / email / inbound HTTP coverage."},{"key":"iso-42001-cert","title":"ISO 42001 third-party certification","status":"considering","description":"Architectural alignment + governance docs landed rev 13. A real certification (vs. self-assessed alignment) is the next procurement-blocker remover for B2B enterprise customers."}]},{"key":"later","phase":"Later","cadence":"On the radar; happy to be talked into pulling forward","items":[{"key":"per-role-ui-controls","title":"Per-role granular UI controls","status":"considering","description":"Viewer gating is wired at the API layer (rev 16) and at the dashboard's top-level forms — per-item controls on signals/memory/tasks still 403 silently rather than render disabled. Acceptable for now; refine when a real viewer use case emerges."},{"key":"mobile-app","title":"Mobile app (iOS / Android)","status":"considering","description":"The dashboard has been mobile-responsive since rev 14 with three breakpoints (900/768/480). A native app is a meaningful step beyond that — but only if the existing mobile-web flow is a bottleneck for real users, which it currently isn't."},{"key":"blog-comments","title":"Blog post comments","status":"considering","description":"/blog has shipped 31 founder-operator posts since rev 14. A lightweight comment thread on each post would close the operator-feedback loop on marketing surface and surface ICP voice for future blog topics."},{"key":"dashboard-visual-refresh","title":"Dashboard visual refresh","status":"considering","description":"The dashboard has accumulated 30+ panels across 96+ revs of incremental polish. A bigger visual story (refreshed typography scale, a denser one-pane mode, a different colour vocabulary for the cost-axis cluster) would compound the existing rev-by-rev micro-polish discipline."}]}]}