How it works Intelligence Core Workflow Engine Pricing Work About Book a walkthrough
How it works

Capture. Propose. Approve. Done.

Every offer we sell is this one loop pointed at a different part of a business. Here it is once, with the real pieces named, so you can see where the human sits and why nothing runs away from you.

Katsura · Inbox
capture propose approve done
Slack · #marketingjust now
Dana R.
New taskfrom screenshot
To do

1 · Capture. An ask arrives the way asks do.

01

Capture: asks arrive the way asks do.

A voice memo recorded with the phone in a pocket. A screenshot of a Slack message, an email, an Asana comment, a text. The audio from a Zoom or Meet call, recorded on the Mac with no bot joining. A Loom someone sent. A forwarded thread.

Nothing is installed in anyone else's workspace. Nothing needs IT approval. If it is on the screen or in the air, it can be captured.

02

Propose: the system writes the task, not the person.

Transcription on infrastructure you own. Then a model with full context (your clients, projects, calendar, and the brain if you have one) turns what was said or shown into proposals: new tasks on the right project, or a new project with its kickoff tasks.

Each proposal carries enough context that an agent, or a new hire, could start cold. A 50-person meeting does not produce 50 action items; it produces the three that are yours.

03

Approve: a person says yes. Nothing happens before this.

Proposals wait in one Inbox. Approve, mark as already done, or dismiss. The screenshot or the recording is attached, so you can see exactly what the proposal was read from. This is the line the system does not cross, and it is enforced in the software, not in a policy document.

04

Agents do the work.

An approved task can be handed to an agent with one button: a coding agent for software work, a research agent for a brief, a writing agent that reads the brain first. The agent works from the task's own context and the company's approved facts, never from a prompt someone had to remember.

05

Report back, for review.

The agent's result lands in the task's activity log and the task moves to Review. A person reads it, accepts it, or sends it back. The record of what was asked, what was proposed, who approved it, and what was done stays with the task forever.

Under the hood

Boring infrastructure, on purpose.

Everything runs in accounts you own. We pick the pieces for cost and durability, not for a logo wall.

# what a Workflow Engine runs on
compute    Cloudflare Workers  one deploy, no servers to patch
data       D1 + R2  your records, your recordings, no egress fees
transcribe  Whisper  on Workers AI, or on a Mac in your office
reason     Claude  Opus for the parse, Haiku for the small stuff
private    open-weight models on Apple silicon  when nothing may leave the building
apps       web, Mac, iPhone  offline queue, sync that does not duplicate
auth       your own  no Google sign-in dependency unless you want one
What does it cost to run each month?
Model and hosting costs are passed through at cost and itemized. For a 20-person team on an Intelligence Core, that is typically under a few hundred dollars a month, with per-person budgets so it cannot run away. The platform fee on each offer covers our time: ingesting new material, updating guides, upgrades, and a monthly usage and quality report.
What if you get hit by a bus?
You own the code and the accounts. Documentation is part of every deliverable, and the system is built from well-known pieces any competent engineer can pick up.
Can it work with the tools we already use?
Yes. Capture works for anything on a screen, so it works with everything. Deeper bridges exist today for Asana (with parent-task context walked in) and calendars, and are straightforward for most tools with an API.

See your ask go through the loop.

Bring one recurring ask to a 30-minute walkthrough. We'll run it live.