Mycelium AI Agents — Agent 04 of 05

The Supplier Assurance & Onboarding Agent.

Built against your vendor risk obligations. Governed by the people who own them.

Status
Available now
Now accepting commissions
Investment
$35K–$120K
Fixed fee, tiered by integration scope, ex GST
Timeline
8–14 weeks
Five-phase managed build
The Proposition

Off-the-shelf AI doesn't know your procurement controls or your risk thresholds.

Generic AI tools don't understand your vendor risk taxonomy, your data classification thresholds, or how a regulated onboarding process actually moves across Procurement, Legal, Risk, AP, and Cyber. They produce outputs that need to be corrected before anyone can act on them — and the team ends up curating instead of approving.

The Supplier Assurance & Onboarding Agent is built for one procurement function, against that function's risk thresholds, by a firm whose primary practice is diagnosing why AI fails. It classifies every new vendor by risk tier, orchestrates due-diligence across the right reviewers, surfaces regulatory flags (Privacy Act, Modern Slavery, sanctions, AUSTRAC), and routes every approval decision back to the humans who own it — with evidence attached.

Phase 1 demo available: a working prototype on synthetic vendor data, no production system access required, in 4 weeks.

"Vendor onboarding is the choke point. Cross-functional coordination, due diligence orchestration, and regulatory flagging are absorbing weeks that should take days. The Supplier Assurance & Onboarding Agent absorbs the coordination layer — freeing your team to decide, not chase." The pattern across Australian regulated procurement

What it does

Three categories of work. One agent, governed.

— It Classifies

Every new vendor against your risk thresholds.

  • Risk-tier classification (Low / Standard / Enhanced) at intake
  • Data-sensitivity assessment based on access requested
  • Regulatory flag detection (Privacy Act, Modern Slavery, sanctions, AUSTRAC)
  • AI-vendor flag triggering CISO and DPO review
  • Geographic and supply-chain risk surfacing
— It Coordinates

The cross-functional due diligence your team chases manually.

  • Parallel routing to Legal, Risk, AP, and (where required) Cyber
  • Vendor questionnaire orchestration with structured response capture
  • Contract clause analysis against your standard terms
  • Financial-stability and reputational signal aggregation
  • Single consolidated Vendor Risk Profile per request
— It Routes

Approval decisions to the right humans.

  • APPROVE / CONDITIONAL / REJECT recommendation with rationale
  • Named human approver determined by tier and findings
  • Conditions list when CONDITIONAL — specific, actionable, owner-named
  • Audit-trail with full data lineage for every decision
  • Never makes the final call — always presents to a human
When it earns its keep

Three scenarios where the Supplier Assurance & Onboarding Agent changes the calculus.

01
New AI vendor request, Friday afternoon
The vendor request that always sits in someone's inbox over the weekend

A new AI-vendor onboarding request arrives via the procurement portal at 3:47pm Friday. Manually, it sits over the weekend waiting for someone to start chasing Legal, Risk, Privacy, CISO, and AP next week. Onboarding stretches across 4–10 weeks of email coordination.

The Supplier Assurance & Onboarding Agent classifies the request as Enhanced tier within minutes (AI vendor + customer data access + overseas hosting). It triggers parallel DD across Legal, Risk, Cyber, and DPO in the same hour. By Monday 9am the Procurement Director sees a consolidated Vendor Risk Profile with a CONDITIONAL recommendation and three named conditions — ready to action.

Outcome: The onboarding clock starts Friday afternoon, not Monday morning. Cross-functional inputs arrive in parallel, not in sequence. The Procurement Director makes the call with full context, not partial.

02
Annual vendor re-certification cycle
The obligation that becomes a backlog

Every regulated function has annual vendor re-certification obligations — APRA-supervised entities under CPS 230, financial advisers under AFSL conditions, healthcare providers under privacy obligations. Re-cert cycles routinely fall behind because manual coordination across hundreds of vendors is unsustainable.

