Pages · around the loop

A workspace for everything your team thinks about.

Pages is a calm, private home for notes, meetings, specs and databases — inside the same tool as your feedback and roadmap. When thinking and shipping live together, both get faster.

What teams do with it

Pick a job. Pages already fits.

Most pages aren't blank. They're a meeting, a spec, a tracker or a place to think. Each one has a head start here.

01

Meetings that finish

Agenda, notes and action items in one template. Set it to weekly and the next meeting page creates itself.

02

Specs before you ship

Write the spec, link the feedback that asked for it, and hand it to an agent as context. The doc becomes the work.

03

Track anything

Tasks, candidates, experiments, launch checklists. Shape the board your team needs — no admin required.

04

Research that compounds

Interview notes, teardowns, decisions. Linked and searchable, so month-old learning is still in reach.

Properties

Fourteen kinds of “keep track of this”.

Give any row the field it needs. Most are what you'd expect. Three of them exist because this is Damper — relations to pages, roadmap items and feedback, the things your docs are usually about anyway.

Views

Same data. Four ways to run a week.

A launch tracker is a board on Monday and a calendar the week before the date. Switch, group and filter without rebuilding anything.

The editor

Write without fear.

Drafts autosave as you type. Every save keeps a revision. Nest pages when a topic grows, move them when it changes, and follow backlinks when you can't remember where you wrote the smart thing.

  • Autosave + revision history — the version you regret deleting is still there.
  • Structure that moves with you — nest, drag, re-parent. Organization is not a one-time decision.
  • Backlinks — every page knows what references it. Your wiki stays honest.
  • Search that covers everything — pages and databases across the project.
Templates

Start from what already works.

Nobody should face a blank page on a Tuesday. These ship built-in — your own templates slot right next to them.

database

Task board

Status, priority and assignee out of the box — grouped into a board your standup can actually use.

meeting

Meeting notes

Agenda, notes, decisions and action items — with a link to the roadmap work each decision caused.

doc

Project plan

Milestones, owners and risks in one doc — the thing everyone opens before they ask “where are we?”

any kind

Blank start

Note, research, doc or database — pick a kind, pick an icon, and your template becomes the team's way.

Why pages in Damper

A docs tool that knows what your customers said.

Any editor can hold a spec. Only one sits on top of your feedback inbox, your demand-scored roadmap and your coding agents.

Docs connected to demand

Link any page or row to the feedback and roadmap items it concerns. When the demand shifts, the context is already attached.

relations · not links-that-rot

Agents read your docs

Pages feed the same context layer your coding agents use. Write the spec, and the agent doing task #42 has already read it.

mcp · get_project_context

One tab fewer

Inbox, roadmap, changelog and now the workspace next to them. No tab-hopping to answer “why did we build this?”

feedback · roadmap · pages — one place

Share a page, not the keys

Guests see one page with view or edit rights — contractors, clients, anyone. Revocable any time, private by default.

per-page invitations

Quietly retires

Included in every plan. No seats for guests who only read one page.

the docs app nobody lovesthe meeting-notes graveyardthe spreadsheet with one maintainer“can you send me that doc?”

Consolidate on purpose.

Move the thinking in. The feedback and roadmap are already here.

The product map

Where this fits in the loop.

01

Collect

Catch feedback where it happens — in your app, in Slack, on a call — and land it in one clean inbox.

02

Prioritize

Rank requests by who is asking. Votes are weighted by plan, so paying customers move the roadmap.

03

Build

Hand the top task to your AI coding agent with the rules that govern it — and get proof when it is done.

04

Ship

Shipped work becomes a changelog entry, and everyone who asked for it hears first.

+

Around the loop

Docs, uptime, errors and team access — the product ops that sit next to the loop.