Cloud Scale Capacity Plan and Budget Allocation Request

Role: Director of Cloud Infrastructure and FinOps with expertise in hyper-growth SaaS architectures.

Context

• Workload / Cluster name: {{cloud_workload_name}}
• Expected utilization surge: {{projected_traffic_growth}}
• Current run-rate: {{current_monthly_spend}}
• Requested capital/operational increase: {{forecasted_budget_delta}}
• Outage or latency consequences: {{risk_of_underprovisioning}}
• FinOps efficiency measures: {{cost_optimisation_lever}}

Task

Draft a data-driven infrastructure capacity planning email to executive leadership justifying an increase of {{forecasted_budget_delta}} to support {{cloud_workload_name}} in response to {{projected_traffic_growth}}, while presenting cost controls via {{cost_optimisation_lever}}.

Method

1. State the immediate business trigger driving the need to resize {{cloud_workload_name}}.
2. Summarize current baseline run-rate using {{current_monthly_spend}} versus projected demand.
3. Break down the {{forecasted_budget_delta}} across compute, storage, and networking layers.
4. Frame {{risk_of_underprovisioning}} in terms of SLA breaches, customer churn, and latency degradation.
5. Present the offsetting efficiency gains provided by implementing {{cost_optimisation_lever}}.
6. Detail the provision timeline, including reserved instance commitments and procurement lead times.
7. Request explicit sign-off with a specific deadline to prevent provisioning bottlenecks.

Constraints

• MUST explicitly correlate the financial ask with system reliability and business growth.
• MUST NOT use overly abstract cloud terminology; keep metrics focused on cost, capacity, and risk.
• Tone MUST be analytically rigorous, financially disciplined, and proactive.
• Limit output length to under 380 words.

Output format

Subject Line: Budget Request & Capacity Plan: Scaling {{cloud_workload_name}} for {{projected_traffic_growth}}

1. Purpose & Financial Summary (1 concise paragraph comparing {{current_monthly_spend}} to {{forecasted_budget_delta}})
2. Capacity Drivers & Demand Forecast (2-3 bullet points on compute needs)
3. Risk Assessment of Inaction (2 bullet points detailing {{risk_of_underprovisioning}})
4. Cost Control Commitments (1 paragraph detailing {{cost_optimisation_lever}})
5. Approval Deadline & Sign-off Request (1 closing sentence)

Self-review

• Is {{forecasted_budget_delta}} justified with concrete traffic metrics?
• Does the memo balance capacity expansion with {{cost_optimisation_lever}} efficiency controls?
• Is the risk of under-provisioning clearly stated in terms of business impact?