Mudo
Start free (opens in a new tab)

The platform

Change one thing — watch what answers

Mudo is not a set of tools that happen to share a login. Pick an event a practice would recognise, and follow it through the parts that actually respond.

  1. ProgrammeWhere the event happens.
  2. Resource planning for architectsWho is free, and when, moves with it.
  3. Fees and variationsThe stage claim moves with the stage.
  4. InvoicingWhat is claimable this month changes.

Every path shown is one the capability pages already declare. A step between two parts of Mudo that are not connected in the evidence model fails the build. 4 of 17 capabilities respond to this event.

The screen it happens on

Move a stage and the dates, the deliverables and the fee stage that depends on it move with it.

Drawn in the product’s own template vocabulary, on a representative programme — a recreation, not a screenshot. No date, project or person is real.

All of it sits behind the building

A low timber-clad pavilion on a snow-covered headland, its glazed entry open to the sea beyond.
Licensed photography by Pavel Danilyuk · not a Mudo project record

All six events

  1. A stage date moves

    The most ordinary event in an architectural project, and the one that costs the most when nothing else hears about it.

    1. Programme
    2. Resource planning for architects — Who is free, and when, moves with it.
    3. Fees and variations — The stage claim moves with the stage.
    4. Invoicing — What is claimable this month changes.

  2. An enquiry becomes a project

    The handover that is usually retyping. Here the fee that was agreed is the fee the project starts from.

    1. CRM for architects
    2. Fee proposals — The enquiry becomes a structured, staged fee.
    3. The Project Pod — The accepted proposal opens as a job.
    4. Programme — Its stages become the programme.

  3. Work gets done

    Where the plan meets what actually happened, and where a fee is quietly absorbed.

    1. Resource planning for architects
    2. Timesheets — Planned effort meets recorded effort.
    3. Fees and variations — The real cost of the stage becomes visible.
    4. Invoicing — What can honestly be claimed is known.

  4. A question comes back from site

    An RFI is not correspondence. It is a record with consequences for the drawings and the job.

    1. RFIs, issues and variations
    2. Drawing review — The answer lands against the drawing set.
    3. The Project Pod — The job carries the decision from then on.
    4. The Brain — The project's attention state reflects it.

  5. The contract changes

    Not the practice's fee — the builder's contract, where a question answered on site can end up moving the date the works must finish by.

    1. RFIs, issues and variations
    2. Contract administration — The RFI becomes what an instruction is raised from, and a variation follows the instruction.
    3. Programme — A determined adjustment of time moves the contractual date. The builder's forecast is a different fact and stays one.

  6. The practice learns something

    The clause that settled an argument, kept where the next project will find it.

    1. RFIs, issues and variations
    2. Practice knowledge and memory — The decision becomes practice knowledge.
    3. The Project Pod — The next job can reach it in place.

Every capability, and what it connects to

The register lists all 17 capabilities with their availability, and what each one is verified to reach.

The capability registerStart free