Tools and Techniques for Pricing, Packaging and Revenue Models

From business context to repeatable pricing mechanics

Unit 5 Lesson 1 argued that pricing is a GTM (go-to-market) choice, not a spreadsheet afterthought. RelayOps (Maya Chen and Jordan Park's incident response platform) must now pick tools: how to choose a value metric, structure packaging tiers, estimate willingness to pay (WTP, the maximum a buyer would pay for the outcome), and model expansion without breaking channel parity from Unit 4. Current facts: $920,000 ARR, 21 customers, ~$44,000 ACV (average contract value), ICP (ideal customer profile) of U.S. Series B SaaS with Datadog and Slack stacks.

This lesson is technical mid-course: formulas, tables, and two worked examples with check lines. You should finish able to build a price book row, compute expansion ARR from metric growth, and defend a metric choice to a board member who only knows "per seat."

Value metric selection: the four-test framework

The value metric is what you count when the invoice generates: seats, on-call rotations, environments, incidents, or API calls. Good metrics pass four tests:

1. Value alignment. Usage of the metric should rise when customer value rises. RelayOps rotations expand when the company adds services and teams; rotations track ops load better than total company headcount.

2. Predictability. Buyers budget quarterly. Pure usage-based pricing per alert creates spike anxiety during outage months. Hybrids cap overage or include alert pools.

3. Expansion path. The metric should grow with customer success: more rotations, more seats in Growth tier, or upgraded tier. NRR (net revenue retention, expansion minus churn on existing customers) depends on natural expansion.

4. Understandability. Procurement and MSP (managed service provider) partners must explain the line item in one sentence. "Per on-call rotation" beats "per 1,000 alert events normalized by severity."

RelayOps ICP buyers (VP Engineering, Head of Platform) think in services and rotations, not every engineer with login. Rotation-led Growth tier is the leading candidate; seats become a fairness cap, not the primary meter.

Packaging architecture: features, fences, and triggers

Packaging bundles features into tiers separated by fences (deliberate limits that create upgrade pressure). RelayOps v2 packaging:

Starter ($2,400/mo annual contract equivalent)

• 4 rotations, 25 seats, Slack, basic incidents
• Fence: no Datadog bi-directional, no SSO

Growth ($3,800/mo list, ICP default)

• 10 rotations, 75 seats, Datadog bi-directional, SSO, postmortem templates
• Overage: $550/additional rotation; $75/seat above 75

Scale (custom from $6,500/mo)

• Unlimited rotations in contract, advanced analytics, 99.9% SLA (service level agreement, uptime commitment), dedicated CSM (customer success manager)

Upgrade triggers map to customer lifecycle:

• Rotation count exceeds 10 for two consecutive months → Growth to Scale conversation
• SSO required by security review → Starter must upgrade to Growth
• Multi-region teams → Scale analytics

Packaging tools:

Feature matrix (sales and website) Price book (internal, versioned) SKU map for AWS Marketplace (rotation packs + seat caps) Partner rate card (software list before margin)

Version control matters. RelayOps names price book v2026.1 effective Q1; all quotes reference version.

Willingness-to-pay techniques at early scale

RelayOps lacks volume for sophisticated conjoint (trade-off analysis surveying feature/price bundles). Useful early techniques:

Van Westendorp (four price questions: too cheap, bargain, expensive, too expensive)

Ask ICP prospects after demo:

• Below what price would quality concern you?
• Bargain price?
• Starting to get expensive?
• Too expensive to consider?

Plot cumulative curves; intersection band suggests acceptable range. Lesson 1 showed $3,600-4,500/mo band for Growth.

Economic value estimation (EVA-style bridge)

Build a spreadsheet with customer inputs:

• Engineers on incident duty per week
• Loaded hourly cost
• Minutes saved per incident × incidents/month
• Optional attrition risk reduction

RelayOps targets 10-25% value capture on documented savings in year one.

Closed-won / closed-lost reviews

Monthly, Maya tags deals: price too high, metric confusion, competitor flat fee, security delay. Patterns drive packaging fixes more than surveys.

Cohort expansion analysis

Existing customers: correlate rotation growth with seat growth and support tickets. If rotations grow 20% year one while seats flat, rotation metric captures expansion better.

Discounting mechanics and price waterfall

Discounting should be structured, not negotiated ad hoc. RelayOps price waterfall (steps from list to invoice):

Maximum discount stack without CEO: 10% prepay only.

Waterfall example for ICP: 8 rotations on Growth (within 10 included), list $3,800/mo.

No volume discount (≤10 rotations). Annual prepay 10% → $3,420/mo → $41,040 ACV

Check: 3,800 × 0.9 = 3,420; ×12 = 41,040 ✓

Compare to legacy $44K ACV: new book slightly lower but cleaner; expansion raises NRR.

Channel parity: MSP and marketplace offers use same waterfall; partner margin applies after customer price.

SaaS pricing models in practice: seat, rotation, usage

Combine models intentionally:

RelayOps Growth hybrid formula

Monthly invoice = Platform fee + (Rotations × rotation rate) + Seat overage + Alert overage (optional)

Platform = $1,800 Rotation rate = $650/rotation (first 10); $550 beyond Seat overage = $75/seat/month above 75 included Alert overage = $0.04/alert above 15,000/month (optional module)

Why optional alert meter: avoids bill shock; only enable for customers with >20K alerts who want lower rotation rate.

Per-seat alternative (legacy)

$110/seat/month, 35 seats → $3,850/mo → $46,200 annual before discount. Simple but discourages adding observers and PMs to incidents.

Pure usage (rejected for ICP default)

$0.12/alert + $25/incident opened → volatile; procurement resists.

Model selection is not religious. RelayOps may sell Scale flat for global enterprises later. ICP beachhead uses hybrid rotation-led Growth.

Packaging communication: website, order form, and talk track alignment

A price book that lives only in an internal spreadsheet fails the moment a prospect reads the website. RelayOps must keep three customer-facing artifacts synchronized:

Marketing site pricing page shows tier fences in plain language (rotations, seats, integrations), not internal SKU codes. Series B SaaS buyers compare RelayOps to PagerDuty on this page before taking a call.

Order form / quote PDF lists exact monthly or annual math with price book version footer (v2026.1). Legal and procurement review this document; vague "custom pricing" language reintroduces complexity.

Sales talk track explains why rotations are the unit ("you pay for operational coverage blocks, not every engineer who might join a war room once a quarter"). AEs who revert to seat language undermine the metric choice.

Maya should run a quarterly pricing audit with marketing and legal: pick five random closed-won deals and trace quote → order form → invoice → recognized revenue. Any break in the chain becomes a RevOps ticket, not a one-off finance fix.

For Datadog co-sell, the talk track must match the site: partners repeating seat pricing while the site shows rotations creates the channel conflict Unit 4 warned about. Enablement includes a one-slide pricing snapshot updated within 48 hours of any book change.

Expansion forecasting with cohort curves

RelayOps can model expansion without waiting for 200 customers by using cohort curves on the 13 Growth hybrid customers from the current base.

Track for each customer quarterly: rotation count, seat count, support hours, incident volume. Compute expansion ARR (additional recurring revenue from existing customers) when rotations increase or tier upgrades occur.

Example cohort insight: among 13 customers, 4 added rotations in months 6-12 averaging +$14,200 annualized each → $56,800 expansion ARR from 31% of cohort. If new logos behave similarly, expansion could contribute 25-30% of new ARR by year two, validating rotation metric choice.

Forecast formula for planning:

Expected expansion ARR in period = (Eligible cohort ARR) × (Expansion rate) × (Average uplift %)

RelayOps Q3 planning: eligible cohort ARR $1.2M × 22% customers expanding × 18% average uplift ≈ $47,520

Check: 1,200,000 × 0.22 × 0.18 = 47,520 ✓

This is rough, but it beats assuming all growth comes from new logos. Boards respect explicit expansion assumptions tied to metric design.

Price elasticity and when to test (carefully)

Price elasticity (how volume changes when price changes) is hard to measure with 21 customers. RelayOps should not run aggressive public price tests. Acceptable tests at this stage:

• New logo cohort test: for one quarter, quote 5% higher list to 50% of inbound ICP leads and compare win rate (minimum 20 opps per arm before concluding).
• Geographic test later: when expanding beyond U.S., test purchasing power parity discounts as separate price book region row, not one-off deals.

Do not test by surprising existing customers with mid-contract increases. Do not publish multiple public prices on the website simultaneously without clear segmentation (Starter vs Growth is fine; hidden coupon codes are not).

If win rate drops more than 6 points when list rises 5%, elasticity is likely high in current segment; hold price and improve value narrative before cutting again.

RelayOps should pair any future price test with win/loss interview (structured debrief with buyer after decision) questions about metric clarity. If losses cite "could not explain rotation billing," fix packaging communication before adjusting list price down.

Worked micro-example: quote calculator output for AE training

Train AEs to produce quotes that match finance recognition. For Growth, 8 rotations, 40 seats, annual prepay:

Check: matches Northwind example in main worked case ✓

AEs should not manually override calculator lines; overrides route to Maya with reason code. Calculator output attaches to CRM opportunity record as PDF for audit trail.

Customer Northwind SaaS: 180 engineers, 9 on-call rotations, 40 named seats, 14,000 alerts/month, Datadog + Slack, annual prepay.

Part A: Tier selection

Needs SSO and Datadog → Growth required.

Rotations 9 ≤ 10 included. Seats 40 ≤ 75 included. Alerts 14,000 ≤ 15,000 cap → no overage.

Part B: Monthly calculation

Platform $1,800 + 9 × $650 = 1,800 + 5,850 = $7,650/mo wait - if first 10 rotations included in platform differently...

Let me define clearly: Platform $1,800 includes up to 10 rotations at $650 embedded → actually simpler:

List Growth = $3,800/mo base includes 10 rotations and 75 seats (from packaging section). Additional rotation $550.

Northwind has 9 rotations → base $3,800/mo.

Prepay 10% → $3,420/mo

Annual = $41,040

Check: matches prior waterfall ✓

Part C: Expansion scenario at month 12

Northwind adds 4 rotations (total 13) and 20 seats (total 60, still under 75).

New monthly before discount: $3,800 + 3 × $550 = 3,800 + 1,650 = $5,450

With prepay renewal 10%: $4,905/mo → $58,860 ACV

Expansion ARR = 58,860 - 41,040 = $17,820 on same customer

NRR contribution = 58,860 / 41,040 = 143% on that logo before churn elsewhere

Check: 3 overage rotations × 550 = 1,650 ✓

Part D: Managerial read

Rotation overage captures growth without renegotiating seat count. Finance models expansion pool as 25% of starting ARR if 30% of customers add ≥3 rotations.

RelayOps must publish AWS Marketplace dimensions.

Part A: SKU options

SKU-1 misaligns if seats unused; SKU-2 approximates; SKU-3 matches price book exactly.

Part B: Recommendation

Primary private offer SKU-3 flat Growth annual; add-on SKU rotation pack 5 for expansion mid-term.

Check: SKU-3 = waterfall prepay $41,040 ✓

Part C: Partner rate card excerpt

Check: 45,600 × 0.78 = 35,568 ✓

RelayOps customer HelioStack on Growth: 12 rotations (2 over fence if base includes 10), 90 seats (15 over 75), monthly list before prepay.

Pricing: base Growth $3,800/mo includes 10 rotations and 75 seats; overage $550/rotation, $75/seat.

HelioStack renews with annual prepay 10% and adds 2 more rotations (14 total) at renewal.

Tasks:

1. Compute monthly list before prepay at renewal.
2. Compute ACV after prepay discount.
3. Compute expansion vs original ACV if original was $41,040 (9 rotations, 40 seats).
4. Should alert overage module be offered if HelioStack runs 22,000 alerts/month at $0.04 above 15,000 cap? Compute annual impact.

Solution

1. Monthly list at renewal

Rotations: 14 → 4 over × 550 = 2,200 overage Seats: 90 → 15 over × 75 = 1,125 overage Base 3,800 + 2,200 + 1,125 = $7,125/mo

Check: 3,800+2,200+1,125 = 7,125 ✓

2. ACV after prepay

7,125 × 0.9 × 12 = 6,412.5 × 12 = $76,950

Check: 7,125 × 12 = 85,500; ×0.9 = 76,950 ✓

3. Expansion vs original

Delta = 76,950 - 41,040 = $35,910 (+87.5%)

Check: 35,910/41,040 = 0.875 ✓

4. Alert module

Overage alerts = 22,000 - 15,000 = 7,000/mo × 0.04 = $280/mo → $3,360/year

Prepay 10% → $3,024/year incremental

Offer if HelioStack wants lower rotation rate tradeoff; otherwise rotation metric already captures growth and alert module adds complexity.

Key takeaways

• Select value metrics with value alignment, predictability, expansion, and understandability tests.
• Packaging uses fences and upgrade triggers; version the price book and SKU map together.
• WTP at early scale comes from Van Westendorp bands, value bridges, and win/loss reviews.
• Discount waterfalls enforce discipline; prepay 10% is RelayOps's default lever.
• Rotation-led hybrid Growth matches ICP ops mental models and expansion better than seat-only legacy.

1. Build a one-page price book for a fictional product with two tiers and one overage metric.
2. Compute prepay ACV for a customer with 11 rotations and 80 seats using RelayOps Growth rules.
3. Continue to Lesson 3: Managing Complexity in Pricing, Packaging and Revenue Models.