Frame financial proposals around decision purpose, users, assumptions, alternatives, and recommendation needs.
A financial proposal is a decision document. It should help a specific user choose, approve, reject, defer, or modify a course of action. A proposal fails when it contains calculations but does not explain the purpose, audience, assumptions, alternatives, risks, and implementation steps.
In the Finance elective, proposal questions often ask whether the work prepared by management is useful. The answer should improve the proposal, not simply repeat its numbers.
Financial proposal work usually involves a project, financing plan, investment, acquisition, sale, restructuring, risk response, or working-capital decision.
| Proposal element | What to identify | Why it matters |
|---|---|---|
| Purpose | What decision is being made and what outcome is desired? | The analysis should answer the decision, not every finance question. |
| Audience | Owner, board, lender, investor, manager, committee, or buyer. | Detail, language, risk emphasis, and recommendation format change by user. |
| Alternatives | Status quo, proposed action, modified action, or competing option. | A proposal is weak if it evaluates only management’s preferred path. |
| Assumptions | Growth, cost, rate, volume, timing, valuation, tax, financing, and risk inputs. | Unsupported assumptions can drive a misleading recommendation. |
| Constraints | Cash, covenant, capacity, policy, deadline, risk tolerance, and governance. | A positive return may still be infeasible. |
| Sensitivity | Key variables that change the result. | Management needs to know what could make the proposal fail. |
| Implementation | Approval, financing, monitoring, controls, and accountability. | A recommendation is incomplete without execution steps. |
The proposal should move from decision to evidence to recommendation.
Different users need different emphasis.
| Audience | Primary concern | Proposal emphasis |
|---|---|---|
| Board | Strategic fit, risk, governance, long-term value, and accountability. | Recommendation, alternatives, risk, implementation, and monitoring. |
| Owner-manager | Cash flow, control, return, taxes, and practical feasibility. | Simple decision comparison, liquidity effect, and action steps. |
| Lender | Repayment capacity, collateral, covenants, and downside protection. | Cash forecast, debt service, security, sensitivity, and risk controls. |
| Operations manager | Capacity, staffing, process, quality, and timing. | Feasibility, resource needs, operational metrics, and rollout plan. |
| Investor or buyer | Value, growth, risk, diligence, and exit potential. | Assumptions, valuation support, risk-adjusted return, and evidence quality. |
| Public-sector or not-for-profit user | Mandate, service, funding, stewardship, and stakeholder impact. | Mission fit, budget effect, service risk, and accountability measures. |
A technical appendix may be useful, but the main proposal should be written for the decision maker.
Assumptions are inputs that require support. They are not proof that the proposal is good.
| Proposal statement | What it really is | How to assess it |
|---|---|---|
| Sales will grow by 12%. | Assumption. | Compare to capacity, contracts, market demand, and history. |
| Financing will be available at 6%. | Assumption and constraint. | Check lender terms, covenant headroom, collateral, and market rates. |
| The project is low risk. | Conclusion or unsupported preference. | Identify downside drivers, operational risk, and sensitivity. |
| Management prefers option A. | Preference. | Compare option A to objective, alternatives, and constraints. |
| Payback is under three years. | Metric. | Test cash timing, reinvestment, risk, and strategic fit. |
| The valuation is fair. | Conclusion. | Assess method, inputs, comparables, and evidence. |
A proposal is stronger when assumptions are visible, supportable, and tested.
A proposal should compare alternatives against the decision criteria. The status quo is often an alternative, even when management does not name it.
| Criterion | Why it matters |
|---|---|
| Value or return | Shows whether the option creates financial benefit. |
| Liquidity | Shows whether the entity can fund the option and survive downside timing. |
| Risk | Shows uncertainty, volatility, exposure, and downside. |
| Strategic fit | Shows whether the option supports the entity’s direction and mandate. |
| Feasibility | Shows whether people, systems, capacity, and approvals can support execution. |
| Stakeholder effect | Shows lender, owner, employee, customer, member, or public impact. |
| Flexibility | Shows whether the entity can adjust if assumptions fail. |
Do not rank options by one metric if another factor is decisive. A lower-return option may be better if it preserves liquidity or fits risk tolerance.
Common proposal weaknesses include:
| Weakness | Why it matters | Better correction |
|---|---|---|
| No clear decision | The analysis may be unfocused. | State the approval, rejection, choice, or funding decision. |
| No audience focus | The proposal may include irrelevant detail or omit critical risk. | Tailor the analysis to the user. |
| No alternative | Management may be anchoring on a preferred option. | Compare status quo and realistic alternatives. |
| Unsupported assumption | The result may be biased. | Add evidence, benchmark, contract support, or sensitivity. |
| No downside case | Risk tolerance cannot be assessed. | Add sensitivity, scenario, or contingency plan. |
| No implementation plan | A good option may fail in execution. | Name approvals, financing, timeline, owner, and monitoring metric. |
| No qualitative constraints | A positive calculation may ignore feasibility. | Add capacity, governance, stakeholder, and strategic constraints. |
The correction should be concrete. “Improve the proposal” is not enough.
Use this structure when asked to prepare or critique a proposal:
This structure makes the recommendation traceable from purpose to evidence.
| Pitfall | Correction |
|---|---|
| Writing the proposal before identifying the audience. | Tailor the level of detail and risk discussion to the decision maker. |
| Treating assumptions as facts. | Support them or test sensitivity. |
| Evaluating only the preferred option. | Compare alternatives, including status quo when relevant. |
| Ending with a calculation. | State the recommendation, conditions, and implementation steps. |
| Omitting qualitative constraints. | Include risk, liquidity, capacity, governance, and stakeholder effects. |
| Giving equal weight to every factor. | Rank the factor that should drive the decision. |