Is our data ever used to train external models?

No. The runtime is on-prem by default. When the runtime is cloud-deployed, your data is segregated and never used to train any external model — ours or a third party's. The data residency is the operator's choice. The training is none.

How is VZU Investor Relations different from Q4 Inc.?

Q4 is a SaaS IR platform. 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. The data is on-prem by default. The audit trail is signed and replicated.

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.

How does the runtime handle MNPI?

Sentinel classifies every artifact by MNPI risk. Kai enforces the access policy. Every access lands in the audit trail. The wall is no longer procedural — it is mechanical, and it is the same wall that runs on the engineering side, the IR side, and the compliance side.

What about Reg FD, MAR, and the Canadian equivalent (CSA 51-352)?

The runtime is built to handle all three. Sentinel tags every artifact with the regulatory regime that applies. Oracle applies the safe-harbour and the materiality caveats. Atlas enforces the disclosure discipline. The audit trail is the regulator's form — for the SEC, the ESMA, and the CSA.

Can the runtime run air-gapped?

Yes. The IR On-Prem tier runs on the operator's hardware. Air-gapped option available. The audit trail is signed, replicated, and regulator-grade without any cloud dependency. The brief is the contract. The work is the work.

How long does it take to deploy?

IR Pod ships in 5 business days. IR Runtime ships in 6-8 weeks. IR On-Prem ships in 12-16 weeks, on the operator's hardware, with the operator's security review. The brief sets the boundary. The work is the work.

Who is this for, and who is it not for?

It is for the pre-IPO founder, the mid-cap CFO, the family-office IR lead, and the PE-backed company's first IR hire. It is not for the F500 with a 50-person IR team and a 10-year Q4 contract. For the F500, the migration path is real — but the wedge is the second-source, not the replacement.

VZU Investor Relations · 13th vertical

Your IR function, on the VZU runtime .

Audit-trail-first. MNPI-aware. On-prem by default. MCP-native. The brief is the contract. The work is the work. The audit trail is the regulator's form. Earnings-call prep in 24 hours, not 14 days.

Brief VZU on IR See the 8 workflows

Vertical

13th · Investor Relations

VZU Investor Relations is the 13th vertical showcase for the VZU family. It is not a 13th agent. The IR function is composed on the existing 12-agent VZU OS runtime — Atlas, Hunter, Quill, Oracle, Sentinel, Kai, Nova, Pixel, Vega, Echo, Sketch, Launch — with eight anchor workflows, audit-trail-first by default, MNPI-aware by design, on-prem by default, MCP-native throughout. The wedge is the audit trail, the on-prem posture, and the mechanical MNPI boundary. The Q4, Workiva, Diligent, and AlphaSense operators can keep their workflow. They get the second-source.

The wedge

Audit-trail-first IR.
MNPI-aware.
On-prem by default.

Line 01

Audit-trail-first IR.

Every artifact, every reply, every revision is in the audit trail from the first character. The trail is signed, replicated, and regulator-grade. The audit trail is the SEC\'s form. The audit trail is the ESMA\'s form. The audit trail is the CSA\'s form.

Line 02

MNPI-aware.

Sentinel classifies every artifact by MNPI risk. Kai enforces the policy. The wall is no longer procedural — it is mechanical, and it is the same wall that runs on the engineering side, the IR side, and the compliance side. Reg FD, MAR, CSA 51-352.

Line 03

On-prem by default.

The runtime ships on the operator\'s hardware. Air-gapped option. The data never leaves the perimeter. The model is the operator\'s choice. The audit trail is anchored on the operator\'s side. Cloud is a deployment option, not a default.

The 8 anchor workflows

Eight workflows. One runtime. One audit trail.

Each workflow composes the existing 12 VZU agents into an IR surface. The audit trail is mechanical. The MNPI boundary is mechanical. The runtime is on-prem by default. The pattern is named per workflow (Relay, Parallel, Supervisor) — the brief is the contract.

