In partnership with
700+ teams have Viktor reading their Google Ads every morning.
Your media team opens Slack at 8am. There's a cross-platform brief in #growth: Google Ads spend vs. ROAS, Meta CPA by campaign, Stripe revenue by channel. Viktor posted it at 6am. Nobody asked for it.
Last week, one team's Viktor caught a spend spike at 2am on a broad match campaign and flagged it in Slack: "CPA up 340%. Recommend pausing and shifting budget to the top two performers." That would have burned $3K by morning. The media buyer woke up to a problem already handled.
Your strategist reviews spend trends. Your account manager checks revenue attribution. Same Slack channel, same colleague, before anyone's first coffee.
Google Ads, Meta, Stripe. One message. No Looker, no Data Studio. Anomaly detection runs around the clock. Cross-platform reporting runs on autopilot.
5,700+ teams. SOC 2 certified. Your data never trains models.
"Viktor is now an integral team member, and after weeks of use we still feel we haven't uncovered the full potential." — Patrick O'Doherty, Director, Yarra Web
Here is a number that should bother you: the average small business owner spends 16 hours a week on administrative tasks.
Sixteen hours. That is two full working days. Tasks that are repetitive, predictable, and, in most cases, automatable.
Today we are going to fix one of the biggest offenders: the gap between your marketing and your sales follow-up. Specifically, we are going to build an automation that captures leads, qualifies them, triggers personalized outreach, and logs everything without you lifting a finger.
This is not a thought experiment. It is a real workflow you can build today in Make.com. I will walk you through every step.
The Problem This Solves
Here is what the manual version of lead follow-up looks like.
Someone fills out your contact form. The notification hits your inbox. You read it. You think, "I will follow up later." Later becomes tomorrow. Tomorrow becomes never. Or you do follow up, but it is four days later, the lead is cold, and you are starting from scratch.
The research on this is pretty clear. Responding to a lead within five minutes makes you 100 times more likely to connect than if you wait 30 minutes. Most small business owners are waiting hours or days.
That gap is not laziness. It is a structural problem. You are busy running your business. Manual follow-up requires you to stop what you are doing, context-switch, personalize a message, send it, and log the contact. That chain breaks constantly.
Automation does not break.
The Workflow We Are Building
Here is the full picture of what this automation does.
Trigger: A new lead submits your contact form.
Step 1: Make captures the form data and parses it, name, email, business type, budget, message.
Step 2: Make checks of a Google Sheet to see if this person is already in your contacts. If yes, it routes to an existing-contact flow. If not, it continues.
Step 3: A personalized follow-up email goes out within five minutes. Not a generic "Thanks for reaching out" email. A specific message that references what they told you in the form.
Step 4: The contact is added to your CRM with tags based on their form responses.
Step 5: A Slack notification hits your team channel with the key details, who they are, what they need, and a link to the new CRM record.
Step 6: A follow-up task is created in your project management tool, assigned to the right team member, due within 24 hours.
Step 7: If no response from the lead in 48 hours, a second follow-up email goes out automatically.
Seven steps. Zero manual effort. Every lead gets a response within minutes.
Building It: Step by Step
Let's get into the actual construction. I will give you the structure and the key settings for each module.
Module 1: The Trigger
Use the Webhook module or the native integration for your form tool (Typeform, Jotform, or whatever you use). Set this as your trigger. When Make receives the webhook from a new form submission, it wakes up and starts running.
Key setting: Set the webhook URL in your form tool's notification settings. Test by submitting a sample form and confirming Make receives the data.
Module 2: The Data Parser
Use a Set Variables module to clean and organize the incoming data. Name your variables clearly: lead_name, lead_email, business_type, budget_range, message. This makes every downstream module much easier to build and debug.
Key setting: Map each variable to the corresponding field from your form data. Use the data inspector to confirm the mapping is correct.
Module 3: The Duplicate Check
Use the Google Sheets Search Rows module to search your contacts sheet for the incoming email address. If it finds a match, use a Router module to branch the flow to your existing-contact path. If it does not find a match, continue to the new-lead path.
Key setting: Set the search column to your email column. Set the filter to an exact match.
Module 4: The Personalized Email
Use Gmail or your email tool of choice. Build a template that references the form data variables directly.
Here is a simple template that works:
That email takes 45 seconds to read and feels like it was written specifically for them. Because, in a meaningful sense, it was.
Module 5: The CRM Update
Use your CRM's native Make module (most major CRMs have them, HubSpot, Pipedrive, Go High Level, and others). Create a new contact, populate the fields from your variables, and add tags based on the business type and budget range from the form.
Key setting: Map your variables to the CRM fields carefully. Budget an extra 15 minutes for this module if you are new to data mapping.
Module 6: The Team Notification
Use the Slack module to post a message to your sales or team channel. The message should include the lead's name, business type, budget, and a direct link to the new CRM record.
Format suggestion: Keep it scannable. Name, business type, budget, link. Four lines. Your team should be able to read it in ten seconds and know exactly what to do.
Module 7: The Task Creation
Use your project management tool (Asana, Trello, ClickUp, Notion) to create a follow-up task. Assign it to the right person, set the due date for the next business day, and include the lead's details in the task description.
Module 8: The 48-Hour Follow-Up
This is the one most people skip, and it is where a lot of revenue hides.
Use Make's built-in scheduling and a filter to check, 48 hours after the initial email, whether the lead has responded. If they have not, trigger a second email, shorter, warmer, lower commitment.
Something like: "Hey [lead_name], just wanted to make sure my message did not get buried. No pressure at all. If the timing is off or you went a different direction, totally fine. But if you are still thinking it over, I am happy to answer any questions. What would be most helpful?"
That email recovers somewhere between 10 and 25 percent of leads who did not respond to the first message. Set it up once and let it run.
What This Costs to Run
Free Make plan: 1,000 operations per month. Each run of this automation uses roughly 8 to 10 operations. You can process about 100 leads per month on the free tier before you need to upgrade.
Paid Make plan: Starts at $9 per month and gives you 10,000 operations. For most small businesses, that is more than enough to run this workflow and several others.
Let's put that in context. If this automation helps you respond faster and recover even 5 percent more leads, and that is a conservative estimate given the research on response time, what does that mean for your revenue? Run that math against the cost of the tool.
The automation pays for itself the first time it recovers a lead you would have let slip.
Three Things to Watch When You Go Live
First: test with real data before you turn on the live scenario. Use Make's test mode to run a sample form submission through every module and confirm the output looks right at each step.
Second: set up error notifications. In your scenario settings, add an email or Slack alert for when a run fails. You want to know immediately if something breaks, not discover it when you notice leads have been dropping.
Third: review the first week's operations manually. Check the CRM to confirm contacts are being created correctly. Read the follow-up emails that went out. Make sure the personalization is working as intended. Small tweaks in week one save headaches later.
This Is Just One Workflow
We built one automation today. One. And it covers lead capture, qualification, personalized outreach, CRM management, team communication, task creation, and follow-up recovery.
That is a significant slice of a sales operation, automated and running without your involvement.
The question is: what else in your business follows a predictable pattern? Client onboarding? Invoice collection? Content publishing? Support routing?
Each one of those is a workflow waiting to be built.
If you want a full map of which automations to build first, in what order, and how to connect them into a system that actually scales, that is the core of the AI Business Accelerator. Reply ACCELERATOR and I will get you the full details.
The Bigger Picture
What we built today is one workflow. One automation that handles one specific gap in a typical sales process. But the pattern is replicable.
Every time you notice yourself doing the same sequence of tasks more than once, you are looking at an automation candidate. The trigger is always some kind of event, a form submission, a calendar event, a new file, a new row in a spreadsheet. The actions are always some version of notify, create, update, or send. The logic in the middle is what makes it specific to your business.
That is the mental model worth developing. Not "what can I automate?" but "what sequence of events happens predictably in my business, and what do I always do in response?" Once you frame it that way, you start seeing automation opportunities everywhere.
Some other workflows worth building after this one:
A client onboarding trigger that fires when a deal closes in your CRM, automatically creating the project folder, sending the welcome sequence, and assigning the kickoff tasks. An invoice follow-up system that sends increasingly firm reminders at 7, 14, and 30 days past due without requiring anyone to manually track overdue accounts. A content repurposing pipeline that takes your newsletter and automatically formats versions for LinkedIn, Twitter, and your blog.
Each of these follows the same structure as what we built today. Different triggers. Different actions. Same underlying logic.
A Note on Maintenance
Automations are not set-and-forget forever. Apps update their APIs. Field names change. Tools get acquired and their integrations shift. Plan to do a quick audit of your Make scenarios every 90 days. Look for failed runs. Check that the data is still mapping correctly. Make sure the emails going out still reflect your current messaging.
That audit typically takes an hour. It protects months of automation infrastructure. Build it into your quarterly operations review and you will never have an automation silently failing while you wonder why leads are dropping off.
The workflow we built today is a foundation. Treat it like one.
Reply ACCELERATOR to get the AI Business Accelerator ($97) and start building today.
Jordan Hale | The AI Newsroom | ainewsroomdaily.com