Company Background

You are advising SignalForge, a B2B SaaS company that provides an API-first product analytics and event-pipeline platform used by mobile and web apps to collect events, run funnels/retention, and trigger downstream activation campaigns. SignalForge competes in a crowded “modern data stack” environment against incumbents (Amplitude, Mixpanel) and newer warehouse-native tools. The company’s differentiation is that it combines (1) a lightweight SDK + API for event ingestion, (2) near-real-time identity stitching, and (3) pre-built lifecycle messaging integrations.

SignalForge is at $48M ARR, growing ~22% YoY (down from 35% last year). Gross margin is 78%, but infrastructure costs have been rising because customers are sending more events and keeping longer retention windows. The company has 2,400 paying customers and a product-led growth motion for SMB/mid-market plus a sales-assisted motion for enterprise. Current pricing is a flat subscription based on plan tier (feature gating + soft usage limits). The CEO and CFO are debating a shift to a more explicit usage-based pricing (UBP) model (priced per million events ingested), potentially with a small platform fee.

Over the last two quarters, competitive pressure has increased. Two warehouse-native competitors are offering aggressive entry pricing and positioning “pay for what you use” as more transparent. Meanwhile, enterprise procurement teams are pushing back on SignalForge’s tiered plans because they perceive they’re paying for features they don’t use. On the other hand, the Sales team worries that pure usage pricing will create bill shock, slow adoption, and make budgeting harder—especially for consumer apps with spiky traffic.

Strategic Situation (Decision Needed)

SignalForge must decide within 6 weeks whether to:

• Option A (Status Quo+): Keep the flat subscription model, tighten enforcement of soft limits, and introduce overage fees only for extreme usage.
• Option B (Hybrid UBP): Introduce a platform fee + usage-based event pricing (e.g., $X per million events), with annual commitments and volume discounts for enterprise.
• Option C (Pure UBP): Move to usage-based pricing with minimal feature gating, positioning SignalForge as a “utility” for event ingestion and analytics.

The board wants a recommendation grounded in a revenue impact estimate (12-month and 24-month view), including sensitivity to customer behavior changes (churn, expansion, and reduced usage). The CFO is also concerned about margin volatility and wants to understand whether UBP better aligns revenue with infrastructure costs.

Data Provided

1) Current customer mix and subscription pricing

Current net revenue retention (NRR): 112% overall (SMB 102%, mid-market 115%, enterprise 125%).

2) Observed usage distribution (events ingested)

SignalForge measures billable usage as events ingested (in millions per month). The distribution below is based on the last 90 days.

3) Proposed usage-based price card (initial strawman)

• Platform fee (includes core analytics UI, SDKs, 3 seats):
  • SMB: $300/month
  • Mid-market: $1,200/month
  • Enterprise: $6,000/month
• Usage fee: $22 per 1M events (list price)
• Enterprise volume discount: average realized price expected $16 per 1M (after discounting)

4) Cost to serve (simplified)

• Variable infra cost: $6 per 1M events (includes storage + compute)
• Support cost per customer per month (fully loaded): SMB $40, mid-market $120, enterprise $900

5) Behavioral assumptions (not guaranteed)

Commercial team’s hypotheses if UBP is introduced:

• SMB: +10% new logo conversion (pricing transparency), but +2 pts monthly churn from bill shock unless guardrails exist.
• Mid-market: neutral new logo, but -5% usage as customers optimize instrumentation.
• Enterprise: -10% churn risk (procurement likes alignment), but sales cycle +1 month due to pricing/legal review.

Your Task (Deliverables)

As the Strategy & Analytics lead, you need to prepare a board-ready recommendation.

1. Baseline revenue model: Estimate current annual revenue and gross profit by segment using the data above.
2. UBP revenue sizing: Under the proposed price card, estimate expected annual revenue by segment. You may assume usage follows a log-normal-like distribution and approximate with provided percentiles.
3. Behavioral impact: Incorporate at least two behavioral changes (e.g., churn, usage optimization, conversion lift) and quantify their revenue impact.
4. Competitive and GTM implications: Use a structured lens (e.g., Porter’s Five Forces + positioning) to explain how pricing affects win rates, expansion, and defensibility.
5. Recommendation: Choose Option A/B/C and propose a pricing and packaging design (including guardrails like caps, commit tiers, or alerts) that maximizes 12–24 month revenue while protecting retention and margins.

Constraints

• Timeline: decision in 6 weeks; pricing change must be ready to launch in 90 days.
• Engineering capacity: only 6 eng-weeks available for billing + metering changes this quarter.
• Contracting: enterprise customers require annual invoicing; cannot introduce monthly true-ups for most of them.
• Reputational risk: CEO will not accept a plan that creates widespread “bill shock” headlines on social media.
• Revenue target: board expects $60M ARR run-rate within 12 months without increasing burn.