Built against the mission. Governed by the people who use it.
Generic copilots don't know your delivery cadence, your risk language, or what "done" means in your portfolio. They produce generic outputs — and the PMO ends up curating the output instead of running the work.
The PM Agent is built for one PMO function, against that function's mission, by a firm whose primary practice is diagnosing why AI fails. It synthesises status across projects, surfaces risk before it reaches the steering committee, drafts board-grade reporting, and hands every decision back to the humans who own it — with reasoning attached.
"Status compilation, board-pack drafting, and steering-committee prep are absorbing 30–40% of senior PM time. The PM Agent moves that work to a governed system, freeing senior PMs for delivery." The pattern across PMOs at scale
Senior PMs spend Monday morning collating updates from 8–15 project leads, normalising the data, and producing a portfolio status that the PMO Director can present at the 10am leadership stand-up.
The PM Agent ingests project data overnight, drafts the portfolio status, flags the three things the PMO Director needs to know first, and lands the draft in the PMO Director's inbox by 7am — with sources cited and confidence levels named.
Outcome: Senior PMs get Monday morning back. The Director walks into the stand-up with sharper context, not just a summary.
Quarterly steering committee prep absorbs 40–60 hours of senior PMO time per cycle — pulling together project narratives, risk registers, financial summaries, and decision-required items into a coherent pack.
The PM Agent drafts the entire pack against the steering committee's standing agenda, with each section pre-populated from the underlying delivery data. The senior PMO team reviews, edits, and adds judgement — without writing the first draft.
Outcome: Steering committee prep moves from 40–60 hours to 8–12 hours. Time recovered goes back to delivery.
The most expensive PMO failure mode is risks that reach the steering committee already in red — when the time to act on them was three weeks earlier, when they were still amber.
The PM Agent monitors leading indicators across the portfolio — slipping commitments, resource gaps, dependency breaks, narrative drift in status updates — and surfaces the amber-to-red transition trajectory to the PMO Director the moment it begins, with the underlying signal visible.
Outcome: The PMO Director gets warning weeks earlier. Steering committee escalations become rare, not recurring.
Most agent builds skip phase one (no mission alignment), compress phase two (assumed workflows, not observed ones), and have no equivalent of phases four and five (built and released without the people who will use it ever signing off).
The Mycelium build loop is slower than the market default. The slowness is the point.
Fixed fee, ex GST. Optional Sustained Alignment Retainer ($3,500–$8,500/month) available post-release for quarterly mission re-alignment, drift monitoring, and governance review.
Every PM Agent is released to broader use only after three sign-offs.
This is what separates a managed build from a deployed tool. The agent is not finished when the code is written. It is finished when the people who will use it have signed off on what it does, what it doesn't do, and how its performance will be reviewed.
The PMs and analysts who will use the agent daily sign off that it works as expected, handles edge cases responsibly, and aligns with the mission as scoped.
The function owner signs off on scope, governance cadence, performance measures, and the explicit list of what the agent will and will not do.
The budget holder receives the executive briefing, confirms the scope and risk envelope, and authorises broader release.
60 minutes with you and your executive sponsor. We assess whether a PM Agent build is the right move for your situation — and tell you if it is not.