Public beta

Take AI folks to work
on your initiatives.

CogniWork is a unified workspace where you and AI agents move the needle, together — a dedicated disk drive, automated workflows, human/AI work rooms, specialised AI workers, and integrated media channels: Slack, iMessage, and many others.

Start free Read the guide

Free while we’re in beta. No card. Your workspace stays yours.

You, in chat

The workspace, staffing itself
  • Lead 9 fields · 1 link
  • Touchpoint linked to Lead
  • Pipeline board grouped by stage
  • Going cold no contact > 14 days
  • Nova 4471 Fridays, 08:00 — briefs you

What a workspace comes with

Every instrument the office gave you, without the office

An initiative used to need a filing cabinet, a whiteboard, a machine to run the numbers, a room to argue in, and someone who remembered how it was done last time. A workspace arrives with all of it.

The filing cabinet Data structures Types you never sat down to design. Describe what you keep track of and the tables appear — including the links between them. Start loose; give a type a proper table once it has earned one. The whiteboard Saved views Boards, tables, charts and forms, each bound to a live query rather than a screenshot. Come back tomorrow and the numbers are today’s. The colleague at the next desk AI workers Named colleagues with one specialization each. Run one on demand, put it on a schedule, or let another system call it. They report back whether or not you were watching. The meeting room Group chat Put your teammates and several workers in one thread. Mention a worker and it must answer; leave it unmentioned and the most it does is offer. The process everyone half-remembers Workflows & triggers Ordered steps that fire when a record changes or when the clock says so. AI judgment where the rule is fuzzy, deterministic machinery where it isn’t, and a stop for a human where someone has to sign. The desk and the machine on it Drive & computer Files land in your workspace and stay there. Each workspace gets its own isolated machine to read, transform and write them — no laptop in the loop. The person who has been here longest Memory & skills Decisions, constraints and hard-won facts survive between sessions, so you stop re-explaining your own operation every Monday.

What it replaces

One workspace instead of four subscriptions

Most operational work ends up spread across a spreadsheet that outgrew itself, an automation tool, a dashboard nobody trusts, and a person whose real job is wiring the three together. That is the thing we are replacing.

  • The spreadsheet that outgrew itself Data structures with real queries
  • The automation tool Workflows with human sign-off
  • The dashboard nobody trusts Views bound to live data
  • The person wiring it all together AI colleagues who do the rounds

Not a Notion replacement — Notion is better at documents and we aren’t trying to be. See the full comparison, including the rows we lose.

How a workspace happens

  1. You describe the initiative

    In chat, out loud, or from your phone. Plain sentences — the shape of the work, not a schema.

  2. It gets built

    Types, records, views, workers and workflows appear as real objects. Open any of them, edit them by hand, delete what you don’t want.

  3. It keeps running

    Schedules fire, triggers watch your records, workers do their rounds and report back — whether or not the tab is open.

The meeting room

Colleagues who sit in the thread

A CogniWork worker has a name, a specialization and a job. Put a few of them in a chat with your team and it behaves like a channel where the work actually gets done.

  • @mention one and it must answer. Direct address always gets a turn, in any direction — you to a worker, worker to worker.
  • Leave it un-mentioned and, at most, it offers. A worker that spots something in its lane says one line and waits. It never acts uninvited.
  • Humans and AI share the thread. Several teammates can sit in the same chat and see exactly what every worker did.
  • You can stop any of them mid-sentence. Interrupt one worker, or halt the whole room.
How group chat works

On the go, and plugged in

The workplace goes where you are

A workspace is not a tab you have to keep open. Reach the whole of it from the chat app in your pocket, and let the assistants you already work with reach it too.

Manage it on the go

Your workspace, in your messages

Wire a workspace to Telegram, WhatsApp, Signal or iMessage. Same data, same memory, same colleagues — plus voice notes in, spoken answers out, and files that land straight on the drive.

Slack — coming Accelerate R&D

Your workspace, inside Claude

Point Claude Desktop, a coding assistant, or any MCP client at CogniWork and your workspace becomes a set of tools it can call. You choose which workspaces that connection may touch — one, several, or all.

 Bring your systems in

The tools you already run

Install an MCP server into a workspace — an issue tracker, a CRM, search, an internal service — and its tools become available to the assistant and to any worker you allow.

Boundaries

Where one initiative ends and the next begins

A system that writes its own code and runs it needs walls you can point at. Here are ours — the whole picture is in the security overview.

One workspace, one boundary

Each workspace holds its own data, its own files and its own compute. Nothing crosses between them by accident.

Run two initiatives at once

Two workspaces in two tabs, both working, with neither one bleeding into the other.

Scoped access for outside clients

An external MCP client gets exactly the workspaces you grant it at sign-in, and nothing more — revoke it whenever you like.

Usage you can see

Every assistant turn, worker run and scheduled job is metered per workspace and shown to you.

Bring an initiative you’ve been putting off.

A spreadsheet that outgrew itself. A process living in three inboxes. Give it a workspace and see what comes back.

Start free Read the guide