Blueprint Playbook for AudioEye

Who the Hell is Jordan Crawford?

Founder of Blueprint. Built a business by scraping 25M+ job posts to find company pain points. Believes the Predictable Revenue model is dead. Thinks mounting an AI SDR on outdated methodology is like putting a legless robot on a horse—no one gets anywhere, and it still shits along the way.

The core philosophy is simple: The message isn't the problem. The LIST is the message. When you know exactly who to target and why they need you right now, the message writes itself.

The Old Way (What Everyone Does)

Let's be honest about what AudioEye's GTM team is probably doing right now. Buying lists of "VP of Digital" contacts at mid-market companies, adding surface-level personalization, then blasting messages about WCAG compliance features. Here's what that actually looks like:

The Typical AudioEye SDR Email:

Subject: Making your website accessible Hi [First Name], I noticed [Company] has a great digital presence. With ADA lawsuits on the rise, ensuring your website meets WCAG 2.1 AA standards is more important than ever. AudioEye helps companies like yours achieve and maintain web accessibility compliance through our automated platform. We serve over 122,000 customers including Samsung and Calvin Klein. Would you be open to a quick call to discuss how we can help [Company] avoid accessibility lawsuits? Best, [SDR Name]

Why this fails: Every accessibility vendor sends this exact email. "ADA lawsuits are rising" is a headline the prospect has read 50 times. There's zero indication you know anything about THEIR specific exposure. You're just another vendor in the inbox waving the compliance boogeyman. Delete.

The New Way: Intelligence-Driven GTM

Blueprint flips the entire approach. Instead of warning prospects about generic lawsuit trends, you show them their specific exposure with data they can verify. You become the person who sees around corners, not another vendor selling fear.

This requires two fundamental shifts:

1. Hard Data Over Soft Signals

