Is this a client case?

No, and we say so plainly: this is our own operation. Every figure on this page is from our house, not a client result. We publish it because it answers the question everyone thinks and almost nobody asks out loud.

Why does the sync only run one way?

Because a board edited by hand and real work that says something else produce two truths, which means there is none. The project leads; Notion reflects. The only exceptions are the fields that make no sense outside Notion — stage, amount, tags — which are edited there and which the sync leaves alone.

What about document history?

Notion always shows the current version of each SOW, proposal, or quote, marked internal or shareable. Earlier versions are never deleted or overwritten: they are archived. An old price presented as current is an expensive problem, and that is the mistake this rule exists to prevent.

Is this the same thing you would propose to us?

The principle, yes: one source of truth, with clear owners, and agents that consult it instead of improvising. The specific pieces change with each organization — ours is tied to project folders because we also write code. What does not change is the order: knowledge first, agent second.

What happens when the system gets it wrong?

It gets things wrong, like everything does. It misfiles a meeting, or over-summarizes. That is why it asks when unsure instead of guessing: a well-written file in the wrong folder is worse than no file, because nobody will look for it there. The difference is that the errors cost us first.

Us first: La Agencia's entire operation lives in Notion | Case study

Q: Where do tasks live?

In Notion, in their own database, linked to the project that produced them and assigned to an owner. They are not captured by hand: they appear. When a set of minutes detects an action item with an owner, the task creates itself. Items that come up outside a meeting can be dictated by message and land in the right project without opening the app.

There is a question a client rarely asks out loud and is always thinking: do you actually use this, or do you just sell it?

This is not a client case. It is our own operation, built on Notion, and we publish it because it is the answer.

What happens in a meeting

A bot joins our meetings. It listens, transcribes in real time, and when someone calls it by name, it answers out loud — in Mexican Spanish, not in a dubbing-studio neutral. Most of the time it says nothing, which is exactly what is asked of it.

Afterward, an agent takes that transcript and does the work nobody wants: it decides which project the conversation belongs to, drafts the minutes, pulls out the agreements and the action items with their owner, and publishes it. When the classification is ambiguous, it asks instead of guessing.

Nobody writes minutes by hand. And because the minutes always exist, the information stops depending on whether somebody had time to take notes.

Where it all lands: Notion

The whole operation lives in seven connected databases.

Projects is the main board: a kanban by stage, from first contact to won or lost, passing through qualification, discovery, proposal, negotiation, and delivery. Each card carries its company, its end client, and the amount.

Meetings hangs off each project. Open the card and you see every session that took place, with its date, its attendees, and the full minutes. Nobody has to ask “what did we agree last time?” again.

Documents holds the current state of each SOW, proposal, quote, and contract, marked internal or shareable with the client. Notion always shows today’s version; the full history is archived.

Tasks is where the work to be done lives, linked to the project that produced it and assigned to an owner. Tasks are not captured: they appear. When a set of minutes detects an action item with an owner, it creates itself. And when something comes up outside a meeting, it is dictated by message and lands in the right project without opening the app.

Companies, Clients, and Demos complete the map: who is who, and what is deployed where.

The decision that holds it together: the sync runs one way

This is the part we usually end up debating with clients, so it is worth explaining with our own case.

Notion is not where somebody records progress. It is where progress is reflected. The real work — the written scope, the quote that went out, yesterday’s minutes, the versioned deliverable — is what leads, and Notion projects it. Changing a deal’s stage means changing the work, not the board, and the board finds out on its own.

The reason is boring and decisive: a board updated by hand goes out of date. Always. And the moment the board says one thing and reality says another, you no longer have a source of truth — you have two versions somebody has to reconcile on Fridays.

There are three deliberate exceptions: deal stage, amount, and tags are edited directly in Notion, because they are commercial judgments that live nowhere else. The sync respects them and never overwrites them. Everything else flows in one direction.

What we learned by breaking it

Almost every rule we apply with clients came out of one of our own mistakes.

Minutes hang off their project rather than a central repository because we once lost track of an important decision that had been written down, just in the wrong place. Documents are versioned and never overwritten because we once presented an old price as current, and it was expensive. And the agent asks which project something belongs to when it is unsure, because an impeccable file filed in the wrong place is worse than no file: nobody will look for it there.

None of those rules occurred to us at a whiteboard.

Why it matters to your operation

All of the above is exactly what we propose: one source of truth, with clear owners, and agents that consult it instead of improvising. Notion is the right tool for that layer — connected databases, permissions by team, all the context one click away — as long as somebody decides what leads and which way the information travels.

So when we say an agent is only as good as its knowledge base, it is not a brochure line. It is what we learned fixing ours, in the one operation where the mistakes cost us.

Want to see it running?

Book a 30-minute session. It is a normal meeting with one difference: when it ends, you get the minutes the system produced, with the agreements and the action items already assigned. It is the cheapest demonstration we have and the hardest one to fake.

Us first: La Agencia's entire operation lives in Notion