Disclosure: Some links in this article are affiliate links. If you sign up through these links, I may earn a commission at no extra cost to you. I only recommend tools I use or have personally tested.
You sent the proposal. The call went great. Then… nothing. You got busy, the contact slipped down your inbox, and three weeks later you remembered you never followed up. That prospect is gone.
This isn’t a discipline problem. It’s a systems problem.
Research from the National Sales Executive Association puts 80% of sales requiring five or more follow-up contacts — yet 44% of salespeople quit after just one attempt. For small business owners running everything themselves, that gap is even wider. You don’t have a sales team sending sequences. You have yourself, a full calendar, and a CRM you check when you remember to.
This article walks you through the exact system that closes that gap permanently. You’ll build a client follow-up automation using HubSpot Free CRM, Make.com, and the Claude API that runs without you touching it. New contact hits your CRM, system waits 48 hours, Claude writes a personalized follow-up email in your voice, Gmail sends it. Done. The whole stack costs between $0 and $14 per month depending on volume.
By the end, you’ll have a working 4-module Make.com scenario and an optional day-7 second touch if the first one gets no response.
Why Manual Follow-Up Breaks Down at Scale
When you have 10 active leads, manual follow-up is annoying but manageable. You can hold names in your head and set calendar reminders. At 30 leads it becomes a part-time job. At 100, you’re losing deals every week and you don’t even know which ones.
Three failure modes show up repeatedly.
Inconsistent timing. You follow up with one lead the same day and another two weeks later, depending entirely on how your week went. Timing affects conversion. A follow-up sent 24–48 hours after initial contact converts at a measurably higher rate than one sent a week later, and the degradation is steep after 72 hours.
Generic messages. When you’re doing it manually under time pressure, you reach for a template. “Hi [Name], just checking in to see if you had any questions.” Nobody reads that. Nobody responds to it. You get silence and conclude the lead went cold, when really you just sent them nothing worth responding to.
No activity log. You send the email from your regular Gmail, it doesn’t get logged in your CRM, and three months later you have no idea what touchpoints that client received before they signed. This matters for troubleshooting your funnel and for handing off to anyone who helps you later.
An AI client follow up system solves all three. Fixed timing, personalized copy, everything logged in one place.
The 3-Tool Stack
You need three tools. Two of them have free tiers that cover most small business volumes.
HubSpot Free CRM ([HUBSPOT AFFILIATE LINK]) — This is your contact database and the trigger point for the whole system. HubSpot’s free tier includes contact management, deal pipeline, activity logging, and the API access Make.com needs to watch for new contacts. If you’re already using HubSpot, you’re set. If you’re on a spreadsheet or nothing, this is the migration you should have made 12 months ago. Free, no credit card required for the base tier.
Make.com ([MAKE.COM AFFILIATE LINK]) — This is the automation layer. Make.com runs the scenario that watches HubSpot, waits, calls Claude, and fires Gmail. Their free plan includes 1,000 operations per month, which handles roughly 250 new contacts per month through this 4-module scenario. Paid plans start at $9/month for 10,000 ops if you need more volume.
Claude API (Anthropic) — This is what writes the emails. You’re not sending a template. You’re sending a short, personalized message generated from the contact’s actual data — their first name, where they came from, what they expressed interest in. Claude API pricing runs approximately $3–5/month at small business volumes. You pay per token, not per seat.
Total stack cost: $0–$14/month. Gmail you already have.
Step-by-Step: Building the Make.com Scenario
Open Make.com and create a new scenario. You’re building four modules in sequence.
Module 1: HubSpot “Watch Contacts” Trigger
Add the HubSpot module and select Watch Contacts as the trigger. Connect your HubSpot account using OAuth — Make.com walks you through this in about 60 seconds. Set the trigger to fire on newly created contacts.
Map the fields you’ll need downstream: contact.firstname, contact.email, contact.lead_source, and whatever custom property you use for expressed interest (commonly hs_lead_status or a custom field like contact.interest). If you don’t have an interest field yet, add it to HubSpot now and start populating it when leads come in — even a short phrase like “website redesign” or “bookkeeping services Q3” gives Claude enough to work with.
Set the polling interval to 15 minutes. This is the lag between a contact entering HubSpot and the scenario checking for them. For most use cases, 15 minutes is fine.
Module 2: 48-Hour Delay
Add a Sleep module immediately after the HubSpot trigger. Set it to 2880 minutes (48 hours).
This delay is intentional. You want the contact to have had time to look at your website, review whatever you sent them, or simply exhale after the initial conversation. Hitting them in the first hour reads as automated. 48 hours reads as thoughtful follow-up timing. The personalization Claude adds reinforces that impression.
If your sales cycle is shorter — say, you’re in e-commerce or a same-day service business — you can compress this to 24 hours or even 6 hours. Test what works for your market.
Module 3: HTTP Request to Claude API
This is the module that separates this system from a basic email drip. Add an HTTP module and configure it as a POST request.
URL: https://api.anthropic.com/v1/messages
Headers:
– x-api-key: your Anthropic API key (store this in Make.com’s connections vault, not hardcoded)
– anthropic-version: 2023-06-01
– content-type: application/json
Body (JSON):
{
"model": "claude-opus-4-5",
"max_tokens": 300,
"messages": [
{
"role": "user",
"content": "Write a follow-up email to {{contact.firstname}}. They found us via {{contact.lead_source}} and expressed interest in {{contact.interest}}. Keep it under 5 sentences. Warm but direct tone. No subject line. End with a single clear question that invites a reply. Sign off as [Your Name] from [Your Company]."
}
]
}
Replace [Your Name] and [Your Company] with your actual details. The {{contact.firstname}}, {{contact.lead_source}}, and {{contact.interest}} tokens pull live data from Module 1 — Make.com injects the actual values before the request fires.
Map the response output: you want content[0].text from Claude’s response body. This is the email body text you’ll pass to Module 4.
Module 4: Gmail “Send an Email”
Add the Gmail module and select Send an Email. Connect your Gmail account.
- To:
{{contact.email}}(from Module 1) - Subject: Something simple — “Quick follow-up, {{contact.firstname}}” works well, or test a subject line that references their specific interest
- Body: The mapped output from Module 3 (Claude’s generated text)
Enable Log Activity to HubSpot if you’re using HubSpot’s Gmail integration, or manually add a HubSpot “Create an Activity” module after Gmail that logs the sent email against the contact record. This keeps your CRM clean and ensures you always know what touchpoints a contact received.
Turn the scenario on. Every new contact that enters HubSpot now gets a personalized follow-up email 48 hours later, automatically.
The Optional 2-Touch Upgrade
If you want a second follow-up for contacts who didn’t engage with the first email, add a fifth module (and a conditional branch) on day 7.
After Module 4, add a Router module with two paths.
Path A — No Engagement: Add a HubSpot “Get a Contact” module and check the contact’s pipeline stage or last activity date. If no email open or reply has been logged (HubSpot tracks this if you’re using their tracking pixel), route to a second HTTP request to Claude with a slightly different prompt: same structure, but ask for a shorter message that acknowledges you’re following up once more and offers an easy out — something like asking if their timeline has shifted. This removes pressure and often re-engages people who were interested but busy.
Path B — Engaged: If the contact replied, opened, or moved pipeline stages, skip the second email. You don’t need automation for a warm lead — get in there yourself.
This 2-touch upgrade adds roughly 2 additional operations per contact through your Make.com scenario. At 100 new contacts per month, you’re still well within the free plan’s 1,000 operation limit.
What the Running System Looks Like
On your end, the day-to-day experience is almost nothing. Leads enter HubSpot the same way they always did — via form, manual entry, LinkedIn imports, whatever your current intake is. You don’t touch the follow-up process.
Inside HubSpot’s contact timeline, you see the automated email logged with a timestamp and the full message text. If a contact replies, that reply hits your Gmail inbox like any other email. You respond as yourself. The system handed off the cold-start problem; you take it from there.
Contacts stop falling through cracks because there’s no longer a human memory requirement attached to the follow-up step. The system fires on every new contact, every time, regardless of how your week went.
One operational note: review Claude’s output weekly for the first month. Occasionally a contact will have sparse data — no lead source, no interest field populated — and Claude will write a more generic message. That’s a data quality issue in your CRM, not an AI problem. Build a habit of filling in those two fields at contact creation and the output quality stays high.
Full Cost Breakdown
| Tool | Cost |
|---|---|
| HubSpot Free CRM | $0 |
| Make.com (up to 1,000 ops/month) | $0 |
| Make.com Core plan (10,000 ops/month) | $9/month |
| Claude API (~250 emails/month) | $3–5/month |
| Gmail | $0 |
| Total (low volume) | $0–$5/month |
| Total (mid volume) | $12–$14/month |
For most small businesses doing 50–150 new contacts per month, you’ll land in the $3–5 range — just the Claude API cost, with both HubSpot and Make.com staying on free tiers.
Compare that to the cost of one lost deal from a dropped follow-up, and this system pays for itself inside the first week it runs.
Build It This Week
The actual build time is 45–90 minutes if you follow the steps above. HubSpot setup, Make.com scenario configuration, Claude API key, Gmail connection. It runs indefinitely once it’s live.
Start with the 4-module core. Get it running on real contacts. After two weeks, look at your HubSpot activity feed and count how many follow-up emails went out that you didn’t write or send. Then decide if you want to add the day-7 second touch.
Get HubSpot free at [HUBSPOT AFFILIATE LINK] and set up your Make.com account at [MAKE.COM AFFILIATE LINK]. Both take under five minutes to sign up and you’ll have the core tools in place before you finish your next coffee.
Leave a Reply