Workflow 01 Pattern · Supervisor

Earnings-call prep in 24 hours.
Not 14 days.

Atlas ingests the prior transcript, the guidance delta, and the sell-side notes. Hunter pulls the latest Street estimates and the consensus drift. Quill reconciles the IR working file. Oracle writes the prepared-remarks draft and the Q&A bank.

Atlas Hunter Quill Oracle
3-step workflow
1. 01
  
  Atlas
  
  Read prior call, S-1, 10-Q. Extract KPIs, language drift, beat/miss deltas.
2. 02
  
  Hunter
  
  Scrape 17 sell-side notes + FactSet/Refinitiv consensus. Surface the delta vs. your guide.
3. 03
  
  Quill
  
  Reconcile the IR working file (cap table, opex, segment KPIs) against the GL close.
Prep cycle

Before

14 days

After

24 hours
Workflow 02 Pattern · Parallel

Live call note-taking + sentiment.
On the call, in the call.

Hunter joins the call bridge as a silent listener (with consent and disclosure). Oracle produces real-time per-question sentiment, named-entity tracking, and a transcript indexed by speaker, ticker, and topic. Atlas flags material discrepancies against prepared remarks.

Hunter Oracle Atlas
3-step workflow
1. 01
  
  Hunter
  
  Join bridge. Capture dual-channel audio. Transcribe with speaker diarisation + timestamp.
2. 02
  
  Oracle
  
  Stream sentiment + named-entity tags. Index every question by topic, ticker, and analyst.
3. 03
  
  Atlas
  
  Cross-check analyst questions vs. the prepared-remarks bank. Flag material deviations.
Call note cycle

Before

Manual notes, 4-6 hour lag

After

Real-time, MNPI-segregated
Workflow 03 Pattern · Relay

Quarterly deck generation.
The deck is the contract.

Quill produces the deck structure from the working file. Atlas lays out the editorial-grade slide master. Nova applies the locked VZU IR palette and typography. Pixel renders the chart style and the cover. The deck inherits the audit trail from the working file.

Quill Atlas Nova Pixel
3-step workflow
1. 01
  
  Quill
  
  Reconcile the IR working file into the deck structure: 24-32 slides, chart-first, comment-light.
2. 02
  
  Atlas
  
  Apply the deck master. Lock fonts, footer disclosures, safe-harbour language, exhibit numbering.
3. 03
  
  Nova
  
  Apply the VZU IR palette + typography. Editorial register, regulator-grade legibility.
Deck build cycle

Before

3-4 weeks, 4 reviewers

After

5 days, audit trail intact
Workflow 04 Pattern · Supervisor

Investor email drafting + reply triage.
Inbox zero, MNPI-clean.

Hunter classifies inbound investor email by topic, urgency, and MNPI risk. Oracle drafts the reply in the operator's voice. Atlas enforces the MNPI boundary — no reply is sent that crosses a wall without the compliance signoff. Every reply inherits the audit trail.

Hunter Oracle Atlas
3-step workflow
1. 01
  
  Hunter
  
  Classify inbound by topic, urgency, and MNPI risk. Route to a triage queue with severity tags.
2. 02
  
  Oracle
  
  Draft the reply in the operator's voice. Pull the working-file context. Apply the safe-harbour footer.
3. 03
  
  Atlas
  
  Enforce the MNPI boundary. Block, escalate, or send based on the operator's MNPI policy.
Investor reply cycle

Before

4-8 hour SLA, 30% miss rate

After

<30 min SLA, 0% miss rate
Workflow 05 Pattern · Relay

Cap-table + shareholder-ID.
The single source of truth.

Quill reconciles the cap table against the transfer agent, the option pool, the SAFE/convertible stack, and the 13D/13G filings. Hunter pulls the latest shareholder-ID feed. Kai enforces the data model and the API surface for downstream systems.

