AI Partners · The Headquarters
Every client gets agents.
This is where they work.
The Headquarters is the portal your clients log into: agents do the work, workflows run logged, the numbers report themselves. Six surfaces live today, three more in build — Agent Studio, Workflow Builder, everywhere access. Real screens on the live ones, honest schemas on the coming ones.
aipartners-platform.staging.app/login
RUNS ON
- Vercel + Supabase — live today, not a mockup
- Three login doors — client password + code, email code, admin
- 14-day sessions, httpOnly, browser never sees the token
WHAT THIS DECK IS
One slide per feature. A real screenshot on every slide. What it does, what it proves. Sample data is labeled sample. Nothing pretends.
AI PARTNERS · FEATURE TOUR
01 / 13
First, the whole journey — one view
From lead to monthly return, in eight steps.
Everything below happens inside the HQ. This is the only process slide; the rest of this deck is the product itself.
/agency/hq — the pipeline
WHAT YOU ARE LOOKING AT
- The HQ pipeline — every engagement by stage, commercial state, next action
- One click turns a website lead into a private client + engagement
- Nothing between stages gets lost: every move is logged
AI PARTNERS · FEATURE TOUR
02 / 13
Surface 1 of 6
Command Center LIVE
The cockpit. One screen answers the owner's only real question: what ran, what did it return, what needs me?
/c/…/command
WHAT IT DOES
- ROI cards up top — improvement, value, hours saved, return multiple
- Every workflow listed with its trend and its status
- Live activity feed — what the agents just did, as it happens
WHAT IT PROVES
The client never wonders what they are paying for. The screen is the receipt. (Sample data labeled sample until their own flows in.)
AI PARTNERS · FEATURE TOUR
03 / 13
Surface 2 of 6
Workflows — the work, done by agents LIVE
Every repeated task becomes a workflow an agent runs: document processing, email triage, follow-ups, quoting. Logged, every run, forever.
/c/…/audit — the operations trail
WHAT IT DOES
- Agents execute the workflow; the audit view shows every step they took
- Risky steps wait in the human gate (approvals, slide 7)
- Approved runs promote the trust ladder: the agent earns autonomy rung by rung
WHAT IT PROVES
Not a black box. Every agent action is inspectable after the fact, by the client, not just by us.
AI PARTNERS · FEATURE TOUR
04 / 13
Surface 3 of 6
Second Brain — where their data lives LIVE
The client's knowledge in one place: documents, sources, decisions. Every workflow and every answer draws from it. Consent-scoped, nothing shared.
/c/…/brain
WHAT IT DOES
- Sources in, answers out — the brain every agent reads before acting
- Brains can be shared company-to-company under explicit grants, read-only or read-write
- What the client puts in stays theirs — it is their asset, not our dataset
WHAT IT PROVES
The agents get smarter about their business specifically, not from generic training data.
AI PARTNERS · FEATURE TOUR
05 / 13
Surface 4 of 6
Business Intelligence — their numbers, in writing LIVE
The append-only ledger underneath everything: hours returned, money found, payback. Computed from the client's own people's numbers, never industry averages.
/agency — every client's numbers
WHAT IT DOES
- Every outcome lands in the ledger: what ran, hours saved, value
- ROI computed from the client's own rates and hours
- Monthly report: what ran, what it returned — the same math we sell
WHAT IT PROVES
If a workflow does not pay back, the numbers say so out loud. That honesty is the product.
AI PARTNERS · FEATURE TOUR
06 / 13
Surface 5 of 6
Agents — the workforce, governed LIVE
A set of agents per client, plus one we deploy to run their HQ workflows. Every agent works under a scoped token, audited, revocable in one click.
/platform — the registry
CLIENT LIST — NAMES WITHHELD BY POLICY
WHAT IT DOES
- aipst_ tokens: each agent gets exact scopes (read:registry, write:companies, run:brain)
- An agent token acts as the platform org, never as a human
- One click revokes any agent. Last-used tracking on every token
WHAT IT PROVES
"Agents, agents, agents" — with a kill switch on every one of them. Power without custody risk.
AI PARTNERS · FEATURE TOUR
07 / 13
Surface 6 of 6
Custom Applications — stop renting your own invoicing SAMPLE · WIRING NEXT
If they pay monthly for an invoicing tool, a quoting tool, a follow-up tool: they can own theirs. Same screens, their brand, their data, no subscription.
/c/…/apps/invoicing

/c/…/apps/quotes

