Pricing for the workspace you actually run.
Start with demand, roadmap, releases, and notes. Upgrade when you need weighted prioritization, more coordination, or broader rollout.
Starter
For small teams validating product ops + notes.
- Core demand capture and inbox
- Roadmap and release basics
- Pages for internal notes
- Enough to prove the one-workspace model
Pro
For teams running demand, shipping, and knowledge together.
- Weighted voting by customer value
- Richer roadmap, releases, and coordination
- Internal notes next to the operating loop
- Best fit for growing product teams
Enterprise
For orgs that need scale, governance, and rollout support.
- Expanded limits and ownership patterns
- Compliance-friendly operational controls
- Multiple teams on the same ops + knowledge system
- Commercial and technical rollout support
You do not need a perfect process to start.
Most teams arrive with feedback, roadmap, release notes, and internal docs scattered. Damper consolidates product ops and team knowledge without a giant rewrite first.
- Start with the pillar that hurts most: demand, roadmap, releases, or notes.
- Layer weighted prioritization when customer segments matter more.
- Add CLI or MCP only when engineering wants a technical path.
The product matches the story.
Damper is product ops and team knowledge — demand, roadmap, releases, and internal notes. AI and CLI are optional extensions, not the reason to buy.
- Human-first workspace for PMs and founders.
- Internal notes stay next to shipping work.
- Technical paths stay available for evaluators who need them.
Questions that usually come up before rollout.
Use the plan page to decide fit for ops and knowledge — not to decode packaging theater.
Can we start on the free plan and upgrade later?
Yes. Validate demand, roadmap, releases, and notes first. Upgrade when prioritization and coordination need more depth.
When does Pro usually make sense?
When customer segments matter enough that equal voting stops representing demand, and the team needs a fuller ops + knowledge workspace.
What pushes teams toward Enterprise?
Usually governance, scale, multi-team rollout, or stricter operational requirements.
Do we need CLI or MCP to justify a paid plan?
No. Those are optional technical layers. The core product is product ops and team knowledge.
Start with the four pillars. Grow coordination later.
Pricing follows how much product ops and team knowledge your process needs today.