The agent runs the re-certification cycle as a scheduled job. For each vendor: pulls the current certification status, identifies what's expiring, drafts the re-cert questionnaire, routes to the vendor and to the relevant internal reviewer, and compiles status reports for the Procurement Director and the Risk function. Vendors that fail to respond by deadline are flagged for escalation.

Outcome: Re-certification becomes a managed process with named owners and named deadlines, not a quarterly fire-fight. The audit trail for the regulator is generated as a byproduct.

03
Sanctions match — overnight
The exposure that materialises before anyone looks

A sanctions list update overnight surfaces a match against one of your active vendors. Manually, the discovery often comes weeks later via a periodic re-screen — by which time the exposure has compounded.

The agent continuously monitors AUSTRAC, OFAC, UN, and DFAT sanctions lists against your active vendor register. A match triggers immediate notification to General Counsel and the Procurement Director with the vendor record, the matching list entry, the active contracts impacted, and a recommended response (suspension, investigation, or false-positive triage). The audit trail is generated automatically.

Outcome: Sanctions exposure is detected within hours, not weeks. General Counsel makes the call with the full evidence pack already assembled — and the timeline is defensible to APRA or AUSTRAC if asked.

How we build it

Every Supplier Assurance & Onboarding Agent build follows the same five-phase loop.

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.

01
2 weeks
Mission Alignment
Workshop with the Program Director and 3–5 of the team. Output: Mission Alignment Document — what the function exists to do, what success looks like, what the agent must never do.
02
2 weeks
Workflow Mapping
Observation and process tracing of how the reporting and compliance work actually happens — not how it is documented. Output: workflow map with tasks, data sources, and human handoff points.
03
3–6 weeks
Build
Agent built against the workflow map and the Mission Alignment Document. Iterative, with the working group reviewing each iteration. No dark builds. Phase 1 demo available on synthetic data from week 4.
04
2 weeks
Departmental Review
Parallel run alongside existing processes. The team uses the agent in production conditions, reviews accuracy, edge cases, and CPS 230 flag logic — and signs off before release.
05
1 week
Executive Release
Executive briefing covering scope, governance, review cadence, compliance boundaries, and performance measures. Released to broader use only after executive sign-off.
Investment

Three tiers, scoped to complexity.

Standard
$35K–$55K
8–10 weeks
Single program, weekly health monitoring, standard integrations.
  • Program health monitoring — one program
  • Standard integrations (Jira, Confluence, ServiceNow)
  • CPS 230 compliance flags — core obligation categories
  • APPROVE / ESCALATE gate in Teams
  • Five-phase build with executive sign-off
  • Handover documentation
Enterprise
$100K–$160K
14–18 weeks
Multi-program portfolio, full CPS 230 coverage, regulated audit trail.
  • Full portfolio health monitoring across multiple programs
  • Comprehensive CPS 230 obligation mapping
  • Regulator-ready audit trail requirements
  • Extended departmental review (4 weeks)
  • Handover plus 90-day stabilisation

Fixed fee, ex GST. Optional Sustained Alignment Retainer ($3,500–$8,500/month) available post-release for quarterly mission re-alignment, CPS 230 obligation updates, drift monitoring, and governance review.

The governance promise

Three sign-offs. No exceptions.

Every Supplier Assurance & Onboarding 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.

01

The working group

The Program Managers and analysts who will use the agent daily sign off that it works as expected, handles edge cases responsibly, and the CPS 230 flag logic aligns with your compliance obligations.

02

The Program Director

The function owner signs off on scope, governance cadence, performance measures, compliance boundaries, and the explicit list of what the agent will and will not do.

03

The executive sponsor

The budget holder receives the executive briefing, confirms the scope and risk envelope, reviews the CPS 230 compliance approach, and authorises broader release.

The first conversation is diagnostic

No pitch. No proposal until it makes sense.

60 minutes with you and your executive sponsor. We assess whether a Supplier Assurance & Onboarding Agent build — or a Phase 1 demo — is the right move for your situation. And we tell you if it is not.

Request a Diagnostic Conversation See all agents →
admin@themyceliumgroup.com.au   ·   +61 401 844 836