Every product team building a visual webapp eventually hits the same wall: the more carefully you write user-value-focused stories, the worse they perform as status updates for non-technical leadership.
"As a returning user, I want to filter my dashboard by region" tells leadership nothing about whether the filter works, whether the data is real, or whether the chart next to it is even hooked up.
Jira shows 200 tickets across 14 epics. The exec wants to see 8 screens with 3 colors. Roll-ups hide failure; ticket lists overwhelm. Neither answers the question.
A visual product deserves visual reporting. Leadership will see screens in the demo — they should see the same screens in the status update, with state painted directly onto them.
Teams that try to solve this by hand end up with a parallel tracking system in Confluence, Miro, or a custom tool. It works for 3 weeks, then drifts. Then nobody trusts it.
Leadership doesn't think in epics. They think in journeys and screens. The right primitive is "this rectangle on this screen, in this state."
Upload a screenshot of your app — staging, prod, or a styled mock. v0 is manual; the headless capture pipeline lands in v1.
Drag rectangles over the parts that matter. Tag each one as shipped, mock, or missing. Add a label and notes if you want.
Send one read-only link. Stakeholders see the same screens you demo, painted with state. No login, no Jira tour required.
One Docker image. MIT license. Designed from day one for the teams that aren't allowed to send screenshots of their product to a third-party server in the first place.
Zero outbound calls. No license server, no phone-home, no analytics.
docker run stateboard — under 60 seconds. SQLite by default, Postgres optional in v1.
Use it, fork it, ship it inside your product. The license means what it says.