Finance & models
AuraScore 89/100

Generative Studio GPU Infrastructure CapEx Allocation Specification

Evaluate on-premise GPU procurement against hyperscaler reserved capacity for multimodal creative studios.

Deploy this specification when structuring high-capital infrastructure decisions for visual generation pipelines. It provides an institutional financial model comparing owned cluster depreciation against managed cloud commitments.

Template

Role: Principal Financial Architect specializing in high-performance computing capital expenditure and generative media infrastructure.

Context

  • Studio Operational Scale: {{studio_tier}}
  • Active Generation Pipeline: {{rendering_pipeline_type}}
  • Infrastructure Strategy: {{compute_provisioning_model}}
  • Asset Depreciation Window: {{depreciation_period_months}}
  • Facility Power & PUE Overhead: {{annual_power_pue_cost}}
  • Target Render Output: {{expected_render_throughput}}

Task

Draft a capital expenditure allocation specification that contrasts on-premise hardware acquisition against cloud reserved instances, detailing amortization schedules, total cost of ownership (TCO), and internal rate of return (IRR) for multimodal image generation clusters.

Method

  1. Establish total upfront capital requirements for bare-metal compute nodes, high-speed interconnects, and storage fabric based on {{compute_provisioning_model}}.
  2. Calculate straight-line and accelerated depreciation schedules across {{depreciation_period_months}} for owned hardware assets.
  3. Integrate {{annual_power_pue_cost}}, cooling, colocation rack space, and maintenance warranties into operationalized physical TCO.
  4. Build an equivalence baseline for hyperscaler reserved instance commitments delivering {{expected_render_throughput}} under {{rendering_pipeline_type}}.
  5. Model residual equipment salvage value at terminal lifecycle state across standard secondary market decay curves.
  6. Compute Net Present Value (NPV) and Internal Rate of Return (IRR) using an 8% cost of capital benchmark.
  7. Detail financial trigger points that justify migration from cloud-first to owned physical clusters for {{studio_tier}}.
  8. Document liquidity risk, technology obsolescence exposure, and hedge provisions against next-generation GPU releases.

Constraints

  • The financial model MUST enforce strict GAAP/IFRS capital asset classification criteria.
  • Calculations MUST include enterprise facility overhead and colocation costs rather than raw compute alone.
  • MUST NOT use speculative secondary hardware residual values exceeding 20% of original equipment cost.
  • Breakeven timeline MUST be clearly articulated in exact operating months.

Output format

  1. Capital Expenditure Summary (formal valuation metadata block)
  2. Comparative TCO Matrix (side-by-side on-prem vs cloud multi-year breakdown)
  3. Amortization & Depreciation Schedule (tabular month-by-month outline)
  4. Risk Mitigation & Residual Value Governance (structured policy rules) Target word count: between 750 and 950 words.

Self-review

  • Confirm that the depreciation period in {{depreciation_period_months}} directly dictates the amortization schedule timeline.
  • Verify that power and data center metrics in {{annual_power_pue_cost}} are fully burdened into operational totals.
  • Check that the financial delta between {{compute_provisioning_model}} options contains no unallocated capital gaps.
AuraScore breakdown
89/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 engineering12/12 · Strong

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

Output specification14/14 · Strong

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.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

business-strategy
business-finance
image-multimodal-prompting
capex-allocation
gpu-cluster
infrastructure-finance