A
AI safety company building reliable, interpretable, and steerable AI systems
1. Inferred ICP Pre-generated
COMPANY SIZE: 20–1000 employees, Series A–D, $5M–$200M ARR
IDEAL ROLE: CTO, Head of AI Product, VP of Engineering, or Principal ML Engineer at companies building AI into compliance-sensitive or high-stakes user-facing workflows
INDUSTRY: LegalTech, HealthTech, FinTech, Enterprise SaaS, government tech, HR automation — any domain where AI output errors carry real consequences
TRIGGER SIGNALS: Compliance requirement blocks use of certain LLM providers, GPT content safety failures in production, building agentic AI that requires reliable instruction-following, enterprise customer asking for AI explainability
2. Sample Prospects 5 profiles
Nathan Blum
Head of AI Product
Verdant Health · 51–200
"Building clinical decision support AI — every output goes in front of a licensed provider"
🎯 Published blog post about evaluating AI safety for healthcare — explicitly referenced Anthropic's Constitutional AI
Jasmine Torres
VP of Engineering
Compliancely · 51–200
"Automating compliance documentation for financial services — clients are Fortune 500 banks"
🎯 Job posting for "AI Safety Engineer" — their first dedicated AI safety role, triggered by enterprise customer pressure
Kwame Asante
CTO
Jurisfy · 11–50
"AI paralegal tool for mid-size law firms — malpractice risk makes model reliability everything"
🎯 Twitter thread about their migration off GPT-4 after a hallucination caused a client escalation
Lila Schwartz
Principal ML Engineer
Hired.ai · 51–200
"AI-assisted job matching at scale — screening 100K resumes per month"
🎯 LinkedIn post about EEOC compliance requirements for AI hiring tools — evaluating model providers
Ravi Patel
Co-Founder & CEO
Govcraft · 11–50
"AI workflow automation for state and local government — FedRAMP process underway"
🎯 Press release about FedRAMP authorization process — requires auditable, explainable AI outputs
Sample illustrative profiles — run a live teardown of your company to get your own.
3. Outreach Angle Ready
POSITIONING ANGLE
Don't compete on benchmark scores — Claude's differentiation is safety, controllability, and long-context reliability for high-stakes workflows. The buyers you want are already burned by a GPT production incident or blocked by an enterprise security review. Lead with "what happens when the model is wrong" as the framing question, not "which model scores higher."

SUBJECT LINE
Your next compliance review will ask about your LLM provider

OPENING (first 2 sentences)
Noticed you're building AI into a workflow where errors carry real-world consequences — which means your model provider choice will eventually come up in a security review or enterprise RFP. The teams we work with in regulated verticals typically switch providers not because of benchmarks but because they need audit trails, predictable refusals, and a vendor whose safety commitments are contractually documented.
4. Signals to Monitor 5 signals
1. LINKEDIN: "AI Safety" or "Responsible AI" engineer hire → formalizing AI governance, vendor choice under scrutiny
2. JOB BOARDS: Enterprise SaaS companies listing "AI compliance" or "AI risk" roles → internal pressure to document model choices
3. TWITTER/X: CTO or founder posts about GPT hallucination in production or "we need more controllable AI" → pain is active and public
4. COMPANY BLOG: Post about responsible AI, model evaluation framework, or "how we test AI safety" → buying signal disguised as thought leadership
5. CRUNCHBASE: Series B+ in HealthTech, LegalTech, or FinTech → enterprise customer pressure on AI provenance arriving with scale

More teardowns