FinancialHeroCard pattern
Portfolio value at risk
Decision-support estimate. P10 is the conservative case; P90 is tail exposure. Method, confidence, and source coverage are visible before any number reaches a board or IC packet.
Design partner
Platform
Verify, quantify, prove, and operate from one evidence spine.
VALTY sits above scanners, control systems, cloud signals, and operating workflows. It normalises what is true, shows what it means financially, ranks the next move, and packages proof that can leave the room: board pack, IC brief, or audit artifact.
The platform boundary
VALTY sits above your sources: and stays there.
These are product and engineering constraints, not marketing principles. They govern what VALTY builds, claims, and ships.
Above the source
VALTY reads. No rip-and-replace to start.
Scanners, EDR, SIEM, GRC, cloud posture, identity, and financial systems stay the authoritative record. VALTY normalises their evidence into financial language and proof artifacts.
Evidence first
No assertion without a source.
Every claim carries a source, confidence tier, and freshness window. Where evidence is absent or stale, confidence drops and the line item is flagged, never gap-filled.
Proof is the product
The deliverable is not a dashboard.
Board packs, IC briefs, and audit packages export the claim alongside its source coverage, confidence tier, and freshness timestamp. The blocked-claim ledger is part of the artifact.
Decision support
Numbers carry their caveats.
Financial estimates are decision-support ranges with method, confidence, and limitation next to the claim, built to be challenged by CFOs and operating partners before approval.
The four motions
One evidence spine, four motions.
Every source signal stays traceable from ingestion to export. Verify what is true, quantify it in dollars, prove it in artifacts, and operate on what matters, without losing the evidence trail.
01 · verify
Verify what is true.
Controls, findings, suppliers, and source signals become evidence objects with owner, freshness, and confidence, normalised from whatever source systems already exist.
- Control evidence freshness
- Source-linked findings
- Supplier and component proof
02 · quantify
Quantify it in dollars.
Dollar impact is calculated from source evidence using FAIR-style factor analysis and Monte Carlo simulation. The assumption set stays visible next to the number so it can be challenged, not just trusted.
- EBITDA bridge with scenario families
- FAIR factor set visible
- P10 / base / P90 range
03 · prove
Prove it in artifacts.
Claims leave the platform as proof cards, board packs, and exportable evidence packages. A blocked-claim ledger surfaces what is not ready to publish before delivery.
- Proof pack anatomy
- Board-ready export
- Blocked-claim ledger
04 · operate
Operate on what matters.
Portfolio and program actions stay ranked by value impact, proof status, and next owner. The command view aggregates across companies or programs without hiding the evidence underneath.
- Portfolio command rollup
- Value-ranked action queue
- Hold-period tracking
Product surfaces shown are illustrative design-partner builds. Actual outputs are generated inside an authenticated workspace against your source systems.
Live proof grammar
Design partner
The financial output
The output is a range, not a point.
Coverage decides how much of the model is measured versus inferred. More automated or API-verified evidence raises source confidence; gaps lower the confidence tier and can block affected line items. V1 does not automatically rewrite the modeled PERT range from coverage alone.
- Range width reflects explicit model inputs; source confidence is labeled separately
- Each driver traces to a FAIR factor and a source evidence object
- Export is blocked if any line item falls below the publication confidence threshold
Financial outputs are decision-support estimates with method, confidence, and limitation adjacent to the claim, not contractual guarantees or insurance valuations.
What leaves the platform
Every claim is published, gated, or blocked.
Buyers can inspect what is supported and what requires owner action before they trust the number. The blocked-claim ledger travels with the artifact; it is not stripped before delivery.
Board claim
- Source
- EBITDA bridge + evidence pack
- Confidence
- Model-based, source-linked
- Freshness
- Reviewed before export
Audit claim
- Source
- Control catalog + proof card
- Confidence
- Evidence-backed, tier-stamped
- Freshness
- Freshness visible to auditor
Insurance claim
- Source
- Risk scenario + control proof
- Confidence
- Decision-support only
- Freshness
- Requires current source coverage
Blocked claim
- Source
- Missing or stale evidence
- Confidence
- Not publishable
- Freshness
- Requires owner action before export
Connect your sources
Bring the evidence you already have.
VALTY reads your scanners, cloud posture, identity, EDR, and GRC through 36 supported connectors, and maps that evidence onto 30+ framework catalogs, 2,700+ source-cited controls, so coverage is measured, not assumed. No rip-and-replace to get started.
Import
Bring what you already export.
Findings, control catalogs, SBOMs, and supplier assessments load as evidence objects: CSV, SARIF, and structured exports, with owner and freshness attached.
Connect
36 supported connectors.
Scanners, cloud posture, identity, EDR, and GRC systems connect directly through 36 supported connectors, so evidence stays current and coverage is measured, not assumed.
Roadmap
More sources, same contract.
New connectors join the same evidence contract: every signal carries source, confidence, and freshness, so the financial model stays honest as coverage grows.
Next step
Choose the workflow you want VALTY to prove first.
Access is segmented by buying motion, so role, intent, and source context reach the right follow-up path without dead-end links.
PE / Operating partner
Request portfolio briefing
Portfolio rollup, value-at-risk view, and board-action path.
Request portfolio briefingCISO
Map your evidence sources
Connect findings, controls, owners, and proof artifacts.
Map your evidence sourcesCFO
Review the financial-risk model
Inspect assumptions, confidence, and source citations around dollar estimates.
Review the financial-risk modelCompliance / Federal
Discuss readiness package
Factual readiness, component provenance, and crosswalk for review.
Discuss readiness package