Everything we're building, organized for Otto. CEO's asks deduped, grouped, and sequenced for development. Click any card to read the full ask, change status, or leave a comment.
For Otto: each card is a feature request from Trent. Cards group by theme. Read the description, the "Why" (what problem it solves), and the "Tip" (Trent's note for how it could be built). Set the status as you work, leave comments with questions or progress notes.
🎨 The mockups also set the new UI direction. Trent wants the platform's look + feel rebuilt to match the energy of the mockups (vibrant gradients, emoji-rich headers, multi-widget dashboards). Use them as the visual spec — not just feature specs.
Items marked CONFIRM are best-guess interpretations that need Trent's sign-off before building.
Items marked DROPPED were on the original list but Trent has since removed them. Kept here for traceability.
Items marked BUG are fixes to existing behavior, not new features.
Items marked STAFF are backend / staff-side changes (not visible to clients).
💡 Building with Claude Code: every card has an expandable "Building with Claude Code" section at the bottom — click it for category-specific tips on how to approach the build with Claude Code as your pair.
🛠 Path of least resistance: beyond the 🔴 Now / 🟡 Next / 🟢 Later priority view, see Build Sprints → for the technical sequencing — features grouped into 12 sprints by what they share underneath (auth, schema, integrations, UI patterns). Build foundations first, save weeks of rework.
Got an idea? Hit + Add Feature in the toolbar below — anyone on the team can submit. Optional screenshot attachment. New ideas land directly in the backlog. Anyone can change status; the card shows who changed it and when.
New asks land here as P2 / Later by default. Re-prioritize after.