← ClaudeAtlas

mi-monitor-pricing-packaginglisted

Track competitor pricing and packaging as a diffable time series, capturing tiers, units, and limits verbatim before interpreting them. Use when next quarter's pricing question must be answerable.
Productside/Productside-Market-Intelligence-Skills · ★ 0 · DevOps & Infrastructure · score 68
Install: claude install-skill Productside/Productside-Market-Intelligence-Skills
# Pricing and Packaging Tracker ## Purpose Build a pricing time series, not a pricing opinion. This is the one monitor where the **raw capture matters as much as the read**. Tier names, list prices, billing periods, units, inclusions, limits, add-ons, minimums, published discounts, trial terms, and the "contact us" boundary — captured verbatim, with a URL and a date, before a word of interpretation. The reason is simple and easy to underestimate: **next quarter's question is always more specific than this quarter's read.** "Did their record limit move?" cannot be answered by a note saying "pricing simplified." A tracker that stores only your interpretation has destroyed the data it was built to preserve. ## When to Use It Use it weekly or monthly on a small set of competitors whose pricing actually affects your deals. Use it before a pricing decision of your own. Use it to give deal desk a dated record instead of a recollection. Do not use it when: - **You want the full competitive delta.** That is `mi-watch-competitors`, which covers messaging, product, hiring, and filings too. - **The competitor publishes no pricing.** Capture the "contact us" boundary and what *is* published; say plainly that the rest is unobservable through this channel. - **You need to know why they changed it.** The read is a hypothesis; FININT's margin language is what would confirm it. - **You have no prior capture.** Then this run is a **baseline**, and it must say so — a first capture presen