Investor Relations.
One connected operating system.
Bring market intelligence, shareholder movement, investor relationships, meetings, feedback, communication, research, earnings and governed AI into one connected workspace — without rebuilding context between workflows.
The IR reality
The problem isn't missing information.
It's information living everywhere.
Investor Relations spans markets, ownership, investors, meetings, research, earnings and communication. When those workflows live apart, the team spends time rebuilding context instead of acting on it.
Context gets rebuilt.
Before the next call or management update, the team searches across files, tabs and conversations to reconstruct what it already knew.
Signals stay isolated.
A shareholder movement, broker revision or investor concern can be visible in one place without becoming the next action somewhere else.
History stays with people.
Meeting context, feedback and follow-ups remain in personal notes or inboxes instead of compounding into institutional relationship intelligence.
IR Command Center is built to remove that fragmentation.
One client. One history. One operating picture. See the connected modelOne connected operating model
Six IR workflows. One client context.
IR Command Center keeps market context, investor relationships, ownership, research, earnings, communication and approved knowledge connected around the same company.
Market intelligence
Company and peer performance, valuation, financial context, news and IR events.
Investor relationships
Investor discovery, rich contact profiles, meeting history, notes and follow-ups.
Feedback & perception
Capture what investors say and turn repeated conversations into institutional memory.
IR Command Center
The company stays at the centre while every workflow adds context to the next decision.
Investor communication
Reusable templates, personalization, collateral, preview, sending and campaign context.
Ownership, research & earnings
Shareholder movement, bulk and block activity, broker estimates, revisions and earnings intelligence.
Governed intelligence
Approved IR knowledge stays queryable through Val.ai with a traceable evidence trail.
The daily operating desk
Start with the operating picture.
Then follow one signal from alert to action and back.
The Dashboard orients the operating day — what needs action, which client it belongs to, what is scheduled and what changed. From there, the same context follows the team into the action and returns as shared relationship memory.
The Dashboard does not replace the underlying workflows. It brings their highest-value signals forward so the team knows where to focus before opening another screen.
Once the Dashboard surfaces what needs attention, carry the same client, investor and relationship context into the action — then return the outcome as shared memory.
Capital market intelligence
Understand the market
before you speak to it.
Price movement is only the starting point. IR Command Center puts the company beside its benchmark, sector and selected peers — then adds trading, valuation, financial and news context to explain what the market is seeing.
Start with the company beside the market.
See the client, benchmark, broad market and sector in one opening view so the first question is always relative: what moved, and compared with what?
See the move — then the trading behind it.
Price, weekly performance, listed-market volume and turnover sit together across the company and selected peers.
Change the lens without rebuilding the peer set.
Move across timeframes and switch between Price, PE, PB and EV/EBITDA while keeping benchmark, sector and selected peers in the same analytical context.
Put financial performance beside market performance.
TTM financials and 52-week positioning help explain whether market behaviour is occurring alongside changes in operating scale, profitability or range.
See liquidity and valuation in the same comparison.
Trading liquidity and valuation metrics sit in a consistent company-versus-peer table, keeping relative positioning visible when investors ask why a valuation gap exists.
Know what changed around the company.
Company updates, peer developments and sector or macro news can be filtered by source and category without leaving the dashboard.
Start with the company beside benchmark and sector performance — before interpreting a move in isolation.
Company performance, peer behaviour, valuation, liquidity and news establish the market context. The next question is when that context matters.
Event & material readiness
Carry market context
into the next IR moment.
Knowing what changed is only useful when the team also knows what is next and can open the right company material immediately. IR Command Center keeps the timeline and the collateral beside the operating context.
See what is next before it becomes urgent.
Results, concalls, investor meetings and conferences stay on one IR timeline, with participation and follow-up context attached.
Open the event, see the relevant context, record participation and feedback, then keep that history available for the next investor conversation instead of rebuilding it from calendar invites and notes.
Keep the right material one click away.
Latest material and history stay organised by company — ready for the next conversation.
Open the current document immediately, then move into earlier versions when deeper context matters.
Market context, event readiness and investor material now travel together into the next conversation.
Investor engagement · Contacts
Know the investor
before the conversation.
Investor engagement starts with finding the right person — not searching through disconnected spreadsheets. IR Command Center combines institution context, market side, category, sector coverage and contact details in one working directory.
Find the right investor by who they are and what they cover.
Search is connected to market side, institution category, institution type, sector coverage and directory source. Instead of knowing the exact spelling or remembering which file contains the contact, the team can progressively narrow the universe.
Every conversation should make the relationship smarter.
Opening a contact brings the relationship history with it: last meeting, next follow-up, perception, investment or research status, feedback and every interaction already captured by the team.
Next we move from relationship intelligence into meeting requests, management confirmation and the operational path from investor interest to a scheduled interaction.
Investor engagement · Meeting requests
Turn investor interest
into a scheduled interaction.
A meeting request should not disappear into email threads. Capture the investor, institution, purpose and preferred format first; let management confirm the final schedule; then carry that interaction back into the relationship history.
Separate the investor request from the management-approved schedule.
IR can capture the request immediately without pretending the timing is final. Management can then confirm the approved date, time, meeting mode and venue in the same workflow.
Investor engagement · Feedback & perception
Capture the conversation.
Then understand the pattern.
A single meeting tells you what one investor thinks. IR Command Center keeps that signal attached to the relationship, then lets the team step back and understand perception across a wider investor audience.
Do not let investor feedback disappear after the meeting.
Bring meeting mode, relationship status, perception, written feedback, follow-up dates and recorded-by context into one searchable feedback view. The team can move from an individual interaction to the exact relationship signal that needs action.
Move from individual comments to a structured view of how the market sees the company.
Build the perception study, choose the questions, mass-circulate it to the selected investor audience, collect anonymous responses and turn the result into management-ready evidence — including question-level scores, investor voice, recurring themes and AI-assisted recommendations.
Investor Communication
Start with the relationship context.
Then choose the right format.
Investor communication should not restart from a blank document every time. IR Command Center keeps reusable email formats, saved templates and work-in-progress drafts in one place — so the team can move from relationship context to a consistent message faster.
Reuse the communication structure. Keep the message specific to the investor.
Search the template library, filter by communication type, reopen saved layouts, continue drafts or start blank. The template is only the starting point; the next step opens the same layout inside Email Studio for editing and personalization.
The next layer adds personalization, rich editing, attachments, preview and sending without leaving the IR workflow.
Investor Communication · Email Studio
Build the message.
Personalize it. Preview it. Send it.
Email Studio turns the selected template into a working communication surface: rich editing, subject and body personalization, attachment preflight, reusable drafts/templates, desktop/mobile preview, test email and controlled private delivery — without leaving the IR workflow.
The template stays reusable. The communication becomes investor-specific.
Edit with familiar rich-text controls, personalize both subject and body, attach supporting collateral, preserve the work as a draft or reusable template, preview the final email on desktop/mobile, send a test, then select the investor audience and deliver separate private emails.
Campaign activity can return to the operating picture, while the underlying investor context remains available for the next follow-up.
Research & Earnings Intelligence
The Street should not live
inside a folder of PDFs.
Research Analyzer first shows the selected-period report library exactly as source material — broker cards and issuer identity only. Analysis appears only after the team runs Val.ai, which then builds Street View, estimates, valuation, guidance and IR actions while keeping every insight traceable to the underlying report.
Turn fragmented research into one management-ready view of the Street.
Start with the research library: each uploaded report is visible by issuer and date before any AI output exists. Run Val.ai only when the team is ready; the analysis workspace then appears with Street stance, target-price range, themes, debates, risks and source-level broker detail.
See not only what the Street thinks — but exactly where the numbers are moving.
Once Val.ai structures the research stack, the same production workspace brings quarterly expectations, annual forecasts, explicit revisions, rating and target changes, valuation methods and broker dispersion together in one audit trail.
Next we connect those expectations with the quarterly snapshot and management commentary from the earnings call.
08 · Earnings intelligence
Carry the quarter from numbers to management voice.
Earnings readiness needs both sides of the quarter: a fast financial snapshot across the company and peers, and the management commentary, guidance and analyst questions that explain what those numbers mean.
See the quarter before opening ten different earnings documents.
The production Earnings Snapshot workspace puts the client and configured peers into the same compact quarterly view, so the IR team can compare revenue, EBITDA, margins, PAT and EPS before a meeting, earnings call or management discussion.
Turn the earnings call into structured management intelligence.
Open a company or peer concall, read the formatted financial snapshot, operational highlights, management commentary, guidance and analyst Q&A, then move directly to the underlying transcript, PDF, PPT or audio when the source matters.
Connect research expectations, earnings performance, management guidance and prior Q&A into the points the IR team should be ready to explain.
Management readiness
Turn the quarter into
the questions management should be ready to answer.
Put Street expectations, the reported quarter, management commentary and analyst Q&A in one preparation view before the next investor conversation.
What is the Street underwriting?
Broker models are constructive on growth; the main debate is the pace of margin normalisation.
What did the quarter actually deliver?
The quarter gives the team the factual base: growth, EBITDA and margin progression.
What did management actually commit to?
Management kept the message measured: constructive growth, gradual margin improvement and cash-conversion discipline.
Where is the market likely to push next?
Prior Q&A keeps the recurring pressure points visible: margin bridge, cash conversion and order quality.
Three themes to be ready for before the next investor conversation.
Connect the evidence already inside IRCC into the explanations and proof points management will need.
Explain the margin bridge.
Broker expectations differ on recovery speed; the quarter improved while management still described the path as gradual.
Make cash conversion concrete.
Working capital remains a recurring concern; management points to collections, milestone billing and project selection as the levers.
Defend the quality of growth.
Investors will test order-book quality; management continues to prioritise risk-adjusted margin and cash characteristics over volume.
Next, move from the question to the governed source behind the answer.
Governed intelligence
Ask the IR knowledge.
Then verify the answer.
Ask approved transcripts, filings, presentations and research in natural language, then move from the answer directly to its source evidence.
Keep the question inside the right company context.
Admins can search the governed corpus by company, while client access remains locked to the company the account is allowed to query.
Search approved IR material — not the open web.
Answers are grounded in the documents available to Val.ai: transcripts, presentations, filings, annual reports and approved research.
Every useful answer should be traceable.
Evidence cards keep document type, period and page context attached to the answer so the IR team can verify the source before using it.
Move from one answer to the next question without rebuilding context.
Use the same company scope to move from performance to guidance, risks, historical commentary or a more specific management question.
The next layer is controlling which documents enter the governed corpus, what remains approved, and what should be quarantined or removed.
RAG governance
Control what Val.ai is allowed to know.
And keep every change auditable.
Govern the document lifecycle behind Val.ai: what is retrievable, quarantined, removed, failed and changed over time.
Retrieval eligibility is explicit.
A document is either governed and active, removed, quarantined or failed. Val.ai does not have to treat every uploaded file as equally trustworthy.
Check the source chain before retrieval.
Source verification, page provenance and embedding coverage are visible at document level instead of disappearing inside an opaque AI pipeline.
Exclude a source without destroying it.
Soft removal can immediately stop retrieval while preserving the source, chunks and vectors so an approved document can be restored later.
Know who changed what and when.
Lifecycle history keeps the movement from quarantine to governed, removed or restored visible alongside the document itself.
Next we connect Val.ai to client-facing widgets and controlled integration surfaces without exposing the underlying IRCC workspace.
Val.ai distribution & integrations
Take governed intelligence to the client website.
Without exposing the private layer behind it.
Distribute governed company knowledge through controlled website widgets or a separate server-side API path.
Choose from six production widget designs.
Clients can select among compact, floating and full research experiences, including light, purple, dark and gold treatments built for different IR website styles.
Keep company scope and browser access constrained.
The widget record controls the governed company and approved website origins. The browser receives a public widget ID — not the private Val.ai API credential.
Change the design without rewriting the embed.
The client integration snippet stays the same while the selected Val.ai presentation preset changes, reducing website-side rework when the experience is updated.
Keep distribution measurable and manageable.
Admin controls cover widget status, allowed origins, request-per-minute and daily limits, alongside recent usage so the public surface remains operationally visible.
Designed for investor-relations websites where the company wants a governed ask-and-answer experience without placing a private API secret in page code.
For direct application integrations, IRCC provides a separate API-key workflow. The full secret is shown only at creation and is intended for a server environment or secret manager rather than browser code.
Next we move from the public integration surface into the controls that decide who can log in, which modules appear, what can be edited, which contacts are visible and who manages the governed knowledge base.
Client & admin controls
Give every client the workspace they need.
Keep the control plane with the IR team.
Map each client login to the right company, modules, contact scope, peer rights and RAG responsibility from one admin control plane.
Activate the account and decide whether that login can manage peers.
Each client login carries its own active state and Capital Markets peer-management permission, so view access and configuration rights do not have to be identical.
Control which modules appear — and where editing is permitted.
Module access is governed for the client company. Tabs can be shown or hidden, with edit rights handled separately. Contacts remain view-only from the client workspace.
Expose the full directory or only the sectors relevant to that user.
Contact access can stay open or be restricted by industry groups and individual sectors. The restriction is enforced on the server rather than only hidden in the interface.
Choose who manages the company's RAG corpus.
Full-service IR clients can remain Valorem-managed, while technology clients can receive scoped document controls for their own company without inheriting widget or platform administration.
Existing passwords are stored as hashes and are not displayed back to the administrator. A new password can be generated or set during reset and shown for handoff in that admin session.
The final product control layer is personal: profile identity, visible role and login history, plus a password-change flow that verifies the current credential before accepting a replacement.
Account & security
Personal identity stays simple.
The account boundary stays explicit.
Users can maintain their profile, see role and last-login context, and replace their password without exposing stored credentials.
Keep the workspace identity current.
Name and work email can be updated from My Account, with email-format and uniqueness validation before the profile is saved.
Role and login context remain visible.
The account page exposes the assigned role and last-login timestamp without turning those governed fields into casual self-service controls.
Verify before replacing the credential.
The current password must verify successfully, the replacement must be confirmed, and the production flow enforces a minimum length before saving a new password hash.
Account changes are not open form posts.
Profile and password updates require an authenticated session and a valid CSRF token; sign-in also regenerates the session identifier after successful authentication.
IR Command Center
One operating system.
One connected IR context.
Markets explain what changed. Investor history explains who matters. Research and earnings explain what the Street is asking. Communication turns preparation into action. Governed Val.ai keeps the evidence within reach.

