Live demo
Experience Naavek
This is the core of how Naavek works. A requirement card moves through a lifecycle, assigned to teams, discussed, and when all parties agree, it locks into a decision. Try it.
API authentication method
System must support OAuth 2.0 and token-based authentication for all API endpoints accessed by third-party integrations.
Click + Assign to bring in teams
The three states
One card. Three moments.
API authentication method
Requirement created, no teams assigned yet.
Requirement created. No teams assigned. Lives in a backlog until actioned.
API authentication method
Two companies assigned. Awaiting acceptance.
Companies assigned. Each company sees Accept and Reject controls. Status shows pending count.
API authentication method
All companies accepted. Card is now locked.
All companies accepted. Strip desaturates, badge locks, text dims. The card is now immutable, a permanent record.
The key insight
The requirement becomes the decision. It doesn't spawn one.
Most tools separate requirements from decisions: two different record types, two different places to look. In Naavek, the same card transitions state. The history is preserved in place. That's what makes the audit trail automatic.
Requirements in Relatics, decisions in email, approvals in PDF. Three sources of truth.
One card. One state machine. Every transition timestamped, linked, and searchable.
Explore the product
There's more to see
Requirements
How requirements are captured, structured, and tracked across a project.
Learn moreRequirements & Decisions
How every requirement and decision is captured, structured, and locked in a single card lifecycle.
Learn moreTrace Graph
The live map from client brief to delivered output, every connection visible.
Learn moreReady to use the real thing?
Join the waitlist and we'll onboard you personally on your first project.
Join the waitlist