Mudo
Start free (opens in a new tab)

MudoInternal

Site Admin

Website intelligence and enquiries

Enter

Who Mudo is for

Built for architects,not for everyone.

Mudo is built for architecture practices first. That focus is the reason the vocabulary is already yours, and the reason it will not suit everybody.

One system. Three practice conditions.

  1. A small practice

    • Resourcing
    • Commercial
    • Knowledge
    • Delivery
    Resourcing, the fee position and what the practice knows all sit on one person, because there is nobody to give any of it to.

  2. A growing practice

    • Resourcing
    • Commercial
    • Knowledge
    • Delivery
    Past one head they come apart, and in a stated order: resourcing first, then the commercial picture, then consistency, then memory.

  3. An architecture practice

    • Resourcing
    • Commercial
    • Knowledge
    • Delivery
    Staged work, fees agreed in advance and issued drawing sets give the same four functions something to be set out against.

By practice

  • Mudo for architecture practices

    Built for practices whose work is staged, whose fees are agreed in advance, and whose projects involve consultants, approvals and drawing sets, not for generic knowledge work.

  • 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.

  • Mudo for growing architecture practices

    For studios past the point where one person can hold it all, where the work is now to make the practice legible to more than one head.

Where Mudo fits, and where it does not

It fits when

  • Your fees are staged and agreed before the extent of the work is known.
  • Your programme depends on approvals you do not control.
  • You work with consultants who are neither employees nor clients.
  • Your deliverables are drawings, issued in sets, with revisions that matter.
  • Somebody in the practice maintains a spreadsheet the software should handle.

It fits less well when

  • Your project work is genuinely generic and a flexible tool would serve you.
  • You need one system across disciplines that are mostly not architecture.
  • You want to design your own workflow model rather than adopt one.

Interior design practices are a secondary audience and much of Mudo applies, but the model is built around architectural delivery, and we would rather say so than imply a fit that is not exact.

Working out whether it suits you

  • How Mudo compares

    Honest comparisons between Mudo and the general work-management platforms architects most often evaluate, written without inventing weaknesses in other people's products.

  • Architecture practice management software

    What architecture practice management software is, what it has to handle that generic work tools do not, and how to judge whether a system is built for architects or configured for them.

  • Pricing

    Mudo pricing in Australian dollars, charged per practice rather than per seat. Starter is free. Basic, Pro and Studio scale with the practice.