Reconciled p.12
Q2 bookings, by segment
+18.4% vs. prior period
Use case
Sales forecasting
Build a bookings and revenue forecast on actuals that are already reconciled to the ledger, so sales leadership and finance are always looking at the same number, not two versions of it.
Built on bookings and revenue already reconciled from
- PDF filings
- Bank statements
- ERP exports
- ZATCA e-invoices
- Excel schedules
Sales planning today
A sales forecast built on a separate spreadsheet is a guess with a due date.
- Bookings live in the CRM; the revenue forecast lives in a spreadsheet nobody outside sales ops can open.
- A quota change means re-keying the same number into three different plans by hand.
- Pipeline assumptions are opinions, not a forecast tied to a reconciled base of actuals.
- By the time finance sees the sales forecast, it is already a version behind the one sales is using.
One number, two teams
Everything a sales leader needs to forecast with confidence.
A guided walkthrough of a live model: every bookings figure on screen still carries its own citation.
The right number, to the right team
Sales leadership works from bookings and revenue actuals already reconciled to the ledger, not a copy pasted into a separate tracker finance never sees.
A forecast tied to a real target
Track rep, region, and segment performance against quota, and watch the forecast recompute the moment an assumption changes underneath it.
See which deals move the number
Drill into the bookings and expansion figures behind the forecast, down to the transaction each one reconciles against.
Key features
Built for effective sales forecasting
Automated data import
Bookings and revenue actuals flow in from the systems already in place (CRM exports, ERP, bank feeds, or a plain CSV) and land in one normalized chart, already reconciled to source.
Change an assumption, watch it flow through
Test a pipeline or conversion assumption in plain language and watch the revenue forecast recompute deterministically, without leaving the reconciled base case.
Drill down
Every bookings and revenue line opens onto the transaction behind it, so a forecast number is never a black box.
Drill down by rep Drill down by region Drill down by channel
Not a rating. A chain.
Every bookings figure in this forecast can show its own proof.
- 1 Filed
- 2 Extracted
- 3 Reconciled
- 4 Cited
- 5 Exported
Reconciled p.9
Expansion bookings, Mid-Market
+9.7% vs. prior period
Reconciled p.15
New-logo bookings, SMB
−3.1% vs. prior period
Keep exploring
Discover more use cases
Territory & quota planning
Territory and quota assignments modeled against the same reconciled revenue base finance already forecasts from.
See it in actionSales capacity planning
Rep count, ramp, and territory load connect into the same model, so a capacity change flows into cost and revenue together.
See it in actionAccount scoring & segmentation
Segment definitions live in one library and carry the same reconciliation and lineage as any other modeled metric.
See it in actionFrequently asked
Questions about sales forecasting.
What is a sales forecast here, if not a copy of the pipeline report?
It is a revenue projection built on bookings and revenue actuals that are already reconciled to the ledger: the same reconciled base finance uses for its own forecast, not a separately-maintained sales export.
What does Rexfin actually give a sales forecast that a spreadsheet does not?
Scenario modeling on the reconciled base case, drill-down to the transaction behind any bookings figure, and a deterministic recompute: change one assumption and every dependent line updates on its own, the same way every time.
How does a pipeline or conversion assumption change the forecast?
State the assumption in plain language (a conversion-rate shift, a ramp delay, a pricing change) and the deterministic engine recomputes the dependent revenue lines against the same reconciled numbers, not a detached copy of the model.
Does this replace our CRM, or sit on top of it?
It sits on top. Bookings and revenue actuals flow in from the systems already in place (CRM exports, ERP, bank feeds, or a plain upload) and land in one normalized, reconciled model rather than replacing the system of record.
Can sales ops and finance work from the same forecast without stepping on each other?
Role-based access and per-organization isolation keep the model shared but scoped: sales sees what it should, finance sees what it should, and both are reading the same underlying reconciled figures.
Can I just ask what is driving the forecast instead of building a report?
The Analyst agent answers plain-language questions over the model and its cited actuals: retrieving the figures, running the calculation, and citing exactly what it computed from.
Get started
See a forecast tied to your own numbers.
Book a walkthrough and we'll build a sales forecast from a sample of your own bookings and revenue actuals, reconciled, cited, and ready to reforecast on the spot.