scroll to the bottom to feed the kiwi ↓
Product

Agent workflows that are easy to build and easy to audit

Three pieces, one tool: a visual studio to build the workflow, an app your team runs it from, and a record of every decision the two produced.

Build the workflow by dragging it

Steps and checkpoints on one canvas, no scripts. Kiwi scores every run against what your team kept and points at the step that is dragging the number down.

Ship it as an app, not a pipeline

A published workflow is a screen your team works in: the inputs it needs, the runs in flight, the drafts waiting on someone. Nothing to hand to engineering.

Every decision on the record

Who approved what, what they changed, what they turned down and why. Attributed, searchable, and the reason the next run is better than the last.

Checkpoints

The agent stops where you tell it to

Drop a checkpoint anywhere in the sequence and write what a person should check there. When a run reaches it, that person sees what the agent read, what it is about to do, and can approve, edit, steer, or end it.

Approvals can be cleared from Slack. Either way the record shows who decided and when.

Account timeline · Acme
Gathered the account contextread Gmail, Gong, Salesforce · 2:31pm
Drafted the renewal summarystayed inside Kiwi · 2:33pm
M
Step 4 of 6 · Share with the account teamstopped for your approval
What it readDana Wright, Sep 12: "can you send a summary before the QBR?"
What it will doSend one email to 3 people at Acme from your address, update the renewal record, post the recap in #acme-account.
Approve, send itEdit, then approveGive feedbackDecline
Send to the Acme team · writes to Gmail · after your approval
The record

Every run leaves a record your team can read

Plain sentences: what the agent read, what it wrote, who approved it, what they changed, and whether the result was kept. Your team reads it to trust the work. Your next run reads it to do better.

Acme, this weekkept
Drafted the summary, 2 versions2:33pm
Melanie said: lead with the migration date2:38pm
Redid the draft with the note2:40pm
Approved by Melanie Chen2:46pm
Sent to the Acme team, 3 peopleGmail, 2:47pm
Where teams start

Built for the work that repeats

Account timelines

Every meeting, thread, and decision on an account, summarized and shared before the QBR.

Renewal prep

Usage, open risks, and the last six weeks of contact, drafted for the owner to approve and send.

Call follow-through

Calls filed to the right account, commitments pulled out, nothing sent without a name on it.

See the product on your accounts

Thirty minutes, live, with your tools connected.

Book a demo