Quill Hunter Kai
3-step workflow
1. 01
  
  Quill
  
  Reconcile cap table vs. transfer agent, option pool, SAFE/convertibles. Produce a single working file.
2. 02
  
  Hunter
  
  Pull 13D/13G, Form 4, and shareholder-ID feeds. Surface material holders, drift, and concentration.
3. 03
  
  Kai
  
  Enforce the data model. Push to the API surface (HR, finance, board portal) with audit trail.
Cap-table reconcile

Before

Weekly, 3 FTE weeks per quarter

After

Daily, audit-trail complete
Workflow 06 Pattern · Parallel

Consensus management + estimate tracking.
Know the Street before it knows you.

Hunter watches the sell-side. Oracle tracks the estimate drift, the revision rate, and the dispersion. Quill builds the consensus model and the IR talking points. The team gets a daily delta — the Street's view, before the Street moves.

Hunter Quill Oracle
3-step workflow
1. 01
  
  Hunter
  
  Scrape sell-side notes, transcript libraries, consensus aggregators. Build a daily delta feed.
2. 02
  
  Quill
  
  Reconcile the consensus model. Surface estimate drift, revision rate, and dispersion by metric.
3. 03
  
  Oracle
  
  Generate IR talking points. Flag the questions the Street will ask on the next call.
Consensus coverage

Before

Quarterly review

After

Daily, sell-side-aware
Workflow 07 Pattern · Supervisor

ESG / sustainability disclosure drafting.
CSRD, ISSB, SASB, TCFD.

Atlas drafts the disclosure against the framework the operator reports under. Kai enforces the data lineage — every metric ties back to a source. Oracle reviews the language for forward-looking safety. Sentinel scans for the standard non-GAAP inconsistencies.

Atlas Kai Oracle Sentinel
3-step workflow
1. 01
  
  Atlas
  
  Draft the disclosure (CSRD/ISSB/SASB/TCFD). Map every metric to a framework tag and a source-of-truth.
2. 02
  
  Kai
  
  Enforce data lineage. Tie every ESG metric back to the operator's source systems with an audit row.
3. 03
  
  Oracle
  
  Review the language for forward-looking safety. Apply the safe-harbour and the materiality caveats.
Disclosure build

Before

6-9 months, framework drift

After

6-8 weeks, framework-locked
Workflow 08 Pattern · Supervisor

MNPI boundary enforcement.
The wall, enforced.

Sentinel classifies every artifact by MNPI risk — earnings drafts, deal memos, customer pipelines, M&A models. Kai enforces the policy: who can see what, when, and under which approval. Every access is in the audit trail. The wall is no longer procedural — it's mechanical.

Sentinel Kai
3-step workflow
1. 01
  
  Sentinel
  
  Classify every artifact by MNPI risk. Tag with the regulatory regime (Reg FD, MAR, CSA 51-352).
2. 02
  
  Kai
  
  Enforce the access policy. Block, log, or escalate. Every access lands in the audit trail.
MNPI controls

Before

Procedural, post-hoc audit

After

Mechanical, pre-trade gate

The architecture

Which 12 agents do the IR work.

The IR function is not a 13th agent. It is the composition of the existing 12. The 12-agent framing is load-bearing in VZU\'s pitch — IR does not break it. Eight agents are on the IR hot-path today. Four are on standby, available on request.

Diagram · The 12-agent IR runtime

  ┌──────────────────────────────────────────────────────────────┐
  │                  VZU INVESTOR RELATIONS                       │
  │         audit-trail-first · MNPI-aware · on-prem              │
  ├──────────────┬───────────────┬───────────────┬───────────────┤
  │  ENGINEERING │    DESIGN     │    REVIEW     │ DATA / AUTOM  │
  │              │               │               │               │
  │  Atlas · IR  │  Nova · deck  │  Sentinel ·   │  Quill · cap  │
  │  app builder │  master, type │  MNPI wall    │  table, deck  │
  │              │               │               │               │
  │  Kai · data  │  Pixel ·      │  Oracle ·     │  Hunter ·     │
  │  model, API  │  chart style  │  prompts,     │  sell-side,   │
  │  surface     │               │  safe-harbour │  consensus    │
  ├──────────────┴───────────────┴───────────────┴───────────────┤
  │  ON STANDBY:  Vega · Echo · Sketch · Launch                   │
  │              (IR web properties, IR portals, on request)      │
  └──────────────────────────────────────────────────────────────┘

