Public Case Study Depth Agent avatar

Public Case Study Depth Agent

Pricing

Pay per event

Go to Apify Store
Public Case Study Depth Agent

Public Case Study Depth Agent

Analyze one public case study, customer story, or success story page for customer, industry, challenge, solution, product, implementation, quantified results, quotes, risks, evidence, and change hashes.

Pricing

Pay per event

Rating

0.0

(0)

Developer

jack su

jack su

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

Extract structured evidence from one public case study, customer story, success story, or customer spotlight page: customer hints, industry, segment, challenge, solution, product mentions, implementation details, quantified result metrics, quotes, stakeholders, timeline hints, before/after evidence, risks, evidence URLs, and stable change hashes.

This Actor is built for AI agents, sales enablement, partnerships, customer marketing, competitive research, vendor evaluation, and GTM teams that need to understand what a single public customer story actually proves without crawling a full website.

What It Returns

  • Case study title and type, customer name hints, industry hints, company size and region hints.
  • Challenge, solution, implementation, product mention, before/after, and timeline evidence.
  • Quantified result claims such as percentages, time saved, cost reduction, speed increases, revenue impact, or ROI.
  • Customer quotes, stakeholder/title hints, related case study links, optional focus-term matches, evidence snippets, evidence URLs, and a stable caseStudyHash.
  • Risk labels and missing fields when the page lacks named customer, challenge, solution, metrics, or quote evidence.

Pricing Behavior

The Actor uses pay-per-event pricing and only charges the useful result event when it finds useful public case study depth evidence.

Paid event:

  • useful-case-study-depth-result

It does not charge the useful event for:

  • invalid or private-network URLs;
  • failed fetches;
  • customer listing pages with no visible case-study narrative;
  • lead magnets, PDFs, press pages, or generic pages without useful case-study depth signals;
  • focusTerms misses;
  • unchanged records when you pass a previous caseStudyHash.

apify-default-dataset-item is intentionally not used.

Scope And Safety

  • Public HTTP/HTTPS pages only.
  • Private-network hosts, credentials, query strings, fragments, path parameters, and token-like account paths are rejected.
  • JavaScript is not executed.
  • Forms are not submitted.
  • PDF files, gated downloads, lead magnet assets, customer directory pages, related case links, images, and external assets are not fetched.
  • The Actor does not discover case studies from a customer page, scrape contacts, enrich companies, identify emails or phone numbers, or build CRM profiles.
  • Output is evidence-based and should be reviewed before sales enablement, competitive research, customer marketing, or vendor evaluation.

Example Input

{
"caseStudyPageUrls": [
"https://www.atlassian.com/customers/canva"
],
"focusTerms": [
"Canva"
],
"requestTimeoutSecs": 20
}

Best Use Cases

  • Turn one public case study into AI-ready evidence for account research.
  • Compare case study quality across vendors without reading each page manually.
  • Extract result metrics and quotes for sales enablement or competitive briefs.
  • Monitor case study pages without paying for unchanged results.