A complete report, exactly as it comes out

# Page fix brief — Pricing page

- **Page:** https://www.checklyhq.com/pricing/
- **Title:** Checkly Pricing Plans: Flexible Synthetic Monitoring Solution
- **Audited:** 2026-08-12 by FAQLens
- **Score:** 67/100 overall · 69/100 completeness · 55/100 AI-extractability
- **In this file:** 5 content issues

## Read this before you change anything

You are editing the source of the page above. Its problem is not that it looks wrong —
it is that an AI assistant reading it cannot answer questions a buyer would ask, so it
either says nothing useful about this product or answers from somewhere else. Each issue
below is one such question, with the answer that should exist.

Rules for this task:

1. **Everything here was inferred from the rendered text of that one page.** It is the
   only evidence you have about this product. Do not add facts from elsewhere, and do not
   fill a gap with something that sounds plausible.
2. **"What an AI extracts today" is a paraphrase, not a quote.** It is what a model could
   assemble from the page, so the exact words may not appear in the source. Find the
   relevant section by heading and meaning — never by string-matching that line.
3. **Never publish a `[bracketed]` placeholder.** Those mark facts the page never stated,
   which means nobody but the site owner can supply them. Leave the placeholder in place
   and list it for them rather than guessing a value.
4. **Anything marked VERIFY contains a specific claim with no source on the page.** Treat
   it as unverified: delete the claim or flag it for the owner. Do not ship it.
5. **Change the page, not the product.** Nothing here is a recommendation about pricing,
   policy, features or positioning, and none of it was measured. Open questions at the
   end are for a human to answer, not for you to decide.
6. **The answer has to survive in the raw HTML.** Content that only appears after a
   JavaScript render — an accordion body, a tab panel, a modal — is invisible to the AI
   crawlers this is meant to fix. Server-render the answer text, or put it in the markup
   directly, or add it as FAQPage JSON-LD as well.

When you are done, report which issues you fixed, which you left for the owner, and every
placeholder still outstanding.

## What this page has to do

A buyer must be able to pick the right plan and confirm total cost, cancellation terms, and target fit without leaving the page.

## How the page should be structured

1. Hero/intro: one-line product description plus explicit audience statement (personas + industries); currently only implied via nav.
2. Plan comparison table: Hobby/Starter/Team/Enterprise with pricing, limits, and features; present today.
3. Detailed feature tables (Uptime, Synthetic, Alerting, Status Pages, Resolve, Platform): granular per-feature breakdown; present today.
4. Social proof section: credibility statement about customers; present today but generic, no names or logos.
5. FAQ: Platform, General, Billing subsections covering upgrades, downgrades, taxes, payment types; present today, missing refund and cancellation clarity.
6. Final CTA: sign-up prompt; present today.

## Where each answer belongs

- What is this product, and who is it for?: belongs in the hero/intro section, needs a short explicit sentence naming the product category and listing target personas/industries directly in text (not just nav links), since nav items are not extractable as page-body content by an AI.
- What is your refund policy?: belongs in the Billing FAQ, needs a new explicit Q&A entry titled with "refund" wording so it is directly matchable; currently absent entirely.
- Can I cancel anytime?: belongs in the Billing FAQ, needs its own explicit Q&A entry (separate from "upgrade or downgrade") stating cancellation mechanics directly, since currently it must be inferred from unrelated downgrade text.
- Does pricing scale per user or per usage?: belongs in the Platform or plan comparison section, needs one consolidated line or short note stating both axes (user seats + usage-based check runs/overages) exist together, since currently the two facts sit in separate tables (Platform "Users" vs Detect "API Check Runs") with no cross-reference.
- Is there a setup fee or hidden cost?: belongs in the Billing FAQ, needs an explicit Q&A entry addressing setup fees directly and pointing to the existing overage pricing explanation, since currently a reader must piece together overage rates from the Billing FAQ and plan tables without one clear statement.
- Who else uses this?: belongs in the social proof section, needs verifiable content (names, logos, or a link framed as continuation of proof) instead of only the generic "world-class engineering and SRE teams" line, since that line is not attributable and the real Customers content lives off-page.

## Issues to fix

> Not all of these are ready to ship: 1 is a template with placeholders to fill in. See rules 3 and 4.

### 1. What is your refund policy?

**CRITICAL · MISSING · TEMPLATE**

*Why a buyer needs this:* Refund clarity is the #1 hesitation before purchase. Its absence kills conversions.

*What's wrong now:* The pricing and FAQ sections cover billing, upgrades, downgrades, taxes, and payment types in detail, but no section titled or worded as "refund" or "money-back" appears anywhere on the page, so an AI cannot state whether refunds are offered or under what conditions.

*Add this. It is a template — replace every `[bracketed]` part with a real detail from the owner, and do not publish it until they have:*

```
Our refund policy allows you to request a refund within [refund window] of purchase, provided [refund conditions]. To start the process, please [refund request method], and refunds are typically processed within [processing timeframe].
```

### 2. What is this product, and who is it for?

**CRITICAL · BURIED**

*Why a buyer needs this:* A buyer arriving from an AI answer lands on this page alone and never sees the homepage. If the page never says what the product is or who it serves, nothing else on it can be judged.

