Deployment Brief
Start with a candidate list that includes result, story angle, evidence strength, customer fit, permission status, and owner.
Difficulty
Medium
Revenue impact
Medium
Operational impact
Medium
Risk level
Medium
When it runs
Evidence in
What AI prepares
- case study candidate list
- proof packet
- story angle recommendation
- permission and sensitivity flag
- outreach draft
- measurement event for case study pipeline
Decision rules
- Require a clear before-and-after story.
- Score evidence strength before outreach.
- Check permission and sensitivity before drafting public claims.
- Match candidates to sales proof gaps.
- Route all outreach and publication decisions to marketing and account owner review.
Human approval point
What stays human
- Do not automate customer outreach, public claims, permission assumptions, sensitive detail publication, or case study approval without human review.
Quality and stop gates
- Trigger is narrow and observable
- Required evidence is listed
- Human approval point is explicit
- Permission and proof claims are protected
- Measurement plan is defined
How it is measured
- Track candidates identified, candidates approved, outreach sent, interviews booked, case studies published, permissions granted, proof gaps filled, and sales use.
Systems involved
Workflow Dataset Record
Deployment evidence and duplicate boundary
This section is generated from the enriched workflow dataset. It is designed for pilot planning, not as validated outcome evidence.
Buyer Problem
Case study candidates are chosen by enthusiasm instead of strategic fit, evidence quality, permission, and story usefulness.
Economic Logic
The workflow focuses production effort on proof assets that sales can actually use for a market, use case, or objection.
Baseline Metric
case_study_candidate_story_fit
Share of candidates with measurable outcome, narrative arc, ICP fit, customer permission, source evidence, and sales-use case.
Source system: CRM, customer success records, project history, usage analytics, marketing proof-asset tracker
Minimum Viable Pilot
- Duration
- 30 days
- Sample
- Top 25 healthy customers or recent wins
- Owner
- Customer marketing
- Threshold
- Top candidates have evidence, permission path, story angle, and sales-use case before outreach.
Unique Workflow Test
Score top customers for measurable outcome, buyer problem, before/after story, permission path, ICP match, and sales proof gap.
Duplicate Guard
Do not merge with case-study positioning extraction. Candidate selection chooses which story to create; extraction reuses messages from finished stories.
Not Ready If
- Outcome evidence is missing.
- Approval path is unknown.
- Sales proof gaps are not defined.
Claim level: Directional. Sources support workflow mechanics and pilot design unless field evidence is attached.
Influitive Support: Identifying Advocates with AdvocateAnywhere
Advocate identification depends on recognizing known users and passing advocate information into the advocacy platform.
HubSpot Blog: How to Write a Great Value Proposition
Value propositions should be clear, specific, differentiated, deliverable, and grounded in customer needs.
HubSpot Blog: Segmentation, Targeting, and Positioning
Positioning depends on defined segments, target audience, and market position rather than a generic everyone audience.
Keep moving
Where this workflow connects next
A useful AI build rarely lives on one page. Check the surrounding workflow, the decision rule, and the deployment path before you commit budget.
Workflow group
Customer Success
Compare the nearby workflows that usually break before or after this one.
OpenDecision tool
Automate vs. keep manual
Check which parts should stay human before this workflow touches customers or records.
OpenIndustry fit
Browse industries
See how this workflow changes by revenue model, buyer urgency, delivery risk, and customer handoff.
OpenService path
AI Deployment Services
Compare the practical ways ADA can help turn one workflow into a working deployment.
OpenRevenue review
Request a workflow review
Bring this workflow and the business number it should move.
OpenTL;DR
A case study candidate needs more than a happy customer. You need a clear story, usable evidence, permission, and sales relevance.
What is case study candidate selection?
Case study candidate selection is the process of identifying customers who have enough evidence, fit, story, and permission potential to become a useful customer story.
Who is this workflow for?
- Agencies, consultants, SaaS companies, service firms, and professional businesses that need stronger proof for sales and SEO.
- Marketing teams that need customer stories but do not want to ask the wrong customer.
- Account owners who know which customers are happy but need a structured proof review.
What breaks in the manual process?
The manual process fails when case studies are chosen by whoever is easiest to ask. The resulting story may be vague, unsupported, or not useful for the sales conversations that need proof.
How does the AI-enabled process work?
The workflow reviews outcomes, feedback, segment, use case, proof gap, relationship context, permission status, and sensitivity. It prepares a ranked candidate list and proof packet for review.
What does this look like in practice?
Example scenario: A professional service client completes an onboarding automation project with clear before/after process data. The workflow assembles the proof, flags permission needs, suggests a story angle around missed inquiry reduction, and routes the candidate to marketing and the account owner.
What decision rules should govern this workflow?
- Require a clear before-and-after story.
- Score evidence strength before outreach.
- Check permission and sensitivity before drafting public claims.
- Match candidates to sales proof gaps.
- Route all outreach and publication decisions to marketing and account owner review.
What are the implementation steps?
- Trigger: A customer shows strong results, gives positive feedback, renews, expands, completes a successful project, or matches a strategic proof gap.
- Inputs collected: customer outcome evidence, before and after context, customer segment and fit, story angle, sales proof gap, permission and sensitivity status, account relationship notes, marketing review rules.
- AI/system action: The system checks source evidence, prepares the proof or feedback output, and flags permission, claim, context, or owner-review requirements.
- Human review point: Marketing and account owners review candidate fit, evidence, customer sensitivity, claim strength, permission, outreach, and publication plan.
- Output delivered: case study candidate list, proof packet, story angle recommendation, permission and sensitivity flag, outreach draft, measurement event for case study pipeline.
- Measurement logged: Track candidates identified, candidates approved, outreach sent, interviews booked, case studies published, permissions granted, proof gaps filled, and sales use.
Required inputs
- customer outcome evidence
- before and after context
- customer segment and fit
- story angle
- sales proof gap
- permission and sensitivity status
- account relationship notes
- marketing review rules
Expected outputs
- case study candidate list
- proof packet
- story angle recommendation
- permission and sensitivity flag
- outreach draft
- measurement event for case study pipeline
Human review point
Marketing and account owners review candidate fit, evidence, customer sensitivity, claim strength, permission, outreach, and publication plan.
Risks and stop rules
- customer asked without enough proof
- sensitive details exposed
- case study based on weak or unsupported claims
- sales usefulness ignored
Stop the workflow when permission is missing, claims are unsupported, customer issues are unresolved, sensitive details are involved, or the next action would create a public proof, customer ask, or relationship-sensitive message without approval.
Best first version
Create a candidate list with result, story angle, evidence strength, customer fit, permission status, and owner.
Advanced version
The advanced version maps candidates by industry, buyer persona, workflow type, keyword target, proof gap, renewal status, and public-use restrictions.
Related workflows
- AI Workflow for Customer Advocate Identification
- AI Workflow for Testimonial Request
- AI Workflow for Account Value Recap
- AI Workflow for Client Reporting
- AI Workflow for Buyer Language Extraction
Measurement plan
Track candidates identified, candidates approved, outreach sent, interviews booked, case studies published, permissions granted, proof gaps filled, and sales use.
What not to automate
Do not automate customer outreach, public claims, permission assumptions, sensitive detail publication, or case study approval without human review.
FAQ
What is case study candidate selection?
It is the process of identifying customers with enough evidence, fit, story, and permission potential to become a useful customer story.
What can AI prepare?
AI can prepare candidate rankings, proof packets, story angles, sensitivity flags, and outreach drafts.
What should stay under human review?
Candidate fit, evidence strength, claims, permission, outreach, sensitivity, and publication plan should stay under marketing and account review.
What is the simplest first version?
Create a candidate list with result, story angle, evidence strength, customer fit, permission status, and owner.
How should this workflow be measured?
Measure candidates, approvals, outreach, interviews, published stories, permissions, proof gaps filled, and sales use.
Related Workflow Group
AI Workflows for Customer Success
Compare this workflow against nearby operating problems before choosing the first build. The group shows what usually breaks together, what evidence is needed, and where review still matters.
View Workflow GroupFurther Reading
AI customer health scoring workflow
A field report on customer risk, retention signals, owner review, and measurable follow-up.
