← Reddit

I built my friend an AI Sales Agent. 300 leads scored, 120 personalized LinkedIn invites, 3 signed deals

Reddit · Illustrious-Bug-5593 · April 18, 2026
A software engineer developed an AI sales agent to automate the repetitive outreach process for a friend in sales development, automating lead research, scoring, personalized LinkedIn outreach, and email drafting while respecting platform engagement caps. The agent was built as ten modular skills and achieved results of 300 leads scored, 120 personalized LinkedIn invites, and 3 signed deals by reading CRM data, analyzing LinkedIn profiles, and managing follow-up workflows. The tool is MIT-licensed, runs locally with no third-party hosting, and operates through natural language commands with human review of all outbound communications before sending.

Detailed Analysis

A software engineer's account of building a custom AI sales agent for a friend engaged in outbound sales represents a practical, ground-level demonstration of how Claude-powered autonomous agents can be deployed to automate complex, multi-step professional workflows. The system, open-sourced under an MIT license on GitHub, integrates with a CRM, Gmail, and LinkedIn through a real browser session, allowing the agent to research leads, score them across fit and engagement dimensions, draft personalized outreach, send connection requests, and classify inbox replies — all within platform-safe daily caps. The reported outcomes are concrete: 300 leads scored, 120 personalized LinkedIn invites dispatched, and 3 signed deals attributed to the pipeline the agent helped build. The agent's architecture centers on ten modular "skills," each encoded as a plain markdown file, covering everything from cold outreach and prospect research to follow-up loops, inbox classification across eight reply categories, and weekly performance reviews. This modularity means the system grew organically, with each new capability added only when a real bottleneck emerged.

The technical backbone of the project is Claude Code, Anthropic's agentic coding and task execution environment, which serves as the runtime harness. However, the engineer is explicit that the skills themselves are harness-agnostic — because they are written in plain markdown, the same agent logic could run inside Cursor, OpenAI's Codex, or any Model Context Protocol-capable environment. This design choice reflects a broader architectural philosophy of building on open, portable standards rather than locking workflows into a single proprietary interface. The LinkedIn integration is particularly notable in its approach to compliance: the agent reuses a warm Chromium session authenticated with the user's real credentials, operates within daily and weekly messaging caps designed to stay below LinkedIn's algorithmic flagging thresholds, and returns personalized notes that reference content the agent actually read from a lead's recent posts. Email output remains in draft form, requiring human review before dispatch — a deliberate design decision that preserves human oversight over the highest-stakes communications.

The broader significance of this project lies in what it demonstrates about the current state of AI agent deployment in knowledge-work contexts. Outbound sales has historically been resistant to full automation precisely because it demands context-sensitivity: a cold LinkedIn note that reads like a template is often worse than no note at all. The agent described here attempts to solve this by grounding personalization in real, freshly scraped data — recent posts, certifications, experience history — rather than mail-merge-style variable substitution. The A/B/C/D tiering system, derived from combining fit scores with engagement scores, further reflects a move away from spray-and-pray outreach toward prioritized, signal-driven pipeline management. This aligns with documented trends in AI-assisted sales, where platforms report dramatic efficiency gains — some citing figures as high as 120x more meetings booked — specifically when AI tools are used to augment human judgment rather than replace it wholesale.

This project also sits at the intersection of two converging movements in AI tooling: the rise of local-first, credential-safe agent deployments and the normalization of Claude as an orchestration layer for multi-tool workflows. By running entirely on the user's machine with no hosted backend or third-party data handling, the system sidesteps a major enterprise adoption barrier — the reluctance to expose CRM data and sales strategy to external SaaS providers. The fact that this was built by a single engineer, not an AI startup, and shared freely underscores how accessible Claude Code and MCP-based tooling have become for developers willing to invest the time. As AI agent frameworks mature, community-built, task-specific agents like this one are likely to proliferate, creating a long tail of highly customized automation tools that address the specific, granular inefficiencies that general-purpose SaaS products are too broad to solve.

Read original article →