*What's wrong now:* The tagline "Test & Monitor your APIs and websites with comprehensive Uptime and Synthetic monitoring" describes the product, but the audience is only implied through separate nav items like "Personas: Developers, SRE & Platform, QA Engineers, Engineering Managers" and "Industries: E-commerce, Financial services, SaaS & B2B software" with no

*What an AI extracts today (paraphrase — do not string-match):*

> Checkly is a code-based uptime and synthetic monitoring platform (APIs, websites, browser checks) for developers, SREs, QA engineers, and engineering managers.

*Replace or surface with this:*

```
Checkly is a monitoring-as-code platform that lets you Detect, Communicate, and Resolve issues via Uptime Monitoring, Heartbeat Monitoring, Synthetic Monitoring, and AI-powered testing, plus Status Pages, Alerts, and AI Root Cause Analysis. It's built for Developers (checks in TypeScript, deployed with your app), SRE & Platform teams, QA Engineers (running Playwright suites as production monitors), and Engineering Managers, and it also serves industries like E-commerce, Financial services, and SaaS & B2B software.
```

### 3. Can I cancel anytime?

**CRITICAL · BURIED**

*Why a buyer needs this:* Subscription anxiety. Buyers won't commit without an exit guarantee.

*What's wrong now:* The FAQ under "Billing" covers "Can I upgrade or downgrade my plan?" and describes downgrades taking effect at end of billing cycle, but there is no explicit line saying "you can cancel anytime" or explaining how to fully cancel a subscription; a visitor asking about cancellation would have to infer it from the downgrade policy, leaving real doubt about refunds or how to actually stop billing.

*What an AI extracts today (paraphrase — do not string-match):*

> Not explicitly stated; page only explains upgrade/downgrade mechanics, implying no lock-in but never confirms cancellation directly.

*Replace or surface with this:*

```
The page doesn't explicitly confirm cancellation, but its billing rules show no lock-in: you can change plans anytime via the self-serve billing portal, and downgrades take effect at the end of your current billing cycle, so you keep your current plan's features until then with no penalty. [Whether a full cancellation option beyond downgrading to Hobby exists] is not stated.
```

### 4. Does pricing scale per user or per usage?

**HIGH · BURIED**

*Why a buyer needs this:* Pricing model affects whether team buyers can predict their bill.

*What's wrong now:* The Platform section lists "Users" per plan (1, 3, 10, Custom) while the Detect/Synthetic tables show usage caps like "API Check Runs 10,000 per month" and overage rates such as "$1.80 per 10k," so pricing scales on both axes but no single line states this tradeoff, forcing a reader to cross-reference multiple tables to conclude it's a hybrid model.

*What an AI extracts today (paraphrase — do not string-match):*

> Both: plans include a fixed user count (e.g. 1, 3, 10 users) plus usage-based limits (check runs, uptime monitors) with per-1k/10k overage pricing.

*Replace or surface with this:*

```
Checkly's pricing scales on both axes: each plan caps team size (Hobby 1 user, Starter 3, Team 10, Enterprise custom) and also includes usage limits like API and Browser/Playwright check runs, uptime monitors, and agentic checks, with overage pricing (e.g. $1.80 per 10k additional API check runs, $4.00 per 1k additional Browser Check runs on Starter and Team) charged automatically once you exceed your included amounts.
```

### 5. Is there a setup fee or hidden cost?

**HIGH · BURIED**

*Why a buyer needs this:* Hidden fees erode trust. Stating none builds it.

*What's wrong now:* The page never states 'no setup fee' directly, but the Billing FAQ explains that overages for Browser Check runs ($6.50 or $6.25 per 1k) and API Check runs ($2.60 or $2.50 per 10k) are added to the next invoice if you exceed plan limits, and additional Uptime Monitors cost $8 per block of 25. A visitor asking about hidden costs would need to piece this together from the FAQ and the plan comparison table rather than finding one clear statement, so an AI risks giving an incomplete answer by saying 'no hidden fees' when usage-based overages can add unexpected charges.

*What an AI extracts today (paraphrase — do not string-match):*

> No setup fee is mentioned; costs beyond plan price come from overages on browser/API check runs and additional monitors, billed per usage.

*Replace or surface with this:*

```
There's no setup fee mentioned on Checkly's pricing page, but usage-based overages can add to your bill: on the Starter plan, Browser Check overages are $6.50 per 1k runs and API Check overages are $2.60 per 10k runs; on the Team plan they're $6.25 per 1k and $2.50 per 10k respectively. Additional Uptime Monitors beyond your plan's included amount cost $8 per block of 25, and these overage charges are added to your next billing cycle's invoice automatically.
```

## Questions only the site owner can answer

The page contains no answer to these, so neither this brief nor you can supply one.
Do not guess and do not write around them — surface them to the owner.

- Do you offer refunds, and if so under what conditions (time window, prorated, none)?
- Can customers cancel their subscription at any time, and what happens to access/billing upon cancellation?
- Are there any setup fees, onboarding fees, or one-time charges beyond the listed plan prices and overages?
- Can you provide specific customer names, logos, or case studies approved for use on the pricing page?

---

Generated by FAQLens from an audit of https://www.checklyhq.com/pricing/. The findings describe that page only.