by PriceLens (LX AI)
PriceLens teardowns a pricing page in a multi-step workflow — tier clarity, positioning gaps, and concrete copy fixes — so you see how your pricing compares in about 30 seconds of reading time.
Decision-support only — confirm before you publish or act.
I open the pricing page in a private browser window to avoid cached sessions or personalized redirects. I copy the exact URL from the address bar and store it in a plain‑text note. This ensures I am reviewing the version that a new visitor sees.
Using the browser’s developer tools I right‑click the <html> tag and choose “Copy outer HTML”. I paste the markup into a local file named pricing‑page‑raw.html. I also capture a full‑page screenshot (PNG) for visual reference.
I note the date, time zone, and any version number shown in the footer or in a query string (e.g., ?v=2024‑09‑15). If the site uses a feature flag I disable it temporarily to see the default experience.
I scan the visual layout and count distinct containers that hold a price, a feature list, and a call‑to‑action button. I write each tier’s exact heading as it appears (e.g., “Starter”, “Professional”, “Enterprise”). I also note any hidden tiers that appear only after expanding a accordion or clicking “Show more”.
For each tier I record:
I build a simple table that lists common features down the left column and tiers across the top row. I place a check‑mark (✓) when the feature is included, a dash (–) when it is not, and an optional note when the feature is limited (e.g., “up to 10 users”). This table makes gaps instantly visible.
| Feature | Starter | Professional | Enterprise |
|---|---|---|---|
| Core API access | ✓ | ✓ | ✓ |
| Advanced analytics | – | ✓ | ✓ |
| Dedicated account manager | – | – | ✓ |
| SLA ≥ 99.9% | – | – | ✓ |
| Custom invoicing | – | – | ✓ |
I verify that tier names follow a logical order (e.g., Basic → Plus → Premium) and that no two tiers share the same name. I also look for vague labels like “Other” or “Custom” that lack a clear definition.
Based on the feature matrix I write a short segment description for each tier (e.g., “Starter: solo founders testing an idea”, “Professional: growing teams needing automation”, “Enterprise: large organizations with compliance needs”). I compare these descriptions to the copy on the page to see if the segment is explicitly mentioned.
I list the primary jobs‑to‑be‑done that the product solves (from the homepage or product docs). For each job I check whether at least one tier highlights that outcome in its headline or bullet points. Any job without a matching tier is flagged as a positioning gap.
I calculate a rough value ratio by dividing the monthly price by the number of core features included (using the matrix). I note whether the ratio rises, stays flat, or drops as you move up tiers. A dropping ratio can signal over‑pricing of higher tiers.
I read the main heading above the pricing grid. I ask: does it state what the visitor will get in plain language? I rewrite it in my own words to see if the meaning changes. If the original relies on jargon or vague promises I mark it for revision.
Under each tier I examine the short paragraph or list of benefits. I look for:
I note the exact text on each button (e.g., “Start Free Trial”, “Contact sales”, “Choose plan”). I prefer verbs that convey action and low friction. I flag any button that uses generic text like “Learn more” without a clear next step.
If I suspect any text was produced by a language model I run a quick mental scan against the OWASP LLM Top 10 to see if it exhibits common failure modes such as hallucinated features or unsafe claims. I also verify that any statement about compliance or security aligns with the NIST AI Risk Management Framework guidance, noting where the copy may overstate capabilities.
I verify that the most important tier (usually the one the business wants to sell) uses a distinct background color, a border, or a badge such as “Most popular”. I check that this visual cue is perceivable in grayscale for color‑blind users.
Using the browser’s ruler tool I measure the vertical padding inside each tier container. I ensure that all tiers share the same padding values; uneven spacing can make a tier look unintentionally emphasized or de‑emphasized.
I look for a column that uses check‑marks and crosses to show what changes between tiers. If the page relies only on text lists I note that a visual diff would improve scan‑ability.
I narrow the viewport to 320 px width and observe whether the tiers stack vertically, retain readable font sizes, and keep the call‑to‑action buttons tappable (minimum 44 × 44 px). I also check that any horizontal scrolling is avoided.
This checklist is a decision‑support aid, not a guarantee that your pricing will convert better. It does not replace:
The output reflects the state of the page at the moment of inspection. Prices, promotions, or tier structures may change without notice. Use the findings as a starting point for further validation, not as a final verdict.
I keep a written checklist next to every release that touches this topic. The list is boring on purpose: name the owner, name the evidence artifact, and name the rollback. If a step cannot produce a file, a ticket, or a log line, it is not a step — it is a wish.
| Signal | What to record | Stop-ship? |
|---|---|---|
| Unexpected write or send | Tool name, args, identity | Yes until gated |
| Missing confirmation on destructive action | Call path and bypass | Yes |
| Untrusted text treated as instruction | Source surface and resulting action | Yes for agent reach |
| Scanner clean, judgment open | Deferred items + owner | Only if core path safe |
pricelens helps with the measurable first pass. Architecture choices, legal sign-off, and customer-facing claims still need a human owner. Treat every checklist row as decision support, not a certificate.
When a prospect asks whether the product "covers everything," I answer with the boundary: automated checks catch known patterns; novel chains and policy judgment still need review. That honesty keeps support load down and keeps the blog aligned with what the product actually does.
If you need a second opinion, pair this write-up with the references below and with your own staging reproduction. Do not skip the reproduction step just because a model wrote a confident summary.
PriceLens teardowns a pricing page in a multi-step workflow — tier clarity, positioning gaps, and concrete copy fixes — so you see how your pricing compares in about 30 seconds of reading time.
Decision-support only — confirm before you publish or act.
Want to try the product? PriceLens
Generated 2026-09-17 · primary sources only · no fabricated traffic metrics