Proposals
AuraScore 81/100

Quantitative Deal Architecture and Financial Model Specification

Build a rigorous mathematical proposal model with ROI projections, cash flow schedules, and sensitivity tables.

Use this template when structuring high-value enterprise sales proposals requiring formal financial justification. It guides the quantitative derivation of net present value, payback milestones, and risk-adjusted pricing tiers.

Template

Role: Principal Commercial Modeler and Pricing Strategist with 15 years of experience in enterprise deal structuring.

Context

  • Client Name: {{client_name}}
  • Contract Term: {{contract_term_years}} years
  • Existing Baseline Costs: {{baseline_operating_costs}}
  • Proposed Solution Pricing: {{proposed_solution_costs}}
  • Target Efficiency Gains: {{projected_efficiency_gains}}
  • Cost of Capital / Discount Rate: {{discount_rate}}

Task

Generate a comprehensive financial architecture specification for the commercial section of an enterprise proposal, establishing definitive mathematical proofs for return on investment, net present value, and tiered cash flow schedules.

Method

  1. Establish the baseline run-rate cost model for {{client_name}} across the full {{contract_term_years}} horizon without intervention.
  2. Model the phased deployment cost curve using {{proposed_solution_costs}}, factoring in one-time implementation and recurring operational expenses.
  3. Compute gross recurring savings by applying {{projected_efficiency_gains}} against {{baseline_operating_costs}}.
  4. Calculate Net Present Value (NPV) and Internal Rate of Return (IRR) across {{contract_term_years}} using {{discount_rate}}.
  5. Conduct a two-variable sensitivity analysis showing ROI variations under -20%, base, and +20% efficiency realization scenarios.
  6. Determine the exact payback period in months where cumulative net cash flow turns positive.
  7. Structure risk-adjusted commercial payment tiers (e.g., milestone-based vs. consumption-based) tied to performance gates.

Constraints

  • Every financial formula MUST explicitly show input variables and calculation methodology.
  • MUST NOT introduce arbitrary discounting without an explicit mathematical justification.
  • All cash flow tables must reconcile to within 0.01% across yearly sums.
  • Must separate capital expenditure (CapEx) from operational expenditure (OpEx) explicitly.

Output format

  • Section 1: Executive Financial Summary (Max 250 words)
  • Section 2: Mathematical Assumptions & Baseline Model
  • Section 3: Multi-Year Cash Flow & NPV/IRR Schedule (Markdown Table)
  • Section 4: Sensitivity Matrix (-20%, Nominal, +20% Scenarios)
  • Section 5: Commercial Payment Terms Specification

Self-review

  • Confirm all formulas use {{discount_rate}} correctly in discounted cash flow lines.
  • Check that cumulative savings strictly derive from {{projected_efficiency_gains}} and {{baseline_operating_costs}}.
  • Verify no placeholders or unverified assumptions remain in the financial schedule.
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering10/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness5/5 · Strong

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

sales
sales-proposals
complex-reasoning-analysis-math
financial-modeling
proposals
roi-analysis