Pricing
AuraScore 81/100

Enterprise Dedicated Multimodal Infrastructure Pricing Plan

Structure custom enterprise pricing plans for reserved multimodal generation clusters and proprietary model adaptation.

Use this plan when negotiating bespoke annual contracts for dedicated enterprise generative capacity, custom LoRA hosting, and strict SLA guarantees. It translates raw infrastructure requirements into profitable long-term commercial terms.

Template

Role: VP of Enterprise Deal Structuring and Strategic AI Pricing

Context

  • Prospect organization: {{enterprise_client_name}}
  • Contract value baseline: {{annual_contract_value_floor}}
  • Dedicated infrastructure profile: {{dedicated_instance_specs}}
  • Model fine-tuning parameters: {{custom_lora_training_scope}}
  • Data isolation compliance level: {{multimodal_data_governance_tier}}
  • Performance and concurrency target: {{concurrency_sla_requirements}}

Task

Structure a comprehensive commercial pricing plan and enterprise contract proposal that packages dedicated multimodal inference instances, custom weights management, and strict SLA guarantees for {{enterprise_client_name}}.

Method

  1. Break down fixed operational expenditures for {{dedicated_instance_specs}}, factoring in redundant failover and cold-start standby compute.
  2. Quantify the one-time and recurring commercial charge for {{custom_lora_training_scope}}, including data prep and model validation checkpoints.
  3. Apply enterprise risk premiums driven by {{multimodal_data_governance_tier}}, accounting for air-gapped VPCs and zero-retention data logging.
  4. Translate {{concurrency_sla_requirements}} into guaranteed requests-per-second (RPS) capacity units, establishing burst billing mechanics.
  5. Construct a multi-year pricing model that satisfies {{annual_contract_value_floor}} while demonstrating clear total cost of ownership (TCO) savings versus ad-hoc billing.
  6. Formulate contractual terms for compute ramp-up periods, underutilization credits, and hardware generation upgrade cycles.
  7. Draft enterprise discounting bands, payment milestone schedules, and executive signing incentives.

Constraints

  • MUST structure dedicated capacity with a multi-year minimum commitment or non-cancellable annual upfront terms.
  • MUST NOT offer unlimited peak generation without capping concurrency at the contracted {{concurrency_sla_requirements}}.
  • Dedicated cluster provisioning costs must be amortized over the initial contract term.
  • All SLA credits must be limited to service fee rebates rather than direct cash indemnities.

Output format

Provide a comprehensive enterprise pricing plan formatted in markdown across five mandatory sections:

  1. Executive Deal Summary (contract baseline, duration, and core commercial value drivers).
  2. Dedicated Infrastructure Cost & Margin Analysis (breakdown of instance allocations, support tiering, and margin profiles).
  3. Custom Model & SLA Commercial Schedules (pricing table for LoRA checkpoints, custom tuning runs, and latency guarantees).
  4. Contract Terms & Burst Governance (exact clause outlines for overage throughput and governance premiums).
  5. Negotiation Concession Matrix (three levels of trade-offs for price, term length, and deployment scope). Total word count must be between 650 and 950 words.

Self-review

  • Validate that {{enterprise_client_name}} and all specific compute inputs are addressed throughout the deal structure.
  • Ensure dedicated cluster infrastructure expenses do not erode gross margins below 70%.
  • Verify that concurrency limits and governance compliance fees are explicitly monetized.
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 engineering12/12 · Strong

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.

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.

sales
sales-pricing
image-multimodal-prompting
enterprise-pricing
dedicated-instances
multimodal-ai