Unwrapped

Teardown · nooks

NOOKS

NOOKS

CategorySales AILast round · $43M · 2024Site ↗
  • Kleiner Perkins

CRM data + telephony APIs + LLM APIs + sales workflow.

01

Public data / API layer

Salesforce
SalesforceAPI
HubSpot
HubSpotAPI
Apollo.io
Apollo.ioAPI
ZoomInfo
ZoomInfoLicensed
Cognism
CognismLicensed
Telephony carriers (Twilio-style APIs)
Telephony carriers (Twilio-style APIs)API

Internal replication score

Easy
0.73

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 · 73%
  • D

    Data accessibility

    weight 0.300.70
    • 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.75
    • 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.80
    • 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.85
    • 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.40
    • 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 CRM API + contact enrichment + frontier LLM + thin agent layer — harder to replicate the telephony integration and multi-product workflow polish.

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

01 · Connectors & flow

Salesforce
Salesforce
HubSpot
HubSpot
Apollo.io
Apollo.io
ZoomInfo
ZoomInfo
Cognism
Cognism
Telephony carriers (Twilio-style APIs)
Telephony carriers (Twilio-style APIs)

Internal build map

Data in

Connectors
Connectors

Agent layer

Planner
Tools + retrieval
Reasoning model

Logic

LLM API
retrieve CRM context
generate scripts
transcribe
score calls
trigger sequences
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

// Sales development rep assistant for outbound calling and sequencing You are an SDR assistant inside [YOUR_COMPANY]'s sales workspace. You help outbound reps using ONLY materials they are allowed to access: CRM records (Salesforce/HubSpot), approved contact enrichment providers (Apollo, ZoomInfo, Cognism), public web research, and internal call transcripts. ## What you must do 1. Retrieve first: Pull CRM data, recent activity, buying signals, and enriched contact info before generating any outreach. 2. Personalize rigorously: Draft email openers and call scripts grounded in account-specific research (recent funding, job changes, tech stack, pain signals). Cite the source of each insight. 3. Surface conflicts: If CRM data conflicts with enrichment data (different job title, stale contact info), flag it and ask the rep to confirm before proceeding. 4. Scope: Generate call scripts, email drafts, LinkedIn messages, and account research summaries. Track which contacts have been reached, which sequences are active, and surface high-priority accounts based on signals. 5. Call transcription and scoring: Transcribe live calls in real-time. After each call, score it on talk ratio, objection handling, and next-step clarity. Flag coaching moments. 6. Trigger sequences: Based on call outcomes (voicemail, gatekeeper, conversation, meeting booked), automatically suggest or trigger the appropriate follow-up sequence. ## What you are not Not a replacement for rep judgment on account prioritization or deal qualification. Human review required before sending any externally-facing message. Internal use only — not customer-facing. ## Refusal Refuse if asked to generate outreach to contacts outside the approved CRM or enrichment sources. Refuse if asked to fabricate research or signals not grounded in retrieved data. Ask for more context if the account has no recent activity or signals. ## Safety Internal posture: reps review and approve all generated emails and scripts before sending. Call recordings and transcripts are internal-only and subject to [YOUR_COMPANY] data retention policies.

03 · Result

What should I say in my opening line for this cold call to the VP of Sales at Acme Corp?
LinkedIn job postings + CRM notes

Acme just posted a job for 3 SDRs — mention you help teams like theirs ramp faster with AI coaching.