Live demos

One worked example per module

Seven modules on one shared substrate, each returning real-shape outputs. The cards below show what a module's agentic specialists return for one representative query. Procure was first to GA and ships with a deeper three-scenario worked example below its card; equivalent deep-dives for the other modules publish as each module's dashboard goes live.

WYRM MEP

Agentic M&E design + coordination, checked by deterministic engines

Scenario

An MFSD is relocated on level 3 — WYRM reconciles the auto-spec against the auto-schedule and cascades the consequences across disciplines.

Sample output
Change detected: MFSD-L3-07 relocated 2.4 m east (model delta vs locked spec)
Consequence: 3 power supplies realigned · DB-L3-B breaker 20 A → 25 A
↳ BS 7671 cable check re-run on the affected circuit — PASS (volt-drop 1.9%)
Spec ⟷ schedule: 2 untracked deltas reconciled · 1 flagged for the engineer
Tasks raised: 4 (2 complete · 1 in progress · 1 outstanding) — tracked to RIBA Stage 4
Calc pack attached · advisory only — awaiting named-engineer sign-off

WYRM Procure

Supply chain + procurement intelligence

Scenario

1,200 kg primary aluminium ingots, destination GB-LON, balanced cost / carbon sort.

Sample output
Best origin: Norway (Nordhordland Aluminium) — total landed £3,840
CBAM liability: £88.20 — embedded carbon 4.0 t CO₂e (renewable smelting)
Sanctions: 0 advisory findings across UK OFSI / US OFAC / EU / UN
Lead time: 14 days sea via Rotterdam — chokepoint risk: low
Confidence: 0.87 (STABLE regime)

WYRM Ledger

Coming soon

Tender opportunities + bid writing + agentic accounting

Scenario

Match Contracts Finder + Find a Tender against your capability profile, then draft a structured response.

Sample output
Tender match: Birmingham CC — supported-housing software framework (£600k–£1.2M, lot 2)
Deadline: 18 working days · ITT response window: 21 days · pre-market engagement closed
Capability fit: 0.81 (strong on case-management, mid on housing-association integrations)
Bid drafter — Section 3.1 first pass: "Our agentic case-management surface ingests Universal Housing exports nightly…"
CBAM-irrelevant · MTD VAT exposure: nil for software supply

WYRM Cyber

16-tool OSINT + threat intelligence with agentic monitoring

Scenario

Onboarding a tier-2 vendor — domain footprint, exposed services, CVE risk on their public stack.

Sample output
Subdomain footprint: 47 hosts · 12 with live HTTPS · 3 on legacy TLS 1.0
CVE-2024-3094 (XZ backdoor) — detected on 1 host, EPSS 0.78, KEV listed
CVE-2025-1974 (Ingress-NGINX) — 2 hosts, EPSS 0.43, no KEV — patch within sprint
Sanctions screen on owning entity: 0 findings · OpenCorporates parent chain clean
Dark-web mention: 1 leaked credential pair (2023, since rotated per HaveIBeenPwned)

WYRM Legal

Clause-by-clause contract review + weekly legal monitoring

Scenario

Vendor MSA against your commercial playbook — flag what to redline.

Sample output
Clause 4.2 (Indemnity cap) — 🔴 RED · cap at 12 mo fees vs your playbook minimum of 24 mo
Clause 7.1 (Data processing) — 🟡 AMBER · DPA Schedule missing UK sub-processor table
Clause 9.3 (Termination for convenience) — 🟢 GREEN · 90 days matches playbook
Clause 11 (Governing law) — 🔴 RED · Delaware vs your standard England & Wales
Suggested redline: "…not to exceed two (2) times the Fees paid in the twelve (12) months…"

WYRM Data

Coming soon

Cross-domain intelligence API — one schema across all seven modules

Scenario

POST /v1/entities/screen — one call returns sanctions, CVE exposure, and tender history for a counterparty.

Sample response
{
"entity": "Acme Engineering Ltd",
"company_number": "04527812",
"sanctions": { "findings": 0 },
"cyber": { "open_cves": 2, "epss": 0.43 },
"contracts_5y": { "count": 7, "value_gbp": 2140000 },
"risk_score": 0.18,
"confidence": 0.91
}

WYRM Healthcare

Coming soon

Clinical-safety-cased go-live RAG for UK NHS providers (WYRM Compass)

Scenario

Ward staff asks Compass: "What's the downtime procedure if Aurora EPR goes offline mid-shift?" Compass retrieves from the trust's own SOP corpus.

Sample output
Answer: From SOP-DT-04 §3.2 (v2.1, valid from 2026-03-14) — switch to paper
observations on form OBS-103, escalate to bleep 4421 (site coordinator),
and capture restored data within 4 hours of system recovery per §4.1.
Citation: SOP-DT-04 §3.2 · supersedes v1.8 (retired 2026-03-14)
Confidence: 0.94 · 1 supporting citation · scope: in-policy
Audit: msg_01HPQ7… · model claude-haiku-4-5 · 218 tokens · £0.0011

Want more depth?

The full Procure worked example

Three procurement decisions, computed end-to-end — aluminium ingots for a UK manufacturer, a used reefer container, and rare-earth magnets for offshore wind nacelles. Equivalent deep-dives for MEP, Data, Ledger, Cyber, Legal, and Healthcare publish as those modules go GA.

About these numbers. Outputs shown above are illustrative — calibrated to plausible 2026 shapes but not live quotes. Real WYRM decisions run against live OpenSanctions, EPSS, KEV, HMRC tariff, Contracts Finder, EPC, and embodied-carbon feeds at the point of query. Coming-soon modules show the output shape they will return on launch.