Skip to content
VZU
VZU Industries · 13th vertical

Audit-trail-first. MNPI-aware. On-prem by default. MCP-native. The 13th VZU vertical — the same 12-agent runtime, configured for the work.

VZU Investor Relations — audit-trail-first IR on the VZU runtime

VZU Investor Relations — audit-trail-first IR on the VZU runtime

The wedge

Audit-trail-first IR. The four incumbents can't ship this.

Q4 Inc., Workiva, Diligent, AlphaSense — the four IR SaaS incumbents — own the workflow, the data, and the audit trail. The VZU wedge is the runtime posture: on-prem by default, MCP-native, MNPI-aware, audit-trail-by-default. The data is the operator's. The audit trail is the regulator's form.

  • IR workflows

    8

  • Agents on the hot-path

    6

  • Auditable on day one

    Yes

  • On-prem by default

    Yes

The eight anchor workflows

What the IR function does, mapped to the 12 agents.

The IR function is not a 13th agent. It is the composition of the existing 12. Eight workflows, three orchestration patterns, six agents on the hot-path, six on standby.

Agent

Atlas

Agent

Hunter

Agent

Quill

Agent

Oracle

Agent

Nova

Agent

Pixel

Agent

Kai

Agent

Sentinel

  • 01

    Earnings-call prep

    Supervisor

    AtlasHunterQuillOracle

    14 days → 24h

  • 02

    Live call note-taking + sentiment

    Relay

    HunterOracleAtlas

    4h → 30 min

  • 03

    Quarterly deck generation

    Sequential

    QuillAtlasNovaPixel

    5d → 1d draft

  • 04

    Investor email drafting + reply

    Supervisor

    HunterOracleAtlas

    4-8h SLA → <30 min

  • 05

    Cap-table + shareholder ID

    Sequential

    QuillHunterKai

    Weekly manual → daily auto

  • 06

    Consensus + estimate tracking

    Parallel

    HunterQuillOracle

    Reactive → proactive

  • 07

    ESG / sustainability disclosure

    Sequential

    AtlasKaiOracleSentinel

    CSRD · ESRS · ISSB

  • 08

    MNPI boundary enforcement

    Always-on

    SentinelKai

    Mechanical wall

Same 12-agent runtime · 3 orchestration patterns · 1 audit trail · 0 closed-source SaaS

The audit-trail advantage

The MNPI wall is mechanical, not procedural.

Q4, Workiva, Diligent, AlphaSense — none of them ship the MNPI boundary as a mechanical wall. They ship procedural controls, configured by humans, applied by humans, audit-logged by humans. The VZU runtime enforces the boundary at the agent level. An agent cannot cross a wall it does not have the role to cross, regardless of what prompt the operator types.

See the IR showcase

The four buyer personas

Who VZU IR is for.

  • Persona · 01

    Pre-IPO founder / CFO

    $50M-$500M ARR, 12-24 months from listing

    Their IR function does not exist yet. They need a runtime that takes them from S-1 drafting to first earnings call to a fully-fledged IR shop without re-platforming. The pre-IPO package is sized to the Series C and the Series D — not to the F500.

  • Persona · 02

    Mid-cap CFO / Head of IR

    TSX or US-listed. 1-3 person team.

    They want the workflow, don't want the SaaS. The mid-cap team gets the second-source, the GC gets the audit trail, the IR lead keeps the workflow. The 12-month contract includes the data export from Q4 or Workiva, the MCP-native integration, the policy migration, and the on-prem posture.

  • Persona · 03

    Family-office IR lead

    Single asset or 5-asset portfolio

    The same compliance obligations as a public company, none of the headcount. VZU IR runs on the family office's hardware, with the family office's audit trail, with the family office's policy. The MNPI boundary is the same wall the F500 gets.

  • Persona · 04

    PE-backed first IR hire

    Pre-exit. Building the data room.

    Prepping the exit narrative. Prepping the eventual public-company IR function. VZU's automation primitives (document automation, data room, audit trail) are already in this market.

