Business proposal — problem, solution, ROI

A business proposal is the document that converts an idea into a decision. Unlike a report (which describes what is) or an opinion essay (which defends a stance), a proposal asks for something specific — budget, headcount, time, a contract, a partnership — and gives the decision-maker the information they need to say yes. At C1 in an American business environment, you should be able to write proposals that get read by executives and approved by committees.

The C1 proposal has a distinctive shape because it is engineered for the reader’s decision process. Executives reading proposals are scanning for four answers: What problem are you solving? What are you proposing? What will it cost? What is the upside? If a proposal fails to answer those in the first page, it does not get to page two. American business writing culture rewards brevity, specificity, and ROI framing — all three are C1-level skills.

This lesson walks through the seven sections of a proposal, the ROI framing conventions, and a full annotated 420-word proposal for a real business decision.

Structure — seven sections of a proposal

1. Executive summary (~80w) — the entire proposal compressed. Problem, solution, cost, benefit, ask, in four sentences.
2. Problem statement (~70w) — what is wrong, in numbers; what it is costing now.
3. Proposed solution (~80w) — what specifically you propose to do.
4. Benefits / ROI (~80w) — the upside, quantified where possible.
5. Costs and timeline (~60w) — what it takes, when it happens.
6. Risks and mitigation (~50w) — what could go wrong, what protects against it.
7. The ask (~30w) — the explicit decision you need, by when.

Word target: 380-450 for the body. Appendices for full financial models, vendor quotes, supporting research.

Step-by-step craft

1. The problem statement — quantify the cost of inaction

The C1 problem statement is the difference between we have a problem and we are losing $400,000 a year to this problem. Executives respond to quantified problems. The framework:

• What is happening (specific, measurable)
• What it is costing (dollars, time, opportunity)
• What happens if nothing changes (trajectory)

Example: Our current onboarding process takes new engineers 11 weeks to reach productive capacity. Across 18 hires last year, this represented an estimated $2.4M in lost productivity. If the engineering team grows at the planned rate, this cost will exceed$4M by FY2027.

This kind of opening earns the next paragraph. A vague Our onboarding could be better does not.

2. The solution — specific enough to be evaluated

The solution section names what you propose, not in vague terms but in specific, evaluable terms. Bad: We propose to improve onboarding. Good: We propose to introduce a structured eight-week onboarding program with named mentors, weekly milestone reviews, and a shared internal documentation hub, replacing the current self-directed model.

The specificity matters because the decision-maker will mentally cost-model what you propose. If they cannot picture the solution concretely, they cannot evaluate it.

3. Benefits and ROI — quantify everything quantifiable

The C1 benefits section converts the proposal into ROI language. The basic framework:

• Direct savings: dollars saved per year.
• Indirect savings: time saved, opportunities unlocked.
• Strategic value: harder to quantify, but named — retention, brand, competitive position.

Worked example: The structured program is projected to reduce time-to-productivity from 11 weeks to 6 weeks. Across an expected 20 hires in FY2026, this represents an estimated $1.6M in recovered productivity, against a program cost of$180,000. Net first-year benefit: $1.4M. Payback period: 2.1 months.

If you cannot quantify a benefit, name it explicitly as strategic rather than financial: In addition, we expect retention benefits and a stronger employer brand among engineering candidates, though we have not modeled these.

4. Costs and timeline — concrete, audited

The costs section is where ethos gets earned or lost. Hand-wavy budgets (roughly $200K) signal that the proposer has not done the work. C1 costs are itemized:

The timeline section names milestones and dates: Q1: program design and mentor selection. Q2: pilot with five hires. Q3: full rollout. Q4: 12-month review.

5. Risks and mitigation — show your work

A C1 proposal does not pretend there are no risks. It names the main risks and shows how each is addressed. Three is the right number — fewer reads as denial; more reads as panic.

Example: Risk 1: mentor burden may reduce mentor productivity. Mitigation: each mentor receives a 10% time allocation and a $2,000 stipend. Risk 2: pilot may not generalize. Mitigation: pilot is structured to match the demographic and role mix of the planned full cohort. Risk 3: documentation platform may underperform. Mitigation: 90-day evaluation period with exit clause built into the SaaS contract.

