Every product gets the full loop.
Each project is a self-contained world — its own inbox, roadmap, widget, changelog, docs and vote weights. Switch between products without losing your place.
One account, all your products.
Side project and main product? Agency with clients? Spin up a project per product and keep every loop separate — while your team and billing stay in one place.
- Isolated everything — feedback, roadmap, votes and branding per project.
- Project slugs — each project gets its own public pages and widget key.
- Per-project vote weights — weight differently for consumer vs. enterprise products.
Roles that match how teams work.
Invite by email, work by role. Keep internal notes internal, publish only what's ready, and never share an admin account again.
- Email invites — teammates join from their inbox, no onboarding doc needed.
- Public vs. internal — every item has a face for voters and a backstage for you.
- API keys & OAuth apps — scoped and revocable; the same key powers your MCP agents.
- Two-factor authentication — authenticator apps for everyone, and required for the whole account on Team.
Write it once. Every agent reads it.
Project docs aren't just a wiki — they're what your AI agents load before writing a line of code. Architecture, conventions, critical rules, code templates. Keep them current and every task starts smart.
- Critical rules — the non-negotiables agents must not break.
- Code templates — teach agents your service, component and test patterns.
- Module registry — monorepo paths and ports so agents edit the right package.
Give your team — and agents — a home.
Create a project, invite the team, publish the roadmap. Minutes, not meetings.
Where this fits in the loop.
Collect
Catch feedback where it happens — in your app, in Slack, on a call — and land it in one clean inbox.
Prioritize
Rank requests by who is asking. Votes are weighted by plan, so paying customers move the roadmap.
Build
Hand the top task to your AI coding agent with the rules that govern it — and get proof when it is done.
Ship
Shipped work becomes a changelog entry, and everyone who asked for it hears first.
Around the loop
Docs, uptime, errors and team access — the product ops that sit next to the loop.