Possibilities for companies
| Use | What it would look like | Note |
|---|---|---|
| Pilot area | A channel with 3–4 people and their agents before taking it to the whole company | The video says migrating one unit at a time works better than everyone at once |
| Project manager agent | Reads the kanban, chases a task stuck for a day, does a daily check-in and fixes outdated status | Direct example from the video, connected to ClickUp |
| Content line with approval | Research → draft → approval in the thread → publishing → metric | It is the INEMA video flow, only visible |
| Supervised support | Customer messages enter the channel, the agent suggests the reply and the human releases it | Connects with the support kits (clinic, restaurant, hotel) |
| Agent council | Agents with different roles (optimist, contrarian, neutral) and the owner deciding | Already exists as subagents in the environment |
| Onboarding | The area's agent answers whoever just joined | Needs memory per channel |
| Cost transparency | Consumption panel per room and per person | Shown in the video |
Counterpoints: a new tool does not always replace what the team already uses. The video recommends connecting ClickUp and Drive instead of recreating them. Automations that nobody uses after a week are a risk the author himself points out.