Stop: "ADA lawsuits are on the rise" (everyone knows this, it's a headline)

Start: "Your site runs accessiBe — the vendor the FTC fined $1M in January 2025 for deceptive WCAG compliance claims. 503 of 2,014 ADA lawsuits in H1 2025 targeted sites using overlays like yours." (Wappalyzer detection + FTC ruling + EcomBack data)

2. Mirror Situations, Don't Pitch Solutions

PQS (Pain-Qualified Segment): Reflect their exact situation with such specificity they think "how did you know?" Use federal court filings, FTC enforcement actions, and industry-specific lawsuit data with dates and case numbers.

PVP (Permissionless Value Proposition): Deliver immediate value they can use today — their competitor overlay detected, their lawsuit history surfaced, their WCAG error profile scanned — whether they buy or not.

AudioEye PQS Plays: Mirroring Exact Situations

These messages demonstrate such precise understanding of the prospect's current situation that they feel genuinely seen. Every claim traces to a specific public data source — federal court records, FTC enforcement actions, or published industry reports.

PQS 8.6/10

Play 1: "Your Accessibility Vendor Was Just Fined by the FTC"

What's the play?

Use Wappalyzer's technology detection API to identify the 13,900+ websites currently running accessiBe's overlay widget. Cross-reference with the FTC's January 2025 enforcement action that fined accessiBe $1,000,000 for making deceptive claims about their WCAG compliance capabilities. Then layer in EcomBack's data showing 25% of all ADA website lawsuits in 2025 explicitly targeted sites using accessibility overlay widgets.

The prospect learns three things simultaneously: (1) their specific vendor was penalized by a federal agency, (2) the overlay technology itself is being treated as evidence of non-compliance by plaintiff law firms, and (3) there's a quantified 25% correlation between overlays and lawsuits.

Why this works

Most accessiBe customers don't know about the FTC fine — it didn't make mainstream news. Learning that your vendor was federally penalized for the exact service they're providing you creates immediate credibility anxiety. The prospect can verify every claim: the FTC ruling is public record, Wappalyzer confirms their tech stack, and EcomBack publishes the overlay-lawsuit correlation. You're not selling fear — you're delivering verifiable facts about their specific vendor relationship.

Data Sources
  1. Wappalyzer API (wappalyzer.com) — Detects accessiBe/UserWay overlay code on any website. Returns: website URL, technology name, version, company details. 13,900+ accessiBe sites indexed.
  2. FTC Enforcement Database (ftc.gov) — January 2025 ruling: $1M fine against accessiBe for deceptive WCAG compliance marketing. Case details, fine amount, and violation specifics are public record.
  3. EcomBack ADA Lawsuit Reports (ecomback.com) — Quarterly reports tracking all ADA website lawsuits. H1 2025: 2,014 cases, 25% targeted overlay-using sites. Breakdown by industry.

The message:

Subject: The FTC just fined your accessibility vendor $1M [First Name] — In January 2025, the Federal Trade Commission fined accessiBe $1,000,000 for making deceptive claims about their WCAG compliance capabilities. [Company] is currently running accessiBe across your digital properties. This matters more than a headline: 503 ADA website lawsuits in the first half of 2025 specifically targeted sites using accessibility overlays. The 40 law firms that filed every ADA website case this year now use automated detection for overlay code as a signal that the underlying site isn't truly compliant. AudioEye takes a fundamentally different approach — automated code-level fixes verified by human testers from the disability community, not a frontend widget that masks issues. Happy to run a free scan of [company.com] to show what your overlay is missing.
PQS 8.4/10

Play 2: "Your Website's Accessibility Error Profile"

What's the play?

Run AudioEye's own WCAG detection engine against the prospect's website (any public site can be scanned without permission). Cross-reference the results against AudioEye's 2025 Digital Accessibility Index benchmarks — which analyzed 15,000 sites across industries — and EcomBack's lawsuit data showing which industries are most targeted.

The message leads with a concrete, company-specific finding: "We scanned [company.com] and found [X] WCAG issues." This is not a generic warning about lawsuits — it's a diagnostic report specific to their website.

Why this works

You're delivering a free accessibility audit in the first email. The prospect gets actionable data about their own website — error count, error types, severity — before you ask for anything. Even if they don't buy, they learned something about their digital exposure. Then you contextualize it: "Retail sites average 350 WCAG errors per page and face 29% of all ADA lawsuits." Their specific error count + their industry's lawsuit rate = a personalized risk calculation they can't ignore.

Data Sources
  1. AudioEye WCAG Scanner — Proprietary scanning engine that tests 32 WCAG criteria against any public website. Returns: error count, error types (low contrast, missing alt text, missing form labels), severity, affected pages.
  2. AudioEye 2025 Digital Accessibility Index (audioeye.com) — 15,000 sites analyzed. Industry benchmarks: retail 350.1 issues/page, healthcare 272/page, hospitality 41% with keyboard navigation failures.
  3. WebAIM Million Report (webaim.org) — Annual analysis of top 1,000,000 homepages. 2025: 94.8% fail WCAG, 51 avg errors/page, 6 error types account for 96% of all issues.

The message:

Subject: [Company.com] WCAG scan: what we found in 60 seconds [First Name] — I ran a quick accessibility scan on [company.com] using AudioEye's detection engine — the same technology that analyzed 15,000 sites for our 2025 Digital Accessibility Index. We detected [X] WCAG issues across your homepage alone. [Industry] sites averaged [X] errors per page in our index — the [highest/second-highest] of any sector we analyzed. This matters because ADA website lawsuits surged 37% in the first half of 2025, with [industry] accounting for [X]% of the 2,014 cases filed. The 40 law firms behind every filing use automated scanners just like ours — if we found [X] issues in 60 seconds, they already have too. I can send you the full scan report with issue severity, affected pages, and a prioritized fix list. Want me to forward it?

AudioEye PVP Plays: Delivering Immediate Value

These messages provide actionable intelligence before asking for anything. The prospect can use this value today whether they respond or not. That's the power of permissionless value.

PVP 8.8/10

Play 1: "Your Accessibility Overlay Is a Lawsuit Magnet"

What's the play?

Combine Wappalyzer's technology detection (which identifies 80,000+ UserWay sites and 13,900+ accessiBe sites) with EcomBack's finding that 25% of ADA website lawsuits specifically target sites with overlay widgets installed. Layer in the prospect's industry-specific lawsuit rate from EcomBack's quarterly reports.

The counterintuitive insight: overlay widgets don't reduce lawsuit risk — they may increase it. Plaintiff law firms now scan for overlay code as a signal that the site has known accessibility problems being cosmetically masked rather than structurally fixed. The prospect gets a risk analysis they didn't know they needed.

Why this works

This is genuinely non-obvious. Companies buy overlays believing they reduce legal exposure. Showing them that 1 in 4 ADA lawsuits targets overlay-using sites — and that plaintiff law firms specifically look for overlay code — is a "wait, what?" moment. You're not pitching AudioEye; you're correcting a dangerous misconception with verifiable data. The prospect can check Wappalyzer to confirm their own tech stack, read EcomBack's report to verify the 25% stat, and review the FTC ruling themselves. Every claim is independently verifiable.

Data Sources
  1. Wappalyzer API (wappalyzer.com/api) — Technology detection across the web. Fields: website URL, technology name (accessiBe, UserWay, AudioEye), category, company name, contact details. API access from $100/mo.
  2. EcomBack ADA Lawsuit Reports (ecomback.com) — 2,014 ADA lawsuits in H1 2025 (37% surge YoY). 25% targeted overlay-using sites. Industry breakdown: Restaurant/Food 30.5%, Apparel 28.8%, Beauty 8.9%, Medical 7.2%.
  3. FTC accessiBe Ruling (ftc.gov) — January 2025: $1M fine for deceptive WCAG compliance claims. Establishes federal precedent that overlay marketing is misleading.

The message:

Subject: [Company]'s accessibility overlay may be increasing your lawsuit risk [First Name] — [Company] currently uses [accessiBe/UserWay] on your website. Here's something counterintuitive: in the first half of 2025, 25% of all ADA digital accessibility lawsuits — 503 of 2,014 cases — targeted sites with accessibility overlay widgets installed. The FTC fined accessiBe $1M in January 2025 for misrepresenting their WCAG compliance capabilities. Your industry ([industry]) accounted for [X]% of all ADA website lawsuits in H1 2025, with a 37% surge over the prior year. Plaintiff law firms now use automated scanners that flag overlay code as a signal the underlying site has known issues being masked rather than fixed. AudioEye replaces overlays with actual code-level remediation — fixing the WCAG violations at the source. Would it be worth 15 minutes to show you what our scanner finds on [company.com] vs. what [overlay vendor] claims to cover?
PVP 9.4/10 ⭐

Play 2: "Your ADA Case Makes You a Priority Re-Filing Target"

What's the play?

Search CourtListener (free) or PACER ($0.10/page) for federal ADA website accessibility lawsuits filed in 2023-2025. Extract defendant company names, case numbers, filing dates, and jurisdictions. Cross-reference these defendants with Wappalyzer to see their current accessibility technology stack (or lack thereof).

The critical insight: 40 law firms and 251 plaintiffs are responsible for every ADA website lawsuit filed. These firms maintain databases of prior defendants and systematically re-scan their websites for new violations or regression. Companies that settled once are considered lower-resistance targets for repeat filings. You're telling the prospect something they don't know about their own legal exposure trajectory.

Why this works

This is the Gold Standard PVP. You're referencing their actual federal court case by number. The prospect can verify every claim by searching their own case in CourtListener. Most companies that settle ADA website lawsuits assume the problem is over — they don't know about serial plaintiff re-targeting patterns. You're delivering intelligence that would cost them $10K+ from a law firm: "You're on a re-filing list." The specificity is undeniable (case number, filing date, jurisdiction), the insight is genuinely valuable (re-targeting risk), and the product fit is perfect (AudioEye prevents the violations that trigger re-filing).

Data Sources
  1. CourtListener / RECAP Archive (courtlistener.com) — Free searchable database of millions of federal court filings. Search by: case type (ADA), defendant name, jurisdiction, date range. Fields: case_number, defendant, plaintiff, filing_date, jurisdiction, case_status.
  2. PACER (pacer.uscourts.gov) — Official federal court records system. $0.10/page, $3/document cap. Authoritative source for all federal ADA filings. 4,187 digital accessibility lawsuits in 2024.
  3. EcomBack Serial Plaintiff Analysis (ecomback.com) — Identifies 40 law firms + 251 plaintiffs responsible for all ADA website filings. Documents re-targeting patterns and plaintiff concentration.

The message:

Subject: Your 2024 ADA case makes [Company] a priority re-filing target [First Name] — [Company] appeared as a defendant in Case #[XX-XXXXX], filed [month/year] in [jurisdiction] for ADA website accessibility violations. Here's something your legal team may not have flagged: the 40 law firms and 251 plaintiffs responsible for every ADA website lawsuit in 2025 maintain databases of prior defendants. Companies that have settled once are considered lower-resistance targets for repeat filings. ADA website lawsuits surged 37% in the first half of 2025 to 2,014 cases. Serial plaintiff firms systematically re-scan prior defendants' websites looking for new WCAG violations or regression from previous fixes. AudioEye provides ongoing code-level remediation plus litigation support — including compliance documentation specifically designed to make re-filing unattractive to serial plaintiff firms. Worth a quick conversation about getting [Company] off the re-targeting list?

The Transformation

Notice the difference? Traditional outreach talks about AudioEye's features and generic lawsuit statistics. Blueprint talks about THEIR specific overlay vendor, THEIR court case number, THEIR industry's exact lawsuit rate, and THEIR website's actual WCAG error count.

The shift is simple but profound:

Stop sending messages about what AudioEye does. Start sending intelligence about what they need to know right now. When you lead with "the FTC fined your vendor $1M" or "your Case #XX-XXXXX makes you a re-filing target" instead of "ADA lawsuits are on the rise," you're not another sales email — you're the person who actually did the research.

The data stack here is uniquely powerful for AudioEye: Wappalyzer detects competitor overlays at scale (80,000+ UserWay sites, 13,900+ accessiBe sites). CourtListener/PACER gives you actual defendant names from federal ADA filings. EcomBack quantifies the overlay-to-lawsuit correlation. And AudioEye's own scanning engine provides company-specific WCAG error counts. Combined, these create hyper-targeted outreach that no competitor is doing.

The companies that master this approach don't compete on features. They compete on intelligence.