CRM: guides & tutorials

Sales teams and founders often use Clay (now rebranded as Mesh) to auto-enrich their contact database. It connects your email, calendar, LinkedIn, and Twitter to build a smart address book with work history, recent activity, and relationship context.

But Clay isn't the only player in the personal CRM and GTM enrichment space. Depending on your workflow, budget, and integration needs, alternatives like Apollo, Hunter, Clearbit, Apify, and others might fit better.

This guide compares seven tools across features, pricing, and use cases so you can pick the right one for your sales stack.

For the deeper breakdown of how Apify scraping complements (rather than replaces) Clay, see Apify vs Clay: web data vs personal CRM.

Both Twenty CRM and EspoCRM are genuinely open-source, genuinely self-hostable, and genuinely capable of replacing a commercial CRM for small-to-mid-size teams. But they occupy different points on the maturity-versus-modernity spectrum — and picking the wrong one means a painful migration later.

HubSpot Marketing Hub Pro starts at $800/month — and that's before you add Sales Hub or Service Hub. You can replace the entire stack with open-source tools on a Liquid Web Managed VPS for roughly $33–$60/month.

TL;DR

• One docker-compose.yml: Cal.com + Chatwoot + Twenty CRM + shared PostgreSQL + Redis + Caddy
• Measured idle RAM: ~3.2 GB; peak: ~4.5 GB
• Minimum Liquid Web tier: 8 GB Managed VPS (~$33–$40/mo)
• Calendly Teams + Intercom Starter + Salesforce Essentials: ~$80+/user/mo; this stack: ~$30/mo flat

Most growth-stage teams stitch together Calendly for scheduling, Intercom for support chat, and Salesforce for pipeline — then pay Zapier to connect them. This guide deploys the open-source equivalents on a single VPS: Cal.com handles scheduling, Chatwoot handles conversations, and Twenty CRM tracks deals. When a prospect books a call, that event flows through the entire pipeline automatically.

TL;DR

• One docker-compose.yml: Twenty CRM + Mautic + Chatwoot + PostgreSQL + MariaDB + Redis + Caddy
• Measured idle RAM: ~3.0 GB; peak: ~4.5 GB on a 16 GB VPS
• Minimum Liquid Web tier: 16 GB Managed VPS (~$30/mo)
• HubSpot Marketing Hub Pro + CRM + Service Hub Pro: $800–$1,340+/mo; this stack: ~$30/mo

HubSpot charges separately for CRM, marketing automation, and customer support — and the Professional tier alone runs $800/mo before seat costs. This guide deploys all three functions with open-source equivalents: Twenty CRM for pipeline management, Mautic for email marketing and lead scoring, and Chatwoot for multi-channel support — on a single Liquid Web 16 GB VPS using one Compose file.

TL;DR

• One docker-compose.yml: n8n + LiteLLM + Twenty CRM + shared PostgreSQL + Redis + Caddy
• Measured idle RAM: ~1.7 GB; peak: ~2.5 GB (parallel workflow executions with live LiteLLM calls)
• Minimum Liquid Web tier: 8 GB Managed VPS (~$33–$40/mo)
• Zapier Pro + unmanaged OpenAI API + HubSpot Starter: ~$69 + variable + $50/mo vs ~$33/mo self-hosted

Most sales teams that want AI-augmented automation end up in one of two bad places: paying for Zapier Pro, a direct OpenAI API key they can't audit, and HubSpot CRM — three separate subscriptions that don't compose well and bill regardless of usage. Or they write fragile Python scripts that break on every API change and nobody wants to maintain.

This guide deploys the middle path: Twenty CRM for pipeline management, n8n for visual workflow automation, and LiteLLM as an OpenAI-compatible AI proxy — all on a single Liquid Web 8 GB VPS. n8n calls LiteLLM for every AI task (lead enrichment summaries, proposal draft generation, inbound form classification), and LiteLLM provides budget caps, model fallbacks, and a unified request log.

TL;DR

• One docker-compose.yml: Twenty CRM + Chatwoot + shared PostgreSQL + Redis + Caddy
• Measured idle RAM: 2.2 GB; peak: 3.4 GB (20 concurrent Chatwoot conversations + 5k Twenty contact load)
• Minimum Liquid Web tier: 8 GB Managed VPS (~$33–$40/mo)
• HubSpot Sales + Service Hub Pro (5 seats): ~$1,335/mo; this stack: ~$33/mo

HubSpot bundles CRM and customer support into one product at a significant price. This guide deploys the open-source equivalents — Twenty CRM for pipeline management and Chatwoot for multi-channel customer support — on a single Liquid Web 8 GB VPS using a single Compose file.

The key is not just scraping data — it is building a complete pipeline that goes from raw web data to scored, enriched leads in your CRM, automatically.

This playbook covers the architecture, tool-by-tool setup, cost model, and compliance framework for building an AI lead generation system in 2026.

TL;DR:

Prerequisites:

• Apify account (Starter plan: $29/mo for production use)
• Claude API key or self-hosted Ollama (see Self-Host AI Stack)
• CRM account (HubSpot free, Clay, or Google Sheets)
• n8n or Make.com for orchestration

Clay (now Mesh) does a lot of the heavy lifting when you connect email, calendar, LinkedIn, and Twitter. What it won’t do on its own is keep polling the open web forever: enrichment tends to reflect what was true when the contact landed in your book, not every headline or title change afterward.

Apify is where scheduled scraping helps — job moves, company news, fresh posts, GitHub activity — then you fold those findings back into Mesh as notes or updates.

Here are three workflows that combine the two without pretending there’s a single “native” button for it.

Managing professional relationships is a problem every founder, salesperson, and consultant faces — and there is no single perfect tool. Clay (now called Mesh), HubSpot, and Notion are three of the most common answers, but they solve fundamentally different problems.

This guide breaks down which tool is right for your specific use case.

Naming note: This comparison covers Clay the personal CRM at clay.earth, now rebranded to Mesh. This is unrelated to Clay.com, the B2B sales enrichment platform.