Non-coder builds full prospecting stack with Claude Code and APIs
A Reddit user on r/ClaudeAI shared how they built a complete outbound prospecting system over a weekend using Claude Code, despite having zero coding experience. The system replaces a manual multi-tool setup and relies on three API-based tools chained together by Claude Code.
Workflow
- ICP file: The user maintains a plain text file with Ideal Customer Profile criteria (industry, headcount range, funding stage, target personas). Claude Code reads this file as context.
- Company search: Claude Code queries
CrustdataAPI with ICP filters, returning structured data (headcount, funding, tech stack, hiring signals). The user tried Exa before but found the data insufficiently structured. - People search: Filters by persona (Director of Sales, Head of Revenue, VP Marketing, etc.) within target companies.
- Contact enrichment: Uses
FullEnrichwaterfall provider checking 20+ sources; only pays for verified contacts. - Personalization: Claude Code pulls recent social posts for each contact and drafts personalized openers referencing specific content.
- Monitoring: Webhooks fire on job changes and hiring signals; Claude Code auto-generates outreach when trigger events occur.
Key lessons
- Read API docs carefully — the user burned credits by using the expensive realtime endpoint when the cached version sufficed for 90% of searches (33x cost difference).
- Claude Code handles chaining API calls well when given enough context in plain English. The ICP file is critical for filtering.
- Personalization quality and webhook relevance still need iteration (some irrelevant job posting alerts).
Stack
- Crustdata: Company/people search, firmographics, hiring signals, social posts (API).
- FullEnrich: Email/phone waterfall with inline verification (API).
- Instantly: Sending with inbox management and warming.
The user emphasizes that for solo founders or small teams running outbound without an engineering team, Claude Code + one good data API + a sending tool is sufficient.
📖 Read the full source: r/ClaudeAI
👀 See Also
Game developer uses OpenClaw for automated feedback collection and code refactoring
A game developer runs OpenClaw as a background service on a MacBook to manage two projects: Heretical (a Steam game) and Duskland (a TypeScript project). The system uses Claude models via Discord and Telegram, with local Markdown memory files.
Hybrid Local+API Approach Cuts AI Costs by 79% in Month-Long Test
A developer running a 24/7 AI assistant on a Hetzner VPS reduced monthly costs from $288 to $60 by strategically combining local models with API calls. The setup uses nomic-embed-text for embeddings and Qwen2.5 7B for background tasks, routing more complex work to Claude models.
Using Claude Code to Fix OpenClaw Configuration Issues
A developer used Claude Code to fix OpenClaw settings, heartbeat, memory, cron jobs, and other configuration problems after failing with manual setup and version switching.
ALTWORLD: A Persistent Life-Sim Architecture That Separates LLM from Database to Solve AI Amnesia
ALTWORLD is a stateful simulation game that addresses the context window problem by storing canonical run state in PostgreSQL tables and JSON blobs, then generating narrative text only after state changes. The architecture uses Next.js App Router, Prisma, and PostgreSQL with strict separation between simulation logic and AI narration.