Scoped agents
No do-anything agent. Each one has a lane, enforced at the integration boundary — so the worst case stays bounded and known.
SELF-EVOLVING OS FOR THE BUSINESS
One place to do the work — with agents you actually control.
Evolve runs scoped AI agents across the apps you already use. Every consequential action lands in an inbox before it happens — you approve, edit, or reject. Nothing ships without your click.
The evolve at month 12 isn’t the evolve at month 1.
It’s the one your business actually needed.
WHAT HOLDS IT TOGETHER
Four ideas
Approvals inbox
Every consequential action arrives drafted, with the agent’s reasoning attached. Approve, edit, or reject — nothing commits without the click.
Everything audited
Every draft, decision, and downstream effect is logged and replayable. You can always answer what happened, and why.
It extends itself
The third time you walk an agent through a task, evolve proposes a workflow that encodes it. Approve once; it runs in one step.
THE APPROVALS INBOX
Your whole operation, one click at a time
Approvals
18 pending · routed to you-
finance-agent
Send dunning email — Invoice #4021 · Acme Co
$12,400 · 26 days overdue
L0 -
support-agent
Draft reply — “Where is my order?” · order #8830
matched skill: order-status
L2 -
ops-agent
Flag exception — supplier shortfall (SKU 33-A)
proposes workflow: shortfall fan-out
L1
EARNED AUTONOMY
The trust ladder
Autonomy is earned task-type by task-type — and only when you promote it. The same agent can be full-auto on one action and approval-only on another. Forever, if you want.
L3
Full auto — routine, eval-backed
L2
Auto unless the agent flags uncertainty
L1
Drafts usually right — still approved
L0
Every action approved — where agents start
MEET IT WHERE YOU WORK
One system, every surface
The relationship layer, approvals, and audit stay in evolve. Reach them from the web app, Slack, the CLI, or any MCP-compatible chat client — and the trust ladder is enforced server-side on all of them.
finance-agent · dunning #4021L0
support-agent · reply #8830L2
evolveAPP
Approval needed · finance-agent
Dunning email · Invoice #4021 · $12,400
$ evolve status
18 pending → #evolve-inbox
$ evolve approve 4021
✓ sent → Acme billing · logged
Top 5 at-risk customers this week?
5 in red band · 3 have open tickets. Drafted check-ins → your approval inbox.
PUT IT TO WORK
Across the business
A starter set — every one is the same loop: the agent drafts, you approve. The catalog grows from your real work.
Reply in your voice
Identify, pull context, draft — you approve. Money-touching replies stay approval-only.
Catch churn early
Health turns red → the why, plus a drafted check-in. Renewals, win-back, cancel-flow saves.
Expand without pressure
Usage signals an upgrade → a factual nudge. Onboarding nudges; celebrate first wins.
Ask across your stack
“Top 10 at-risk this week — and what to do about each.” Investor updates from real data.
Patterns, not anecdotes
“What went wrong?” → a weekly digest by reason. FAQ and content from your own threads.
Alert → pull request
An error alert → a fix on a branch → tests → a PR. Gated by your review, never merged alone.
See it on your own operation.
Evolve is built internal-first, then with a small number of design partners shaping the connector catalog and workflow templates.