6. The ask — explicit and decidable

The proposal ends with the ask, named explicitly. We request approval of a $180,000 FY2026 budget allocation for the structured onboarding program, with hiring authorization for one 0.5 FTE program manager. We seek a decision by January 31, 2026, in order to begin Q1 program design.

The ask is the sentence the executive will action on. Vague asks (we hope you will consider this) do not get decided on; specific asks do.

7. Executive summary written last

The executive summary, like in a formal report, is written last. It is the entire proposal compressed into four sentences: problem, solution, ROI, ask. Our onboarding process is costing $2.4M a year in lost productivity. We propose an eight-week structured program with named mentors and milestone reviews. The projected first-year ROI is$1.4M against $180K in costs. We request budget approval and one 0.5 FTE allocation by January 31, 2026.

If the executive reads only the summary, they have what they need to decide.

Full model proposal — 420 words, annotated

Proposal: Structured Engineering Onboarding Program — FY2026

Executive summary

Our current engineering onboarding process is costing an estimated $2.4M per year in lost productivity, a figure projected to exceed$4M by FY2027 at planned hiring rates. We propose a structured eight-week onboarding program with named mentors, weekly milestone reviews, and a shared documentation hub. Projected first-year benefit is $1.6M against$180,000 in costs, for net ROI of $1.4M and a payback period of 2.1 months. We request budget approval and one 0.5 FTE program manager allocation by January 31, 2026.

Problem statement

New engineering hires currently reach productive capacity in an average of 11 weeks, against an industry benchmark of 6 weeks for comparable roles. Across 18 hires in FY2025, this lag represented an estimated $2.4M in lost productivity, calculated as five weeks of additional ramp time at a fully-loaded average cost of$26,700 per engineer per week. At the planned FY2026 hiring rate of 20 engineers, the cost will rise to approximately $2.7M; by FY2027,$4M.

Proposed solution

We propose a structured eight-week onboarding program comprising: (1) a named mentor for each new hire, with a 10% time allocation and a $2,000 stipend; (2) weekly milestone reviews with manager and mentor; (3) a shared internal documentation hub for systems, processes, and team norms; (4) a final-week capstone project with engineering leadership review. This replaces the current self-directed model.

Benefits and ROI

The program is projected to reduce time-to-productivity from 11 weeks to 6 weeks. Across 20 planned hires in FY2026, this represents recovered productivity worth approximately $1.6M (5 weeks x$26,700 x 20 hires x adjusted utilization). Net first-year benefit, after $180,000 in program costs, is$1.4M. Payback period: 2.1 months. Strategic benefits — retention, employer brand — are expected but not modeled.

Costs and timeline

Total Year 1 cost: $180,000, comprising program manager (0.5 FTE,$90,000), mentor stipends ($40,000), documentation platform ($24,000), onboarding materials ($26,000). Timeline: Q1 design and mentor selection; Q2 pilot with five hires; Q3 full rollout; Q4 12-month review.

Risks and mitigation

Risk 1: mentor productivity loss. Mitigation: 10% time allocation and stipend. Risk 2: pilot may not generalize. Mitigation: pilot cohort matched on role and demographic mix to planned full cohort. Risk 3: documentation platform underperformance. Mitigation: 90-day evaluation with exit clause in the SaaS contract.

Ask

We request approval of a $180,000 FY2026 budget allocation and authorization for one 0.5 FTE program manager position. Decision needed by January 31, 2026, to begin Q1 program design on schedule.

Annotations: executive summary compresses problem, solution, ROI, and ask in four sentences. Problem statement quantifies cost and trajectory. Solution is itemized and specific. Benefits section has explicit ROI math. Costs are itemized; timeline is dated. Risks are named with mitigations. The ask is decidable.

Common pitfalls

