AI Workforce

Staff you configure,
not software you prompt

Six roles ship ready. Each one is a configured instance of a single runtime — same permissions, same budgets, same audit trail — so adding an agent is a staffing decision rather than an engineering project.

CMO

Owns the marketing picture

Reads campaigns, analytics, CRM and assets. Drafts campaigns and content, and proposes budget moves with the reasoning attached.

Needs approval
Spending advertising budget · publishing
Denied outright
Payroll, billing settings, deleting the organisation

Sales

Turns interest into conversations

Scores intent, qualifies leads, drafts outreach and keeps CRM records current.

Needs approval
Contacting a customer · changing CRM records
Denied outright
Image and video generation, finance

Content

Produces the work

Turns a brief into copy, images, video and audio, files them as drafts and schedules them.

Needs approval
Publishing anywhere public
Denied outright
Crawling, customer contact

Research

Watches the outside world

Tracks competitors, audiences and market shifts across search, the open web and your own data.

Needs approval
External tool calls
Denied outright
Writing to CRM, generating media

Analytics

Explains what happened

Joins campaigns, CRM, conversions and spend to answer why a number moved, not just that it did.

Needs approval
Nothing — it only reads
Denied outright
Browser, crawler, any outbound reach

Operations

Keeps the machine running

Opens tasks, chases deadlines, triggers workflows and keeps integrations moving.

Needs approval
External systems
Denied outright
Nothing by default — its remit is internal

Control

Every agent has a job description you can read

Autonomy is granted per capability, not per agent. An agent might draft freely, need a person for anything public, and be refused entirely on things it has no business touching — and that boundary is enforced on the server, not suggested in a prompt.

High-risk actions need approval for that specific step. Approving one campaign does not approve the next.

AGENT INTENTL1RUNSL3WAITS FOR A HUMANDRAFT · ANALYSE · ORGANISESPEND · PUBLISH · CONTACT CUSTOMERS

Configuration

What you actually set up

IDENTITY

Name, avatar, persona and tone. An agent your team recognises, not 'Assistant 3'.

INSTRUCTIONS

System prompt, objectives, behavioural rules and the outcome it is accountable for.

KNOWLEDGE

Domain knowledge and a memory scoped to one workspace, so a client's context never crosses into another.

TOOLS

The exact capabilities it may call, from language models to your connected integrations.

PERMISSIONS

A matrix per capability: allow, require approval, or deny. Denied wins, and an empty allow list denies by default.

BUDGET

Token and monetary ceilings per task, plus the threshold above which spending needs a human.

MODEL

Which model backs it, so cost and capability are a choice rather than a default.

Accountability

Managed like staff, measured like staff

Each agent carries its own record: tasks completed, approval rate, activity volume, and the real cost of the work it did — provider spend attributed to that agent, not pooled into an anonymous AI line. When one earns its keep you give it more remit. When one does not, you can see that too.

base44
Edit with Base44