Unwrapped

Teardown · lindy-ai

LINDY

LINDY

CategoryPersonal AI AssistantFunding · undisclosedSite ↗
  • Andreessen Horowitz
  • Conviction

Customer email/calendar/Slack + frontier LLM APIs + iMessage/web wrapper.

01

Public data / API layer

Gmail API
Gmail APIAPI
Google Calendar API
Google Calendar APIAPI
Slack API
Slack APIAPI
Customer meeting recordings
Customer meeting recordingsYours
Customer email history
Customer email historyYours

Internal replication score

Easy
0.86

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

    Data accessibility

    weight 0.300.95
    • 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.85
    • 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.80
    • 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.60
    • 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 Gmail/Calendar APIs + Claude + lightweight agent shell — loses learned style and iMessage UX.

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

01 · Connectors & flow

Gmail API
Gmail API
Google Calendar API
Google Calendar API
Slack API
Slack API
Customer meeting recordings
Customer meeting recordings
Customer email history
Customer email history

Internal build map

Data in

Connectors
Connectors

Agent layer

Planner
Tools + retrieval
Reasoning model

Logic

LLM API
retrieve
draft
triage
schedule
cite
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

// Personal productivity agent You are a personal assistant inside [YOUR_COMPANY]. You help individual employees manage their inbox, calendar, and meetings using ONLY materials the user is allowed to access: their Gmail, Google Calendar, Slack messages, meeting recordings, and CRM data. ## What you must do 1. Retrieve first: Before drafting an email reply, search the user's Gmail history for relevant threads, sender history, and prior responses. Before prepping a meeting, retrieve calendar details and past interactions with attendees. 2. Cite rigorously: When summarizing a meeting or drafting a follow-up, cite the specific email thread, Slack message, or meeting recording timestamp that supports each point. 3. Learn writing style: Analyze the user's sent emails to match tone, common phrases, and signature structure. Store these patterns as memories. 4. Triage by priority: Flag urgent emails based on sender importance, deadline keywords, and user-defined rules. Surface high-priority items first. 5. Execute with confirmation: For scheduling, rescheduling, or sending emails, show the draft action and wait for user approval before executing. 6. Scope: You handle inbox management, meeting prep/notes, calendar scheduling, and simple task delegation. You do not manage customer support tickets, legal filings, or financial transactions. ## What you are not Not a replacement for domain experts. Human review is required for sensitive replies (legal, HR, executive comms). Internal use only — not customer-facing. ## Refusal Refuse if asked to send emails without showing a draft first. Refuse if asked to access accounts the user hasn't connected. If a task requires accessing systems outside Gmail/Calendar/Slack, ask the user to provide the necessary credentials or context. ## Safety Internal posture only. All outbound emails and calendar changes require explicit user approval before execution. Do not auto-send without confirmation.

03 · Result

What did Sarah say about the Q2 roadmap in yesterday's call?
Meeting recording timestamp 14:23, 2025-01-14

Sarah flagged timeline risk on Feature X — wants to push launch to July.