About CardBoard
CardBoard is a user story mapping tool that syncs two-way with Jira and Azure DevOps, so product teams and their AI agents build what the team meant.
The original story mapping tool, since 2012. More than 235,000 boards. Used by product teams at Target, Nike, and Verizon.
What CardBoard does
User story mapping
Lay out the user's journey as a backbone of activities, break it into tasks, and draw release slices across it. Cards snap to a real structure instead of floating as sticky notes, so the map still makes sense a month after the workshop.
Two dozen map types
Beyond story maps, CardBoard ships sitemaps, kanban, journey maps, personas, the business model canvas, retros, mind maps, process maps, and more. Each map type knows its own rules, so a team can go from persona to story map to kanban in one workspace.
Two-way Jira and Azure DevOps sync
Connect a board to Jira or Azure DevOps and cards become real work items. Changes flow both ways, so the map and the backlog never drift apart, while card position stays yours to move.
AI agents that read the map
Point Claude, Cursor, or any MCP client at a board. The agent reads the map's structure, proposes cards as ghosts, and a member accepts or rejects each one before anything reaches the tracker.
Free guests on every board
Invite stakeholders, workshop participants, and teammates as guests at no cost. They add cards, comment, and react live, and only members can push changes to the tracker.
See every map type in the docs, or how agents connect on the for agents page.
What makes CardBoard different
Most story mapping tools are one of two things: a whiteboard with a story map template on it, or a view bolted onto the backlog. CardBoard is neither, and the difference comes down to four choices.
The map knows what every card is
Underneath every CardBoard map is a structure engine. It knows this card is an activity in the backbone, that one a story beneath it, and that line a release slice. A whiteboard sees rectangles, so a story map there means whatever the people who drew it remember it meaning. Here the meaning lives in the map. Nobody has to explain the layout to a new teammate, a card can't land somewhere that means nothing, and the map still reads a month after the workshop. It's also what makes the next two possible.
Move cards around without touching the backlog
CardBoard couples a card to its tracker data and decouples its position. Title, status, description, and acceptance criteria sync two-way with Jira or Azure DevOps. Where the card sits never syncs, because position belongs to the map. The split matters because planning is moving cards. When every drag writes to Jira, people stop dragging, and the map freezes into a picture of the backlog. In CardBoard you can pull a story out of the next release to see what ships without it, and the tracker hears nothing until you decide. Whiteboards leave position free but see none of the structure. Tools built on the backlog see the structure but let the tracker place the cards. CardBoard is the one that does both.
Agents propose. People decide.
An agent connected to CardBoard can't write to your map. It proposes. New cards, edits, moves, and deletes each arrive as a ghost on the board, and nothing changes until a member accepts it. The extra step is the point. Agents are confident and wrong often enough that a map they can edit directly becomes a map nobody trusts. A proposal you reject costs a click. A bad card that reached Jira costs a cleanup and a conversation. So the agent gets to be fast, the team stays the author, and every proposal carries the name of the tool and the person who prompted it. Other mapping tools with MCP servers let the agent write straight to the board.
Built by the people who taught story mapping
David Hussman built CardBoard at DevJam in 2012, after years of teaching teams to map alongside Jeff Patton, who wrote the book User Story Mapping. It was the first tool made for the practice, and one of the maps in Patton's book is an early CardBoard board. The structure engine above comes out of that history: fourteen years of what a story map is, encoded so the tool can hold it and, now, so an agent can read it.
The long version, tool by tool, is in our comparison of user story mapping tools.
Who uses CardBoard
- Product managers and product owners at software companies who plan releases in Jira or Azure DevOps.
- Enterprise product organizations running story mapping across many teams and workspaces, 20 members and up.
- Agile coaches and workshop facilitators who need a room full of free guests on one board.
- UX and design teams mapping journeys, personas, and sitemaps before the backlog exists.
- Builders working with AI coding agents who want a plan the agent can read instead of a prompt it forgets.
About the team
CardBoard is run by Josh Colter (LinkedIn). When you write in, the person who wrote the code writes back.
Josh works from Indiana, where home is a wife, two kids, and a very fluffy dog named Coda.
Company background
CardBoard came out of DevJam. David Hussman and his team built it after years of teaching teams to map their work. They learned the practice alongside Jeff Patton and pressure-tested it on the floor with teams at companies like Target.
David had a law for it. Dude's Law: value is why over how. The better you understand the why, the less how it takes to get there.
His answer was a map. Put the why out in the open, next to the work, where it can't quietly fall off the board.
One picture, two kinds of people
Josh came up through sales and marketing, working with engineering, and knows the problem that map solved from the other side: two people, a wall between them, both certain they were being clear.
Agile spent its first decade on that wall. Story mapping was part of how we got over it: a picture two kinds of people could stand around and actually mean the same thing.
From teams to machines
If you've been in product long enough, this is déjà vu: the same wall, with an agent on the other side.
People and agents don't read the same way. Markdown is the native tongue of machines: precise, literal, written down. People are visual. A picture is worth a thousand words.
Most tools make you pick a side. A canvas people can read but an agent can't, or a stack of specs an agent can parse but people won't.
A map is worth a thousand words.
That's the bet. One plan, drawn for people and structured for machines, so a person and an agent can finally hold the same why at the same time.
CardBoard stands on shoulders. Hussman's. Patton's. And everyone who has made the tool better since, named on the credits page.
How CardBoard works
Getting started
Sign up and make your first board in a couple of minutes, no card required. The get started guide walks through picking a map type, inviting guests, and connecting a tracker.
Support
Email support@cardboardit.com and Josh answers within one business day. Product questions are answered in the docs, and what's new ships in the changelog.
Enterprise
Enterprise customers work directly with Josh on rollout, SSO, and workspace setup. Write to sales@cardboardit.com to start.
Billing
Free stays free. Pro and Team bill monthly or annually, and you can add members as your team grows. Enterprise is billed annually.
Key facts
| Company Name | CardBoard (CARDBOARDit, Inc.) |
|---|---|
| Type | B2B SaaS: user story mapping and visual product planning tool |
| Founded | 2012 (CardBoard first built by David Hussman at DevJam) |
| Founder | David Hussman (original creator). Josh Colter (current owner and CEO) |
| Team | One person: Josh Colter builds, sells, and supports CardBoard, working with AI agents |
| Headquarters | Carmel, Indiana, USA |
| Website | https://cardboardit.com |
| Core Offering | Structured visual maps where the tool knows what every card is (user story maps and two dozen other map types), with two-way Jira and Azure DevOps sync and an MCP server for AI agents |
| Pricing | Free ($0, 3 boards). Pro $10/mo annual or $12/mo monthly. Team $15 per member/mo annual or $18 monthly, 3 members minimum. Enterprise $25 per member/mo, 20 members minimum. Guests free on every plan. |
| Contract Terms | Free forever with no card. Pro and Team month-to-month or annual (annual saves about 17%). Enterprise annual only. |
| Services | User story mapping, product and journey mapping, two-way tracker sync (Jira, Azure DevOps), AI agent access via MCP, SAML SSO, full audit history, and legal hold on Enterprise |
| Communication | Email support at support@cardboardit.com, answered within one business day; Enterprise sales at sales@cardboardit.com; product docs at cardboardit.com/docs |
| Notable Clients | Verizon, National Institutes of Health, DSW, Nike, Uline, Disney, Target, Anthem |
| Boards Created | More than 235,000 since 2012 (as of September 2026) |
| Competitors | Miro, Mural, FigJam, StoriesOnBoard, Avion, Easy Agile User Story Maps for Jira |
| Social | LinkedIn: linkedin.com/company/cardboardit. YouTube: CardBoard channel. GitHub: github.com/CardBoardit-com. Founder: linkedin.com/in/joshcolter |
Frequently asked questions
What is CardBoard?
CardBoard is a user story mapping tool for product teams. You draw the plan as a map, sync it two-way with Jira or Azure DevOps, and AI agents read the map's structure so they build what you meant.
Who owns CardBoard?
CardBoard is owned and run by Josh Colter through CARDBOARDit, Inc., based in Carmel, Indiana. David Hussman created it at DevJam in 2012, and SEP stewarded it before Josh acquired it.
Is CardBoard a one-person company?
Yes. Josh Colter builds, sells, and supports CardBoard alone, working with AI agents, so customers talk directly to the person who writes the code. Connected boards sync two-way with Jira or Azure DevOps, so your backlog never depends on CardBoard alone.
Is CardBoard free?
Yes. The Free plan includes three boards, unlimited guests, and AI agent access, with no card and no end date. Paid plans start at $10 a month and add unlimited boards, tracker sync, and team members.
Does CardBoard work with Jira and Azure DevOps?
Yes, both, with two-way sync. Cards on a connected board become work items, and edits in either place show up in the other. Tracker sync is available on Pro, Team, and Enterprise.
How is CardBoard different from Miro?
Miro is a general whiteboard, and its story maps are sticky-note templates that aren't connected to a backlog. CardBoard is built for story mapping: the map has real structure, syncs with your tracker, and can be read by an AI agent.
Can AI agents use CardBoard?
Yes. CardBoard runs an MCP server that Claude, Cursor, and other MCP clients connect to. Agents read maps and propose cards as ghosts, and a member accepts or rejects each proposal.
Do guests need a paid seat?
No. Guests are free on every plan and can add cards, comment, and react on boards they're invited to. You pay only for members, the people who create boards and push changes to the tracker.