-

Everything not yet collected, across your businesses, read from the database this second. Every number below comes from the running system.

Nothing leaves without you.

Anything irreversible stops here and waits. These are real requests from the running system, not examples.

Watch it work.

Every tool call as it happens, naming what it touched. Credentials are never shown, by design.

Your staff.

Each is a brief the assistant can be asked to wear. Naming one changes how it answers, not what it is allowed to do: the approval ring is the same for every one of them.

Everything on your plate, and where it stands.

Meetings from your calendar, Calendly included, holidays excluded. Deals, proposals and tasks from the ledger the departments keep. Tell Madar what changed, in chat, and this board moves.

The book, as the system holds it.

A projection of the CRM. Nothing here is typed in by hand.

-

Signed and not yet collected. A won deal with nothing received is a promise, not revenue, and the gap between the two is the work. This page exists because the board counted them as the same thing.

-

Madar OS's own customers, read from the events Paddle signs and sends. Recurring revenue counts paying subscriptions only; trials show what they would add. Money stays in its own currency, never added across currencies.

Everyone we could contact, and everyone we have not.

The Clients view is who we already work with and the Pipeline is what is closing. This is the middle, where the work actually is: sourced businesses, whether we can reach them, and whether anyone has.

Your companies, kept apart on purpose.

Each brand owns its own clients, work, pipeline and documents. They are separated here because they are separated in reality: one entity may invoice for several of them, and mixing one brand's proposal into another brand's deck is the one mistake that cannot be walked back.

What is actually being built.

Money that has not landed yet, and what happens next.

A deal with no next step is not a pipeline entry, it is a hope. That column is the one worth reading first.

What is moving, stage by stage.

The same book as the clients table, arranged by where each relationship stands. Nobody drags a card; it moves when the CRM record moves, and the CRM record moves when the work does.

The B2C list, what is queued and what it did.

loading

Cold email, first contact.

loading

What it knows, so you never say it twice.

Every fact below was told once or learned once, and every department reads the same memory. This is the part that compounds, and it is yours: it ships with your deployment and leaves with you.

Your documents, answered from.

Add policies, price lists, contracts, proposals and procedures. Madar reads them here, answers from them, and names the document it used. They stay inside your workspace; only the passage that answers a question goes to the AI with it, the same as anything you type.

What this Madar can actually reach.

Named, not implied. Each row is a real MCP server this Madar loads, and Test proves it by asking the server for its tools. Add your own below from a Claude config, a command on this machine, or an address on the web. A new connector's tools ask you before they act, and scheduled work never gets them.

People talk to one assistant. Behind it, Madar picks the model for each request from what it needs, your rules, each provider's health and the cost, and moves to the next one if a provider fails. Your conversations, memory, tools and approvals stay in Madar whichever model answers.