The Optimal Tool Stack

A map of the tools that make up a modern AI systems stack. Not a deep dive · just enough context so nothing feels unfamiliar later.

You don't need to use all of these. You do need to know what they are and why they exist, so that when they come up in a build or a client conversation, you understand where they fit.

Think of the stack in layers:

The core · Claude ecosystem

Tool	What it does
Claude	Chat, research, drafting
Claude Code	Building and running agents, terminal-based
Claude API	Embedding intelligence into systems

This is the layer you'll spend the most time in.

Knowledge and context

• Notion · the default for structured knowledge bases, client portals, project docs, and second brains. Most of the systems here are built around it.
• Obsidian · more granular, local-first, open source. Better for personal knowledge management if you want full control over your data.

Workspace and connectivity

• Google Workspace · Docs, Sheets, Gmail, Calendar, Drive. Most clients are already on it. Connects to Claude via MCP or Google CLI.

CRM

• HubSpot · the most common choice for B2B service businesses. Strong MCP support, good pipeline management.
• Airtable · more flexible, better for custom workflows and smaller teams.

Research and scraping

• Exa · AI-powered semantic web search built for agents. Finds contextually relevant pages, not just keyword matches.
• Jina Reader · converts any URL to clean markdown Claude can read. No install needed.
• Firecrawl · scrapes full websites into structured data. Good for competitor research and content extraction.
• Apify · pre-built scraping actors for LinkedIn, Google Maps, Amazon, Instagram, and more.

Outbound

• Apollo · lead sourcing. Search by ICP filters, export to CSV or push directly to Clay.
• Clay · lead enrichment and personalisation. Connects to Claude API to generate personalised email copy per lead.
• Instantly · email sending, sequencing, reply detection, inbox rotation.
• HeyReach · LinkedIn outreach automation. Good complement to Instantly for multichannel sequences.

Infrastructure

• Vercel · deploy web apps and dashboards in one command.
• GitHub · version control. Every build, skill file, and agent template should live here.
• Supabase · open source database and backend. Good for builds that need to store and query data.
• Stripe · payment processing. Has an MCP for checking revenue and invoices from Claude directly.

Meetings

• Fireflies · AI meeting recorder and transcriber. Joins calls automatically, produces searchable transcripts and action items. Connected as an MCP here · Claude can pull and read your transcripts directly.

Note on n8n: Still useful for certain integrations, but largely superseded by Claude Code for most of what we cover here. Claude Code can now orchestrate directly via APIs without needing a separate workflow builder. If you already use it, it works fine alongside Claude Code · but it's not something you need to learn for the builds here.

You don't need to set all of this up on day one. The builds and MCPs here will tell you exactly what you need for each system. This overview just means you'll know what something is the first time you encounter it.