What is YAGNI and how does it run a business?

What does “one agent that has read your whole business” mean?

YAGNI is built around a single agent with a handle: @yagni. One identity, one memory, across every tool you connect. It is not a per-app helper that knows one tool’s slice of the picture. It reads your email, your chat, your CRM, your issue tracker, and your billing in one pass, so when it tells you a deal stalled, it already knows about the unanswered thread in Gmail and the open issues in Linear that are blocking it.

That single memory is the difference between an agent worth listening to and a text box that makes you do the assembling. You talk to it like a colleague, and it answers with its read and how confident it is, cited back to the rows it came from.

Which surfaces make up a YAGNI workspace?

Every workspace is organized around the same small set of surfaces. Each one has its own lesson in the Academy, but here is the map:

Surface	What it is
Front	The always-current page of where the business stands right now
Brief	A dated snapshot of the Front, composed by @yagni
Team	A part of the business @yagni watches and runs, defined by its Responsibilities
Feed	The doing surface: one item, one chat, rendering the real artifact
Inbox	Triage with honest receipts: amber needs you, teal is handled
Library	The shared store of docs and context the Teams read and write
Calendar	The agenda @yagni reads and prepares against
Work	The cross-Team surface for work-items that span Teams
Connections	The tools YAGNI reads and ships approved work back to

The surfaces share one register: finite, edited, and citable. You read to the bottom, you make the calls that are yours, and you are done. There is no infinite feed to scroll.

What does @yagni do on its own?

The routine and reversible work. It triages the inbox and files the noise. It keeps the Front current before you open it. It drafts the replies, follow-ups, and updates that are obviously next, and it logs every action it takes so you can see exactly what happened. Every receipt carries the actual tool call underneath it. It is never a black box.

What stays in your hands?

The consequential and irreversible calls. When something carries real weight, @yagni stops, shows you the real thing rather than a summary of it, an editable draft, the evidence it checked, its confidence, and waits. You approve, decline, or talk it through. Every call you make teaches it your judgment, which is how each Team earns wider autonomy over time. The floor is permanent: irreversible and high-blast actions always need a person.

Where does YAGNI sit in your stack?

On top of it. YAGNI is additive: it connects to the tools you already pay for, reads across all of them, and ships approved work back into them. It does not host your apps and it does not migrate your data. The Connections lesson covers the native connectors and what each one feeds, and the security page covers how workspace data is isolated and audited.

Where should you start?

Connect your tools and read your first Brief. The next lesson, How do you get your first Brief?, walks through it step by step. If you would rather see it live first, book a demo or look over the plans. Every plan includes the full workspace and every connector; the difference is how much work @yagni can carry for you.