How it works Intelligence Core Workflow Engine Pricing Work About Book a walkthrough
Offer 03 · the loop

Every ask becomes a task. Every task gets done.

A Workflow Engine is the loop on our how it works page, pointed at one recurring kind of ask in your business. Each engine ships in three to five weeks and runs in accounts you own.

Book a walkthrough Pricing
Four engines we have already built

Pick the ask that costs you the most time.

These four run inside Katsura today. Each one maps to something a team already does by hand, badly, on a Friday afternoon.

A

Meeting captureZoom, Meet, in person

Calls are recorded on the Mac with no bot joining, matched to the calendar event, transcribed, and summarized. Action items are filed to the right project and person. The other forty people on the call do not become your to-do list. Drop in a Loom someone sent and it goes through the same pipe, with tasks deep-linked to the moment.

from $12,000+ $1,500/mo
B

Capture inboxSlack, email, Asana, texts

Screenshot the ask, drop it on the Dock, the menu bar, a hotkey, or the iPhone share sheet. A vision model reads it, writes the proposal, attaches the image, and links back to the source when there is one. Nothing is installed in anyone else's workspace, so there is nothing for IT to approve.

from $12,000+ $1,500/mo
C

Agent dispatchcoding, research, writing

Approved tasks handed to an agent with one button, with the task's full context and the company brain if you have one. The result comes back into the task's activity log and the task moves to Review. Software teams use it for real tickets; everyone else uses it for research briefs and first drafts.

from $15,000+ $2,000/mo
D

Tool bridgeAsana, Jira, HubSpot, your CRM

Assigned tasks, mentions, and flags pulled in with full context. Many Asana tasks say "see the parent task for the strategy doc"; the bridge walks parent tasks and attachments so nothing arrives context-free. Completion is written back where your team already looks.

from $12,000+ $1,500/mo

Bundle: three engines for $40,000 and $4,000 a month. Every engine includes the Inbox, the native apps, and the approve-first contract. Prices are starting points for a 20 to 200 person company and firm up after the Readiness Audit.

The contract

Three promises every engine keeps.

  • ✓
    Nothing acts without approval.Proposals wait. A person approves, marks already done, or dismisses. The approval is logged with the task.
  • ✓
    Every proposal cites its source.The screenshot is attached. The recording is linked, with the timestamp. The Slack permalink is kept when there is one.
  • ✓
    You own it.Your Cloudflare account, your API keys, your model choice. Documentation is part of the deliverable. We can be fired without anything breaking.
  • ×
    It does not send, publish, or delete.Drafts are drafts. Replies are drafted, never sent. If your team wants auto-send for a narrow case, that is a decision you make in writing, later, with a log.
How a build runs
  1. week 1Map the askWhere it comes from, who handles it, what good looks like. We watch it happen a few times.
  2. weeks 2 to 3BuildThe capture path, the proposal prompt tuned on your real examples, the Inbox in your account. You approve the first proposals with us watching.
  3. week 4Agents and bridgesDispatch wired to the agents that fit. Write-back to the tools your team already lives in.
  4. week 5HandoverNative apps installed, team trained, documentation delivered. Care begins.
Workflow Engine
from $12,000per engine · 3 to 5 weeks

Then from $1,500 a month per engine for platform and care: prompt tuning as your work changes, upgrades, monitoring, and a monthly report of what went through the loop.

  • Three engines: $40,000 and $4,000 a month
  • Transcription and model costs passed through at cost
  • Built on the same code we run every day
Start with a walkthrough

Which ask eats your Fridays?

Bring it. Thirty minutes, and you will see it as a task.

Book a walkthrough