Can your revenue lead show where the next twelve months of revenue will come from?
A forecast helps you decide before the results arrive. Hiring, delivery capacity and cash commitments depend on when the company expects to earn revenue and what has to happen first.
Milestone 13 establishes the strategy. Milestone 14 defines the customer path and acquisition economics. Milestone 15 turns that work into maintained records, a supported forecast and a review the team can use.
Define the decision before configuring software
Open one meaningful line in today’s forecast and ask, “Where did this number come from?” Follow it to opportunities, orders, renewal records or demand evidence. The first unsupported assumption gives you a useful starting point.
A spreadsheet, CRM, order system and accounting package can work together. Name the source that governs each important fact and the person who maintains it. “One system” means a connected way of working, not a requirement to buy one application for everything.
Define stages with observable evidence of customer progress. A proposal under review might require confirmation that the right person received it and agreed to a next step. A salesperson’s confidence alone cannot establish that. Capture activity and source information without confusing engagement with a qualified purchase.
Make the underlying records trustworthy
The Tech Stack Audit connects each decision to the reports, sources, responsibilities and system connections it needs. The Data Hygiene SOP describes definitions, necessary fields, updates, corrections and checks.
Require information when it becomes available and useful. Forcing a guessed amount into a first-contact form can make a complete-looking record less trustworthy. Keep important unknowns visible and assign follow-up.
During a review, select records to trace, including exceptions and different revenue lines. Then check completeness and totals. A few accurate examples do not prove that important orders have not been omitted or that opportunities have not been duplicated. Preserve history and contact preferences when correcting records.
Build the monthly revenue view from actual sources
The Bottom-Up Forecast Build separates three sources of expected business:
- Existing contracted work, with delivery timing and relevant conditions.
- Expected renewals or repeat business, supported by history and current evidence.
- New business, separating current opportunities from demand still to be generated.
Build twelve months by meaningful product or service line. Explain conversion, retention, pricing, sales-cycle timing and the source of each material assumption. A new offer can lack a long history; identify that uncertainty and test a weaker outcome. A top-down target alone does not establish demand.
For illustration, eighteen comparable qualified opportunities × 40% expected conversion × $75,000 average booking value produces $540,000 of expected bookings. The implied 7.2 wins is a planning average; actual contracts are whole deals. If the pipeline is already measured in dollars, multiplying it by average deal size again would count the amount twice. Use sales-cycle evidence to place expected wins in the right months.
Carry bookings through to revenue and cash
Signing an order, earning revenue, issuing an invoice and collecting cash are different events. The CRO supplies customer and timing evidence, operations tests delivery, and finance confirms the accounting treatment and financial connection.
A hypothetical $120,000 service agreement starts in October and covers twelve months. If finance confirms the service is earned evenly, recognized revenue is $10,000 per month, with $30,000 in October through December. An upfront invoice or payment would not make all $120,000 October revenue under that stated treatment.
Use the actual contract and company accounting policy. Reconcile the forecast to an identified financial-model version and monthly revenue lines. A rolling October-to-September view and a January-to-December budget cover different periods; compare overlapping months and explain the extension.
Keep three things distinct: the goal is what you want, the forecast is what current evidence supports, and the adopted budget is the fixed plan used for comparison. Updating the outlook must not quietly erase the original budget or prior forecast.
Test whether the company can sell, deliver and fund it
The revenue lead examines demand, sales capacity and conversion. Operations tests the people and delivery schedule. Finance tests acquisition spending, working capital and other material funding needs. One person may carry several responsibilities; every question still needs an answer.
When the evidence shows a gap, examine the response. Better qualification, different pricing, changed terms, additional capacity or a revised timetable have different consequences. Do not increase a win rate merely to make the forecast reach the goal.
You can improve stages, records and the operating forecast while the financial model is being completed. Financial judgments that depend on unresolved information remain provisional.
Preserve what you expected before results arrive
The Pipeline Coverage and Forecast Review connects source cleanup, the forward view and the comparison with actual results. Inspect stale dates, missing renewals, wins, losses and changes. Preserve the checked version used for the meeting.
In a hypothetical month, a forecast saved beforehand shows $100,000 of revenue; the matched actual is $90,000. The difference is minus $10,000, or minus 10% using the forecast as denominator. A delayed delivery, cancellation and accounting correction would require different responses. Trace the cause before moving the number into next month.
Coverage compares defined eligible pipeline with a defined remaining goal. State dates, scope and weighting. Use an appropriate demand or backlog measure where it fits better. A generic 3× ratio or accuracy percentage cannot establish whether your plan is supported.
Installed requires three consecutive completed monthly forecast-versus-actual reviews. Each uses a forecast saved before results were known, matched actuals, explained material differences and a recorded response. Suitable existing reviews count. Reconstructed predictions do not. Three cycles demonstrate repeated maintenance, not guaranteed results or a complete seasonal history.
Prepare your CRO Monthly Review
Use one dated record. The existing two-page review places the dashboard and priorities on the first page, with discussion and commitment on the second. Link the full reports instead of copying every number into another file.
| Part | What to prepare |
|---|---|
| Five dashboard groups | Revenue versus plan, conversion rates, CAC and payback, pipeline coverage, retention and churn. Use agreed definitions, units, dates and targets. |
| Explanation and forward view | What changed, why, what remains unknown and the implications for the coming periods. Preserve the earlier forecast. |
| Quarterly work | Progress on the revenue function’s selected priority and the leader’s development priority, where established. Check the previous commitment. |
| Discussion and decision | What is working, what needs attention, the recommendation, help or authority needed, responsible person and next review. |
The function assessment and leader-readiness assessment each have their own /81 scale. Keep both separate from the owner’s Velocity Score. You can begin the monthly practice before completing Module 7 or hiring a new CRO.
The CEO combines the revenue explanation with finance and operations for the separate owner-and-CEO meeting. The owner need not join every sales huddle. Urgent decisions return before their deadline rather than waiting automatically for the next quarterly review.
Complete the seven requirements
Reliable records, a supported forecast, financial reconciliation and actual repeated use all matter. A missed result can reveal a functioning review process; hitting the number once can hide a weak one.
Open the seven completion requirements
1. Define the stages the team actually uses.
So a forecast stage represents evidence about a customer decision, rather than a salesperson’s optimism.
Ask: What changed for this customer, and what evidence permits the next stage?
Sufficient evidence: Current stage definitions and advancement criteria, named responsibilities, and actual opportunity or demand records showing their use. Reuse M14’s customer map and agreed handoffs; add sales detail only when it improves a decision.
Work route: Data Hygiene SOP; Customer Journey Map Template; Sales + Marketing SLA Document. Reuse suitable current records.
- The requirement is supported by evidence and its required use.
Record: complete / incomplete / not reviewed; evidence location and date; what remains; responsible person and next review.
2. Establish trustworthy sources and maintenance.
So the revenue lead can show where a number came from and resolve conflicting reports.
Ask: Where does each important fact live, and who checks and corrects it before a review?
Sufficient evidence: Named authoritative sources for pipeline, orders, renewals and financial actuals; agreed definitions and necessary fields; demonstrated correction/exception handling. Trace important records to source evidence and reconcile report totals, including completeness, duplicates and stale records. A reviewer can select records, not just inspect prepared examples. A spreadsheet or connected set of systems can qualify. Material errors or unknowns preventing a defensible revenue conclusion keep the requirement incomplete; minor bounded exceptions remain visible.
Work route: Tech Stack Audit Worksheet; Data Hygiene SOP. Reuse suitable current records.
- The requirement is supported by evidence and its required use.
Record: complete / incomplete / not reviewed; evidence location and date; what remains; responsible person and next review.
3. Build the supported twelve-month revenue view.
So the company can see expected revenue by month and meaningful product or service line.
Ask: Where will the revenue come from, when will it arrive on the income statement, and what could change it?
Sufficient evidence: A dated twelve-month monthly forecast by meaningful revenue line. Separate contracted/existing work, expected renewals and new work. Distinguish observed facts from future assumptions; identify sources, conversion/retention basis, pricing, sales-cycle timing and material risks or downside. Test assumptions against available history and current evidence, with new or weakly supported assumptions identified. Do not double count current opportunities and future lead generation. A top-down goal alone does not establish operating support; future certainty is not required.
Work route: Bottom-Up Forecast Build Template. Reuse suitable current records.
- The requirement is supported by evidence and its required use.
Record: complete / incomplete / not reviewed; evidence location and date; what remains; responsible person and next review.
4. Reconcile the revenue view with finance.
So the revenue plan and financial plan describe the same business and period.
Ask: Can you trace this revenue line into the current financial plan and explain any difference from the approved budget?
Sufficient evidence: A CRO/CFO review identifying forecast dates, model edition, line mapping and monthly recognized revenue. Bookings, billing and collections are distinct. Calendar or scope differences are reconciled explicitly. The adopted budget remains the fixed comparison; a later forecast does not silently overwrite it. Essential unresolved mapping or accounting issues keep this item incomplete.
Work route: Bottom-Up Forecast Build Template; company Financial Model project. Reuse suitable current records.
- The requirement is supported by evidence and its required use.
Record: complete / incomplete / not reviewed; evidence location and date; what remains; responsible person and next review.
5. Test the ability to sell, deliver and fund the plan.
So growth assumptions do not commit money or capacity the business cannot support.
Ask: Who will win and deliver this work, and what cash or spending does that require before it pays back?
Sufficient evidence: Responsible revenue, operations and finance leads review sales capacity, delivery timing, acquisition spending and material funding implications. Supported constraints, chosen responses and unresolved risks are visible. One person may hold multiple roles. A separate hire, another financial model or a new spending commitment is not required.
Work route: Bottom-Up Forecast Build Template; existing acquisition guardrail and financial plan. Reuse suitable current records.
- The requirement is supported by evidence and its required use.
Record: complete / incomplete / not reviewed; evidence location and date; what remains; responsible person and next review.
6. Run the pipeline and monthly forecast review.
So the team learns from what happened instead of quietly moving the forecast to match the result.
Ask: What did the saved forecast say, what actually happened, and what explains the difference?
Sufficient evidence: Actual operating review of opportunity/demand evidence and three consecutive completed monthly forecast-versus-actual reviews. Each compares a contemporaneous forecast saved before the result was known with matched actuals; reconstructed forecasts do not count. Preserve snapshot date, horizon, period, revenue line and units. Explain material volume, price, timing, renewal and data differences, and record the response. Use coverage or an appropriate demand/backlog measure with a stated basis. Suitable existing review records count. Three cycles demonstrate repeated maintenance, not annual forecasting reliability or a universal accuracy percentage.
Work route: Pipeline Coverage Calculator; CRO Monthly Review. Reuse suitable current records.
- The requirement is supported by evidence and its required use.
Record: complete / incomplete / not reviewed; evidence location and date; what remains; responsible person and next review.
7. Use the result and keep it current.
So the forecast changes company choices and remains usable between planning events.
Ask: What real decision did this evidence inform, who owns the follow-through, and when will you review it again?
Sufficient evidence: Dated company or ownership reviews, supported decisions and reasoning, a named maintainer, a documented update process and the next review. Another capable person can follow the records and reproduce the explanation; the owner may still hold the revenue role. Continuing the current approach can qualify when supported. Weekly revenue work, monthly ownership reviews, quarterly priorities and annual planning use the same current evidence at their appropriate detail. A calendar invitation or simulated decision does not establish use; no compulsory hire or full owner transition is added.
Work route: CRO Monthly Review; existing quarterly/annual record; current 90-Day Game Plan when selected. Reuse suitable current records.
- The requirement is supported by evidence and its required use.
Record: complete / incomplete / not reviewed; evidence location and date; what remains; responsible person and next review.
Review the milestone-specific 0–3 score and evidence test
0 (Not Started). You have not yet begun applying the revenue-systems and forecasting work and cannot yet explain the connected approach this milestone requires. Unavailable evidence is recorded as not reviewed, not automatically scored zero.
1 (Learning). You can explain how agreed customer stages, trustworthy records and supported assumptions produce a revenue forecast, why bookings, revenue and cash differ, and how review improves the forecast. You can identify what your company needs to build or verify, but have not yet begun applying that understanding to its records or decisions.
2 (In Progress). You have begun applying the approach to your company, but one or more of the seven requirements remain incomplete. Records, definitions or a forecast may exist while essential support, financial reconciliation, actual review or continuing responsibility is still missing.
3 (Installed). All seven requirements are met. The team uses agreed customer stages and maintained, verifiable revenue records. Its supported twelve-month monthly forecast distinguishes facts from assumptions, reconciles with finance and has reviewed sales, delivery and funding implications. Three consecutive completed monthly reviews compare forecasts saved beforehand with actual results, explain material differences and record the response. A named person maintains the work through a documented process another capable person can follow. Decisions and continuing reviews use that evidence. Material errors or unknowns preventing those judgments keep the affected requirement incomplete; future certainty and a universal accuracy percentage are not required.
The verification test. Open the current forecast with the responsible revenue lead. Select important records to trace to their sources, check completeness and reconcile the report totals; do not rely only on prepared examples. Show how existing business, renewals and new work support the monthly forecast without double counting, distinguishing facts, assumptions and downside. With finance, reconcile the revenue timing to the identified financial plan while preserving the adopted budget. Show the sales, delivery and funding review. Open three consecutive completed monthly reviews, each with its forecast saved before results were known, matched actuals, explained differences and response. Follow the documented update process, name the maintainer and next review, and show a real decision the evidence informed. Suitable existing records count and documents may be open. Completion does not require a particular software system, recall speed, compulsory hire, full owner transition or generic coverage/accuracy target. This verifies the installed revenue system, not future results or a buyer’s complete diligence.
Review suitable existing work before creating more documents. Record each requirement as complete, incomplete or not reviewed, with its evidence and date. You choose the saved score. Keep owner, peer, coach and AI assessments separate, including their reasoning and any disagreement. Unavailable evidence remains unreviewed; it is not automatically a zero. Preserve earlier reviews and choose the next useful action, responsible person and review date.
Keep the same forecast in use
Current definitions, operating sources and CRO tools belong with Your Leadership Team. The financial model and adopted budget belong in The Numbers. Dated forecasts, reviews and decisions belong in The Rhythm, with links to the versions used.
Name the maintainer and document the update process so another capable person can follow it. Weekly revenue work maintains the operating detail; monthly reviews explain results and the outlook; quarterly reviews revisit assumptions and priorities; annual planning uses the evidence to build the next budget.
Explore the idea further
- The 12-Step Revenue Forecast with Kim, episode 463. Connect market context, customer activity and timing to a supported revenue explanation.
- What a CRO Does to Create Predictable Revenue with Kim, episode 480. Clarify who maintains the complete revenue result.
- Revenue Architecture explains the strategic choices behind the forecast. Sustainable Financials connects the result to profit, position and cash.
Choose your next step
Review the wider system. The Ownership Assessment helps you consider this capability beside your ownership goals and the other milestones. Keep missing evidence visible and choose the work that matters next.
Connect the work with support. The 90-Day Boardroom Blueprint brings ownership direction, the financial foundation and decisions into a first usable Playbook. You can explore that support directly; completing the Assessment is not a prerequisite.
← M14: Customer Journey & CAC · Module 5 · Module 6: Transferable Margins →