Skip to main content

Boardroom Answers · Revenue & Global · Business Value & ROI

RED FLAG — FIX BEFORE THE DEMO: Your pricing page’s search-listing text says "Enterprise from $9,000/yr" while your pricing engine, your tier card and your revenue-recognition code all say $9,000 per MONTH. Which is it — and what does a CFO conclude when your own materials disagree by a factor of twelve?

The question a Managing Director / Regional President asks.

The short answer

Canonical is $9,000 per month — engine, tier card and revenue recognition all agree; the search-snippet "/yr" is a metadata typo being fixed before the demo. Minimum Enterprise contract: $108K a year.

The full executive answer

The canonical answer is per month — and the code is unambiguous about it. The single-source-of-truth pricing module stores Enterprise at $9,000 monthly with the label "from $9,000 / mo", the revenue-recognition function counts an Enterprise org at $9,000 of monthly revenue, and the pricing page’s visible tier card reads "From $9,000 / month · billed annually". The one deviant string is the page’s SEO meta description — the snippet search engines display — which says "/yr". That is a typo in marketing metadata contradicting the billing engine by 12x, sitting in the single most visible sentence Google shows about our pricing.

Why this is a pre-demo emergency rather than a cleanup ticket: an eagle-eyed CFO who googled us before the session has "from $9,000/yr" in their notes. If VK quotes the monthly floor on stage, that CFO hears either a 12x price hike mid-conversation or a vendor who does not know his own prices — and for a product whose entire brand is "a single source of truth for governed decisions", pricing metadata that contradicts the pricing engine is a self-inflicted counterexample. The irony would not be lost on this panel: the codebase’s own comments record that price drift across surfaces is exactly the disease the canonical pricing module was built to cure.

The fix is a one-line edit to the metadata string — "/yr" to "/mo" — plus a two-minute sweep for any other surface quoting the annual figure, done and deployed before demo day. If a panelist has already cached the wrong snippet and raises it live, the recovery line is honest and brief: "Sharp catch — that was a typo in our search-listing text, already fixed; the billing engine has only ever known $9,000 a month, and here is the tier card." Then move on. What must not happen is VK discovering the discrepancy for the first time on stage.

Grounded in: Single-source-of-truth pricing governance — every price surface must derive from the canonical module, and metadata is a surface; pre-mortem discipline (find the stage-killers before the stage does).

Want this answered live, on your data?