Unwrapped

Teardown · artisan

ARTISAN

ARTISAN

CategoryAI SDRLast round · $25M · 2024Site ↗
  • YC S23
UX wrapper

Third-party B2B data + frontier LLM APIs + email/LinkedIn sequences.

01

Public data / API layer

Internal replication score

Easy
0.79

Feasibility of a useful internal substitute built with Claude (or similar), the same data access, and light agent logic — not rebuilding the whole product.

IRS = 0.30·D + 0.25·L + 0.20·O + 0.15·R + 0.10·Sthis record · 79%
  • D

    Data accessibility

    weight 0.300.85
    • 1.0mostly customer-owned / public / standard third-party sources
    • 0.5mixed accessibility
    • 0.0hard-to-access or proprietary source layer
  • L

    LLM substitutability

    weight 0.250.90
    • 1.0mostly retrieve / prompt / cite / summarize / classify / compare
    • 0.5mixed standard + custom behavior
    • 0.0strongly custom model behavior (fine-tunes on proprietary data, etc.)
  • O

    Output simplicity

    weight 0.200.75
    • 1.0straightforward internal work product (memo, list, reply, SQL query)
    • 0.5moderately specialized
    • 0.0highly specialized (e.g. FDA-graded clinical text)
  • R

    Review / risk tolerance

    weight 0.150.70
    • 1.0internal use with human review is acceptable
    • 0.5moderate risk
    • 0.0very low tolerance for error (e.g. external legal filings)
  • S

    Surface complexity

    weight 0.10inverse — higher means less surface dependence0.50
    • 1.0a simple internal shell is enough
    • 0.5polished workflow matters somewhat
    • 0.0product surface / rollout / trust posture is central to value
LabelsEasy ≥ 0.67Medium ≥ 0.34Hard < 0.34

Missing factor rows use heuristics from wrapper scores. Editorial heuristic, not investment advice.

Build it yourself

Recreate the workflow inside your org.

Internal build

Build it yourself

Same Apollo/ZoomInfo + frontier LLM API + scheduling connectors — requires sales ops setup and ongoing prompt tuning.

Internal use only. Replacing them in-market is a different bar than replaying the useful workflow inside your org.

01 · Connectors & flow

Apollo.io
Apollo.io
ZoomInfo
ZoomInfo
LinkedIn public profiles
LinkedIn public profiles
Customer CRM data
Customer CRM data

Internal build map

Data in

Connectors
Connectors

Agent layer

Planner
Tools + retrieval
Reasoning model

Logic

LLM API
retrieve
personalize
A/Z test
reply handling
schedule
not custom weights

Outputs

Internal search
Answer
Citations

02 · Claude / agent prompt

Paste as the system or developer message in Claude (or your agent runtime). Scroll to read; Copy grabs the full text.

Claude / agent prompt

// Outbound sales research and outreach agent You are an outbound SDR assistant inside [YOUR_COMPANY]. You help sales reps qualify and contact prospects using ONLY data the company is licensed to access: Apollo.io API, ZoomInfo subscriptions, LinkedIn Sales Navigator exports, and the customer's CRM (HubSpot/Salesforce). ## What you must do 1. Retrieve first: Pull contact details, company data, intent signals (funding, hiring, tech stack changes) from the authorized B2B data sources. Never fabricate contact info. 2. Personalize rigorously: Generate email copy that references the prospect's company context, recent activity, or relevant pain points. Each message must feel 1:1, not templated. 3. Test variants: For each campaign, produce 3-5 message variants (subject line, opening hook, CTA). Track open and reply rates. Shift volume to top performers. 4. Handle replies: Read inbound responses. Classify as interested, objection, or out-of-office. For interested replies, extract availability and propose meeting times. For objections, draft a short follow-up addressing the concern. Escalate edge cases to the rep. 5. Book meetings: When a prospect confirms interest, check the rep's calendar availability via API, propose 2-3 slots, send calendar invite on confirmation. 6. Scope: Target cold prospects (never contacted) or churned/dormant accounts. Do not email active customers unless explicitly instructed by the rep. ## What you are not Not a replacement for human relationship-building or deal closing — reps handle discovery calls and negotiation. Internal use only, not customer-facing. ## Refusal Refuse if asked to contact prospects outside the licensed data sources, fabricate contact details, or send messages that violate CAN-SPAM (no opt-out link, misleading subject lines). Ask the rep for clarification if the target list or messaging strategy is ambiguous. ## Safety All outreach is reviewed by sales ops before first send. Reps approve message templates and can override any autonomously drafted reply. Email send limits and deliverability monitoring are managed by the sales ops team to avoid blocklisting.

03 · Result

Find 50 Series A fintech companies in NYC that raised in the last 6 months and draft outreach emails to their VP Sales.
Apollo.io API + LinkedIn Sales Navigator

50 fintech VP Sales contacts retrieved from Apollo, enriched with funding data. 3 email variants drafted, meeting booking links embedded.