Company profile

This is the home of one Company: everything about that team in one place. The screen leads with a hero (avatar, name, mission) and then a tab strip that groups the Company’s surfaces into three phases — Build it, Run it, and Know it — so the tabs read as a natural progression from “set it up” to “operate it” to “what it knows.”

How to get here

Open the Companies screen and click a Company tile (its header, or the Open button). You can also land here from a Dashboard tile or by asking Theodor.

The hero

The top strip shows the Company avatar, name, optional mission, and a chip with the role count. If the Company is a client engagement, a “for {client}” chip appears too. On the right is a stack of actions:

• 💬 Talk to {top role} — chat with the most senior role (or pick from a dropdown when there are several). The conversation is auto-scoped to this Company, so the worker’s Library, OS, and doctrine are wired into its context from the first message.
• ✎ Edit company, ⬇ Export (pack the whole Company into a JSON bundle), 💾 Save as template (turn it into a re-applyable Wizard template), and 🌱 Transplant a worker (pull a worker from a saved template into this Company).

🏠 Overview

The default landing tab — a traffic-director that summarizes the Company and points you to whichever sub-tab you need next.

Build it (set-up surfaces, blue band)

Visited occasionally, when you’re shaping the team.

• 🏛 Org chart — the tree of roles. Click a role to inspect the worker behind it, use + to hire an employee under a role (so a manager can delegate to them), and drag roles to re-parent them. A coach auto-appears on small charts to suggest roles.
• ⚙️ Company OS — the Company’s “operating system”: brand voice, doctrine, cadence, SOPs, compliance notes, and vendors. This is the shared context every scoped worker inherits.

Run it (daily work, green band)

The surfaces you touch most.

• ⚡ Operations — the unified pulse. Plans, Routines, tasks, and recent activity for this Company, all on one page. The natural “what’s happening right now?” landing.
• ✅ Tasks — the Company’s kanban board (To-do → In progress → Review → Done). This is the task board; it lives per-Company, here.
• 🎯 Goals — the Company’s goals and OKRs, with progress.
• 📁 Projects — projects scoped to this Company. Each opens a per-project kanban board with its own tasks, library, and comments.
• ⏱ Routines — scheduled or triggered jobs for this Company’s workers (a cron time, a watched folder, a webhook).

Where delegation comes from

Talk to a manager — a role with reports — and they’re handed a delegate_to_subordinate tool listing their direct reports. Delegation chains are capped at three levels deep, and every tool call shows in the timeline so you can see who did what.

Know it (reference, amber band)

The knowledge layer for the team.

• 📚 Library — the Company-scoped knowledge base: documents, SOPs, links, files. It’s searchable and, whenever a chat is scoped to this Company, folded into the worker’s context via RAG. See the full Library page.
• 💬 Chat — speak with the Company itself as a single voice (a synthetic “company voice” persona, grounded in the Library and OS), and use 📣 Broadcast to post a message to the whole team via the Company’s Kafenio room.

Tasks, goals, and routines are per-Company

These primitives don’t live at the top level — each Company has its own scoped view of them under Run it. The workforce-wide Workers hub is about people, not their task board.

In practice

The Company OS is the highest-leverage thing on this screen. Brand voice, doctrine, SOPs and cadence written once are inherited by every scoped worker, which means you stop repeating “keep it formal, we never promise delivery dates, always cite the source” in individual prompts. When output across a whole team drifts off-tone, the fix usually belongs in the OS, not in five separate personas.

The org chart is functional, not decorative. Hiring a worker under a role is what hands the manager a delegate_to_subordinate tool listing its reports. Two things follow:

• You can ask one worker for a multi-part deliverable and it will farm out the pieces — but only if there are workers beneath it. A flat chart means no delegation, whatever you ask for.
• Chains stop at three levels, and every hand-off appears in the timeline, so “who actually wrote this” is answerable rather than a mystery.

Scoped chats bring context automatically. Talking to a role from this screen wires that Company’s Library, OS and doctrine into the conversation from the first message. It’s why the same worker gives noticeably better answers here than from a cold chat window — and why pasting the brand guide into a prompt is redundant once it’s in the Library.

Save as template once a Company works. It becomes re-applyable from the Wizard, so the second client engagement or the second product team starts from your proven structure rather than a generic one. 🌱 Transplant does the same for a single worker you got right.

Tasks live here, per-Company — the kanban board is under Run it → ✅ Tasks, not on the Workers hub. If a Company’s board is permanently empty while its workers are busy, work is arriving via chat rather than tasks, and nothing is tracking it.

🎓 Learn it hands-on: Company OS: brand, compliance, vendors · Org roles & reporting lines

Terms in this page

• Company — a named team of AI workers with its own org chart, knowledge, and operating surfaces.
• Mission — the one-line purpose of the Company, shown in the hero and folded into scoped workers’ context.
• Org chart — the tree of roles showing who reports to whom; the basis for delegation.
• Role — a seat in the org chart (e.g. “Head of Marketing”) filled by a worker.
• Delegate / delegation — a manager handing a sub-task to a worker beneath them, who runs their own loop and reports back. Capped at three levels deep.
• Company OS — the Company’s shared “operating system”: brand voice, doctrine, SOPs, cadence, compliance, vendors — context every scoped worker inherits.
• Doctrine — the Company’s standing rules and principles, part of the OS.
• SOP — Standard Operating Procedure; a documented how-to the team follows.
• Scope / scoped conversation — binding a chat to a Company so its Library (RAG), OS, and doctrine are added to the worker’s context automatically.
• Kanban — a board with columns (To-do, In progress, Review, Done) where each task is a card you move across as it progresses.
• Goal / OKR — an objective with measurable key results; the Goals tab tracks progress toward them.
• Project — a scoped unit of work with its own kanban board, library, and comments.
• Routine — a job that runs on a schedule or trigger (cron time, watched folder, webhook), usually unattended.
• Plan — a multi-step effort a worker breaks down and executes; surfaced on the Operations tab.
• Library (RAG) — the knowledge base. RAG (Retrieval-Augmented Generation) feeds relevant documents to a worker so its answers are grounded in your material.
• Broadcast — posting one message to every worker on the team at once, via the Company’s Kafenio room.
• Kafenio — the in-app “café” room where a Company’s workers talk; the Chat tab broadcasts here.
• Template — a saved blueprint of a whole Company you can re-apply from the Wizard.
• Transplant — copying a worker out of a saved template into another Company as a fresh persona.