Reconciled p.12
Enterprise tier: Q3 revenue rollup
+18.4% vs. prior period
Use case
Account scoring & segmentation
Define account tiers once (SMB, mid-market, enterprise, strategic) and reuse the same segment definitions across finance and go-to-market reporting, with reconciled lineage on every tier rollup.
Segment rollups reconciled from
- PDF filings
- Bank statements
- ERP exports
- ZATCA e-invoices
- Excel schedules
The old way
Segmentation doesn't have to mean four different definitions of “enterprise.”
Knowing which accounts deserve the enterprise team and which stay self-serve isn't just a go-to-market call: it decides where revenue, comp, and forecast attention land for the rest of the cycle.
But the tiering behind that call is usually informal: a spreadsheet column one analyst maintains, redefined whenever the account list changes hands. Nothing forces the next report to agree with the last one.
- Account tiers get redefined ad hoc by whichever team touches the account list next, so "enterprise" in the plan doesn't match "enterprise" in the pipeline report.
- A segment figure gets pasted into a slide once, then treated as fact for the rest of the cycle even as the underlying accounts keep moving.
- When a re-tiered account ripples into revenue forecast and comp, nobody can point to the reconciled number it started from.
- Re-scoring a book of accounts means opening a workbook to re-derive every dependent rollup by hand, tier by tier.
One governed segment, everywhere
Watch a tier rollup trace back to its own reconciled accounts.
A guided walkthrough of a live model: every tier on screen still carries its own reconciled citation.
One definition, every report
Account tiers, thresholds, and scoring inputs live in the definitions library once, finance and go-to-market read the same segment, not two versions of it.
Segments that carry their lineage
A tier rollup is a modeled figure like any other: reconciled, cited, and traceable back to the accounts and periods behind it.
Deterministic, not a black box
Scoring math runs through the same deterministic engine as the rest of the plan: no opaque model assigning a tier nobody can explain or re-derive.
Key features
Built for account scoring & segmentation
Segments defined once, reused everywhere
Set the tier thresholds and scoring inputs in the definitions library one time, every dashboard, forecast, and go-to-market report reads the same segment from then on.
38% SMB
64% Mid-Market
86% Enterprise
52% Strategic
Reconciled at the segment level
Roll an account up into a tier and the rollup carries the same reconciliation and citation trail as any other modeled figure, not a copy-pasted total.
Governed access to segment data
Role-based access keeps sensitive account-level detail scoped to the people who should see it, even as the tier rollup is shared broadly.
Re-score without breaking the model
Move an account to a new tier and every dependent rollup (revenue, comp, forecast) recomputes deterministically in place.
Not a rating. A chain.
Every tier rollup in this plan can show its own proof.
- 1 Filed
- 2 Extracted
- 3 Reconciled
- 4 Cited
- 5 Exported
Reconciled p.9
Mid-Market segment: bookings mix
+6.7% vs. prior period
Reconciled p.15
Strategic accounts: retention variance
−2.1% vs. prior period
Keep exploring
Discover more use cases
Territory & quota planning
Territory and quota assignments run against the same reconciled revenue base finance forecasts from, keeping both sides aligned on one number.
See it in actionSales capacity planning
Rep, ramp, and territory-load plans connect to the same financial model, so a capacity change flows into cost and revenue forecasts together.
See it in actionSales forecasting
Sales forecasts run against bookings and revenue actuals already reconciled to the ledger, so sales and finance never quietly disagree.
See it in actionFrequently asked
Questions about account scoring and segmentation.
What exactly gets defined once when we set up account segmentation?
Tier thresholds, scoring inputs, and the segment names themselves live in the definitions library: set them up once and every downstream report, forecast, and dashboard reads that same definition.
How is a segment tier here different from just tagging accounts in a CRM?
A CRM tag is a label with no lineage. A segment tier in Rexfin is a modeled rollup: reconciled to the accounts behind it and citable back to the source figures, the same way any other line in the plan is.
Does re-scoring an account touch the revenue forecast automatically?
Yes. Move an account to a different tier and every dependent rollup (revenue, comp, capacity) recomputes deterministically, so the forecast never quietly drifts from the segmentation that fed it.
Is account scoring based on a proprietary machine-learning model?
No. Scoring math runs through the same deterministic engine as the rest of the plan: the criteria are explicit and reproducible, not a black-box prediction nobody can re-derive.
Can finance and sales end up looking at different segment definitions?
That's exactly what this is built to prevent: one governed definitions layer means finance's "enterprise" segment and the pipeline report's "enterprise" segment are the same segment.
Do segment-level figures carry the same reconciliation as top-line actuals?
Yes. A tier rollup is checked and cited the same way any other modeled figure is: it is never a separate, unreconciled summary sitting alongside the real numbers.
Do we need a live CRM connection before segmentation works?
No. The Excel, CSV, or PDF upload path works standalone, so segment definitions and scoring can be modeled before any live connection exists.
Get started
Score and segment on evidence, not a copy-pasted total.
Book a walkthrough and we'll build your account tiers from a sample of your own actuals: reconciled, cited, and ready to reforecast the moment a tier changes.