• Vague problem statements — without quantified cost, the problem feels optional.
• Hand-wavy costs — roughly $200K signals incomplete work; itemize.
• Benefits without ROI math — name the dollars where you can; flag the strategic-only items honestly.
• No mitigation for stated risks — naming risks without mitigations creates more anxiety than confidence.
• Asks that are not decidable — we hope to be considered gets shelved; we request approval of $X by Y gets decided.
• Executive summary written first — produces a summary that drifts from the body.

Connectors and phrases bank

Problem framing: Our current [process] is costing an estimated $X per year…, Across [period], this represents…, At planned [rate], the cost will rise to…, The trajectory is not sustainable.

Solution framing: We propose [specific intervention] comprising: (1)…, (2)…, (3)…, This replaces the current [model] with…, The intervention has [N] components, each addressing…

ROI framing: Projected first-year benefit is $X against$Y in costs., Payback period: N months., Net first-year benefit: $X., Strategic benefits are expected but not modeled.

Risk framing: Risk N: [risk]. Mitigation: [protection]., The main risk to delivery is…; this is addressed by…, In the unlikely event of [risk], the fallback is…

The ask: We request approval of [specific amount] and authorization for [specific resource], by [date]., Decision needed by [date] to begin [milestone] on schedule.

Proposal subgenres

Different business contexts call for different proposal shapes:

The seven-section model in this lesson is the universal core; subgenres extend it. A board-level proposal adds governance and strategic-fit sections; an RFP response adds capability and references; a grant proposal adds an evaluation plan.

The ROI calculation — showing your work

C1 ROI sections show the math. A figure presented without its derivation is harder to defend. The convention:

A reader who challenges the ROI must challenge a specific assumption. A reader who agrees with the assumptions agrees with the conclusion. This is how persuasion-by-math works at C1 — every number is checkable.

When the proposal goes to committee

Most material business proposals are reviewed by committees, not single deciders. The committee dynamic shapes how you write:

• Different members have different concerns — the CFO wants ROI; the COO wants operational risk; the CEO wants strategic fit; the CHRO wants people impact. The proposal must serve each.
• One veto kills the proposal — even if six members support it, a single skeptic on the steering committee can block it. Address the most skeptical concern explicitly.
• The meeting is short — committees rarely spend more than 15 minutes per item. The proposal must be skim-readable; the discussion will focus on two or three issues, not the whole thing.
• Sponsor pre-alignment matters more than the document. A proposal that has been pre-walked with each committee member before the meeting passes. One that arrives cold fails.

The discipline: write the proposal as if each committee member will read only the sections relevant to their concern. The executive summary serves all of them; the costs section serves the CFO; the risks section serves the COO; the timeline serves operations.

Sensitivity analysis — handling skeptical readers

A C1 proposal anticipates the question what if your assumptions are wrong? The sensitivity-analysis move:

• Identify the two or three most consequential assumptions.
• Show what happens to the ROI if each assumption is wrong by 25%.
• Demonstrate that the proposal still justifies itself in the most-likely downside case.

Worked example for the onboarding program:

The ROI calculation assumes a reduction in ramp time from 11 weeks to 6 weeks. If actual reduction is only 50% of the projected benefit — i.e., 11 weeks reduced to 8.5 weeks — annual recovered productivity is $800K against$180K in program costs, for net first-year benefit of $620K. The program clears its costs in any realistic downside scenario; the question is the size of the upside, not whether the upside exists.

The sensitivity move converts a skeptical reader from what if your numbers are wrong to even if your numbers are wrong, the case still holds.

Common Russian-speaker writing mistakes

1. Over-deferent closings — We humbly hope you will favorably consider our proposal calques Russian formal business politeness. American business proposals close with the ask, not with deference: We request approval by [date].

2. Conditional in the ask — We would request approval if possible. The conditional sounds tentative and weakens the proposal. Use the simple present: We request approval.

3. Calque в случае положительного решения — translated as In the case of a positive decision. Sounds Soviet. Natural C1: If approved, [next step]. Or assume approval and describe the plan: On approval, we begin Q1 design.

4. False friend perspective — Russian перспектива means prospect / outlook. English perspective means viewpoint. We see good perspectives for the project should be We see strong prospects for the project.

