The tools we use to keep the lead system moving.

Stack tools: 77
Categories: 21
Stack layers: 8
Main job: Leads

All stack tools

Google Ads

Use it for high-intent search demand when the business can answer calls and follow up fast.

GoMarble

Use it as an AI layer for paid media review, creative checks, and faster account insight.

LeadSimple

Use it when a property management or local service team needs cleaner lead stages and follow-up.

Apollo

Use it for B2B account and contact data before enrichment, outbound, or CRM cleanup.

Anymail Finder

Use it to find and verify work emails before enrichment, outreach, or lead routing.

Instantly

Use it to run cold email campaigns, manage sending accounts, and move replies into the sales loop.

Zapmail

Use it to set up domains, mailboxes, DNS, and inbox health before cold email starts.

HeyReach

Use it to run LinkedIn outreach, manage lead lists, and route replies into one follow-up loop.

Trigify

Use it to find social signals that show when a prospect or account may be ready for outreach.

RB2B

Use it to turn anonymous website visits into company or person signals for faster follow-up.

GA4

Use it as the baseline view for traffic, events, and landing page behavior.

WhatConverts

Use it to connect calls, forms, chats, and conversion sources back to the lead system.

Google Search Console

Use it to check search visibility, indexing, queries, and page issues from Google.

Google Business Profile

Use it when local demand, calls, maps visibility, and reviews affect the lead path.

Zapier

Use it for simple form, CRM, calendar, and alert handoffs when speed matters.

Publora

Use it to schedule approved social posts across several platforms from one API or workspace.

Docupilot

Use it to turn form, CRM, or database fields into finished documents and signature workflows.

Claude

Use it for planning, research synthesis, copy refinement, and code-assisted operations work.

OpenAI

Use it for AI features, structured generation, internal tools, and repeatable workflows.

OpenRouter

Use it to route an AI workflow through the right model without rebuilding the rest of the system.

Codex

Use it as the coding agent layer for reading repos, editing files, running checks, and shipping changes.

Google Gemini

Use it as a second AI model path for analysis, generation, and Google-connected workflows.

Perplexity

Use it for fast market, tool, and competitor research before deeper review.

Supabase

Use it for fast internal tools, databases, auth, and small app backends.

Neon

Use it for serverless Postgres when an app needs a real database without a full backend platform.

Render

Use it for background workers, cron jobs, small services, and API tasks.

Vercel

Use it for fast Next.js sites, landing pages, and frontends connected to real tools.

DataForSEO

Use it for search data, keyword checks, and ranking workflows that need an API.

ShowMojo

Use it when leasing and showing workflows need to connect with lead operations.

ColdIQ

Use it as a reference on outbound tooling and campaign structure, from an agency that publishes what it runs across hundreds of B2B clients.

Firecrawl

Use it to crawl websites into structured research inputs for strategy, SEO, and lead systems.

ScrapeCreators

Use it to pull public social posts, profiles, comments, and metrics into research workflows.

Next.js

Use it for fast marketing sites, resource pages, internal tools, and app frontends.

React

Use it for reusable interfaces, dashboards, forms, and tool surfaces.

TypeScript

Use it to keep app data, API payloads, and component contracts easier to change.

Tailwind CSS

Use it for fast, consistent interface styling without waiting on a heavy design system.

Radix UI

Use it for accessible dialogs, menus, tabs, and interface primitives.

Lucide

Use it for clear interface icons in tools, nav, buttons, and dashboards.

Framer Motion

Use it for interface motion that guides attention through states and sections.

GSAP

Use it when a page or visual needs more controlled motion than basic UI transitions.

Higgsfield

Use it for generated visual assets when the image needs to explain a business system.

Remotion

Use it to create videos, explainers, and repeatable motion assets with React.

Playwright

Use it to test real browser flows, screenshots, forms, and visual regressions.

Puppeteer

Use it for browser automation, screenshots, and scraping workflows that need Chrome control.

Zod

Use it to validate forms, API payloads, and data moving between tools.

Payload CMS

