← All use casesUC-10 · use case

Back-office ops

The boring stuff, done deterministically.

Mostly-deterministic agents generate invoices, send follow-ups and sync data — the LLM only handles the fuzzy bits.

Two ways to start: provision a ready-made solution and connect your own keys, or build it yourself from the template. Free during beta — see pricing.

In practice

Month-end arrives. The invoicing agent generates and sends every invoice from the same template, the follow-up agent chases overdue ones on schedule, and data syncs between tools — no spreadsheet marathon.

The team

Positions in the org — each filled by an agent, a person, or both.

Invoicing agent
AI agent
Follow-up agent
AI agent
Data agent
AI agent
Ops lead
Human

How everyone works together

People and triggers reach the agents, which act on your services and escalate to a human.

PEOPLE & TRIGGERSAGENTSSERVICES & TOOLSrequestsact onescalate · approveCustomersmessages · eventsInvoicing agentFollow-up agentData agentHTTP / MCP sourcesSchedulingGmailAccountingSOONHUMANS · OVERSIGHTOps lead

How it works

  1. 1

    An invoice is due or a follow-up cadence fires.

  2. 2

    Deterministic steps generate invoices and send follow-ups.

  3. 3

    Data is synced between tools.

  4. 4

    The LLM is used only for the fuzzy parts.

Set it up with prompts

Three ways to build this — pick a variant and type the prompts in order. Each step says which agent to address. A working Back-office ops workspace in minutes.

The most boring, most valuable loop: work done → invoice drafted → chased until paid.

Apps in this variantQuickBooks OnlineGmail
  1. 1Build the loopOnboarding box

    New workspace → "Describe your company" → Build my company

    Set up back-office invoicing: an Invoicing agent that drafts invoices in QuickBooks when I mark work delivered (I approve every send), and a Follow-up agent that chases unpaid invoices — friendly at 7 days, firmer at 14, and flags 30+ days to me instead of escalating on its own. Ops lead seat for me.

    Cash collection becomes a machine with a human face — and your approval on every send.

  2. 2Connect the appsYou (UI)

    Apps → Connect

    Connect QuickBooks Online and Gmail with your keys/OAuth. Agents only pull real numbers from connected apps — do this before asking for reports.

  3. 3AR widgetAnalytics Agent

    Inbox → Analytics Agent

    Add a widget: outstanding invoices by age bucket (0–7 / 8–14 / 15–30 / 30+ days).

    The receivables aging you should have had all along.

Make it yours
  • Tone ladder: paste your own three follow-up emails so the chasing sounds like you.
  • Auto-thanks: "When a payment lands, send a one-line thank-you the same day."

What you get

Invoices and follow-ups go out like clockwork

Deterministic steps mean predictable results

Your team stops doing copy-paste work

What it connects to

HTTP / MCP sourcesSchedulingGmailAccountingsoon

Available today via Google, HTTP and MCP sources. Items marked soon are on the connector roadmap.

Set this up for your Back-office ops

Provision a ready-made solution, or build it yourself — start with one agent in one role and grow into the full team.

← More use cases