The CFO Looks at Revenue from a Different System Than Sales
Monday morning. The sales director opens the CRM and sees €1.2M in pipeline. The CFO opens the accounting system and sees €680,000 in confirmed orders with invoices outstanding. The CEO asks for a revenue forecast for the board meeting on Thursday.
Three different numbers. Three different definitions of “revenue.” Three different levels of confidence in the answer.
In field service, construction, and professional services companies, finance and sales run on different data, different vocabulary, and different time horizons. The CFO tracks recognized revenue, cash flow, and balance sheet positions. Sales tracks pipeline value, win rates, and deal momentum. Operations tracks project status, resource utilization, and delivery timelines.
All three are looking at the same business. None of them are looking at the same numbers.
CFO involvement in RevOps is what fixes this — and it is not optional.
Why Finance and Sales Speak Different Languages
The gap between finance and sales is structural, not personal. Both functions were designed to operate in opposite directions.
Sales was designed to maximize deal volume and velocity. It runs on forward-looking probabilities: this deal is 70% likely to close by end of quarter for €150,000. Finance was designed to report actuals accurately and conservatively. It runs on confirmed past events: this invoice was sent for €150,000 on March 15th and payment is due April 15th.
Both perspectives are necessary. The problem is that they stay separate — the probability-weighted pipeline in the CRM never informs the cash flow forecast, and payment trends in the accounting system never feed back into the sales team’s understanding of which customers are actually valuable.
The result: sales chases deals that finance would flag as credit risks. Finance builds forecasts that ignore the pipeline sales has spent weeks building. Operations staffs up on gut feeling because nobody has combined pipeline and capacity data into a single view.
72% of companies lose more than 10% of revenue to process gaps. Most of those gaps sit at the intersection of finance and sales — where data should connect but doesn’t.
The CFO’s Role in RevOps
In companies that implement RevOps successfully, the CFO architects the revenue system — not receives reports from it.
Traditionally, finance reports on what happened. In a RevOps-enabled business, finance informs what should happen — using financial data to drive better sales strategy, better pricing, better customer selection, and better resource allocation.
The CFO brings three things to RevOps that no other function can provide:
Unit economics discipline: Sales identifies which deals look exciting. Finance identifies which deals are actually profitable after accounting for acquisition cost, delivery cost, and support cost. Without the CFO’s cost visibility, RevOps optimizes for revenue at the expense of margin.
Cash flow perspective: A €500,000 deal that closes in Q4 but pays in Q1 doesn’t solve a Q4 cash flow problem. The CFO translates pipeline probability into cash timing — and ensures the business has sufficient runway regardless of whether optimistic forecasts materialize.
Historical pattern recognition: Finance holds the data that reveals which customer segments have the lowest churn, which project types carry the highest margin, and which deal sizes produce the best LTV:CAC ratios. This data is the foundation for strategic customer selection — and it lives in the accounting system, not the CRM.
Finance Data as RevOps Foundation
The metrics that drive RevOps are financial metrics. Most companies already hold the underlying data — just not in a form usable for operational decisions.
Customer Acquisition Cost (CAC)
True CAC includes sales commission, marketing spend, the time sales spends on deals that don’t close, onboarding costs, and any free or discounted work done to win the relationship. Finance is the only function that sees all of these costs — and therefore the only function that can calculate an accurate number.
Customer Lifetime Value (LTV)
For field service and construction companies, LTV requires connecting maintenance contract history, project revenue, callout frequency, and renewal rates — data spanning the ERP, CRM, and accounting system. The target is LTV:CAC of at least 3:1. Most SMBs cannot calculate this accurately because the data sits in separate systems.
Recurring Revenue Metrics
For any company with maintenance contracts or retainers, the recurring revenue base is the most predictable part of the business. Tracking MRR, ARR, renewal rates, and expansion revenue requires finance to categorize revenue by type — not just by customer or project. That categorization produces forecasting accuracy that project revenue alone never delivers.
Project Margin by Segment
A €100,000 project at 15% margin is worth less than a €70,000 project at 35% margin. Finance calculates actual project margin when cost data from operations connects to revenue data from billing. That analysis typically reveals that 10–20% of projects are unprofitable — without the company knowing it.
Cash Flow and Pipeline Forecasting Together
Connecting finance to RevOps produces better cash flow forecasting immediately. It requires two data streams:
From the pipeline: Probability-weighted revenue by expected close date and expected payment date. A €200,000 project closing in Q2 with 60-day payment terms delivers cash in Q3. A pipeline that looks healthy for Q2 creates a Q3 cash gap if payment terms are ignored.
From finance: Historical payment behavior by customer type and deal size — which customers pay on time, which don’t, which project types accumulate change orders that delay final invoicing. Applied to the current pipeline, this produces a cash flow forecast built on how the business actually behaves.
Companies that build this combined view can answer: “If we win everything currently in pipeline, what does our cash position look like month by month for the next 12 months?” RevOps makes that question answerable. Most CFOs currently cannot answer it with confidence.
Revenue Recognition Automated
For project-based businesses, revenue recognition is a persistent operational problem. Revenue is recognized when work is delivered, when milestones are hit, or when invoices are sent — depending on contract terms and accounting standards. Manual processes make this slow and error-prone.
The same project manager managing delivery also estimates what percentage of the project is complete for revenue recognition. That is not a reliable input for financial reporting.
Automated revenue recognition connects project completion data — work orders, milestone approvals, delivery confirmations — directly to the recognition calculation. Revenue accrues as work is confirmed. The monthly close shortens. Accuracy improves because recognition is driven by operational data, not estimates.
Practical Steps: Connecting Accounting to RevOps
Step 1: Audit Your Revenue by Category
Categorize last year’s revenue by type — project, recurring contract, one-off service, emergency callout — and calculate the margin for each. This baseline analysis almost always reveals surprises and sets the agenda for what to optimize.
Step 2: Connect Pipeline to Cash Flow Forecast
Build a model that translates CRM pipeline — probability-weighted, by expected close date — into a monthly cash flow forecast. Include historical payment terms and typical delays. Review it weekly with sales leadership and refine it as the gap between forecast and actuals becomes visible.
Step 3: Build LTV:CAC by Customer Segment
Use historical finance data to calculate true acquisition cost and lifetime value for each main customer segment — by industry, geography, or deal size. Identify which segments carry the best economics. Feed this directly to sales as guidance on where to focus prospecting and which deals to prioritize.
Step 4: Automate Revenue Reporting
Build a dashboard showing in real time: recognized revenue this month, pipeline-weighted revenue next quarter, MRR/ARR trend, and project margin by type. This replaces the monthly finance report as the operational heartbeat of the business — visible to the full leadership team, not just finance.
Step 5: Establish a Revenue Review Cadence
The CFO, sales director, and operations lead meet weekly to review the same numbers from the same system. This is where finance and sales stop speaking different languages and start making decisions from shared data. RevOps is an operating model, not a software project.
The CFO as Revenue Architect
The CFO who engages with RevOps stops reporting on revenue and starts designing how it is created — building the pricing model that optimizes margin, identifying the customer segments with the best economics, and constructing the forecasting model that makes the business’s future visible and manageable.
Companies that operate this way grow 19% faster and achieve 15% better profitability — not because they have better salespeople, but because every decision runs on better information.
The finance system holds the data. The sales system holds the pipeline. RevOps connects them. The CFO who drives that connection delivers more strategic value than any amount of backward-looking reporting ever could.
If you want to build the financial foundation for RevOps — or understand how your current finance and sales data could work together — Resappi is built to make that connection practical for field service, construction, and professional services companies.
Further reading: our RevOps metrics guide covers CAC, LTV, and pipeline metrics in depth. Our implementation roadmap shows how to build this in stages without disrupting current operations.