5. Over-formal to undertake the realization of — calque on осуществить реализацию. Replace with the verb: We will implement… or simply We will…

6. Vague significant, considerable, substantial — Russian business writing tolerates vague intensifiers; American C1 prefers numbers. Significant cost reduction should be $1.4M cost reduction.

7. Date format — US format is January 31, 2026 (or 1/31/2026). European 31 January 2026 signals non-US; ambiguous 1/31 vs 31/1 causes misreadings in international contexts.

8. Calque с целью — translated as with the aim/goal of. Often unnecessary in English. We propose this with the goal of reducing time-to-productivity should be We propose this to reduce time-to-productivity.

Summary

• Seven sections: executive summary, problem, solution, benefits/ROI, costs/timeline, risks/mitigation, the ask.
• Quantify the problem in dollars or time; the cost of inaction earns the next paragraph.
• The solution is specific enough to be evaluated, not vague aspirations.
• ROI framing converts the proposal into the decision-maker’s language; payback period is the executive metric.
• Risks are named with mitigations; three is the right count.
• The ask is decidable — specific amount, specific resource, specific date.
• Russian speakers should especially watch over-deferent closings, conditional in the ask, and vague intensifiers in place of numbers.

Phasing — when to propose Big-Bang vs Phased

Proposals come in two execution shapes:

• Big-Bang: implement the whole solution at once. We will roll out the new program across all engineering hires starting Q3. Lower coordination cost; higher risk; faster to full value.
• Phased / Pilot-first: implement on a subset, measure, then expand. We will pilot with five hires in Q2, evaluate at the twelve-week mark, expand in Q3 if results match projections. Higher coordination cost; lower risk; slower to full value.

The C1 choice depends on three factors:

• Reversibility: irreversible changes (hiring, infrastructure investment) favor phased; reversible changes (process tweaks, tool trials) tolerate Big-Bang.
• Evidence base: well-evidenced interventions tolerate Big-Bang; speculative ones favor phased.
• Political risk: high-visibility initiatives favor phased — early wins build the political coalition for expansion.

A C1 proposal explicitly names the phasing choice and defends it. We propose a phased rollout because the productivity-recovery model has not been validated on our specific role mix; a Q2 pilot generates the data that justifies a Q3 expansion. This kind of explicit phasing rationale is what high-band proposals do.

Tone in business proposals — confident but not selling

A C1 business proposal reads as confident-but-not-selling. The line is subtle:

• Selling tone uses words like exciting, transformative, game-changing, innovative. These signal marketing rather than analysis and burn executive trust.
• Confident tone uses words like substantial, measurable, projected, defensible. These signal that the proposer has done the work.

Compare:

• Selling: This exciting new program will transform our onboarding into a game-changing competitive advantage that delivers unprecedented value.
• Confident: The program is projected to reduce time-to-productivity from 11 weeks to 6 weeks, recovering an estimated $1.4M in net first-year value.

The selling version sounds like a vendor pitch; the confident version sounds like an internal analyst who has actually run the numbers. Executives respond to the second.

Two common selling-tone failures at C1:

• Adjective inflation: stacking innovative, cutting-edge, transformative signals that the case lacks substance. One adjective is fine; three signal panic.
• Future-tense overuse: This will deliver, this will transform, this will enable sounds prophetic. Mix in present tense and conditional: The projected benefit is X; if executed as planned, the program delivers Y.

Pre-submission proposal checklist

Before submitting a business proposal:

• The ask is decidable — specific amount, specific resource, specific date.
• The executive summary works as a standalone four-sentence compression.
• The problem is quantified in dollars or time, with a trajectory.
• The solution is itemized enough to be evaluated, not aspirational.
• Costs are itemized; no hand-wavy round numbers.
• Benefits include ROI math; payback period is calculated.
• Three risks are named with concrete mitigations.
• Sensitivity analysis shows the proposal survives plausible downsides.
• Each committee member’s concern is addressed in the relevant section.
• The proposal is skim-readable for a 15-minute committee discussion.

Next lesson: Academic five-paragraph essay — PEEL paragraphs and the hook-thesis-conclusion arc.