WHAT IT DOES
- Invoicing, Quote Desk, Follow-up, Sentinel, Voice — app screens inside the client's portal
- Each app reads the client's own rules and rates (their pricing logic, not generic)
- Every quote and invoice lands in the ledger as an outcome
WHAT IT PROVES
The subscription pile shrinks. Screen data is sample today, labeled as such — wiring is the next build phase, on each client's real rules.
AI PARTNERS · FEATURE TOUR
08 / 13
The compounding mechanic
Workflow proves itself. Then it becomes an app.
The same move every time: a workflow runs for one client, the ledger proves what it returns, we duplicate it as an application — and every future client gets it on day one.
/agency/snapshots — the app library
THE LOOP
- 1. Workflow runs for one client, logged and measured
- 2. The ledger proves the return
- 3. It is duplicated as a reusable application, data-free
- 4. The library grows — every new client starts with everything we ever built
WHY CLIENTS CARE
Month 12 costs less and does more than month 1. The HQ compounds; subscriptions only renew.
AI PARTNERS · FEATURE TOUR
09 / 13
The build · Surface 7
Agent Studio ROADMAP · IN BUILD
A person at home opens their Headquarters, checks in on their agents, and makes a new one. Directions, tasks, connectors, folder structure, APIs, MCPs — bang, up, agent is made.
/studio/new-agent — interface schema, not a screenshot
THE AGENT FORM
- Name + role ("Dispatch Agent")
- Directions — what it may do, in plain words
- Tasks — what it owns, on what schedule
- Guardrails — what always waits for a human
ITS TOOLBOX
- Connectors — inbox, calendar, Drive, the client's tools
- APIs + MCPs — plugged in, scoped, revocable
- Folder structure — its own workspace, versioned
- Second Brain access — what it may read
DEPLOY
- 1. Draft it — the agent proposes its plan
- 2. Test it — run on sample work, inspectable
- 3. Gate it — trust ladder starts at rung zero
- 4. Bang. — live, logged, revocable
WHY IT MATTERS
Agent power stops being a developer service and becomes a thing the client operates from their kitchen table. Check in, make one, throttle one.
BUILT ON WHAT EXISTS
- The scoped aipst_ token system (slide 07) is its engine
- The trust ladders + approvals are its guardrails
AI PARTNERS · FEATURE TOUR
10 / 13
The build · Surface 8
Workflow Builder & Mapper ROADMAP · IN BUILD
Map the process once, test it live, promote it to production. The client watches their own workflow get built instead of reading a proposal about it.
/studio/workflows — interface schema
TEST
Dry runs, inspectable
WHAT THE MAPPER SHOWS
- Every step: who does it (which agent, or which human)
- Every handoff: what triggers it, what it touches (brain, connectors, apps)
- Every run after that: the same map, animated — where work sat, where it flowed
WHAT IT DOES
- Test a new workflow without a build cycle
- Proven workflows duplicate into apps (the flywheel, slide 09)
- The map becomes the audit view: live runs on the same picture
WHY IT MATTERS
"What would you automate?" becomes a screen they play with, not a questionnaire they dodge.
AI PARTNERS · FEATURE TOUR
11 / 13
The build · Surface 9
Everywhere access — the HQ is the home, any front-end ROADMAP · IN BUILD
Browser today. And because we build the connectors, the same Headquarters answers from Claude Code, Codex, ChatGPT, or the CLI: check in, chat with the agents, run a workflow, from whatever the client already lives in.
the HQ in the browser — live today

same HQ, from the CLI / your AI — schema
$ hq agents
dispatch · idle 2m · 14 runs today · 3.2h saved
inbox-triage · running · 61 runs · 5.8h saved
$ hq chat dispatch
> All rides confirmed for tomorrow.
$ hq workflow test quote-v2
> dry run ok · 3 steps · human gate on pricing
HOW
- MCP + APIs: the HQ exposes its surfaces to any AI client
- Same scoped tokens, same audit trail, whichever door they enter
- Claude Code, Codex, ChatGPT, CLI: one Headquarters behind them all
WHY IT MATTERS
No new habit required. The client's favorite tool becomes their HQ window. Adoption stops being our problem.
AI PARTNERS · FEATURE TOUR
12 / 13
The Headquarters
It runs today. Come click it.
Six surfaces, one login, agents doing the work and humans holding the gate. The screens in this deck are real — the next ones could be yours.
LIVE APP
aipartners-platform-staging.vercel.app
BOOK 15 MINUTES
cal.com/bjovibes/15minaipartners
AI Partners · Leuven · client names withheld by policy
AI PARTNERS · FEATURE TOUR
13 / 13