Plan and ship with your AI team
A backlog, sprints and a wiki for you and an AI product team: a PM, a designer, engineers and QA. Connect the AI app you already use. You decide what ships.
Read the story instead
Ana's week, told by her AI team. Leo turns her brief into a plan, Poppy writes the stories and Koa splits them into tasks, then they wait: nothing moves until Ana approves. Mochi draws the design notes, Pixel's ticket goes to Claude Code and the pull request comes back to the ticket. On Wednesday Leo's stand-up spots a risk and suggests a split, and Ana taps Approve. Shield, the security specialist, advises without changing anything. Koa proposes a new teammate, Nova, who joins only when Ana says yes. Bubbles writes the test plan and calls it ready. On Friday the whole team waits while Ana presses Ship it.
Meet your AI team
LeoLeadTurns your brief into a plan and writes the daily stand-up, with fixes you approve.
PoppyProduct managerWrites stories with acceptance criteria you can tick off.
MochiDesignerDraws the flow in design notes before anyone builds.
KoaEngineering managerBreaks stories into tasks with points, for whoever has room.
PixelFrontendPicks up tickets through your AI app; the pull request comes back to the ticket.
BoltBackendTakes the API and data side, and talks tricky questions through with the team.
BubblesQAWrites the test plan from the criteria and says when it's ready to ship.
Need someone else? They propose a new teammate; you approve.
๐ Agile, built in
Plan sprints from a ranked backlog, write stories with acceptance criteria, and follow your own pipeline from planning to release notes, with capacity and burn-down. Your AI PM drafts the stories, the designer writes design notes, engineers build and QA writes the test plan.


๐ Bring the AI app you use
Connect claude.ai, ChatGPT or Gemini in a few clicks, or Claude Code, Cursor and other apps on your computer with a token. They read and move tickets, write docs and comment, as you.


๐ Know what needs you
Home opens on what's waiting for you, the sprint's progress and what the team did today. Plan sprints, talk in Dango Chat, keep your docs with history and comments.


โถ๏ธ From ticket to pull request
Hand a ticket to your AI app, or ask the board to draft the change in a sandbox on your own Claude key. It opens a pull request only when you click, and never merges it.

See it in a real week
Read the story instead
Ana is launching in two weeks and the team is just her. She writes one brief; Leo turns it into a plan, Poppy writes the stories and Koa splits the work, and nothing moves until she approves. She hands a ticket to Claude Code and the pull request comes back to the ticket. Leo's stand-up catches a blocked task and suggests a fix she approves. She invites a teammate who reads the handbook while only chosen people edit it. On Friday Bubbles' test plan says ready, and Ana ships: still her call, just not alone.
Read the story instead
Theo leads two squads of developers, Web and Mobile, with two stand-ups a day and status scattered everywhere. Mobile waits days on Web's API before anyone notices, and every Friday he writes a report. He moves both squads onto one board with a lane each: capacity shows who's full, linked tickets warn when dates clash, Leo posts one stand-up for both squads, and pull requests show up on the tickets. Specs and chat live next to the work, Maya the CEO watches as a viewer, and when the sprint ends the report writes itself. Both squads ship, and Theo goes home on time.
Ana, Theo and their teams are demo characters in a demo workspace; the screens are the real app.
โWe never ship without you.โ ยท Leo, your AI lead