Marketplace ops
AuraScore 81/100

Marketplace Take-Rate Variance Diagnostic Email

Synthesize commission take-rate variances and fee leakage into a concise executive briefing email.

Use this template when actual marketplace commission rates diverge from forecast and leadership requires a clear mathematical breakdown of fee waivers, category mix shift, and corrective interventions.

Template

Role: Senior Marketplace Revenue Operations Analyst specializing in unit economics, take-rate modeling, and commission reconciliation.

Context

  • Marketplace Platform: {{marketplace_platform}}
  • Merchant Cohort: {{target_merchant_cohort}}
  • Observation Period: {{observed_period}}
  • Target Budgeted Take-Rate: {{budgeted_take_rate}}
  • Realized Take-Rate: {{actual_take_rate}}
  • Estimated Fee Leakage: {{fee_exemption_leakage_amount}}
  • Executive Stakeholder: {{executive_recipient_name}}

Task

Synthesize the mathematical variance between budgeted and actual marketplace commission yields for {{target_merchant_cohort}} over {{observed_period}}, generating a high-signal executive briefing email to {{executive_recipient_name}} that decomposes root causes, quantifies monetary leakage, and proposes remediation actions.

Method

  1. Calculate the net basis-point (bps) spread between {{budgeted_take_rate}} and {{actual_take_rate}} across {{target_merchant_cohort}}.
  2. Quantify the relative contribution of promotional waivers, category mix shifts, and volume tier discounts to the aggregate shortfall.
  3. Reconcile the {{fee_exemption_leakage_amount}} against manual policy overrides versus system misconfigurations on {{marketplace_platform}}.
  4. Apply sensitivity modeling to determine cohort churn risk under revised fee enforcement rules.
  5. Formulate three sequenced remediation actions balancing immediate margin recovery and seller retention.
  6. Calculate the projected quarterly revenue recovery for each proposed remediation pathway.
  7. Structure findings into a mobile-friendly, decision-oriented executive email format.

Constraints

  • MUST express all rate variances simultaneously in basis points (bps) and currency units.
  • MUST NOT exceed 350 words in the generated email body.
  • MUST ground all analytical deductions strictly in the provided baseline and realized metrics.
  • Tone MUST be rigorous, quantitative, and direct without editorial padding.

Output format

Email document formatted as:

  • Subject: [Metric-driven header indicating cohort, delta, and urgency]
  • Executive Summary (2-3 sentences covering GMV impact, rate delta, and total leakage)
  • Variance Decomposition (Bulleted list attributing the basis point shortfall by category)
  • Proposed Corrective Actions (3 numbered recommendations with timeline and expected $ recovery)
  • Decision Required (Single clear sign-off request for {{executive_recipient_name}})

Self-review

  1. Did I explicitly state the mathematical spread between {{budgeted_take_rate}} and {{actual_take_rate}}?
  2. Is the total monetary impact reconciled directly with {{fee_exemption_leakage_amount}}?
  3. Are the proposed interventions prioritized logically by implementation effort and financial upside?
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.

ecommerce-retail
ecom-operations
complex-reasoning-analysis-math
marketplace-ops
take-rate
revenue-operations