Sales Projections Template

In plain language: Identifies the company preparing the projections, the executive authorizing them, and any counterparty (lender, investor, or board) to whom they are being submitted.

Common mistake: Naming a department or team rather than the legal entity and an authorized officer. If projections are submitted to a lender and the signatory has no authority to bind the company, the document may be challenged as unexecuted.

In plain language: States the exact calendar period covered by the projections, the product lines or business segments included, and any explicit exclusions.

Common mistake: Leaving the forecast period vague ('fiscal year' without specifying start and end months). Ambiguous periods create disputes when actuals are compared to projections — particularly in lender covenants.

In plain language: Documents every material assumption driving the revenue estimates — unit volumes, average selling price, market growth rate, pipeline conversion rates, and seasonality adjustments.

Common mistake: Embedding assumptions in narrative prose rather than a numbered or lettered list. Buried assumptions are missed by reviewers, and when actuals diverge, the company cannot point to documented inputs that were agreed upon.

In plain language: Sets out the specific revenue figures the company expects to achieve in each month and for the full forecast year, by segment or product line.

Common mistake: Showing only annual totals without monthly breakdowns. Lenders and investors use monthly schedules to track variance in real time; a forecast with annual-only figures cannot be monitored or enforced against covenants.

In plain language: Explains the basis for the year-over-year or period-over-period growth rates embedded in the projections, referencing historical performance, market data, or strategic initiatives.

Common mistake: Projecting growth rates materially higher than historical performance without explaining the specific driver. Unsupported hockey-stick assumptions are the single most common reason lenders and investors reject a projection document.

In plain language: Specifies how often actual results will be compared to projections, who is responsible for producing the variance report, and what threshold triggers a formal notification or remediation plan.

Common mistake: Omitting a variance threshold and notification obligation when the document is submitted to a lender or investor. Without this clause, the company has no contractual duty to disclose significant underperformance until a covenant breach occurs.

In plain language: Lists and incorporates by reference all schedules, spreadsheets, CRM exports, and market research reports that support the projection figures.

Common mistake: Referencing schedules that are not actually attached. If a lender or investor later requests the supporting data and it is inconsistent with the projection figures, credibility is damaged and contractual obligations may be triggered.

In plain language: States that the projections are prepared in good faith based on information available at the date of signing, and disclaims any guarantee of future results while representing that the assumptions are reasonable.

Common mistake: Omitting any limitations language when submitting projections to an external party. Without it, a material shortfall can expose the company to claims of misrepresentation — even when the underlying assumptions were sound at the time of signing.

In plain language: Specifies the jurisdiction whose law governs interpretation of the document and the mechanism — arbitration or litigation — for resolving disputes.

Common mistake: Omitting a governing law clause entirely on the assumption that projections are 'just a planning document.' When projections are incorporated into a loan covenant or investment agreement, ambiguous governing law can mean costly jurisdictional disputes.

In plain language: Records the signatures of the authorized preparer and the reviewing executive or counterparty, along with the date the document becomes effective.

Common mistake: Collecting only one signature when two are required by a financing agreement or internal governance policy. A single-signature projection submitted under a dual-authorization covenant can trigger a technical default.

Sales projections are documented estimates of expected future revenue over a defined period — monthly, quarterly, or annually — derived from specific stated assumptions about unit volumes, pricing, market conditions, and pipeline conversion rates. They differ from a casual forecast in that they are formally prepared, signed off on by an authorized executive, and used as binding inputs for budgeting, investor reporting, lender covenants, or internal quota-setting.

A signed sales projections document creates a formal record of the figures and assumptions that an authorized officer of the company has reviewed and approved. When projections are submitted to a lender or investor, the signature establishes accountability, supports a representations clause, and typically satisfies a documentary requirement in the financing agreement. Unsigned projections are often treated as informal estimates and carry no contractual weight.

The terms are often used interchangeably, but in formal financial and legal contexts, a sales projection is a structured, documented, and signed document incorporating specific stated assumptions, whereas a sales forecast is typically an operational or CRM-generated estimate used for internal planning. When a lender or investor requires a formal deliverable, they generally mean a signed projections document, not a spreadsheet export.

At minimum, the assumptions section should document average selling price, unit volume or deal count, pipeline conversion rate, market growth rate with its source, seasonality adjustments, and any named strategic initiatives expected to drive incremental revenue. Each assumption should be stated as a discrete numbered item with a reference to the data source or historical basis — not embedded in narrative prose where it can be missed during review.

For operating budgets, 12 months with monthly detail is the standard. For bank loan applications, lenders typically require 2–3 years. For equity fundraising, investors expect 3–5 years of projections with the first year in monthly detail and subsequent years in annual totals. Projections beyond 5 years are rarely credible and generally not requested unless you are in a capital-intensive industry with long project timelines, such as real estate or infrastructure.

Most commercial loan covenants use a 10–15% monthly variance as the threshold requiring a written notification to the lender. For investor reporting, a 15–20% negative variance is a common trigger for a formal update call. The exact threshold should be negotiated with the counterparty and written explicitly into the variance tracking clause — not left to judgment at the time the gap appears.

Yes, provided the template is completed with real, documented assumptions, includes a monthly revenue schedule, attaches historical actuals as a supporting schedule, and is signed by an authorized officer. Most SBA lenders and commercial banks have specific formatting preferences — confirm their requirements before finalizing the document, and consider a review by your accountant before submission.

If projections are submitted to a lender and actual revenue falls materially short, the company may breach a financial covenant, triggering a default notice and accelerated repayment. If submitted to investors, a significant miss can damage credibility and affect future fundraising terms. Including a well-drafted representations and limitations clause — stating the projections are good-faith estimates based on reasonable assumptions, not a guarantee — provides meaningful protection in both scenarios.

In most commercial and investment contexts, notarization is not required — wet or electronic signatures from authorized officers are sufficient. However, some government grant programs, regulated lenders, or cross-border financing arrangements may require notarization or apostille. Check the specific requirements of the counterparty or program before executing.