How it stays current
Automation that runs your playbooks, not around them.
Most AI automation asks you to trust a black box with your name on it. Here, automation fires your approved playbooks — the ones with your voice and your process attached — and everything it produces waits for a person before it counts.
Start your 14-day free trial$149/mo after trial · Cancel any time
Three kinds of trigger
Runs fire when you say so: manually, on a schedule, or when content changes. The weekly content batch kicks itself off. A recurring client deliverable runs on retainer cadence instead of a calendar reminder. A change to a source document can set off the playbook that depends on it. The team's job shifts from starting the work to reviewing it — cadence without a project manager.
Every run leaves a ledger
Each run is recorded: what fired, what it produced, what was decided about it, and what the outcome was. Retainer work stops living in calendar reminders and starts living in a ledger you can show a client. And because outcomes are recorded, Patina can suggest tuning — which triggers earn their keep and which just make noise.
Output lands as proposals
Nothing a scheduled run produces publishes itself. The work arrives in the review queue like everything else: a side-by-side of what the agent did, with its sources attached, waiting for a yes. Automation raises how much gets done; it doesn't lower the bar for what gets in.
The heartbeat of an agent-run company
Recurring ops that fire themselves and leave receipts — that's what lets agents carry real workload while the memory stays current and your team stays in charge.
Start your 14-day free trial$149/mo after trial · Cancel any time