Kendu
Request early access
Specs · Approvals · Decisions

The single
source of why.

Your spec knows what the plan was. Kendu knows what is true now: every requirement, its approval, and the decision that last changed it. Connected, up to date, and easy to trace.

Request early access See how it works
Billing & exposure spec v14 UPDATED 2026-08-04
D-19 Live SUPERSEDES D-14
Credit line billed on summed accounts
RATIONALE Client operates 3 accounts under one limit; per-account billing double-counts exposure.
Finance Product
REQ-12 Fee calculation per client Needs review
Re-approval requested from Finance.
Modules

One connected record, three ways to work on it

Specification collaboration is live in early access today. Approvals and estimates build on the same connected record, in that order.

Specifications

Live

Create it in Kendu or import what you already have. Requirements, rules, open questions and decisions stay connected, so you can see what changed, why, and who needs to look again.

Approvals

Coming next

Approve what changed, not the whole document. Each requirement keeps its own record: who approved it, which version, and when. Legal reviews three requirements, not forty pages.

Estimates

Later

Price the spec you actually agreed to. Estimates hang off requirements, so when one changes you can see what it costs before anyone argues about scope.
How it works

Start with a spec. Keep it true.

We started building Kendu after watching carefully written specifications go out of date almost immediately. Decisions moved into meetings and messages. Approvals became hard to trace. The project kept moving - but its shared memory did not.

Request early access
01
Bring the spec in
Import the document you already argue over, or write it in Kendu. Every requirement and rule gets an ID and an owner.
02
Record the decision, not the thread
Context, options, choice, rationale, who agreed, when. A new decision can supersede an earlier one without erasing the reasoning behind it.
03
Ask why, six months later
“Why is the credit line an override?” Requirements, decisions, approvals and revisions stay connected, so the answer stays with the project.
Who it's for

Built for specs that keep changing

Kendu suits projects where several people depend on the specification and the reasoning behind each decision needs to stay visible.

Kendu is most useful when

Several people contribute to or approve the spec. Product, legal, compliance, commercial, implementation, QA.
Projects run for months or years. The context has to outlive the people who originally held it.
Changes require traceability. Regulatory, contractual, or just internally expected.
You deliver client work. An untracked change becomes unbilled work, or a dispute later.

Kendu may be more than you need when

A small, closely aligned team holds the context informally and the work is short-lived and low-risk.
Changes need no formal review, traceable approval, or written rationale.
Your main need is task or sprint management. Kendu complements those tools, it does not replace them.
Early access

Book a walkthrough

We're inviting a small group of teams to use Kendu early and help us shape it around real projects. 

If this problem feels familiar, request access. We'll learn how your team works and explore whether Kendu could be useful.

Early access is feedback-led. No sales theatre, just an honest conversation about whether Kendu can help.

Thanks, we will be in touch

Usually within one working day.

Send another
Request a walkthrough