Pricing that matches how your product process grows.
Start with collection and visibility. Upgrade when you need weighted prioritization, broader coordination, and a more technical workflow.
Starter
For small teams validating the workflow.
- One project with core feedback capture
- Public roadmap and changelog basics
- Enough surface area to test the operating loop
- Best fit for early-stage teams proving demand
Pro
For product teams prioritizing by customer value.
- Weighted voting and richer prioritization signals
- More team coordination around roadmap and releases
- Better fit for teams with paying customer segments
- The main operating plan for growing SaaS teams
Enterprise
For orgs with compliance, scale, or deeper workflow needs.
- Expanded controls, limits, and ownership patterns
- Support for stricter operational requirements
- Better fit when multiple teams share the same loop
- Commercial and technical rollout support
You do not need a perfect process to start.
Most teams arrive with feedback scattered across support, chat, docs, and spreadsheets. Damper is designed to consolidate that without forcing a giant implementation project first.
- Start with one project and the public loop you want to improve first.
- Layer in weighted prioritization once customer segments matter more.
- Add CLI or MCP workflows only when the team is ready for them.
The site and the product tell the same story.
The product is not pretending to be a single magic AI button. It is an operational system with technical extension points when those are useful.
- Human-first workflow for PMs and founders.
- Clear path for engineering and technical evaluators.
- Public-facing surfaces stay aligned with internal work state.
Questions that usually come up before rollout.
Use the plan page to decide fit, not to decode a maze of packaging rules.
Can we start on the free plan and upgrade later?
Yes. The free plan is intended to let teams validate the operating model before they need richer prioritization and coordination.
When does Pro usually make sense?
When customer segments matter enough that equal voting stops being a useful representation of demand.
What pushes teams toward Enterprise?
Usually governance, scale, rollout support, or the need to coordinate the same process across more stakeholders.
Do we need to adopt CLI or MCP to justify a paid plan?
No. Those are optional technical layers, not the reason the core product exists.
Start with a clean loop, then grow into deeper coordination.
Damper pricing is built around how mature your prioritization and release process needs to be today.