Engineering

The runtime, the data model, the API surface.

Atlas VZU Build — full-stack IR app builder. The audit-trail spine.
Kai VZU Stack — backend + infra. The data model, the API surface, the lineage.

Design

The deck master, the chart style, the cover.

Nova VZU Surface — editorial UI. The deck master, the typography, the palette.
Pixel VZU Canvas — motion + WebGL. The chart style, the cover render, the motion.

Review

The MNPI wall, the prompt discipline, the safe-harbour.

Sentinel VZU Audit — code reviewer + security auditor. The MNPI classifier, the wall.
Oracle VZU Prompts — production prompt engineer. The safe-harbour, the language drift, the eval suite.

Data

The working file, the cap table, the consensus model.

Quill VZU Sheets — spreadsheet engineer. The cap table, the deck structure, the consensus model.

Automation

The Street feed, the call bridge, the inbox.

Hunter VZU Scrape — resilient scraper. The sell-side notes, the consensus, the shareholder-ID feed.

On standby

Available. Not on the IR hot-path today.

Vega VZU Web — React/Next.js engineer. IR web properties on request.
Echo VZU Design — WCAG auditor. IR web properties, IR portals, on request.
Sketch VZU Sketch — wireframer. IR portal UX on request.
Launch VZU Launch — landing page composer. IR campaign pages on request.

The workflow map

Eight workflows. Three patterns. The same 12 agents.

Each IR workflow maps to a specific combination of the 12 VZU agents. The composition is the configuration. The runtime stays the same.

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 4 buyer personas

Four buyers. One runtime.

The IR function is not a single buyer. It is four distinct briefs, four distinct budgets, four distinct decision-makers. The runtime ships to all four.

Persona 01

Pre-IPO founder / CFO

$50M-$500M ARR. Series C through pre-IPO. The founder is still the IR voice. The CFO is doing IR at night. The board wants a public-market posture. The team is 4-8 finance people and 1 IR-adjacent hire.

Right tier

IR Pod · monthly retainer · 3 agents · Hunter + Oracle + Atlas

Wedge

You don't need a Q4 contract. You need an audit-trail-first, on-prem IR runtime that ships inside the next funding round.
Persona 02

Mid-cap CFO / Head of IR

TSX- or US-listed. $500M-$5B market cap. A real IR team. A real transfer agent. A real IRO. A real Q4 or Workiva contract — and a real reason to look at the second-source. The board has asked the GC to re-bid the IR stack.

Right tier

IR Runtime · 12-month · 6 agents

Wedge

Migration path. The audit trail is mechanical. The on-prem posture is the wedge. The runtime replaces the bolt-on.
Persona 03

Family-office IR lead

Single-family office or multi-family office. $500M-$5B AUM. Concentrated public-equity book. Direct private investments. Quarterly LP letters. The IR lead reports to the CIO and the family principal. The mandate is alignment, not asset-gathering.

Right tier

IR Pod · monthly retainer · 3 agents

Wedge

You're not selling securities. You're reporting to LPs. The audit trail is the LP's form. The on-prem posture is the family's posture.
Persona 04

PE-backed company's first IR hire

First IR hire in the company's history. Sponsor is preparing the exit. The CFO has 12 months to build a public-market-grade IR function on a Series-D-sized budget. The brief is "make the company IR-ready, on-prem, and audit-grade."

Right tier

IR Runtime → IR On-Prem · 24-month · all 8 workflows

Wedge

