11 dashboards
Business view of billable volume from laminr-prod: processed (billable, status=2) vs submitted loan packages per day with support-ticket load overlaid as a cost signal; time-to-processed p50/p95 from the package state history (packages_historicalloanpackage); customer trends (top 14 customers + Other) with counts/share views; and a range-aware top-customers table with share, billable rate, growth vs the prior window, and new-customer badges. Internal/test tenants excluded (Laminr, demo and pentest accounts). Ranges: 7/30/90/180 days. Support tickets from the Open Support Tracker 'Laminr Tickets' tab. Static snapshot captured Jul 18 2026.
Customer-satisfaction view of laminr-prod: unique active customers and users per day and per window (with prior-window growth); time to first terminal state (under review OR processed — how fast the customer gets an answer) vs time to final processed; review rate (share of packages needing support review); and support latency (review → processed — the support team's contribution to wait time). Fast processing = happy customer. Internal/test tenants excluded. Ranges: 7/30/90/180 days. State-history coverage begins Apr 13 2026. Static snapshot captured Jul 18 2026.
One row per customer combining the other dashboards' snapshots — 30-day processed volume and growth (Revenue Report), override burden and packages touched (Overrides), zero-touch rate (Zero-Touch Rate), and daily active users (Adoption) — into a simple health grade: Healthy, Watch, or At risk. Built entirely from sibling data.js files with no database dependency; refreshes after the source dashboards each morning. Static snapshot captured Jul 18 2026.
How actively lender teams use the product, from the API audit log: write-actions per day with daily active users, what those actions are (file uploads, overrides, income modeling, package management, settings — endpoint families, never raw paths), and per-customer engagement. Excludes internal admin actions and internal/test tenants; weekends excluded; ranges 7/30/90/180 days. Static snapshot captured Jul 18 2026.
Which financial institutions our customers' borrowers actually bank with, and how well we handle each: bank-statement file volume per institution (normalized brand names) over the trailing 180 days, weekly trend of the top banks vs the long tail, per-institution parse-failure and cashflow-check pass rates, and newly-appearing institutions — a roadmap prioritization tool (which bank to fix or integrate next = volume × failure). Institution detection began 2026-05-07. Internal/test tenants excluded. Static snapshot captured Jul 18 2026.
Product-health view of manual overrides from overrides_override (laminr-prod): every override is work our product failed to do for the customer — fewer overrides = more joy. Tracks override burden in aggregate (overrides per processed package, share of packages needing any manual work, inclusion vs exclusion split) and per customer, plus an automation-opportunities panel grouped by theme (keyword-bucketed: payment processors, payroll labeling, transfers, …) listing the customers who need each rule, with inclusion-vs-exclusion direction analysis that flags contradictory signals — consistent themes are global-rule candidates, mixed themes need tenant-scoped rules. Internal/test tenants excluded; weekends excluded; ranges 7/30/90/180 days. Static snapshot captured Jul 18 2026.
Where packages stall between submission and processed: the submitted → under review → processed funnel per submission-day cohort, the share that goes straight through vs. stops in review, and time-to-processed medians for each path plus review dwell time (submission → first review → processed, from package state history). Window starts 2026-04-13 (state history is only reliable from then). Internal/test tenants and weekends excluded; ranges 7/30/90 days. Static snapshot captured Jul 18 2026.
The product north star: share of processed packages that went submission → processed with no human intervention — no manual override and no under-review stop. Splits every touched package by what touched it (overrides only, review only, or both), tracks the zero-touch rate with trend, and breaks it down per customer. Window starts 2026-04-13 (package state history is only reliable from then). Internal/test tenants and weekends excluded; ranges 7/30/90 days. Static snapshot captured Jul 18 2026.
Parser agreement dashboard over waterfall_cashflowcheckresult + waterfall_parser (laminr-prod). The truth parser is per-unit: the last parser that actually ran on that unit (file × account × statement period) — not necessarily the last parser configured in the waterfall. Each earlier parser's attempt is scored against it: MATCH when both pass or when both extract the same cashflow within tolerance (matching numbers on a bad document count as parsing success), MISMATCH when the extracted cashflow differs. Consistent matches per bank = skip-check / early-parser optimization opportunity; consistent mismatches = parser improvement opportunity. Truth-parser failures are user errors (bad documents) — excluded from metrics, shown for volume. Includes waterfall config with fail_on_cashflow flags, bank × parser agreement matrix, and a Today/Yesterday/7/30/90-day range selector. Static snapshot: data since Jul 18 2026, captured Jul 18 2026.
Operational health of the parsing waterfall from waterfall_waterfallrun, waterfall_waterfalltaskexecution, and waterfall_filepageparser (laminr-prod). Daily run outcomes (completed / failed / cancelled) with average run duration and stuck-retry counts; per-parser task execution performance (volume, failure rate, avg/p50/p95 duration, retries, skips); pages parsed per day by parser with count/share views (which parser is actually doing the work — cost view); and task errors by type over time with top parser × error hotspots. Rolling 30-day window with Today/Yesterday/7/30-day range selector. Static snapshot captured Jul 18 2026.