Mudo
Start free (opens in a new tab)

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.

  • Resourcing
  • Commercial
  • Knowledge
  • Delivery
They are already set out against staged work, agreed fees and issued drawings.

Mudo is built for architecture practices first. Not for creative agencies, not for professional services generally, and not for construction.

That focus is the product decision everything else follows from.

What it assumes about you

That your fees are staged and agreed before the extent of the work is known. That your programme depends on approvals you do not control. That you work with consultants who are neither employees nor clients. That your deliverables are drawings, issued in sets, with revisions that carry weight. That somebody in your practice is currently maintaining a spreadsheet the software should have handled.

If those are true, the vocabulary in Mudo will already be yours.

What changes

The practical difference is that the connections between things are held by the system.

A programme stage moves and the resourcing plan moves with it. A variation is agreed and the fee position reflects it. A set is issued and the deliverable is recorded. Time is booked against the stage the fee was structured around, so the next proposal can be priced from evidence.

None of that is exotic. It is what practices already do by hand, on Mondays, imperfectly.

Where to start

Start with one live project rather than the whole practice. Put its programme, fee and registers in, and use the Brain to watch it alongside whatever else you are running.

The free Starter tier covers one user and two projects, which is enough to find out whether the model fits how you work.

Connected to this

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

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

  • The platform

    Everything Mudo does, arranged the way a practice actually works: winning, running, delivering, the money, the knowledge and the making.

Try it on a real project

Start free (opens in a new tab)Book a demo

Free for solo practices: one user, two projects, no card.