Sales deck · v0.7 · updated 2026-09-28, press ⌘P / Ctrl+P to save as PDF.

Decide once.
Enforced every time.

Your agent already proposes refunds, credits or account changes. A person still executes every one.

keep the queueEvery action waits.The agent drafts. A person finishes it.
or
hand it the keyEvery action runs.The tool can execute. Nothing says how much.

The third option: the owner decides the agent's authority once, and KIFF enforces it on every action.

Cheap actions multiply the decisions.

ActionsAn agent's action costs almost nothing.So teams ask it to do far more of them.
VolumeThe number of consequential actions grows.Refunds, credits, access changes, deploys.
ApprovalA person approving each one becomes the whole cost.Supervision grows with the work, and the saving stops there.

When something gets cheaper, we use far more of it: the Jevons paradox. Applied to agents, the limit moves from doing the work to deciding it.

Three answers today. None of them scale.

approve everythingA person clicks each oneSafe, and the agent saves typing, not work.
hand over the keyThe agent can do anythingFast, and nothing bounds how much.
write the limit inA prompt, a config, a functionNobody on the business side can read it, and every change is a deploy.

Move people from actions to authority.

BeforeA person approves every refund.400 drafted, 400 executed by hand.
With a cardThe owner sets what the agent may do, once.Actions, valid states, conditions, a ceiling over a window.
AfterThe clear cases run. A person sees the exceptions.Judgment is spent where it matters, not on every click.

Correct, and still refused.

Illustrative: Refund Card, one day€1,100 ceiling
€42 drawn€990 drawn€68 left
Next refund: €88. Valid order. Permitted agent. €20 over the ceiling. KIFF refuses before execution.

An alert tomorrow would tell you what happened. The card decides what may happen now.

Change the authority, not the agent.

€5,000 a day. €20,000 for Black Friday. €5,000 again on Monday. Revoked at 2 a.m. if something looks wrong.

The owner changes the card. The agent keeps running the same code: no prompt edit, no config change, no deploy.issue · widen · narrow · revoke
IssueWidenNarrowRevoke

A limit you write yourself breaks under load.

Two at onceTwo runs both read €1,000 left.KIFF locks draws per card: the second is refused.
RetryA timeout retries the same refund.KIFF keys the draw to the proposal: it counts once.
RestartThe agent scales to three workers.One balance per card, held centrally: no fresh allowance.
OutageThe balance cannot be read.KIFF refuses. Unknown is never read as zero.

One holder. Separate cards.

refundsRefund Card€5,000 / day · REFUND_ORDER
creditsStore Credit Card€2,000 / day · ISSUE_STORE_CREDIT
plansPlan Change Card40 / day · CHANGE_PLAN
Revoke one capabilitywithout stopping the agent's other work.

“Who allowed this?” has an answer.

IssuedWho gave this agent which authority, and when.Every ceiling change is attributed.
DrawnWhat each authorization used.The statement shows the balance and how it moved.
RefusedWhat was stopped, and why.Ceiling, revocation, or a balance that could not be read.

Issuing and ceiling changes are attributed revisions. Each authorization and refusal has a signed, tamper-evident receipt. The agent can write neither.

Your organization issues it. KIFF checks it.

Your organizationIssues the card.Actions, valid states, conditions, and the ceiling. The owner changes or revokes it; the agent cannot.
KIFFChecks every proposal.Allow, hold for a person, or refuse, using current state and the card.
Your systemRuns what's allowed.Your code keeps the execution path. KIFF never moves anything itself.

A card narrows what your domain and permissions already allow. It cannot make a forbidden action legal.

Start with one action.

one card, one actionObserve firstagreed before it starts · founder-ledSee how it runs →
what you receive
  • Observe. KIFF on the action's path, deciding and recording while refusing nothing, on your real traffic.
  • Issue. Your organization issues the card, with a ceiling from the observed number.
  • Prove. Control tests on that path: limits, retries, concurrency, revocation.
  • Hand over. The owner accepts the boundaries; your team runs it.

Issuing, the tests and the handover are scoped from what observing shows. If almost everything still needs a person, stop there.

Bring us one action.

card review30 minfounder-led · no costBook the review →
bring three things
  • One action your agent proposes.
  • How many a person executed unchanged last month.
  • The system that would execute it.