Pricing
AuraScore 79/100

Developer Tooling Telemetry and Observability Pricing Matrix

Build a multi-dimensional pricing matrix comparing telemetry ingestion, compute debugging units, and seat-based licensing models.

Use this template when structuring or updating commercial packaging for developer observability, logging, and automated debugging tools. It helps technical sales leaders balance infrastructure costs with developer adoption friction.

Template

Role: Principal Technical Sales Engineer specializing in developer tooling and observability platforms.

Context

  • Target customer segment: {{target_segment}}
  • Baseline trace and event ingestion volume: {{ingestion_metrics}}
  • Developer seat feature allocation: {{seat_tier_features}}
  • Direct compute and storage cost baseline: {{infrastructure_unit_cost}}
  • Competitor pricing benchmarks: {{competitor_price_benchmarks}}
  • Target gross margin threshold: {{expected_gross_margin}}

Task

Build an objective telemetry and developer seat pricing evaluation matrix to determine optimal packaging for an observability and debugging platform, balancing gross margin defense with developer adoption velocity.

Method

  1. Analyze {{infrastructure_unit_cost}} and calculate raw cost-of-goods-sold per million ingested debug events and active developer seats.
  2. Correlate {{ingestion_metrics}} with typical team usage profiles in {{target_segment}} to establish consumption percentiles.
  3. Segment {{seat_tier_features}} across Free, Team, and Enterprise tiers based on enterprise security and debugging capabilities.
  4. Map each tier against {{competitor_price_benchmarks}} to identify under-priced and over-priced feature boundaries.
  5. Apply {{expected_gross_margin}} to calculate floor pricing, target list price, and maximum discounted pricing bands.
  6. Model potential customer migration scenarios from pure seat licenses to hybrid consumption-plus-seat models.
  7. Construct the comparison matrix highlighting pricing mechanics, unit economics, risk factors, and net revenue impact.

Constraints

  • MUST express all margins as explicit percentages calculated against {{infrastructure_unit_cost}}.
  • MUST provide clear unit metrics (e.g., price per GB, price per 10k spans, price per seat).
  • MUST NOT recommend negative-margin tiers even for developer acquisition without explicit volume caps.
  • Keep explanatory matrix commentary strictly under 250 words per tier.

Output format

  • Section 1: Executive Unit Economics Summary
  • Section 2: Core Pricing Decision Matrix (Markdown table with columns: Tier Name, Packaging Mechanic, Unit Price, Margin %, Target Segment, Usage Cap, Overage Rate)
  • Section 3: Commercial Trade-Offs and Governance Rules

Self-review

  • Ensure every tier satisfies {{expected_gross_margin}} under baseline {{infrastructure_unit_cost}}.
  • Confirm that all 6 context variables are directly addressed in the matrix calculations.
  • Verify that overage mechanics are explicitly defined for usage spikes.
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 engineering10/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.

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
software-engineering-debugging
pricing-matrix
observability
dev-tools