- 2026‑014Enquiry
- 2026‑014Fee proposal
- 2026‑014Project
One record. Not three, and never retyped between them.
The enquiry is the project, earlier
It changes what it is. It does not change hands.
Enquiry
Somebody asks whether you can do the work. What they said, who they are, and where they came from.
Fee proposal
The same record proposes stages and amounts. Nothing about the enquiry is re-entered to do it.
Project
Accepted, it starts with those stages and that fee already in place, and the conversation that won it still attached.
This is not a sales pipeline with architectural labels. Nothing moves between columns, because there are no columns — the record becomes the next thing where it already is.
Count what was carried. Count what was retyped.
CRM
It does not move to the project. It becomes the project
- Lead
- Fee proposal
- Project
- Who it is for
- What they are asking for
What was agreed while winning the job is what the job starts with. No client, contact, value or date is real — these are the kinds of thing a proposal settles.
In short
AvailableAvailable now to practices on a qualifying plan.- What it is
- Lead and enquiry tracking for architecture practices, who got in touch, what they want built, where the conversation has reached, and what happens next.
- Who it is for
- Practices where new work arrives through relationships and referrals rather than through a sales team, and currently lives in an inbox.
- What is different
- It is not a generic sales pipeline relabelled. A lead in Mudo becomes a fee proposal and then a project without leaving the system, so what was agreed while winning the job is what the job starts with.
- Availability
- Available on every plan, including the free Starter tier.
- How it connects
- Leads become fee proposals, and accepted proposals become projects with their stages and fee structure already in place.
Part of Win.
Verified against the Mudo application on .
Won work is not a stage, it is a handover
The most expensive moment in a small practice's commercial life is the week a job starts. The fee was discussed over three conversations and one revised proposal. The scope shifted twice. Somebody agreed to include something.
Then a project gets created, and roughly none of that comes with it.
Mudo keeps the lead, the proposal and the project as one continuous record, which means the project begins knowing what was agreed rather than what somebody remembered to type.
Built for how architectural work actually arrives
Architectural work does not arrive through a funnel. It arrives through a builder you worked with, a client's sister, a planning consultant, a house someone walked past.
What a practice needs is not lead scoring. It is a reliable memory of every conversation and what it turned into.
Common questions
Do architects need a CRM?
Most small practices do not need a sales CRM, because they do not run a sales process. What they need is a record of who enquired, what it was about, and what was promised, so that a conversation from four months ago is findable when the client calls back. That is what this is.
How is this different from a general CRM?
A general CRM ends at "won". In Mudo the same record continues into a fee proposal and then into the project, carrying the scope and the fee structure with it. The handover between winning work and doing work is where most detail is lost, and removing it is the point.
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.
- /growth/lead-trackerThe lead tracker screen in the application.
- /pipelineThe pipeline view where leads progress toward proposals.
Stop rebuilding the job you already won.
Free for solo practices: one user, two projects, no card.