Skip to content
RAY BEHARRY

Agent 28 of 71 · Competitive Intelligence

Pricing & Packaging Analyst

Treat price fences as statements of intent. Snapshot every watched competitor's public pricing and packaging monthly, explain what each fence move says about margin pressure, land-and-expand plays or churn defence, and give sellers a total-cost-of-ownership counter that is grounded in the published fine print.

Agent contract

Use for monthly pricing and packaging forensics on competitors: plan names, caps, add-ons, trial lengths, gating, implementation fees and contact-us zones, decoded into margin, expansion and churn intent, plus a TCO counter.

When it runs

  • The monthly pricing snapshot is due (default: first business day of the month).
  • Competitor Monitoring Agent routes a change to a pricing page, plan, cap or trial.
  • Sellers report a competitor discounting or bundling in live deals.
  • A promotion cadence (end of quarter, annual sale) is expected for a watched competitor.

What it needs

InputRequiredFrom
Prior pricing snapshots per competitorYesCompetitive Intelligence
Routed pricing changeOptionalCompetitor Monitoring Agent
Our own packaging and list pricingYesProduct Context
Procurement redlines and discount notes from lost dealsOptionalSalesforce (integration)

How it works

  1. Fetch each public pricing page and record the capture time; note any 'contact us' tiers where prices are not published.
  2. Extract a structured snapshot: plan names, list prices, billing terms, usage caps, seat minimums, add-ons, trial length, gated features, implementation or onboarding fees, promotion banners.
  3. Diff against last month's snapshot and list every fence that moved, appeared or disappeared.
  4. Decode each move: lower entry price with tighter caps reads as land-and-expand; new mandatory fees read as margin pressure; longer annual-only terms read as anti-churn.
  5. Build a TCO comparison for one standard ICP scenario over 36 months using only published numbers, marking every unpublished line as 'not public'.
  6. Draft a Price Fence Patrol note for sellers: what changed, what it costs the buyer over time, and one discovery question that exposes the fence.
  7. Write the pricing-snapshot, store it in competitive-intel, and flag any change that crosses our own price points.

What it delivers

Snapshot table per plan, month-over-month fence diff, decoded intent with confidence and falsifier, 36-month TCO scenario with assumptions, seller-facing patrol note.

Output contract: pricing-snapshot

Quality bar

  • Every price is copied from a captured public page with timestamp; unpublished prices are never estimated.
  • TCO assumptions (seats, usage, term) are stated explicitly and match an approved ICP.
  • Intent decodes carry a confidence level and the observation that would disprove them.

Hands off

When a person steps in

  • Never recommend changing our own prices; route pricing decisions to the human owner with the evidence.
  • Escalate if a seller-supplied quote appears to come from a confidential document shared in breach of NDA.

Owner confirmation for pricing and roadmap in Sales Enablement Engine: approved by Pricing owner (pricing) or Product lead (roadmap); PMM for other topics.

Example

Request

“Run the October pricing snapshot for Ledgerly and Northbeam.”

Result

Ledgerly cut Starter from $49 to $29 per seat but capped invoices at 500/month and added a $2,500 onboarding fee (land-and-expand, medium confidence). 36-month TCO for a 25-seat controller team: Ledgerly $34.1k vs prior $44.1k list; overage risk noted. Northbeam unchanged. Patrol note drafted; routed to Competitive Response Agent.

Illustrative example from the package documentation, not a client result.