You're the first IR hire. You need the runtime, the audit trail, and the on-prem posture — on day one. Not the consultancy.

The 3 pricing tiers

Three tiers. One runtime. One audit trail.

IR Pod, IR Runtime, and IR On-Prem. The pricing scales with the agents, the workflows, the contract length, and the deployment posture. The audit trail is on from the first character. The MNPI boundary is mechanical. The brief is the contract.

Tier 01

IR Pod

3 agents · monthly retainer

For the pre-IPO founder, the family-office IR lead, and the team that needs a wedge — not a contract.
- 3 agents: Hunter + Oracle + Atlas
- 2 of the 8 anchor workflows
- MNPI boundary enforcement (read-only)
- Audit trail on from the first character
- Email support, 1 business day
2 workflows · 3 agents

Monthly retainer. Cancel any time.
Tier 02 Most chosen

IR Runtime

6 agents · 12-month

For the mid-cap CFO, the head of IR, and the team that needs the second-source — not the second-best.
- 6 agents: Atlas + Hunter + Quill + Oracle + Sentinel + Kai
- 6 of the 8 anchor workflows
- MNPI boundary enforcement (write-side)
- Migration path from Q4 / Workiva / Diligent
- Audit trail, MCP-native, RBAC at the agent level
- Priority support, 1 business day
6 workflows · 6 agents

12-month. Migration path from Q4 or Workiva.
Tier 03

IR On-Prem

All 8 workflows · 24-month · on the operator's hardware

For the F500 with a real GC, the sovereign operator, and the team that does not negotiate on data residency.
- All 12 agents, all 8 anchor workflows
- Deployed on the operator's hardware. Air-gapped option.
- MNPI boundary enforcement, full read/write
- Audit trail, signed, replicated, regulator-grade
- Sentinel + Kai MNPI controls: mechanical, pre-trade gate
- 24/7 follow-the-sun support
8 workflows · 8 agents

24-month. Air-gapped option. On the operator's hardware.

Pricing sized to the brief. Pilot engagement available. Brief VZU on IR →

The 4 incumbents

VZU vs. Q4, Workiva, Diligent, AlphaSense.

The four incumbents in the IR stack are real, well-run, and entrenched. VZU is the second-source — not the replacement. The wedge is the audit trail, the on-prem posture, and the mechanical MNPI boundary. The migration path is real.

Incumbent 01

Q4 Inc.

IRO Agent™. The most direct competitor. SaaS IR platform. VZU is the runtime alternative — on-prem by default, audit-trail-first, MNPI boundary mechanical.
Incumbent 02

Workiva

Intelligent Finance / Sustainability. The disclosure incumbent. VZU is the second-source on disclosure drafting, with the audit trail anchored on the operator\'s side.
Incumbent 03

Diligent

AI Board Member. The board portal incumbent. VZU is the second-source on the IR side — the audit trail, the MNPI boundary, the on-prem posture.
Incumbent 04

AlphaSense

Earnings Call Sentiment Index. The research-data incumbent. VZU\'s Hunter + Oracle ship the same signal — on the operator\'s hardware, in the operator\'s audit trail.

10 questions, answered

The questions the GC, the CFO, and the IRO ask.

Q01

Is our data ever used to train external models?

A

No. The runtime is on-prem by default. When the runtime is cloud-deployed, your data is segregated and never used to train any external model — ours or a third party's. The data residency is the operator's choice. The training is none.
Q02

How is VZU Investor Relations different from Q4 Inc.?

A

Q4 is a SaaS IR platform. 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. The data is on-prem by default. The audit trail is signed and replicated.
Q03

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

A

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.
Q04

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

A

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.
Q05

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

A

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.
Q06

How does the runtime handle MNPI?

A

Sentinel classifies every artifact by MNPI risk. Kai enforces the access policy. Every access lands in the audit trail. The wall is no longer procedural — it is mechanical, and it is the same wall that runs on the engineering side, the IR side, and the compliance side.
Q07

