Building a capex approval memo that survives a CFO review

Key Takeaways

• The memo should open with the "Bottom Line Up Front" (BLUF): what you want, why, how much it costs, and what happens if the answer is no, stated in the first few lines, not built up to over several paragraphs.
• A complete submission includes the asset description, business justification, expected benefits or cost savings, estimated cost with supporting quotes, proposed timing, and the useful life for depreciation purposes.
• For significant investments, a formal business case needs payback period and net present value (NPV) stated explicitly with numbers, not described qualitatively, and CAPEX must be clearly distinguished from OPEX since only CAPEX is depreciated.
• If a project genuinely has no hard financial return, regulatory compliance being the clearest example, the memo should say so directly rather than forcing a weak ROI number to justify what's actually a risk-avoidance decision.

A capex memo that opens with background and context, and only reaches the actual ask on page two, is asking a CFO to do the work of finding the number themselves. The memos that get approved quickly are structured the other way round: the answer first, the supporting case after.

Lead with the answer, not the build-up

The memo should provide the "Bottom Line Up Front": what you want, why you want it, how much it costs, and what happens if the answer is no (PM Resource Hub, executive approval memo structure, retrieved 2026-09-08). This isn't a stylistic preference, it's a structural fix for the most common failure mode in weak capex memos: burying the actual decision the CFO needs to make under several paragraphs of context they have to read through first to find it. State the ask, the cost, and the consequence of inaction in the opening lines, and let everything after that support, rather than build toward, the headline.

What a complete submission actually includes

Beyond the opening summary, a complete capex submission needs: a description of the asset or investment itself, the business justification explaining why it's operationally necessary, the expected benefits or cost savings it will produce, the estimated cost backed by supporting quotes (not a rough estimate), the proposed timing, and the useful life the asset will be depreciated over (8020 Consulting, writing a better capital expenditure report, retrieved 2026-09-08). Missing any one of these tends to generate a follow-up question that delays approval, a memo that anticipates the standard questions is the one that moves through review in a single pass rather than two or three rounds.

The numbers section: specific, not qualitative

For any investment of meaningful size, a formal business case with ROI analysis, payback period, and NPV calculations is expected (8020 Consulting, retrieved 2026-09-08). Specifically, this means stating the payback period as a number, in months, and the NPV as a dollar or dirham figure over a stated horizon, not describing the investment as having "a strong payback" or "solid long-term value" without the underlying figures. Run the actual cost, expected benefit, and timeline through the ROI calculator to generate these figures directly rather than estimating them by feel, since a CFO reviewing the memo will expect to see, and may recompute, exactly these numbers.

The memo also needs to clearly distinguish CAPEX from OPEX: capital expenditure is a one-time cost that gets depreciated over the asset's useful life, while operational expenditure is expensed as incurred (8020 Consulting, retrieved 2026-09-08). A request that blurs this distinction, treating an ongoing subscription cost as if it were a one-time capital purchase, or vice versa, signals to a CFO reviewer that the financial modelling underneath the request may not be reliable either.

When there's no hard financial return, say so explicitly

Not every capex request is justified by a payback period or an ROI figure, and pretending otherwise is a common way to weaken an otherwise legitimate request. If a project doesn't have a hard financial return, a regulatory compliance requirement is the clearest example, the memo should state that plainly, and frame the justification as risk avoidance rather than force-fitting a weak or speculative ROI number onto a decision that isn't actually about return on investment (8020 Consulting, retrieved 2026-09-08). A CFO who spots an artificially inflated ROI figure on what's obviously a compliance-driven purchase will trust that number less, not more, and it can cast doubt on the ROI figures in other memos from the same requester.

Naming the stakeholders and the approval path

The memo benefits from being explicit about who else is involved in the review: department heads, financial controllers, executive management, and, for larger requests, the board, each typically holding a defined role in reviewing and approving the expenditure (Manifestly, capex approval checklist, retrieved 2026-09-08). Naming this path in the memo itself, rather than leaving the CFO to work out who else needs to sign off, shortens the actual approval cycle by making the next steps visible from the outset rather than something that has to be chased down after the memo lands.

Putting the structure together

The memo that survives review, in order: a BLUF opening stating the ask, cost, and consequence of inaction; the asset description and business justification; expected benefits with supporting quotes for cost; explicit payback period and NPV figures (or an explicit statement that this is a non-financial, risk-avoidance case); a clear CAPEX/OPEX distinction; the useful life for depreciation; and the approval path naming who else needs to sign off. Each section anticipates a specific question a CFO would otherwise have to ask, which is what actually shortens the review cycle, not a more persuasive tone. Before drafting the memo, it's also worth confirming the request fits the business's actual financial position rather than just the project's own numbers, which is what the financial health review is for: a memo asking for capex the balance sheet can't comfortably support gets scrutinised on that basis long before the payback period is even discussed.

Frequently asked questions

Should I lead a capex memo with background context or with the ask itself?

With the ask. Structure it as a Bottom Line Up Front: what you want, why, how much, and what happens if the answer is no, in the opening lines. Background and supporting detail come after, to support that headline, not build up to it.

What if my capex request doesn't have a strong ROI or payback period?

State that directly if the investment is justified on other grounds, such as regulatory compliance or risk avoidance, rather than forcing a speculative ROI figure to justify a decision that isn't really about financial return. A transparent non-financial justification is more credible than an inflated financial one.

Is it necessary to name the other approvers in the memo itself?

It's not strictly required, but it shortens the approval cycle by making the next steps visible upfront, department heads, financial controllers, executive management, or the board, depending on the request's size, rather than leaving the reviewing CFO to identify and chase down who else needs to sign off.

The bottom line

A capex memo survives CFO review by answering the questions a CFO will otherwise have to ask: what, why, how much, how long until it pays back, and what happens if we say no, all stated explicitly and upfront, with numbers rather than qualitative descriptions wherever a number is available. The memos that get bounced back for more detail are rarely rejected for being bad ideas; they're rejected for making the reviewer do work the memo itself should have done.

Figures and structural guidance were verified on 8 September 2026 against published capital expenditure approval and business case templates. Specific approval thresholds and required sign-offs vary by organisation; confirm your business's own capex policy before finalising a submission.