Your Pricing Page Has Not Changed Since Series A

It is the 19th of the quarter, 11:24 AM. Your CFO opens the dashboard. Net new ARR for the month reads $620K. Discount-adjusted ARR reads $478K. The variance reads 23 percent. She filters the closed-won deals from the last 30 days. 38 deals signed, 31 carried a discount, median discount 22 percent, mean 27, largest 41 percent on a three-year prepay. She opens the Notion page titled "Pricing v3" and the last edit reads March 2024.

The pricing page on the website reads the same three tiers it shipped at $4M ARR. Starter at $99, Growth at $499, Scale at $1,999 a month. No usage component. No platform fee. No enterprise SKU. The page that 86 percent of inbound prospects land on before booking a demo carries pricing built for a smaller, simpler product than the one your team ships in July 2026.

Your AEs hold the gap together with a Notion doc, a CPQ tool nobody trusts, and a Slack DM to the CRO every Thursday at 5 PM. The deal desk approves a 22 percent average discount. The CFO carries the variance into every board pack. The pricing slide on the QBR deck has read "pricing review Q3" for five consecutive quarters.

Pricing and packaging is a function. Most Series B and C teams have not staffed it because the page shipped at Series A, the AEs work around it with discounts, and the CRO marks pricing as a Q3 project on every roadmap. The function lives in the gap between the AE who quotes off a stale price card, the product manager who ships a feature without a packaging slot, the CFO who watches blended ACV slide, the CRO who refuses to touch the page during a quota year, and the founder who notices the deal review queue is 80 percent discount requests. On the org chart it sits between Product, Finance, and Revenue. In the calendar it eats zero hours because nobody owns it.

The price card that drifted off the product

Pull every artifact the company uses to quote and sign customers. The public pricing page, the sales price card in Notion, the CPQ catalog, the order forms from the last 90 days, the discount approval log, the win-rate by quote variant, the closed-lost reason field for pricing, the renewal uplift accepted versus asked, and the usage telemetry per plan. Map every SKU the AE can sell to every feature the product ships today. Most teams find six to twelve features that landed in the last 12 months with no SKU attached. Three to five SKUs on the price card describe features the product retired a year ago.

Walk the order forms. The 41 percent discount on the three-year prepay was a price the AE invented to close a deal that should have carried a platform fee for the volume tier. The 22 percent average discount maps to AEs anchoring off a Scale tier that prices the product at $1,999 when the comparable competitor lists at $3,400. The closed-lost reason field reads "price" on 18 of the last 60 deals, but the win-loss notes on 12 of those 18 read "could not figure out which tier they were on." Pricing did not lose those deals. Packaging did.

The team that should own this knows it is broken. The CRO refuses to ship a new page mid-quota year. The PM cannot add a SKU because the CPQ tool needs three engineering tickets to update. The CFO watches the blended ACV slide and writes the variance off as macro. The AEs have stopped trusting the price card and quote off a personal spreadsheet. The function sits unstaffed while gross margin holds and net revenue retention drags.

Hiring a pricing manager is the slow answer

The textbook fix is a pricing and packaging lead. Loaded comp in the US runs $160K to $220K a year. Months one through three go to a discovery cycle, interviewing AEs, mapping the product to SKUs, and benchmarking 8 to 12 competitors. Months four through six are when the first packaging proposal lands on the CRO's desk and stalls in committee. Months seven through nine are when the new pricing ships on the website, after a legal review and a CPQ rewrite.

The fractional version is faster to start and stops at the same wall. Eight to twelve thousand a month buys ten hours a week of senior pricing time, a competitor benchmark refresh, and a quarterly packaging recommendation. The recommendation lands in a slide deck. The deck gets debated. Nothing ships because the CPQ catalog needs an engineering sprint nobody scoped.

Both versions assume the work is a quarterly study. The work itself is reading every order form within a day of signature, scoring every discount against win rate and segment, watching every closed-lost reason for pricing language, mapping every shipped feature to a SKU slot, refreshing the competitor benchmark monthly, and recommending a price card change with the math attached. On 38 deals a month plus a 200-deal pipeline that is 80 to 160 hours of senior pricing work a quarter, and no pricing manager clears that pile while also running the annual packaging refresh.

What a fractional AI pricing function does

