In the channel your team already uses

Meet your first AI coworker.

Not a chatbot, and not another tool to learn. Someone with one job, who works where your team already works, checks with a person before anything leaves the building, and writes down everything they did. No hype. No bro nonsense.

The coworkers

They come as roles, not as features.

You do not configure a coworker, you hire one. Each has a job you could describe to a new starter in a sentence, and an expert who signed their name to how they do it.

The assistant

Repetitive, well-scoped work: list-building, data prep, first-draft replies. The things your team does at 5pm because nobody had time at 11am.

The operator

Runs a function with judgment — the content calendar, CRM hygiene, the weekly report. Knows your brand rules because somebody wrote them down for it.

The specialist

Owns a channel or an outcome: ad-ops, pipeline, the recurring deliverable a client notices when it slips. The hire you have been putting off.

The first week

What it is like to work with one.

No migration, no training programme, no new window to keep open. Your team meets them the way they would meet anyone new — in the channel, doing one job.

Day one, they are in Slack

You add them to a channel and ask for something. There is nothing to install and nothing to learn.

They have one job

Not twenty automations. One role, one owner, and a plain answer to “what is this for?” that everybody on the team can repeat.

They ask before they act

Anything that sends, spends, writes or deletes stops and waits for a person in the thread. That step cannot be configured away.

You can see everything they did

Every step is recorded and every record names who asked — in words, not identifiers. Nothing is reconstructed after the fact, because it was written as it happened.

You can stop them with one word

“/a12 pause”, in Slack, mid-sentence. They stop. Nothing else about your workspace changes.

The twelve

The demo is the easy part.

Anything can look good once. These are the twelve things a coworker here will not skip, whether or not anybody is watching — the reason there are twelve is the reason it is called Agentic12.

Install

They arrive in the channel the work already happens in.

Intent

One job, described in a sentence. Not a box of automations.

Owner

A named human owns the output, set per workspace by an admin.

Boundary

What they may touch is a grant, and everything else is refused.

Context

Brand rules and source material they retrieve from, not a pasted prompt.

Preflight

An uncertified version is refused at load. Not warned about — refused.

Execution

Each tool call made with a credential handed over at the moment of use.

Validation

A graded run before they are certified; your ratings after.

Approval

Sends, spends, writes and deletes stop for a person in the thread.

Logging

An append-only record of what ran, what it touched and who asked.

Adoption

“/a12 status, pause, resume, audit” — the off switch is one word.

Packaging

What works becomes a version you can revoke, re-certify or hand on.

Pricing

One price, while we’re building this with our first customers.

An implementation, then a flat monthly for five coworkers. Nothing to diagnose before you can read it, and nothing that changes with how much they work.

Founding Company

$2,500once

Once. Setting them up, connecting your accounts and certifying the first coworkers.

$499/mo

5 coworkers included. Flat — no per-seat arithmetic, and no usage bill to explain to finance.

Start a workspace