Driver-based forecasting: map each driver to its source system

Driver-based forecasting links a few operating drivers, such as tickets per customer or hours per project, to financial outputs. Tracing each driver to its source system and years of history gives a metadata-only map that also answers SourceX's fit questions about system breadth and record depth, without exporting records.

How do you build a driver-based forecast, and what does it tell you about records?

Build it by choosing the few operating drivers that move revenue and cost, tracing each one to the system where it is recorded, and linking them to the financial model. The by-product is a map of systems and years of history, which is also what a data licensing fit screen asks for.

A forecast that says "revenue follows tickets per customer" is only as good as the ticketing history behind it. Writing down where each driver lives, and how far back it goes, is half the work of the model and costs nothing extra.

Prerequisites

A current P&L and the last two to three years of monthly actuals
Access to the controller and the heads of sales, operations and support
A list of the company's operating systems, even a rough one
Agreement that you are collecting metadata about the systems, not copies of records

Step by step: from driver to source system

List the outputs. Pick the three to five lines the board argues about: revenue, gross margin, headcount cost, working capital.
Name one driver per output. For example, orders per sales rep, hours per project, tickets per customer, or utilization per consultant.
Trace each driver to its system. Write the system, the field and the report that produces the number today.
Record the history. Note the first year the driver was captured consistently and whether older years sit in an archived system.
Test the link. Back-cast the driver against actuals for at least eight quarters. A driver that cannot be back-tested usually has a data problem.
Assign an owner. Each driver needs a person who can explain and export it.

The driver-to-system map

Keep it in one table. This is the artifact the rest of this page reuses.

Driver	Typical source system	Years of history to note	Outcome label present?
Tickets per customer	Helpdesk or support platform	First consistent year, any prior tool	Resolved, escalated, refunded
Hours per project	PSA or time tracking	Years since the current tool, plus archive	Budget versus actual
Orders per rep	CRM and order management	Years of closed deals	Won or lost, with reason
Headcount and attrition	HRIS and payroll	Years of employee records	Hire, promotion, exit
Collections days	ERP receivables	Years of invoices	Paid, disputed, written off

The chart of accounts redesign guide is the companion task when drivers do not line up with legacy account structures.

Reading the map as a licensing fit screen

Count rows and years. The program's company baseline asks for 50+ full-time employees at peak (contractors excluded), several years of documented operations and breadth across systems. Strong companies often keep records in 10-15+ systems, and 5-10+ year histories help. A completed driver map shows quickly whether a client is near that profile.

What the map shows	What it suggests	Next action
Fewer than five systems, under three years	Thin breadth and history	Park it; revisit after growth
Eight or more systems, five or more years	Plausible depth	Run the company fit checker with the owner
Many drivers with outcome labels	Records tied to results	Flag as a stronger candidate
Key driver lives only in spreadsheets	Weak system record	Ask who can export and how
History sits in a retired tool	Risk of loss	Raise preservation first

The map does not decide qualification. SourceX does that after the introduction, once the company completes its own data inventory.

When to refresh the map

A driver map goes stale quickly, so tie it to the calendar. Revisit it at annual planning, after any system change and whenever a new owner joins the finance team.

Annual budget: confirm each driver still comes from the same system and field.
System change: record the cutover date and where the old history now lives.
Leadership change: make sure the new owner can find the exports and knows who approved them.
Lender or board request: reuse the map instead of rebuilding a systems list from memory.

Keeping one dated version per year also gives the next CFO a record of how the business measured itself, which is useful whether or not licensing ever comes up.

Common mistakes

Mistake	Why it hurts	Fix
Too many drivers	The model cannot be maintained	Cap at one driver per output
Drivers with no owner	Nobody can explain or export them	Name an owner per driver
Ignoring archived systems	Years of history go unrecorded	Add a "retired tools" row
Copying data into the model deck	Confidential records spread	Keep only labels and counts
Assuming the company holds the rights	Customer contracts may restrict use	Flag for counsel before any introduction

Illustrative example

Illustrative: a fictional 140-person engineering services firm builds a forecast around billable hours per project and utilization. The map shows time in a PSA for six years, an older tool for four more, project documents on shared drives, a CRM with nine years of proposals and a helpdesk used by the client portal team. The CFO notes the older tool is scheduled for shutdown next quarter and tells the controller to keep a full export. That one line may matter more than the forecast.

What to say to the owner

How the introduction and rewards work

You never export or describe confidential records. After the owner agrees, register as a partner and share your referral link or use the referral form. SourceX qualifies the company, the company completes the inventory, price and terms are agreed, buyers review, and a closed deal pays the company before your reward is considered.

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. Rewards become payable only after the buyer pays and SourceX receives its fee, and no reward is guaranteed. The reward is never deducted from what the company receives. Check your own engagement letters and fee rules, and see the fractional CFO playbook. For e-commerce clients, the e-commerce CFO guide shows how the same map looks for order data. If the company is financing against receivables, the borrowing base guide explains why a license receivable needs separate handling.

Next step

Add a "years of history" and "owner" column to your next driver map. When a client looks like a fit, register as a partner and make the introduction, or have the owner apply at sourcex.si/apply. Our CAS growth guide and the explainer on audited financials in a sale cover adjacent questions.

Step 1Share your linkSend your personal link to a company you know.
Step 2Company appliesThe company applies itself at /apply.
Step 3Buyer selects and paysThe buyer selects and pays for the data and SourceX receives its fee.
Step 4You get your rewardYour share of SourceX fees becomes payable.

Common questions

How many drivers should a driver-based forecast have?

Fewer than most first drafts. One driver per major output line, three to five outputs in total, is easier to maintain and to explain to a board. If a driver has no owner, no source system or cannot be back-tested against eight quarters of actuals, remove it or fix the data first.

Do I need to export any data to build the system map?

No. The map holds metadata only: the driver, the system, the first year captured, the owner and whether outcomes are labeled. Nothing from the records themselves needs to leave the company, and nothing should be pasted into decks or shared with a referral partner or SourceX at this stage.

Does a good forecast model mean the company will qualify?

No. A clean model shows the company knows its systems, which helps screening, but qualification is decided by SourceX after the introduction, based on size, history, data breadth and rights. Treat the map as a preliminary signal and never promise a client an outcome.

What if a key driver lives only in spreadsheets?

Ask who maintains the files, how many years exist and whether the numbers come from a system export. Spreadsheets can still be part of a record set, but a driver with no system behind it is a weaker signal for fit and a forecasting risk in its own right.

Should the CFO raise licensing during the forecasting engagement?

Only if it fits the engagement and your own rules on referral fees and disclosure. A natural moment is the end of the build, when the system map is complete and the owner is already thinking about assets. Keep the message short and free of promises.

Free resources

Days sales outstanding calculator — How many days customers take to pay.
Business succession planning assessment — Ten questions on successor, transition and documentation.
NPV calculator — Net present value with a discounted cash flow table.
All free tools · MCP resource center

By SourceX Partnerships Team · Published 2026-10-09 · Updated 2026-10-09

Know a US company with valuable proprietary data?

Become a referral partner from anywhere we support, get your link and introduce an owner or authorized decision-maker.

Refer a company →

I own a business

Explore licensing your company's data to AI developers worldwide. Start a short assessment; no uploads needed.

Start an assessment