The revenue number your board trusts without asking why.
Verity connects read-only to your CRM and runs every active deal through a three-layer governance engine: eligibility gates, composite scoring and tier assignment. The result is an assured revenue number, built only from what your CRM can evidence, before the forecast call and before the board meeting. For finance, the same evidence becomes a monthly statement of assured revenue by landing month.
Forecasts rest on judgement and require explanation rather than trust. Revenue numbers become political under pressure. Risk surfaces too late to act. The board interrogates and the CEO defends.
With Verity
Every deal carries a timestamped confidence record. The assured number is earned, not estimated. Pipeline reviews start from evidence, not opinion. The CFO has an audit trail from day one.
CRMs
Store activity. They don't govern it. Excellent at capturing data, silent on whether that data is strong enough to stand behind a revenue number.
Forecasting tools
Estimate probability. They don't explain it. Models predict outcomes but can't tell you which rule was broken or why confidence fell.
CRMs capture activity. Forecasting tools model probability. Nobody governs the pipeline before it becomes a forecast. That gap is the category Verity was built for: Revenue Assurance (Pre-Close).
Forecast call versus assured number
Your forecast call
Commit, Best case, Pipeline. Categories called by reps and managers. Essential for running the quarter, but they move with judgement, pressure and quarter-end optimism.
Verity tiers
Assured, Partial, Unassured. Assigned by fixed rules against what the CRM actually records. A deal cannot be talked into Assured. It can only be evidenced into it.
Verity does not replace the forecast call. It shows which part of the call your CRM can back, and exactly what is missing from the rest.
What Verity produces
Sample pipeline · 10 opportunities
Sample data · Every deal traceable to its governance evidence
Quantum Retail scored a raw composite of 72, enough for the Partial tier. But an eligibility gate fired (Overdue: closing date expired), capping the final score at 45. The deal stays out of the assured number, not because the deal looks weak, but because the CRM record no longer supports it. That mechanism is explained next.
For finance · Monthly Assurance Statement
The CEO asks how much of the pipeline can be trusted. The CFO asks how much trusted revenue lands in which month. The Monthly Assurance Statement answers that on the 1st of every month: assured revenue by landing month, a planning number finance can put in the model, and a reconciliation of last month's statement against what actually closed.
Monthly Assurance Statement · August 2026
Sample data · Issued 1 August · Immutable once issued
CFO module · Early access
Planning number · August
R2.17M
R2,380,000 assured intake × RAR 0.91
August
R2.17M
Assured intake R2.38M
September
R1.93M
Assured intake R2.12M
October
R1.50M
Assured intake R1.65M
July · assured intake scheduled at 1 July
R2.31M
Promised
Booked from schedule
R2.13M
RAR 0.92
Slipped to August Slip
R180K
Tracked
Won from Partial, never on the calendar
R380K
Review
The planning number is the assured intake landing in the month, adjusted by Verity's own Revenue Accuracy Ratio (RAR): what actually booked against what earlier statements scheduled. The adjustment is never scaled above 1.0, and the number of outcomes behind it is disclosed on every statement. Buckets carry full assured deal value, so the calendar sums back to the assured number. Verity applies no probabilities of its own. Partial-tier deals never enter the planning number. View the sample statement →
Three layers of governance
Verity doesn't score deals with a single model. Every deal passes through three sequential layers, each with a distinct job. Every score traces back through all three: which gate fired, which dimensions contributed, which tier was assigned. That traceability is what makes the assured number defensible under questioning.
Layer 01
Eligibility gates
Hard governance ceilings
Deals that fail baseline governance (missing names, zero value, no recent activity, expired close dates, excessive stage dwell) are capped before composite scoring begins. No amount of logged activity rescues an abandoned deal. Governance failures never reach the assured number.
Deals that clear eligibility are scored across six dimensions of deal quality: stage, activity, time, stakeholders, commercial readiness and ecosystem integrity. A weighted composite produces a score from 0 to 100. Each dimension is independently inspectable, so the source of any movement is always visible.
6 dimensions · 0 to 100 composite
Layer 03
Tier assignment
Evidence-based classification
Only Assured (75 and above) enters the assured number, at full value. Partial (60 to 74) is tracked separately as conditional pipeline. Unassured (below 60) stays out entirely. Thresholds are configurable per sector profile. The output is conservative by design: earned, not estimated.
Connects to HubSpot today, with Zoho CRM in early access. Verity never writes to your CRM. Data flows up to Verity; nothing flows back down.
Step 02 · Score
Deterministic governance engine
Every deal runs through the three-layer engine. No AI inference, and Verity never generates its own win probabilities. Each score links to the exact rule, gate or dimension that produced it.
Step 03 · Govern
Append-only confidence ledger
Every scoring run is timestamped and written to a ledger that cannot be edited after the fact. You can show the assurance position of any deal on any date, and exactly why it moved.
Inside Layer 2 · Six governance dimensions
01
Stage discipline
Has the deal progressed through valid stages, with the fields each stage requires? Skipped stages and missing information are flagged immediately.
02
Activity consistency
Is the customer being engaged often enough? Days since last customer-facing contact, measured against stage and sector thresholds.
03
Time integrity
Has the deal sat in its current stage too long? Is the closing date still valid? Stale deals surface before they reach the board pack.
04
Stakeholder completeness
Are enough people on the buying side associated with the deal, with their roles recorded? Single-threaded deals become visible weeks before close.
05
Commercial readiness
Is deal value set? Are the commercial details expected at this stage present? Gaps that would block close are flagged early.
06
Ecosystem integrity
Is the deal anchored to an established, complete account record? New or incomplete accounts reduce the score. Assessed from CRM records only.
Who relies on it
CEO and CFO
One number that holds up
An assured revenue figure where every rand traces to a timestamped record, and a monthly statement finance can plan and reconcile against.
Sales leadership
Reviews that target the gap
Deal-level evidence of exactly what is missing, by gate and by dimension. Pipeline reviews focus on the specific gap in the record rather than the story around the deal.
Advisors and partners
A rule set you can calibrate
Sector profiles with configurable thresholds. Closed outcomes are recorded against the score each deal carried, so calibration is grounded in evidence as it accumulates.
Ready to see your pipeline governed?
Tell us about your CRM and pipeline. We'll assess fit and set up a read-only connection. Nothing in your CRM changes.