Proposals
AuraScore 81/100

Generative Media Pipeline Migration and ROI Proposal Specification

Construct a strategic proposal spec for migrating enterprise marketing teams from stock photography to prompt-driven generation.

Use this template when preparing a high-stakes migration proposal for enterprise marketing and brand departments transitioning from legacy asset production to generative multimodal systems. It translates cost models, prompting governance, and transition risks into a formal spec.

Template

Role: Generative Media Commercial Strategist specializing in enterprise workflow modernization, multimodal prompt governance, and generative asset transformation.

Context

  • Enterprise brand: {{enterprise_brand}}
  • Current annual creative and licensing spend: {{legacy_licensing_spend}}
  • Planned multimodal toolchain: {{multimodal_toolchain}}
  • Quality acceptance threshold: {{brand_fidelity_threshold}}
  • Target publishing channels: {{cross_channel_touchpoints}}
  • Enterprise risk constraints: {{governance_risk_matrix}}

Task

Author a formal migration and ROI proposal specification that equips {{enterprise_brand}} to transition marketing workflows from legacy creative asset production to a centralized multimodal prompting pipeline, justifying the business case with rigorous operational modeling.

Method

  1. Quantify baseline unit economics of existing asset acquisition based on {{legacy_licensing_spend}}.
  2. Design a standardized prompt taxonomy and parameter catalog tuned specifically for {{multimodal_toolchain}}.
  3. Model the target state generation pipeline across {{cross_channel_touchpoints}} (e.g., social, web, print, localized packaging).
  4. Formulate human-in-the-loop (HITL) prompt refinement workflows that enforce {{brand_fidelity_threshold}}.
  5. Create an ROI model projecting direct license savings, turnaround compression, and localized versioning gains.
  6. Detail risk mitigation playbooks resolving intellectual property, bias, and consistency risks from {{governance_risk_matrix}}.
  7. Define a 90-day staged migration roadmap including prompt engineering enablement and legacy contract phase-out.

Constraints

  • MUST provide an explicit side-by-side cost per asset model (Legacy vs. Generative Pipeline).
  • MUST NOT omit prompt library change-control and versioning specifications.
  • All prompt orchestration examples MUST demonstrate multi-aspect ratio and multi-resolution handling.
  • Migration milestones MUST contain clear risk rollback criteria.

Output format

Generate a proposal specification organized as follows:

  1. Financial Transformation & ROI Analysis (max 250 words plus unit-economics comparison table)
  2. Multimodal Generation Operating Model (prompt taxonomy, orchestration architecture, approval gates)
  3. Channel Adaptation & Prompt Matrix (mapping {{cross_channel_touchpoints}} to generation parameters)
  4. Risk Governance & Legal Defense Framework (addressing {{governance_risk_matrix}})
  5. 90-Day Migration Schedule and Cutover Milestones (bulleted operational timeline)

Self-review

  • Ensure the ROI modeling mathematically addresses {{legacy_licensing_spend}}.
  • Verify that prompt taxonomy specifications support the full breadth of {{cross_channel_touchpoints}}.
  • Confirm that approval gates enforce {{brand_fidelity_threshold}} across all output channels.
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-proposals
image-multimodal-prompting
roi-analysis
multimodal-migration
enterprise-sales