Know exactly what was agreed.
Prove it months later.
Capture client requirements from a reusable catalog, lock the approved version as a baseline, and turn every later change into a tracked, separately-approved Change Request.
No card required · External reviewers are always free
From catalog to evidence, in four steps
One clear path your team follows on every project.
Catalog
List your product's standard features once, with their options and how much the client can adjust each one.
FRD
Start a project and capture its requirements into a structured FRD — not a Word file, typed features with stable IDs.
Baseline
Internal sign-off, then the client reviews and approves the exact version. The approved state is locked as a baseline.
Change requests & evidence
Every later change is its own approved Change Request. Export an evidence pack — a single PDF — on plans that include it: the version, its hash, every approval.
Built around the evidence
Structured requirements
Not a Word file — typed features and options with stable IDs, captured in each project's FRD.
Immutable approvals
An approved version can't be edited. Each approval is an application approval record — a change means a new version, reviewed again.
Baselines & Change Requests
Every CR is an explicit before/after, approved on its own before it becomes the next baseline.
Evidence pack
One PDF: the version, its content hash, every approval, and the audit trail behind it.
Magic-link client review
Clients review and approve with no account and no seat — just an email address and an OTP-verified decision.
Audit trail
A tamper-evident, hash-chained log of every approval, version and baseline.
External review is always free — that's the funnel. Anyone you send a version to for approval — a client, a stakeholder, anyone outside your team — needs no account and pays nothing. They give an email address, complete an OTP-verified decision through a magic link, and that decision becomes part of the application approval record.
Built by someone who ran these projects by hand
Agreedum started inside a large technology-implementation team, where requirements were re-typed for every client and the approved version lived in someone's inbox. We built the tool we wanted: a fast catalog for standard functionality, a clean approval trail, and a change history that survives people leaving. It works for any vendor delivering a standardized-but-configurable product or service.
Simple pricing
You pay for the people creating requirements. Everyone you send things to for review is free.
Agency
extra seats · roles · separation of duties
Start freeCustom (SSO, residency and retention controls, SLA) is invoiced — talk to us.