Mudo for small architecture practices
For studios of two to ten, where the director is also the resourcing plan, the fee tracker and the QA process, and the cost of that is invisible until it is not.
- Resourcing
- Commercial
- Knowledge
- Delivery
A small practice has no operations team. It has a director who is also the resourcing plan, the fee tracker, the quality process and the institutional memory.
That works, and it works well, right up to the point where it does not, usually when a fourth project arrives, or when the person holding it takes a fortnight off.
The specific failures
They are always the same three.
Resourcing is rebuilt weekly from memory, takes an hour, and is wrong by Wednesday because the programme moved on Tuesday.
The commercial position is known twice a year, thoroughly, and approximately the rest of the time. Variations get agreed on site and never invoiced.
Knowledge lives in one person. When they are unavailable, the practice slows down; when they leave, it loses years.
Why per-practice pricing matters at this size
Priced per seat, a small practice pays a penalty for including the people who most need to see the system: the part-time technician, the bookkeeper, the graduate.
Mudo is priced per practice. Adding a graduate does not change the bill, which means the whole studio can be in the system rather than only the people who could be justified.
Starting small is the point
Starter is free: one user, two projects, 1GB. That is not a trial with a countdown. It is enough to run a real job and find out whether the model matches how you work.
Try it on a real project
Free for solo practices: one user, two projects, no card.