Use it when a site needs a real content model, admin UI, media, and publishing workflow.

Python

Use it for data scripts, research utilities, automation helpers, and analysis workflows.

FastAPI

Use it for small Python APIs and services around data or automation workflows.

Postgres

Use it as the durable database for lead records, app state, reporting, and internal tools.

Amazon S3

Use it for media, files, exports, and CMS storage that need durable object storage.

SQLite

Use it for small local databases, research stores, and lightweight workflow state.

Docker

Use it when a service, worker, or local stack needs a repeatable runtime.

Resend

Use it for transactional email from apps, forms, alerts, and internal tools.

Nodemailer

Use it for Node-based email sending where the workflow needs direct SMTP control.

Slack

Use it for internal alerts when a lead, task, job, or workflow needs quick visibility.

Twilio

Use it when calls, SMS, or phone workflows need to connect with the operating system.

Stripe

Use it when apps, memberships, products, or service flows need payments.

Google APIs

Use it to connect Sheets, Drive, Calendar, Gmail, Maps, and other Google data sources.

Google Sheets

Use it for simple reports, lead lists, QA sheets, and shared operating views.

Anthropic

Use it for Claude-backed analysis, agent workflows, copy review, and code-assisted work.

Perplexity API

Use it for research workflows that need web-grounded answers inside tools or scripts.

Obsidian

Use it as a local Markdown vault for project context, decisions, source notes, and working memory.

Printful

Use it when a commerce or fan product flow needs print-on-demand fulfillment.

Buildium

Use it when property management operations need leasing, tasks, or back-office data connected.

GitHub

Use it for source control, pull requests, CI checks, and the work trail behind shipped changes.

Clay

Use it to build and enrich a target list in one table, then push clean records into the outbound engine.

Apify

Use it to run hosted scrapers for LinkedIn, listings, and review sources without maintaining browser infrastructure.

Calendly

Use it to turn interest into a booked call without a back and forth email thread.

Google Tag Manager

Use it to control tracking tags and conversion events in one place instead of scattering scripts through the code.

Microsoft Clarity

Use it to watch session recordings and heatmaps when the numbers say a page leaks but not where.

Meta Ads

Use it for demand that has to be created rather than captured, with the Conversions API carrying the signal server side.

ElevenLabs

Use it for voiceover on explainer and ad video when a recording session is not worth the schedule.

Cloudinary

Use it to store, transform, and serve images and documents that an automation generates on the fly.

HubSpot

Use it when a team needs one CRM for contacts, deals, and marketing, and the outbound work has to land somewhere the whole company can see.

Hunter

Use it to find and verify work email addresses at a company domain when all you have is the business.

Findymail

Use it as the second pass on email discovery, because no single provider covers every domain.

RapidAPI

Use it to reach a niche data API through one account and one key instead of a separate contract per vendor.

How it fits together

Eight layers, one lead path.

Every tool on this page sits in at least one layer. A tool can appear more than once when it does real work in two places.

Create and capture demand

Ads, lead data, research, and search inputs help find demand before the page or CRM gets blamed.

More qualified buyers enter the system.

Turn attention into action

Frontend, design, analytics, and testing tools shape the page path after someone arrives.

More clicks become calls, forms, or booked next steps.

Route and enrich the lead

CRM, data, and automation tools connect the lead record, owner, task, and source.

Lead data lands where the team can act on it.

Build the data layer

Databases and schemas hold the truth when spreadsheets and tools are not enough.

Reports and tools use cleaner source data.

Ship sites and services

Hosting, workers, containers, and typed code keep pages, APIs, and jobs moving.

The growth system can run beyond the homepage.

Send alerts and close the loop

Email, forms, CRM tasks, and automation alerts reduce the quiet gaps after a lead arrives.

Follow-up is faster and easier to prove.

Make the proof visible

Motion, visuals, decks, and generated assets make complex work easier to understand.

The buyer can see the point faster.

Test before traffic grows

Browser checks, scraping, QA, and source validation catch gaps before a buyer does.

The stack gets safer before more spend hits it.