Discovery
AuraScore 79/100

Multimodal Prompting Economic Impact Analysis

Presales discovery analysis modeling unit economics, compute trade-offs, and labor productivity gains for generative visual assets.

Use this template during business value discovery to model financial returns, agency cost reduction, and inference economics. It translates raw generation volume into hard ROI metrics for executive buyers.

Template

Role: Lead Presales Value Engineer specializing in generative AI unit economics and multimodal infrastructure optimization.

Context

  • Target Client: {{client_name}}
  • Current Creative Spend: {{annual_creative_spend}}
  • External Agency Overhead: {{agency_contract_overhead}}
  • Chosen Inference Tier: {{model_inference_tier}}
  • Quality Review Threshold: {{human_review_threshold}}
  • Expected Scaling Target: {{projected_content_scale}}

Task

Produce an advanced economic discovery analysis that models the total cost of ownership, operational savings, and labor reallocation impact of transitioning to enterprise multimodal image generation.

Method

  1. Baseline the client's current visual asset creation unit cost using {{annual_creative_spend}} and {{agency_contract_overhead}}.
  2. Project future generation volumes based on {{projected_content_scale}} across varying visual fidelity bands.
  3. Model inference consumption costs using {{model_inference_tier}}, accounting for base image generation, prompt expansion tokens, and upscaling compute.
  4. Calculate human-in-the-loop validation overhead applying {{human_review_threshold}} to model realistic designer curation hours.
  5. Compute net cost per finished asset under the proposed multimodal platform versus the legacy manual creation baseline.
  6. Structure a 3-year financial trajectory comparing baseline run-rates against the optimized generative infrastructure.
  7. Identify non-linear productivity multipliers such as rapid localization, personalized variants, and abbreviated campaign cycles.

Constraints

  • MUST explicitly present both conservative and aggressive scenario estimates.
  • MUST calculate the exact estimated cost per generated asset across both compute and human validation.
  • Do not include generic marketing metrics; focus entirely on financial, unit-economic, and labor capacity metrics.
  • Limit total analysis to under 800 words.

Output format

Provide the economic analysis organized into four sections:

  1. Unit Economics Baseline vs. Generative Model (comparative breakdown covering cost-per-asset, speed-to-market, and compute fees).
  2. 3-Year Total Cost of Ownership Projection (summary financial breakdown detailing software licensing, inference, and internal labor).
  3. Capacity Reallocation & Productivity Multipliers (detailed narrative explaining how designer hours shift from production to creative direction).
  4. Value Realization Roadmap (3-step discovery milestone plan to prove economic assumptions in a paid pilot).

Self-review

  • Confirm all context variables (e.g. {{agency_contract_overhead}}, {{model_inference_tier}}) are used in mathematical calculations.
  • Ensure the comparison covers both compute cost and human validation cost as specified.
  • Check that conservative versus aggressive scenarios are clearly distinguished in the text.
AuraScore breakdown
79/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 engineering8/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-discovery
image-multimodal-prompting
roi-analysis
unit-economics
value-engineering