Agreed
Recorded
Baseline without acceptance — an integrity anomaly, not a status
The commercial position of the practice
Four commercial facts. One defensible answer.
Fees
Two records, one position — they agree or they do not
Both records agree. The fee the client accepted is the fee the project runs on.
Mudo’s own acceptance state machine. Acceptance is a state and a fee amount is a value; neither is ever inferred from the other, which is why this instrument reconciles without naming a figure. No amount, percentage or invoice appears here.
In short
AvailableAvailable now to practices on a qualifying plan.- What it is
- The fee structure of every project: staged amounts, agreed variations, what has been claimed and what has not, and the practice-wide financial position that follows from it.
- Who it is for
- Directors who currently learn the practice's commercial position from the bookkeeper, in arrears.
- What is different
- The fee is connected to the programme that triggers it and the time being spent against it, so the position is current rather than assembled quarterly from three systems.
- Availability
- Available on every plan, including the free Starter tier.
- How it connects
- Fees originate in the accepted fee proposal, move with the programme, are consumed by invoicing, and are compared against recorded time.
Part of Money.
Verified against the Mudo application on .
Where the money actually goes wrong
Very few practices lose money because they priced the job badly. They lose it in three quieter ways: a stage slips and the claim slips with it; a variation is agreed verbally and never invoiced; the job absorbs three weeks of somebody's time that nobody costed.
All three are visibility problems, not pricing problems.
Fees that know about the programme
A fee stage is claimable when something happens: concept complete, DA lodged, set issued. Holding the fee and the programme in one model means the practice can see the cash effect of a programme change when it happens.
Fees that know about the time
Recorded time against the same stages the fee is structured around gives the comparison that matters: what a stage was worth, and what it cost.
That comparison is the only reliable input to the next fee proposal.
What this is not
It is not accounting software, and Mudo does not claim to replace it.
Common questions
How does Mudo connect fees and programme?
Architectural fees are claimed against stages, and stages live in the programme. Because both are held in the same project model, a stage that moves changes when the fee becomes claimable, so the cash consequence of a programme decision is visible at the time the decision is made.
Does Mudo replace accounting software?
No, and it should not be presented as doing so. Mudo holds the practice's commercial position: what has been agreed, what is claimable, and what has been invoiced. Your accountant's system remains the accounting record.
How are variations handled commercially?
A variation is a record with a value that changes what the practice is owed. Because it is attached to the fee structure rather than kept as a note, the position reflects it when it is agreed rather than at the end of the job.
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.
- /practice/financeThe practice finance screen in the application.
- /projects/:projectId/variationsVariations are a first-class per-project register, not free text.
Know where the practice stands without asking the bookkeeper.
Free for solo practices: one user, two projects, no card.