The compliance posture

The audit trail is the regulator's form.

The runtime is built to handle Reg FD (SEC), MAR (ESMA), DTR 2 (FCA), 51-352 (CSA). Sentinel tags every artifact with the regulatory regime that applies. Oracle applies the safe-harbour and the materiality caveats. Atlas enforces the disclosure discipline.

  • SOC 2 Type II

    In pursuit

  • ISO 27001

    Aligned

  • PIPEDA

    Aware

  • HIPAA

    Aligned

FAQ

Operator questions, answered.

What is the IR function, on the VZU runtime? +

It is the composition of the existing 12 VZU agents, configured for the IR function. 8 anchor workflows. Audit-trail-first. MNPI-aware. On-prem by default. The runtime is the same runtime that powers every other VZU capability.

How is this different from Q4 Inc.? +

Q4 is SaaS. VZU is a runtime. Q4 owns the workflow, the data, and the audit trail. VZU runs on the operator's hardware, the operator's audit trail, the operator's policy. The MNPI boundary is mechanical, not procedural.

What about a small-cap with no existing IR function? +

That's the IR Pod. Three agents, monthly retainer, two anchor workflows. You get the audit trail, the MNPI boundary (read-only), and the Hunter/Oracle/Atlas spine. The team builds the rest. The pre-IPO package is sized to the Series C and the Series D — not to the F500.

What about an F500 with an existing Q4 or Workiva contract? +

That's the IR Runtime, and the migration path is real. The 12-month contract includes the data export from Q4 or Workiva, the MCP-native integration, the policy migration, and the on-prem posture. The mid-cap team gets the second-source, the GC gets the audit trail, the IR lead keeps the workflow.

Is the runtime SOC 2 / ISO 27001 / PIPEDA aligned? +

SOC 2 Type II in active pursuit. ISO 27001-aligned. PIPEDA-aware. The audit trail is the regulator's form. The MNPI boundary is enforced by the runtime, not by a procedure. The data is on-prem by default. The posture is regulator-grade on day one.

A case study · Mid-cap CFO / Head of IR

Case study

14 days. → 24 hours.

01

The brief

A mid-cap CFO's IR function was running 8 distinct workflows — earnings prep, live call note-taking, quarterly deck generation, investor email triage, cap-table reconciliation, consensus tracking, ESG disclosure, and MNPI boundary enforcement. Every workflow was in a different system. The four incumbents (Q4, Workiva, Diligent, AlphaSense) owned the workflow, the data, and the audit trail. The auditors had no single source of truth.

02

The analysis

The 8 workflows shared one constraint: MNPI. The audit trail needed to be on from the first character. Sentinel needed to audit every record. Oracle needed to write the disclosure prompts. Quill needed to produce the brief. Kai needed to orchestrate the 8 workflows on one runtime. The data needed to stay on-prem.

03

The build

8 workflows on the VZU runtime. Atlas built the apps. Hunter pulled the data. Quill produced the briefs. Oracle wrote the prompts. Kai orchestrated the 8 workflows. Sentinel audited every record and enforced the MNPI boundary. The audit trail is per-record, per-workflow, per-decision. The MNPI boundary is mechanical, not procedural.

04

The result

Earnings-call prep: 14 days → 24 hours. Live call note-taking: 4 hours → 30 minutes. Quarterly deck: 5 days → 1-day draft. Investor email SLA: 4-8 hours with 30% miss → <30 minutes with 0% miss. The data stays on-prem. The audit posture is the runtime. The disclosure controls run on the same model as the earnings prep.

Brief VZU on your IR

The runtime is on the operator's hardware. The audit trail is the regulator's form.

Reply within 1 business day. No credit card. No demo gate. The brief is the contract. The work is the work.

Brief VZU on your IR See the IR showcase

✓ Reply within 1 business day · No credit card · No demo gate

See also

VZU Industries →