How it works

Four steps. Twenty minutes. You have an AI workforce.

Connect the tools you already use. Meet 28 named AI employees the moment you sign in. Hire your own in plain English. Approve, reject, watch the company brain compound under an earned-autonomy gate. The product is the demo.

01·
Connect
·
~5 minutes
Connect the tools you already use.
Sign in. You see the integrations page. Click Stripe → OAuth in 4 clicks. Click HubSpot → OAuth in 4 clicks. Click ClickUp, Harvest, Gmail, Notion, Slack — whatever stack your business runs on. Nango handles every OAuth handshake. We never see your API keys.
Your side
—Click the integrations you use. Stripe + HubSpot + ClickUp + Harvest + Gmail + Notion + Slack is the common starter set.
—Approve each OAuth scope as it pops up — read scopes by default, write scopes per tool.
OpsRadar’s side
—Nango brokers the OAuth and holds the token. OpsRadar never stores customer API keys.
—Every read live-fetches from source — your client business data never lands in our database.
—25 integrations live today, growing toward Nango's full 500+ catalog.
What you walk away with
Your AI workforce now has the live data it needs to start working. No CSV uploads, no nightly ETL jobs, no syncing.
↳
Stripe, HubSpot, ClickUp, Harvest, Gmail, Notion, Slack, Calendly, Pipedrive, Apollo, QuickBooks, Google Calendar / Analytics / Ads, LinkedIn, Asana, Monday, Toggl, BambooHR, Gusto, Typeform, Intercom, Zendesk are live now.
02·
Meet the workforce
·
Instant
28 named AI employees already work for you. They started the moment you signed in.
💰 Riley already has access to your Stripe. 📐 Scott already has access to your Harvest. 📨 Cole already has access to your overdue invoices. None of them have done anything yet — they ship daily and weekly schedules. You can also run any of them on demand from the COO chat. Each has their own emoji, their own bio, their own page.
Your side
—Each of the 28 named employees appears in the YOUR TEAM section of the sidebar from day one.
—Click any one to read their bio, schedule, and which tools they're scoped to.
—Toggle the autonomy tier per tool — Ask / Auto / Off — if you want to override the defaults.
OpsRadar’s side
—11 named domain agents — Riley (Revenue), Cole (Collections), Scott (Scope), Devon (Delivery), Brian (Briefing), Penny (Profitability), Tia (Team), Grace (Growth), Renee (Renewals), Sam (Stack), Evan (Evaluator).
—17 toolkit specialists underneath them — Stripe Specialist, HubSpot Specialist, Harvest Specialist, and so on. They feed findings up to the named domain agents (orchestrator-worker pattern).
—Senior-COO operator judgment baked into every prompt — signals, thresholds, decision trees, verbatim conversation scripts.
What you walk away with
A full team running on day one. No build phase. No 30-day onboarding. No template configuration. They're hired the moment you are.
↳
The 28 ship the same for every customer. Your custom hires (step 3) are where the workforce becomes yours.
03·
Hire
·
~4 minutes
Describe a role. Sign the offer. They start tomorrow.
Open the Hire chat at /dashboard/hire. Tell us who you want: "I want a Bookkeeper named Sarah, every day at 8 AM, she pulls yesterday's Stripe charges and flags anything over $5,000 for my approval." We compile the spec — name, role, schedule, scoped tools, system prompt, first task on hire. You read it as an inline card. Click Hire. Sarah starts tomorrow at 8 AM.
Your side
—Describe the role in plain English. No JSON, no templates, no nodes.
—Read the spec card. Edit anything you want (system prompt, tools, schedule) before clicking Hire.
—Sarah appears in your sidebar under YOUR TEAM. Click her name → her own chat page opens. She greets you.
OpsRadar’s side
—Compile the spec from your description — name, schedule, tools, scope, first task, 30-50 line system prompt.
—Provision Sarah's row in custom_employees + register her cron on Trigger.dev.
—Sarah gets her own /dashboard/employees/sarah page, her own memory, her own approval queue inheritance.
What you walk away with
A custom AI employee, scoped to the tools you chose, running on the schedule you set. The first hire takes 4 minutes. Most customers spend the next 10 minutes hiring two more.
04·
Approve · learn · graduate
·
Forever
Earned autonomy. The workforce starts cautious. Graduates to fast as you build trust.
Every time an employee wants to do something — send an email, create an invoice, update a deal, post in Slack — the first 30 times that action type fires, it shows up in your approval queue at /dashboard/actions. You read it, see exactly what it'll do, approve or reject. Reject something? OpsRadar learns the rule (Apprentice Mode). After 30+ approvals at >90% rate on a routine action type, that action graduates to Auto-with-notification. Your time stops being burned on the obvious yeses.
Your side
—Read the queue at /dashboard/actions. Approve, reject, or edit each proposed action with a reason.
—Reject anything. The reason you give becomes a permanent rule for that employee (Apprentice Mode).
—Trust accumulates per action-type, not globally. High-risk actions stay Ask forever, regardless of confidence.
OpsRadar’s side
—Classify every proposed action by risk tier: HIGH (Ask forever), MEDIUM (Ask → Auto-with-notify after earned trust), LOW (silent Auto).
—Track approve/reject/edit history per action type per employee. Graduate to Auto only after 30+ approvals at >90% rate on routine action types.
—Apprentice Mode: derive a generalizable rule from every rejection reason. Write it to the employee's permanent learned-rules brain prefix.
What you walk away with
Week 1: Sarah has written 14 Pattern Cards to Real P&L. Week 4: ~80 Pattern Cards, ~40 Decision Logs, ~12 Risks. Apprentice Mode has applied 22 of your rejections as permanent learned rules. Week 12: the brain knows your business. Every employee sounds like a member of your team, not like ChatGPT.
↳
Three things have to align in the same moment: the agent has to propose it, you have to see it, you have to click Approve. The product is structurally incapable of acting without you.

