The platformIntelligence
The Brain reads relationships, not records.
One question is asked of every live project, and answered only where the evidence supports an answer.
The Brain
Everything is evidence. Not everything is a reason.
One question, asked of the whole practice: does this project need attention? Seven records could answer it. Watch what happens to each.
Seven records could bear on the question. Not one of them is an answer yet.
The interpretation
RecordWhat the practice wrote down
Frank6 active projects · all clear
Frank states what the Brain computed and nothing more — he cannot report a figure it did not produce. Every branch drawn here is a rule in the product. No project, client, person, date or amount is real.
What it was reading
Every state on that drawing came from somewhere.
In short
AvailableAvailable now to practices on a qualifying plan.- What it is
- A live map of the whole practice. Every active project is a node, sized by how much work is open on it and coloured by whether it is stable, under building pressure, or needs attention now.
- Who it is for
- Directors and project leads who need to know where the practice stands without opening eleven projects to find out.
- What is different
- It is the default landing screen. Most practice software makes the dashboard a report you navigate to; in Mudo the practice-wide view is the front door, and the detail is what you drill into.
- Availability
- Available on every plan, including the free Starter tier.
- How it connects
- The Brain reads projects, programme, resourcing, time and fees. Selecting a project opens its Project Pod. Frank narrates the same data in a sentence.
Part of Intelligence.
Verified against the Mudo application on .
How the Brain decides what needs attention
Attention is derived, not declared. One question is asked of every live project — does this need attention? — and the same rule answers it for the Brain and for the projects register, so the two cannot disagree.
Overdue work is a reason on its own, and so is a blocked item. Work due in the next seven days is not: it becomes a reason only once it accumulates past a fixed threshold, and below that the project is one to watch, which is a separate state rather than a quieter version of the same one. A record past its date that also carries a completion is set aside, and dated work on a prospect is left out because attention is asked of active client delivery.
A project with nothing dated recorded against it is held rather than answered. It is not reported as clear, because nobody knows that it is. Software that always has an answer is software you have to check.
Why it is the front door
The decision that gives the Brain its value is a product decision, not a visual one: it is where Mudo opens.
A practice-wide view that lives three clicks away gets looked at on Mondays. A practice-wide view that is the landing screen gets looked at every time anyone signs in, which is the only frequency at which "this project needs attention" is useful information.
What it is not
It is not a predictive model, and it does not generate advice. It reads records and applies rules. That is a weaker claim than most software makes about its dashboard, and it is the reason the states can be trusted. Every one of them can be traced back to the thing that caused it.
Common questions
What is the Mudo Brain?
The Brain is Mudo's practice-wide view. Each live project is drawn as a node whose size reflects the volume of open work and whose colour reflects its attention state. It is the screen Mudo opens on, so the state of the practice is the first thing you see rather than something you assemble.
Is the Brain the same as a dashboard?
It serves the same purpose but sits in a different place in the product. A dashboard is usually a summary you visit; the Brain is the default landing screen and the way you navigate into projects. The attention states are derived from the underlying records rather than entered by hand.
Is there a Project Brain?
No. There is no product called Project Brain. The project-level equivalent is the Project Pod, which holds one job completely. Describing a Pod as "a brain for the project" is a description, not a product name.
What this page is based on
Every capability described here was checked against the running application before publication. These are the parts of it you can open for yourself.
- /brainBoth the Brain and the dashboard home resolve here, which is what makes it the screen the application opens on.
The answer you can trust is the one it refused to guess.
Free for solo practices: one user, two projects, no card.