Cobenian Oversight
Sign in Start free

How Oversight works

From "something happened" to "we did something about it."

Oversight watches your business, notices things worth doing, and takes action on your behalf — within the limits you set. Here's how that loop works, end to end.

1

Notice

Oversight watches what's happening across the tools you've connected — email, calendar, accounting, time tracking, and more.

Things it notices
  • 📧 A client emailed you
  • 📅 You have a meeting scheduled
  • 💰 An invoice was paid (or is overdue)
  • ⏱️ Time was logged but not yet billed
  • 🤐 A client hasn't replied in 18 days
  • 📈 A client's engagement is trending down

The first three come from direct events ("a thing happened"). The last three are patterns Oversight computes by watching over time.

2

Think

Oversight considers what it noticed against your business goals — retain revenue, bill on time, follow up on proposals — and decides whether there's something worth doing about it.

If nothing's worth doing

Oversight stays quiet. Most things it notices don't warrant action.

If something is worth doing

It forms a hypothesis — its best understanding of what's happening and what should happen next.

Example hypotheses: "ACME has gone silent — we should send a check-in." "Carey's timesheet has 6 unbilled hours — we should draft an invoice." "Pat's renewal is up next month — we should propose a meeting."

3

Decide how

For every hypothesis, Oversight picks one of three ways to handle it.

A · Just do it (internal stuff)

no clicks, ever

When the action is purely internal — like noting something in the knowledge base or refreshing a rollup — Oversight just does it. No goal, no plan, no approval. These are zero-stakes housekeeping.

B · Make a goal & work the plan

may or may not need approval — depends on your settings

When the action affects a client (drafting an email, sending an invoice, proposing meeting times), Oversight turns the hypothesis into a goal ("re-engage ACME") with a plan (the sequence of steps to get there). Each step then runs — automatically or after you approve, depending on your autonomy settings.

C · Promote to a procedure (SOP)

happens after a pattern repeats 4+ times

When Oversight sees you approving the same kind of thing over and over ("welcome new client" emails, for example), it offers to make that automatic — a Standard Operating Procedure. Once activated, Oversight handles future occurrences without asking again. If you've explicitly opted in via the SOPs catalog, well-known patterns activate automatically; otherwise you'll see a "make this automatic" card in your Inbox.

4

Act (or ask first)

For each step, Oversight asks itself: "Am I allowed to do this on my own, or do I need to ask first?" The answer depends on your autonomy settings.

Observe Oversight watches but never acts on its own.
Drafts only Drafts get created automatically. You click to send.
Ask to act Asks before acting. (Default for new accounts.)
Act within window Acts on its own — you can reverse anything within a configurable window.
Full concierge Acts on its own, no reversal window. You see what happened, never the "may I?"
Auto-fire

If your autonomy allows it, Oversight sends the email, drafts the invoice, books the meeting — and tells you what it did.

Queue for review

If approval is needed, it lands in your Inbox. You click Approve, Edit, or Dismiss.

5

Learn from what happened

Oversight watches for the results of what it did — replies that come in, invoices that get paid, meetings that get booked — and connects them back to the action that prompted them.

Proven value rolls up

Per-goal and per-objective dollars — "Re-engaging ACME brought back $1,200 in MRR." You see proven impact, not just activity.

Oversight gets better

When you dismiss suggestions, Oversight learns to stop suggesting them. When you approve a pattern over and over, it offers to make it an SOP. Your corrections feed back into how it reasons.

What you control

Settings → Governance
  • ⚙ Autonomy level — five tiers from "observe only" to "full concierge."
  • ⚙ Per-capability overrides — pin a specific tool (like sending invoices) to a different autonomy than the rest.
  • ⚙ Hard limits — things Oversight will never do, even at full autonomy (bulk actions, public posts, etc.).
  • ⚙ Cost caps — daily ceiling on LLM spend. If you hit it, Oversight pauses gracefully.
  • ⚙ Reversal window — how long after a fired action you can roll it back.
  • ⚙ Which connectors are on — Gmail, Outlook, QuickBooks, Harvest, Slack, etc. The more you connect, the more Oversight can do.
  • ⚙ SOP auto-activation — turn on per-SOP to let well-known patterns activate without your click.

Ready to try it?

Connect one source. See what Oversight notices. Turn up autonomy as it earns your trust.

Start free Back to home →