What about Reg FD, MAR, and the Canadian equivalent (CSA 51-352)?

A

The runtime is built to handle all three. Sentinel tags every artifact with the regulatory regime that applies. Oracle applies the safe-harbour and the materiality caveats. Atlas enforces the disclosure discipline. The audit trail is the regulator's form — for the SEC, the ESMA, and the CSA.
Q08

Can the runtime run air-gapped?

A

Yes. The IR On-Prem tier runs on the operator's hardware. Air-gapped option available. The audit trail is signed, replicated, and regulator-grade without any cloud dependency. The brief is the contract. The work is the work.
Q09

How long does it take to deploy?

A

IR Pod ships in 5 business days. IR Runtime ships in 6-8 weeks. IR On-Prem ships in 12-16 weeks, on the operator's hardware, with the operator's security review. The brief sets the boundary. The work is the work.
Q10

Who is this for, and who is it not for?

A

It is for the pre-IPO founder, the mid-cap CFO, the family-office IR lead, and the PE-backed company's first IR hire. It is not for the F500 with a 50-person IR team and a 10-year Q4 contract. For the F500, the migration path is real — but the wedge is the second-source, not the replacement.

Get in touch

Brief VZU on your IR.

Audit-trail-first IR. MNPI-aware. On-prem by default. MCP-native. The brief is the contract. The work is the work. Reply within 1 business day. No credit card. No demo gate.

Brief VZU on IR See the 8 workflows

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

Your IR function, on the VZU runtime .

Audit-trail-first IR. MNPI-aware. On-prem by default.

Audit-trail-first IR.

MNPI-aware.

On-prem by default.

Eight workflows. One runtime. One audit trail.

Earnings-call prep in 24 hours. Not 14 days.

Live call note-taking + sentiment. On the call, in the call.

Quarterly deck generation. The deck is the contract.

Investor email drafting + reply triage. Inbox zero, MNPI-clean.

Cap-table + shareholder-ID. The single source of truth.

Consensus management + estimate tracking. Know the Street before it knows you.

ESG / sustainability disclosure drafting. CSRD, ISSB, SASB, TCFD.

MNPI boundary enforcement. The wall, enforced.

Which 12 agents do the IR work.

Eight workflows. Three patterns. The same 12 agents.

Earnings-call prep

Live call note-taking + sentiment

Quarterly deck generation

Investor email drafting + reply

Cap-table + shareholder ID

Consensus + estimate tracking

ESG / sustainability disclosure

MNPI boundary enforcement

Four buyers. One runtime.

Pre-IPO founder / CFO

Mid-cap CFO / Head of IR

Family-office IR lead

PE-backed company's first IR hire

Three tiers. One runtime. One audit trail.

IR Pod

IR Runtime

IR On-Prem

VZU vs. Q4, Workiva, Diligent, AlphaSense.

Q4 Inc.

Workiva

Diligent

AlphaSense

The questions the GC, the CFO, and the IRO ask.

Is our data ever used to train external models?

How is VZU Investor Relations different from Q4 Inc.?

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

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

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

How does the runtime handle MNPI?

What about Reg FD, MAR, and the Canadian equivalent (CSA 51-352)?

Can the runtime run air-gapped?

How long does it take to deploy?

Who is this for, and who is it not for?

Brief VZU on your IR.

Audit-trail-first IR.
MNPI-aware.
On-prem by default.

Earnings-call prep in 24 hours.
Not 14 days.

Live call note-taking + sentiment.
On the call, in the call.

Quarterly deck generation.
The deck is the contract.

Investor email drafting + reply triage.
Inbox zero, MNPI-clean.

Cap-table + shareholder-ID.
The single source of truth.

Consensus management + estimate tracking.
Know the Street before it knows you.

ESG / sustainability disclosure drafting.
CSRD, ISSB, SASB, TCFD.

MNPI boundary enforcement.
The wall, enforced.