Hand the order forms, the CRM, the CPQ catalog, the discount approval log, the win-loss notes, the usage telemetry, the product roadmap, the public pricing page, and a refreshed competitor list to a fractional AI agent that runs on a continuous cadence. The agent does the work a pricing manager, a RevOps analyst, and a finance partner would do together. The cadence is per-deal on order form review, weekly on discount drift, monthly on packaging gaps, quarterly on a recommended price card revision with the math attached.

Every order form read the day it signs. New order forms get parsed within a day of signature. Discount, term, prepay, SKU mix, ramp schedule, and add-ons get pulled into a structured record. The 41 percent prepay deal flags inside 24 hours, not at the end of the quarter when the CFO opens the dashboard.

Discount patterns scored against win rate, not blended. The 22 percent average discount splits by AE, segment, deal size, and tier. The agent finds the three AEs anchoring 12 points below the rest of the team on identical deal profiles. The deal desk gets a brief naming the pattern and the revenue impact. The CRO walks into the next forecast call with the number, not a gut feel.

Packaging gaps surfaced against the shipped product. Every feature shipped in the last 12 months gets mapped to a SKU slot. The six features without a slot get a recommended placement. The three retired features on the price card get a removal recommendation. The PM stops shipping into a price card that does not name the feature.

Closed-lost pricing reasons synthesized, not freeform. The agent reads the win-loss notes on every pricing-flagged loss, codes the actual reason against the tier confusion, the missing SKU, the competitor anchor, or the true price ceiling. The 18 deals lost to "price" resolve into 12 packaging losses and 6 ceiling losses. The pattern mirrors the voice-of-customer function on the product side.

Quarterly price card recommendation with the math attached. The agent rolls the deal data, the discount patterns, the packaging gaps, the competitor benchmark, and the usage telemetry into a recommended price card revision every 90 days. Each change carries a projected ACV lift, a projected win-rate impact, and a sensitivity band. The CRO walks into the pricing meeting with a proposal and a spreadsheet, not a deck and a debate.

The unit economics of frozen pricing

A Series B company at $14M ARR signing 38 deals a month at a 22 percent average discount is leaving 4 to 6 points of ACV on the table on every deal. On $620K in net new ARR a month that is $24K to $36K a month, $290K to $430K a year. Add the 12 packaging losses at $60K to $120K ACV each and the annual cost of a frozen price card runs $1.0M to $1.9M.

Layer in the people math. The CRO, the CFO, the deal desk lead, and the PM spend a combined 30 to 60 hours a quarter on ad-hoc pricing reviews, discount approvals, and Slack threads about tier mapping. That is 120 to 240 hours a year of senior leadership time on a function a fractional agent covers, against a fully loaded hour of $220 to $300. The pricing manager hire runs $200K to $290K loaded with a six to nine month ramp before the first new price card ships. The fractional consultant lands a deck and stalls in committee.

A 14-day sprint to stand up the agent runs in the low to mid five figures. Ongoing cost lands closer to one senior contractor than a pricing org. The first order form parse runs in week one. The first discount pattern brief lands in week two. The first packaging gap map sits on the PM's desk before the sprint closes.

What changes after the sprint

Picture the same 19th of the quarter, 11:24 AM moment, fourteen days after the sprint ships. The CFO opens the pricing dashboard. Net new ARR reads $620K, discount-adjusted reads $542K, the variance reads 13 percent and trending down. The brief on her screen names the three AEs anchoring 12 points low. The packaging map flags six features without a SKU and three retired features still on the price card. The recommended price card revision sits in the shared Notion with a $340K projected annual ACV lift and a sensitivity band.

By Friday the CRO has approved a deal desk rule that caps discount at 18 percent without exec sign-off. The PM has assigned packaging slots to the six unmapped features. The pricing page on the website ships a new enterprise SKU on a Tuesday morning. The next 30 days of order forms come in with an average discount of 14 percent and the closed-lost reason field reads "price" on 6 deals instead of 18.

If your pricing currently lives on a page that shipped at Series A and a Notion doc the AEs work around, the version where every order form gets parsed the day it signs and the price card carries the math behind every change is fourteen days away. Pricing and packaging is a function. You can hire against it, you can outsource a fractional pricing consultant for it, or you can scope a sprint and have it running this month. The work is the same. The math is not.