WorkflowTriggerAvg. time savedAccuracy
Month-end closeSchedule · 1st of month120 hrs / cycle98.4%
Invoice → paymentEvent · email arrival9 min / invoice99.1%
Cash applicationEvent · bank feed4 min / payment99.6%
Revenue forecastSchedule · nightly40 hrs / month94.2%
Vendor renewal reviewSchedule · 60d pre-renewal6 hrs / contract97.0%
Headcount planningConversation · ad-hoc12 hrs / scenario95.5%
Anomaly investigationThreshold · variance >5%2 hrs / event98.0%
Board packetSchedule · monthly30 hrs / cycle
SOX evidence pullSchedule · quarterly45 hrs / cycle99.8%
NetSuite migrationOne-off— weeks vs. quarters99.9% balances
Anatomy of a workflow

The same loop, every time.

TRIGGER
Schedule / Event / Chat

Cron, webhook, threshold, or a teammate asking in Slack — any signal can start a run.

PLAN
Decomposition

The planner reads the request, your policies, and the state of the ledger. It drafts a typed task graph.

RUN
Tool-use loop

Executors call MCP-compatible tools with bounded retries, idempotency keys, and sandboxed I/O.

SETTLE
Verify & report

An independent verifier checks every mutation. The writer produces a human-readable trace with citations.

Build your own

A natural-language workflow builder.

Describe the workflow. Bizos drafts the agent, the tools, the eval set and the review UI. You approve and it ships to your tenant.

Workflow StudioBeta
> describe
“When a Stripe payout posts, reconcile it against open invoices in NetSuite, write the journal entry, and Slack me if anything’s off.”
> bizos drafts
trigger: stripe.payout.paid tool: netsuite.openInvoices() tool: ledger.writeJournal() verifier: balances.match() notify: slack #finance