What’s running underneath

The architecture, in one diagram.

You ──→ COO chat / Hire chat / per-employee chat
                           │
                           ▼
                    streamText loop
                           │
                           ▼
                  Nango tool call
                           │
                           ▼
                   Approval gate
                  (Ask / Auto / Off)
                           │
                           ▼
                   ┌───────┴───────┐
                   │               │
                Stripe        HubSpot   (and 23 more)
                  │               │
                  ▼               ▼
              [response]      [response]
                  │               │
                  └───────┬───────┘
                          │
                          ▼
                  Agent writes finding
                  to your company brain
                          │
                          ▼
                  ┌───────┴───────┐
                  │               │
        OpsRadar Postgres   Your Notion
            (versioned)       (mirror)

Every read live-fetches from source. Every write routes through the approval gate. Every finding is signed by the agent and written to two places — OpsRadar Postgres (versioned, immutable) and your Notion (your copy, your forever).

From sign-in to first hire

The first four minutes, click by click.

01
Sign up — email + password. No credit card.
15 sec
02
Connect Stripe — OAuth, 4 clicks.
45 sec
03
Connect HubSpot — OAuth, 4 clicks.
45 sec
04
Open /dashboard/hire. Describe your first AI employee in plain English.
60 sec
05
Read the spec card. Click Hire.
15 sec
06
Click their name in the sidebar. Chat with them. They greet you.
30 sec
07
That's it. They start working on their cron tomorrow.
0 sec

Total time: 3 minutes 30 seconds. Most customers spend the next 10 minutes hiring two more employees.

On ownership

The brain is the asset. It’s yours.

Every AI employee writes findings to a versioned company brain — Pattern Cards, Decision Log, Risk Register, Real P&L, KPI Snapshots, Client Profiles. Every entry is signed by the agent that wrote it, with a timestamp and a commit message. The whole brain is mirrored to your Notion workspace.

If OpsRadar disappeared tomorrow, your Notion still has everything. You can also download the full versioned brain as a markdown zip from /dashboard/brain/download at any time, on any tier. The brain is the artifact you sell when you exit — documented agencies sell at 8–12× EBITDA vs 5–9× undocumented.

Realistic concerns

What founders ask before they start.

Start here

Get on the list.

OpsRadar is in private beta. Join the waitlist for when the front door opens — or talk to the founder for 20 minutes if you’d rather see it run on your stack first.

Coming soon — join waitlist Talk to the founder — 20 min

Private beta · Limited spots · Brain stays in your Notion

Connect the tools you already use.

28 named AI employees already work for you. They started the moment you signed in.

Describe a role. Sign the offer. They start tomorrow.

Earned autonomy. The workforce starts cautious. Graduates to fast as you build trust.

The architecture, in one diagram.

The first four minutes, click by click.

The brain is the asset. It’s yours.

What founders ask before they start.

What stops an AI employee from going rogue?

What do we actually own?

Where does our client business data live?

What if the 28 built-in agents don't cover what we need?

Will we get a surprise bill from token usage?

Get on the list.