From requirements catalog to evidence pack
One path your team follows on every project, from the first meeting to a change requested months later.
Catalog
List your product's standard features once, with their options and how much the client can adjust each one. You do this once per product, not per client.
FRD
Start a project and capture its requirements into a structured FRD — not a Word file, typed features with stable IDs, switched on or off and filled in from your template, plus anything client-specific.
Review & approval
Your own team signs off internally, then the client reviews the exact frozen version through a secure magic link — no account or seat required on their side. Their decision, plus an OTP-verified identity, becomes the application approval record.
Baseline & change requests
The approved version is locked as a baseline — the agreed state, on the record. When the client asks for something new, you open a Change Request against that baseline: an explicit before/after, reviewed and approved on its own, then applied to produce the next baseline. Nothing overwrites history.
Evidence, whenever you need it
Every version has a content hash, every approval is an application approval record, and every step is a tamper-evident, hash-chained audit event. Export an evidence pack — a single PDF — on plans that include it: the version, its hash, and the approvals behind it, for a client audit, a dispute, or your own records.
Prefer a step-by-step walkthrough? Read the guides →