How to Follow Up With Every Lead in Under 5 Minutes (Without Hiring an SDR)

The Goal

A new lead submits a form on your website. Within five minutes, they get a personalized text message acknowledging the inquiry, an email with the next step, and you (or someone on your team) gets a notification with their full context so you can call if it warrants a call. No leads slip through the cracks. No "I'll get to it later." No leaving money on the table because the prospect already booked your competitor.

The Tools

• Google Forms — your intake form, embedded on your site
• Google Sheets — the system of record for every submission
• Google Apps Script — for the trigger logic (free)
• IFTTT or Zapier free tier — for the SMS trigger
• Gmail — for the auto-reply email
• Your phone or a free TextMagic trial — for the actual SMS send

Step 1: Build the Intake Form

Open Google Forms and create a form with the absolute minimum fields a lead will tolerate. Name, phone, email, and a one-line "what are you looking for." Every additional field cuts your conversion. In the form settings, link the responses to a new Google Sheet — this becomes your living lead database.

Embed the form on your website using the iframe code Forms gives you. If you care about styling, you will need to either rebuild the form in HTML and POST to a Forms endpoint (fragile) or live with the default Google Forms aesthetic.

Step 2: Set Up the Apps Script Trigger

In your linked Google Sheet, open Extensions → Apps Script. You are going to write a function that fires every time a new row is added. Here is the skeleton:

1. Create an onFormSubmit function that reads the new row's columns into named variables.
2. Send an email via MailApp.sendEmail() to your auto-reply address.
3. POST the lead data to your IFTTT or Zapier webhook URL to trigger the SMS.
4. Send yourself a notification email with the full lead context.
5. Set the trigger via Apps Script → Triggers → "Add Trigger" → from spreadsheet, on form submit.

Test it ten times. Apps Script will silently fail in ways you only catch when you check the execution log. Budget half a day for trigger debugging alone.

Step 3: The SMS Trigger

IFTTT's "Webhooks → SMS" applet on the Pro plan ($3/mo) will send an SMS from a US number when your Apps Script POSTs to the webhook URL. Zapier free tier can do the same with the SMS by Zapier action, capped at 100 SMS per month. For higher volume, open a Twilio account, provision a number ($1.15/mo), and POST directly from Apps Script using UrlFetchApp.fetch() — you will pay roughly $0.0083 per SMS plus a one-time A2P 10DLC registration that takes 2–6 weeks to clear.

Step 4: Write the SMS Templates

Your auto-SMS should sound human. Not "Thank you for your inquiry, a representative will be in touch." Something like: "Hey {{firstName}} — thanks for reaching out about {{interest}}. I'm reviewing your info now and will text you back personally within the hour. — Jay"

The Apps Script populates the merge tags from your sheet columns before posting to the webhook. You will need a separate template for each lead source, otherwise everyone gets the same generic message.

Step 5: The Manual Loop

Here is the part most people leave out. The auto-reply gets you to "acknowledged within five minutes." It does not get you to "qualified within five minutes." For that, you or someone on your team has to actually look at the lead, decide if they warrant a call, and make the call.

You will need to set up notifications on your phone for the lead-alert email, build a habit of checking it during business hours, and create a fallback for nights and weekends. Most people who try this end up either ignoring after-hours leads or going slightly mad checking their phone every fifteen minutes.

Step 6: Track What Works

Add columns to your sheet for response time, contact attempts, and outcome. Build a pivot table for weekly review — what's your average response time, which sources convert, where are you losing leads. Without this you have no idea if the system is working.

Realistic Time Investment

• Initial build: 15–25 hours, assuming you are reasonably comfortable with Apps Script and webhooks
• A2P 10DLC compliance: 4–6 weeks of waiting plus 1–2 hours of paperwork if you go the Twilio route
• Ongoing maintenance: 2–3 hours per month for trigger failures, template updates, sheet cleanup
• Daily operational time: 30–90 minutes of you or your team manually reviewing alerts and making calls

Where This Breaks

The system works until it doesn't. Apps Script triggers silently die when Google updates permissions. IFTTT changes its pricing every six months. Zapier hits its free tier cap on a Friday afternoon during your best campaign of the quarter. The phone you use for SMS gets flagged for spam because you sent too many messages too fast. None of these failures are visible until a lead complains — or worse, until you check your conversion numbers a month later and realize you have been losing leads silently.

You also have no centralized customer record. Every lead's history is fragmented across a sheet, your inbox, your text messages, and your phone's call log. Reconstructing context for a callback takes ten minutes per lead.

Speed-to-lead is a system, not a hack. Building it from free parts is possible. Keeping it running is the hard part.