Scrunch AI

# Scrunch AI review

Scrunch AI extends beyond visibility monitoring. It tracks prompts, citations, competitors and personas; audits pages; reports agent traffic; and offers AXP, an infrastructure layer that serves an AI-oriented representation of site content to retrieval agents. That breadth can connect diagnosis to delivery. It also creates more governance risk than a read-only dashboard.

The first buying decision is unexpectedly basic: determine which official price table is active. The canonical pricing content shows Starter at $300 month-to-month or $250/month billed annually, with 350 custom prompts, 1,000 industry prompts, three personas, five page audits and three users. Growth is $500/$417 with 700 custom prompts, 2,500 industry prompts, five personas, ten audits and five users. Another current official FAQ describes Core at $250 with 125 prompts and four LLMs, plus different trial terms. We preserve that contradiction rather than choosing the more convenient version.

Distinctive strength

Scrunch combines four surfaces that are often separate purchases: AI-answer monitoring, page-level recommendations, agent-traffic attribution and an optional delivery layer for AI retrieval systems. For a mature team, that can shorten the path from “we are not cited” to a governed content change and measurement cycle.

Where it stops being an advantage

More layers create more failure modes. A visibility monitor can be wrong without changing the website. A page-audit recommendation can produce low-value edits. AXP can serve an AI-facing mirror of content, so a stale or poorly governed source of truth becomes operational, not merely analytical.

Pricing is also multidimensional. Custom prompts, industry prompts, personas, page audits, users and potentially enterprise features are separate capacity gates. A buyer should size the first exhausted resource, not the headline prompt total.

Prompt engines, not prompts, drive the bill

On the published Starter table, 350 custom prompts are the scarce, buyer-controlled allowance; the additional 1,000 industry prompts are a different inventory. If a team tracks 25 commercial topics across four answer engines and wants one observation per topic-engine pair, a single sweep consumes 100 prompt-engine observations. Three comparable sweeps already require 300. That leaves little room for regional variants, troubleshooting or an additional competitor set unless Scrunch counts the allowance differently.

This is planning arithmetic, not a claim about Scrunch's billing implementation. The trial must establish whether one saved prompt is counted once, once per engine, once per run, or under another denominator. A headline allowance cannot support a budget decision until that denominator is known.

Which Scrunch price is real?

The public record is conflicted. Capture the actual checkout page with date, monthly/annual basis, renewal amount, trial card requirement, prompt definitions and included engines. Do not rely on an article that silently combines Starter/Growth packaging with older Core/Explorer terms.

Annual amounts are commitments, not month-to-month prices. The displayed 17% reduction should be represented as annual billing, never as a permanent monthly discount independent of term.

What are custom and industry prompts?

The pricing page separates 350 custom prompts from 1,000 industry prompts on Starter. The useful question is control: which prompts can the buyer edit, which are supplied by Scrunch, how are industry prompts selected and updated, and can both sets be audited down to exact model responses?

A large industry panel is valuable only if it maps to the buyer’s real market. During trial, compare a frozen custom panel with the supplied industry panel. Measure overlap, relevance and whether the same finding survives both.

Does AXP create SEO or brand risk?

Scrunch says AXP serves an AI-optimized mirror to AI retrieval agents without changing the human experience and does not rely on `llms.txt`. That is a material architectural choice. Before activation, legal, brand, security and SEO owners should know exactly which agents receive alternate content, how it is generated, how canonical source changes propagate, how rollback works and how divergence is detected.

The correct use is a governed derivative of approved brand truth. It should not become a hidden publishing channel where an optimization agent can state claims that the public site cannot support.

The AXP approval gate

Ask Scrunch to demonstrate one complete change cycle before enabling broad delivery: identify the canonical source, show the generated representation, name the eligible agents, approve the change, observe delivery, update the source page, detect the drift and roll back. A buyer should be able to answer who can publish, what is logged and how quickly the AI-facing representation can be withdrawn. If any of those steps depends on an undocumented support intervention, AXP is not yet a routine production control for that team.

Can agent traffic and citations be trusted?

Use independent controls. Compare Scrunch citation extraction against saved responses, and compare agent-traffic events against edge/server logs where policy permits. Attribution should distinguish a verified agent request from a generic user-agent string and should never be interpreted as a human conversion without additional evidence.

Customer outcome numbers and “trusted by” lists are vendor claims. They do not establish the buyer’s expected uplift.

Security and privacy

Scrunch states that it is SOC 2 Type II compliant and supports SAML/OIDC on Enterprise. Its public privacy policy distinguishes general personal information from Customer Data governed by commercial agreements. The consent/security material says Scrunch collects AI responses and citations but not personal information from consumers issuing prompts on public AI systems.

Procurement should still inspect the actual SOC 2 scope, customer-data terms, retention, subprocessors, breach commitments and API controls. Enterprise-only API and identity features should be priced as part of the required package.

Scrunch or a monitoring-only alternative?

• Choose Scrunch when monitoring must connect to audits, agent traffic and a governed delivery layer.
• Choose Profound when prompt-demand intelligence and governed agents are the priority.
• Choose Peec AI when the team needs a simpler brand/citation visibility matrix.
• Choose ZipTie.dev when self-serve monitoring-to-optimization at a lower public price is sufficient.

Test AXP as a governed intervention

1. Record checkout terms and resolve the plan conflict.
2. Freeze 50 custom commercial prompts.
3. Compare them with the supplied industry prompt set.
4. Replay a stratified response sample manually.
5. Reconcile mentions, citations, sentiment and competitors independently.
6. Human-review every page-audit recommendation.
7. Compare agent-traffic events with first-party server evidence.
8. Model persona and prompt allowance expansion.
9. Review AXP source, serving, approval, drift and rollback controls.
10. Inspect SOC 2 scope, API, SSO, retention and customer-data terms.

The pilot that earns an AXP review

Trial the monitoring and audit layer before discussing AXP. If the evidence is reproducible and recommendations survive human review, run an architectural review of one non-critical content set. Do not let a bundled delivery feature turn a monitoring trial into an ungoverned publication decision.

Continue through the AI SEO directory, compare Profound vs Scrunch AI, and read how to validate AI visibility data.

Our Scrunch verdict

Scrunch is differentiated because it spans measurement, recommendations, attribution and AI-facing delivery. It can justify a premium for teams ready to govern all four. It is not ready for an unqualified buying recommendation while official plan/trial pages conflict, and AXP should be treated as infrastructure with approval and rollback requirements—not as another dashboard toggle.

Official sources

• Scrunch pricing ↗
• Scrunch AI-readable pricing content ↗
• Scrunch pricing FAQ ↗
• Scrunch Help Center ↗
• How AXP serves content ↗
• Scrunch Privacy Policy ↗
• Scrunch security and consent information ↗

Sources checked 2026-08-28. Verify current plan and trial at checkout before any purchase.