Build the forecast from operating drivers, not a single top-line growth guess. Tie revenue to customers, volume, price, retention, or capacity; connect margins to delivery costs and staffing; and translate the plan into working-capital movements, capital expenditure, debt service, and cash. For every important assumption, record its owner, period, source, rationale, and whether it is historical, contracted, management-planned, or speculative. Then show a base case, downside case, and upside case with explicit changes to the drivers. A defensible projection does not pretend uncertainty is absent. It lets a prospective buyer trace the path from evidence to earnings and cash, understand what must happen, and test the consequences if it does not.
Start with the valuation question and the forecast boundary
Before opening a spreadsheet, define what the projection is meant to support. A buyer may want to understand sustainable earnings, cash available for debt service, investment required to maintain the business, or the effect of a planned growth initiative. These are related but not identical questions. Write down the valuation date, the period covered, the currency and units, and whether the model describes the business as it operates today or includes a specific, documented change.
Also separate historical results, management assumptions, and valuation judgments. Historical revenue is evidence about what happened. A proposed price increase is an assumption. Selecting a discount rate or an earnings measure is a valuation judgment that may require professional advice. The IRS business valuation guidelines illustrate why scope, effective date, purpose, assumptions, limitations, and information sources should be identified before analysis begins [2]. A private sale is not automatically governed by those guidelines, and the appropriate method can depend on the transaction and jurisdiction.
Build a driver tree instead of guessing growth
A driver-based model explains revenue as a chain of observable activities. Depending on the business, that chain might include leads, conversion, active customers, units per customer, average price, renewal, utilization, or delivery capacity. Choose only drivers that the owner can define and update. If revenue is simply increased by a percentage with no operational explanation, a reviewer cannot tell whether the forecast depends on more demand, higher prices, more staff, or an assumption that several favorable events occur together.
For each driver, show the historical starting point and the forward assumption in the same unit. Explain the reason for the change. A signed contract, order backlog, recurring renewal pattern, published price list, capacity plan, or documented sales pipeline is different evidence from a hope that demand will improve. The SEC Financial Reporting Manual, in its reporting context, describes reasonable support as potentially including market surveys, economic indicators, operating-history trends, and internal data and analyses [3]. That principle is useful even when a private company is not preparing a public filing.
Link margins and staffing to the work required
Revenue should not grow independently of the resources needed to deliver it. Map direct costs to the same volume, product, customer, or service drivers used for revenue. Then map payroll and contractors to roles, headcount, start dates, compensation assumptions, and productivity constraints. Include benefits, recruiting, training, overtime, commissions, and other costs when they are economically relevant. If a margin improves, identify the mechanism: price, mix, vendor terms, utilization, process change, or a cost that is genuinely variable.
Separate committed changes from possible improvements. A planned hire supported by an approved offer is not the same as a future team that may be needed if sales arrive. Likewise, a proposed automation or renegotiated supplier contract should not be treated as a realized saving until its timing and basis are documented. In a different but relevant present-value context, IAS 36 says projections should use reasonable and supportable assumptions, give greater weight to external evidence, and exclude benefits from uncommitted restructuring or performance improvements [1]. For a sale forecast, use the same discipline: label the assumption and show what evidence would cause it to enter the model.
Translate profit into working capital and cash
A projection becomes more useful when it explains when money moves, not only when revenue is recognized. Build receivables from billing and collection timing, inventory from purchasing and turns where relevant, and payables from supplier terms. Identify deposits, deferred revenue, retainers, taxes, debt payments, lease commitments, and other cash items that can make cash differ from accounting profit. Then connect capital expenditures and maintenance spending to the capacity or service level they support.
A cash-flow forecast should cover at least the business's cash-flow cycle and should list receipts when cash is expected to arrive, rather than merely when a sale is recorded [4]. List outgoings by period, calculate net cash flow, and carry forward the cash balance. This exposes a common valuation risk: a growing business may require more working capital before the growth produces distributable cash. It also gives a buyer a clearer basis for asking which investments are recurring, which are one-time, and which are optional.
Document every material assumption and its evidence
Create an assumption register beside the model. For each material line, record the assumption, unit, owner, effective period, source, date checked, and confidence category. Useful categories include observed, contracted, management plan, external estimate, and scenario-only. Link the assumption to a source record such as a general ledger report, customer agreement, payroll schedule, supplier quote, operational report, or market reference. Keep the underlying documents organized and access-controlled rather than copying confidential material into a public narrative.
The register should also state what would invalidate the assumption. For example, a renewal assumption may be revisited after a cohort review, while a hiring assumption may stop if a role is not approved by a specified date. The IRS guidelines emphasize that workpapers should document the steps, techniques, evidence, facts, and conclusions supporting a valuation analysis [2]. A business owner can apply that idea without presenting the register as a formal appraisal or claiming that a particular method is required.
Use scenarios to expose uncertainty
Build scenarios by changing a small number of identifiable drivers rather than applying an unexplained percentage to every line. A downside case might combine slower conversion, longer collection, delayed hiring, and higher delivery cost. An upside case might use stronger conversion only if the staffing and capacity plan can support it. State which inputs change in each case and which remain fixed. Avoid calling a scenario a probability unless the basis for that probability is documented.
Review the effect on revenue, operating profit, working capital, capital spending, cash balance, and any valuation output. Sensitivity tables can show which drivers matter most, but they do not make the estimate certain. IAS 36's present-value guidance says estimates should reflect a range of possible outcomes and that cash-flow and discount-rate assumptions should be consistent so uncertainty is not double-counted or ignored [1]. The exact valuation treatment depends on the method and professional context, so use scenario analysis to clarify risk rather than to manufacture precision.
Reconcile the forecast to history and test stopping conditions
Bridge the latest historical period to the first forecast period. Explain changes in volume, pricing, mix, gross margin, payroll, working capital, and investment. Reconcile the forecast income statement to cash and check that the balance sheet or working-capital schedule does not create unexplained plugs. Compare each forecast period with the immediately prior forecast and record the reason for material changes.
Set review triggers before sharing the model. Examples include a driver moving outside a defined range, a contract not signing by its assumed date, collections exceeding the modeled days, a hiring plan losing approval, or a required funding balance falling below the operating threshold. When a trigger occurs, pause the affected scenario, investigate the source record, and revise or remove the assumption. This is stronger than quietly overwriting an input because the new result looks more attractive.
Present the model so a buyer can challenge it
Share a concise assumptions summary with the forecast, not a spreadsheet that requires the reader to infer the logic. Show historical actuals beside forecast periods, identify non-recurring items, define any adjusted earnings measure, and explain the bridge to cash. Put sources and dates beside material assumptions. Distinguish management's plan from a market observation and from a buyer's own valuation conclusion.
Do not imply that one projection proves a price. The IRS guidance recognizes asset, market, and income approaches and calls for judgment in selecting methods and benefit streams [2]. A buyer may test the forecast against other evidence, request supporting records, or apply a different method. Before sharing sensitive schedules or customer-level information, use a confidentiality process appropriate to the transaction and obtain legal or accounting advice where the issue is jurisdiction-specific.
Use software as a controlled workflow, not an authority
A practical workflow can assign one person to maintain the source-of-truth financial records, one accountable owner to approve operating assumptions, and a named reviewer to challenge the model before it is shared. If software or AI is used to classify records, summarize variances, or flag unsupported inputs, define the task narrowly. Give it only the data it needs, preserve permissions, require a human to verify each material output, and keep the original record available for comparison. Stop the pilot if it invents a source, changes a period, drops a caveat, or cannot show which input produced a conclusion. Do not allow the tool to send disclosures, negotiate, approve changes, or contact buyers autonomously.
Acquivo is a software platform that delivers the entire sell-side M&A process, valuation, marketing materials, buyer matching, and deal management, on one platform for business owners, M&A attorneys, and boutique investment banks. Acquivo gives business owners the entire sell-side process an investment bank would run, as software, with no success fee. The software is user-operated, so the owner remains responsible for deciding what to include, checking source records, setting permissions, and obtaining qualified legal, tax, accounting, or valuation advice where needed.
Key Points
- Define the valuation question, date, period, currency, units, and forecast boundary before modeling.
- Link revenue to operating drivers and connect margins and staffing to the work required to deliver it.
- Convert earnings into working-capital movements, capital needs, debt service, and cash timing.
- Maintain an assumption register with owners, dates, source records, confidence categories, and invalidation triggers.
- Use explicit base, downside, and upside scenarios that change identifiable drivers rather than hiding uncertainty in one growth rate.
- Require human review, permissions, source checks, and stopping conditions before any model or automated analysis is shared.
Sources and references
Source retrieval dates record research access, not article publication. Read our editorial and date policy.
- [1] IAS 36 Impairment of Assets · Accessed
- [2] Business Valuation Guidelines · Accessed
- [3] SEC Financial Reporting Manual Topic 3 · Accessed
- [4] How to create a cash flow forecast in 4 steps · Accessed
Choose your next step
Acquivo is user-operated software. Owners and their professionals remain responsible for decisions, communications, and professional review.
Educational information, not individual legal, tax, or investment advice. Consult qualified professionals for your circumstances. Acquivo provides software, not representation or negotiation on your behalf.