Marketplace ops
AuraScore 81/100

ISV Cloud Marketplace Listing and Metering Operations Framework

Build a clear operational framework for private offers, metered billing, and co-sell fulfillment across cloud marketplaces.

Deploy this framework when transitioning software products onto hyperscaler marketplaces like AWS or Azure. It aligns finance, operations, and technical fulfillment workflows.

Template

Role: Cloud Marketplace Operations Principal specializing in hyperscaler ISV co-sell and transactional fulfillment.

Context

  • Target hyperscaler: {{cloud_provider}}
  • Product package: {{product_tier}}
  • Commercial structure: {{pricing_model}}
  • Revenue settlement cadence: {{billing_frequency}}
  • Deal routing ceiling: {{deal_size_threshold}}
  • Distribution channel: {{channel_partner}}

Task

Construct an operational framework that governs private offer generation, license provisioning, metered billing telemetry, and revenue reconciliation for cloud marketplace transactions.

Method

  1. Define private offer creation parameters, approval hierarchies, and custom legal amendment routing above {{deal_size_threshold}}.
  2. Outline entitlement ingestion and automated customer account provisioning workflows upon offer acceptance.
  3. Map usage data pipeline architecture from the software instance to {{cloud_provider}} metering APIs under {{pricing_model}}.
  4. Establish error-handling and replay mechanisms for dropped or delayed metering events.
  5. Align disbursement schedules and finance ledger synchronization based on {{billing_frequency}}.
  6. Detail operational touchpoints for co-selling credit alignment involving {{channel_partner}}.
  7. Define key performance indicators for fulfillment speed, metering accuracy, and disbursement variance.

Constraints

  • MUST maintain separation between public listing self-service flows and custom private offer flows.
  • MUST NOT introduce manual intervention for routine telemetry ingestion.
  • All workflows MUST account for the role of {{channel_partner}} in offer execution.
  • Total framework must remain operationally practical for mid-sized operations teams.

Output format

Deliver the operational framework across 4 distinct sections:

  1. Offer Architecture & Approval Rules: Standardized terms and threshold gates.
  2. Provisioning & Entitlement Flow: Step-by-step technical fulfillment upon purchase.
  3. Metering & Telemetry Pipeline: Integration mechanics and error recovery.
  4. Revenue Operations & Audit: Disbursement reconciliation and reporting cadences. Maintain a direct, professional tone under 650 words.

Self-review

  • Confirm every variable ({{cloud_provider}}, {{pricing_model}}, {{product_tier}}, {{billing_frequency}}, {{deal_size_threshold}}, {{channel_partner}}) is explicitly addressed.
  • Check that metering failure and recovery steps are clearly defined.
  • Verify output section names match the exact required contract.
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
technology-software
marketplace-ops
cloud-marketplaces
metering-operations