Product notes
Show the product. Explain the limits.
Why our website uses real application captures, with the example data plainly labeled.
A screenshot should answer a question
What will I actually work with? Where does the bill list live? How does the workspace look when there are no notifications?
Those are reasonable questions to ask before a sales conversation. A product website should help answer them.
Real screens, visible context
The Civitas tour uses unaltered browser captures from our September 2026 interface work. They show the actual application rendered with example data. They are not illustrations of an imagined future interface, and they are not live customer accounts.
We preserve the screen’s context, including source-status labels and empty states. Each image can be opened at full size so the interface can be inspected rather than treated as decoration.
A capture is not a coverage report
The presence of a bill in a screenshot does not verify a production data pipeline. A freshness number in example data does not establish how recently a live source was checked.
Likewise, a product area visible in the sidebar does not mean it is included in the planned legislative subscription.
These distinctions are explained next to the tour and on the pricing and coverage pages. They should not require a footnote hunt.
Let people decide
A good marketing page makes the product easier to understand. It gives someone enough information to decide whether a closer look is worth their time.
For us, that means real screens, a clearly stated planned price, a description of current limits, and a straightforward way to ask about a workflow.