Operations · Internal system

AI operations manager for a team

Tasks lived in Notion, a CRM, kanban boards and chats, and every morning went into pulling them together. We automated the layer between the tools, and we have been using it ourselves ever since.

Built and running here
Notion + CRM Plan for the day Automatic reports
0
reports written by hand, summaries build themselves
1 plan
instead of tasks in three separate tabs
Every morning
a personal plan for the day, per person
0
reporting assembled by hand
01 Context

The team's work was spread across tools

The team worked in several tools at once: Notion, a CRM, kanban boards and work chats. Every morning people spent time pulling their tasks into one list, and the lead had to ask around to find out what was done and what wasn't.

As the team grew this got more obvious. The more projects ran at the same time, the harder it was to keep a common rhythm.

02 Why we started here

The time went into assembling the work, not doing it

The problem wasn't how the team worked. It was how long it took to work out who was doing what.

We didn't build another task tracker: the tools were already there. We automated the layer between them, which is where the time went every day.

03 What we built

One agent assembles the team's work for them

Every morning the AI agent collected tasks from all the work services and put them in order. Instead of a list spread across three tabs, people got a finished plan for the day.

Through the day it reminded people about deadlines and checked status. By evening it was clear what had been done and what hadn't.

In the evening it wrote up a report, on Mondays a plan for the week, on Fridays a summary for the lead.

04 One working day

What it looks like from the inside

first thing

The team gets a personal plan for the day.

Morning brief: a list of priority tasks for the day with importance markers
The morning brief with priorities. Names and client projects are hidden.
midday

The AI reminds people about tasks and checks where things stand.

Task status for the day: how many are done, in progress and still queued
The agent pulls together task status: done, in progress, queued.
end of day

It asks for a report on the day.

Evening report request: the agent asks what got done today
In the evening the agent asks for the report itself, in plain text, no template.
end of week

The lead gets a summary of the week.

Weekly summary for the lead: results, problems, and direction for the next week
The week for the lead: what got done, where it slipped, what to aim at next. Names are hidden.
05 What changed

Coordination stopped eating the day

The team no longer spends time on daily coordination or on writing up reports by hand.

The lead sees the whole picture at once, without switching between services.

0
reporting assembled by hand
1 plan a day
instead of tasks in three tabs
One picture
of every task, without switching
Get started

We'll show you a solution built for your problem

Let's find the process that takes time from your team every day.