Live Ledger · Full Transparency

How we count the wins

The dollar figure on our homepage comes from a real, append-only ledger of value events logged by RollForge customers — not a marketing estimate. Here's exactly how each number is calculated.

Live data · updated automatically · no manual entries

What the number means

The ticker shows the cumulative dollar total of value recovered or saved by RollForge customers since the platform launched. Every dollar in that total is tied to a specific, attributable event: an overdue invoice collected through an AR workflow, dispatch callbacks eliminated through scheduling optimization, a cash-flow gap identified and closed, or margin recovered after a pricing analysis.

Each event is recorded once — we use a unique attribution_key per event so the same win is never counted twice, even if a customer runs the same workflow multiple times.

No individual company data is ever exposed. The homepage shows only the aggregate total across all customers. No company names, no revenue figures, no individual breakdowns.

The four value sources

Each dollar in the ledger comes from one of four sources, each with its own calculation rule:

Source 1

AR Recovered

Overdue accounts-receivable balances that were identified through RollForge AR aging reports and subsequently collected.

amount = invoice_balance_at_collection

Source 2

Callback Saved

Revenue recovered by reducing dispatch callbacks — technician re-visits that were eliminated using RollForge dispatch optimization insights.

amount = callbacks_eliminated × avg_callback_cost

Source 3

Cash Gap Closed

Cash-flow shortfalls identified by RollForge's 13-week forecast that were resolved before they became a crisis — measured at the size of the gap closed.

amount = forecasted_gap_at_detection

Source 4

Margin Recovered

Gross margin improvements from pricing corrections identified through RollForge job-margin and pricing analysis tools.

amount = revenue × margin_delta_pct

Attribution and dedup rules

Every event row in the ledger has an attribution_key — a unique string that ties the event to its source. Examples:

ar_invoice:42 — invoice #42 collected through the AR workflow
dispatch_action:7 — dispatch optimization action #7
cash_gap:org:5:2025-09 — September 2025 cash gap for org 5
margin:portco:12:2025-10 — October 2025 margin recovery for portco 12

Each attribution_key is unique per organization — if the same playbook runs again on the same source event, the duplicate insert is silently ignored. The total only grows when genuinely new value is created.

What's not counted

Conservative by design. We only count events that completed a specific RollForge workflow and recorded a dollar amount at that time. We don't estimate potential savings, don't count trial accounts, and don't project future value.

Specifically excluded:

Sample / demo data (flagged and excluded at query time)
Events with $0 amount (logged for analytics but not counted)
Potential or projected value — only completed events count
Internal Polsia / test organization activity

How the number updates

The public API endpoint (/api/public/wins-stats) caches the aggregate for 5 minutes to keep database load low. The homepage refreshes the number every 30 seconds via a client-side fetch. In practice, the figure updates whenever a customer completes a value-creating workflow — several times per day across the customer base.

Frequently asked questions

Can I see my company's contribution to the total?

Not from this page — that's intentional. Your organization's value events are visible inside your RollForge dashboard under the Value Creation section. The public ticker is aggregate-only.

What currency is this?

US dollars. All events are stored in cents and denominated in USD.

Does the number go down?

No. The ledger is append-only — events are never deleted or modified. The number can only increase over time.

Who audits this?

The events are written by RollForge product code at the time a playbook completes. No human can manually add or edit rows. Each event requires a unique attribution_key scoped to the organization — duplicate inserts fail at the database level.

Add your shop to the ledger

Connect your books, run your first playbook, and start recovering real dollars from your own data.

Start 7-Day Free Trial →