Marketing automation for startups: start with the leaks

The leak test

Answer these five questions honestly:

1. Do all inquiries (forms, ad leads, calls, messages) land in one place?
2. Does every inquiry record where it came from?
3. Does every open lead have an owner and a next-step date?
4. Does anyone get reminded when a quote goes unanswered?
5. Can you see which channel produced paying customers last month?

Every “no” is a leak. Fix those before you automate anything else.

How to run the leak test in 30 minutes

You don’t need a consultant for this. Open your inboxes, your ad accounts and your CRM or spreadsheet side by side.

1. List every place an inquiry can arrive. Website form, ad-platform lead forms, email, phone, text, DMs, marketplaces. Most founders find two or three they forgot.
2. Pick the last ten inquiries. For each one, write down where it arrived, when you first replied, and what happened next.
3. Mark the gaps. A reply later than one business day, a missing source, no next step, a quote with no follow-up.

The pattern is usually obvious after ten rows. But founders rarely look, because each inquiry felt handled at the time. So write it down once; the gaps you find are your automation list, in order.

Automate in this order

Capture → source tagging → owner and next step → reminders → follow-up → reporting

1. Capture. Every form and ad-platform lead creates a CRM record automatically.
2. Source tagging. UTM tags and the landing page are saved on the record.
3. Owner and next step. New records get an owner and a due date.
4. Reminders. A daily list of who to contact today.
5. Follow-up. Routine messages (confirmations, reminders, check-ins) go out on time.
6. Reporting. A weekly view of leads, qualified leads, deals and payments by source.

Only after these six does it make sense to add nurture sequences and newsletters.

What each step looks like in practice

Capture. A form submission, a Meta lead or a missed call creates one CRM record with the person, the company and the request. No copy-paste, no screenshots in a notes app.

Source tagging. The record stores the UTM tags, the landing page and the ad-platform lead ID when there is one. Six months later, this is the field that tells you which channel to keep.

Owner and next step. Even if you are the only person, the record gets an owner and a due date. A lead without a next date is already slipping.

Reminders. One list each morning: who to call, who to answer, which quotes are waiting. This replaces the feeling that something is falling through the cracks.

Follow-up. Confirmation after an inquiry, a reminder before a meeting, a check-in two days after a quote. Each message is short, and each one is something the customer actually needs.

Reporting. Once a week: new leads, qualified leads, won deals and payments, by source. Five numbers, one screen.

Workflow recipes to copy

Recipe 1: inquiry intake

When a website form or ad lead arrives → create a person and a deal in the CRM → save source, campaign and landing page → assign owner, due today → send a short confirmation to the customer → notify you by text or chat.

This single workflow fixes the most expensive leak for most founders: slow or missing first replies.

Recipe 2: stale quote

When a deal has been in “Quote sent” for 2 days with no reply → create a follow-up task → draft a short message with a new angle for your review → repeat on day 5 → on day 10 ask whether to close it out.

Most deals are lost to silence after the quote, not to a competitor. This recipe keeps every quote alive until you get a clear answer.

Recipe 3: weekly report

Every Monday → count new leads, qualified leads, won deals and confirmed payments from last week → group by source → send the table to your inbox.

It takes an hour to set up and saves you from guessing which channel works.

Recipe 4: missed call

When a call to your business number is missed → send a short text: “Sorry I missed you, what can I help with?” → create or update the CRM record with the caller’s number → add a task to call back within the hour.

Calls often come from the most ready buyers. But a missed call with no reply looks like nobody is there. So a text-back keeps the conversation alive until you can call. If you text people for marketing, check the consent rules that apply to your state and your use case before you turn it on.

Recipe 5: meeting booked

When someone books a call → move the deal to “Meeting” → send a confirmation with the time and the link → send a reminder the day before and an hour before → prepare a one-page brief from the CRM record for you → if they don’t show, create a task to rebook.

The brief is the quiet win. You walk into every call knowing the source, the request and what was said before.

Recipe 6: lost deal

When a deal is marked lost → require a reason from a short list (price, timing, fit, no reply, chose another option) → if the reason is timing, create a task to check in after 90 days.

Lost reasons are free market research. After twenty of them, you will know whether to fix your price, your targeting or your follow-up.

Recipe 7: payment received

When a payment is confirmed → mark the deal as paid → send a thank-you and the next step → create the delivery or onboarding task → record the amount against the original lead source.

This closes the loop. The weekly report can now show which source produced paid revenue, not just signed deals.

Tools by job

Many founders combine a CRM with one workflow tool. n8n is popular with technical founders because it can be self-hosted.

How to choose

Whatever you pick, keep one rule: every automation writes to the same customer record. Two tools that each keep their own copy of the customer will disagree within a month.

The data you need before you automate

Automations are only as good as the fields they read and write. Agree on these once, and keep the names the same everywhere:

• Contact: name, email, phone, company.
• Request: what they asked for, in one line.
• Source: UTM source, medium and campaign; landing page; ad-platform lead ID when there is one.
• Stage: one of a short list (Inquiry, Qualified, Meeting, Quote sent, Follow-up, Won, Paid, Lost).
• Owner and next-step date.
• Lost reason: from a fixed list, not free text.

If two tools call the same thing by different names, they will drift apart. One list of field names prevents most automation bugs.

Example: building the intake recipe in n8n

Here is how Recipe 1 looks as a workflow in n8n. The same steps work in Zapier or Make.

1. Trigger: a webhook that your website form and ad-lead sync send data to.
2. Clean the data: trim names, format the phone number, and copy the UTM fields.
3. Check for duplicates: search the CRM by email or phone. If the person exists, update them instead of creating a new record.
4. Create the deal: stage “Inquiry”, owner set, next-step date today.
5. Reply to the customer: a short confirmation by email or text.
6. Notify yourself: a message in the channel you actually check.
7. Log errors: if any step fails, send yourself an alert with the raw data, so no inquiry is lost.

Step 7 matters most. But it is the step most founders skip. So add it first, before you trust the workflow with real leads.

What not to automate

• Pricing and discounts.
• Replies to objections.
• Anything that sounds like the customer is making a decision.
• Relationship-building messages pretending to be personal.

Founders in the r/Solopreneur community on Reddit say it clearly: automating relationships adds noise.

Common automation mistakes

1. Automating before the process is clear. If you can’t write the steps on a napkin, a workflow will only make the confusion faster.
2. Too many tools. Each new tool adds a login, a bill and another copy of the customer. Add one only when it removes work.
3. Messages that pretend to be personal. “Just bumping this to the top of your inbox” fools nobody. Short and honest beats fake personal.
4. No owner for the automations. When a form changes or an API breaks, something silently stops. Check your key workflows once a month.
5. Measuring sends instead of outcomes. Emails sent is not a result. Replies, meetings and payments are.
6. No way to stop. Every sequence needs a stop rule: they replied, they said no, or they asked you to stop.

Where AI fits in marketing automation

Classic automation follows fixed rules: when X happens, do Y. AI adds judgment to some of those steps. But judgment can be wrong, and a wrong message to a customer costs more than a slow one. So use AI where a human still reviews, or where a mistake is cheap.

A good test: if the step went wrong once a week, would a customer notice? If yes, keep a human in the loop.

Example: Stretch Tent

At Stretch Tent, a tent business in Southern California operated by Yaro Korets, the first automations were intake and follow-up: website and Meta leads sync into the CRM with their source, every inquiry gets a call and then a text, and every quote has a follow-up date. One person now handles 20+ leads a day, including individually prepared quotes (first-party, October 2026).

The order mattered. The business did not start with newsletters or nurture sequences. But once every inquiry had a source, an owner and a next date, the daily list of who to call became short and clear. So one person could keep up with the volume without leads going cold.

A two-week rollout plan

How to know it is working

Watch four numbers for a month:

• First response time: how fast a new lead hears from you.
• Leads with a next step: the share of open leads with a date.
• Quotes followed up within 3 days: the share that got a second touch.
• Leads with a source: the share you can trace to a channel.

If these four improve, revenue usually follows. If they don’t, the automation is running but the leaks are still there.

When automation breaks: a troubleshooting table

Most problems are not the tool. They are a missing rule: who owns this event, when does this stop, and where does the error go.

What to automate next, once the leaks are closed

When intake, follow-up and reporting run without you thinking about them, three automations usually pay off next:

• Review requests. A few days after delivery, ask happy customers for a review in the place your buyers look. Send it once, with a direct link.
• Referral asks. When a customer says something kind, a task reminds you to ask whether they know someone with the same problem.
• Nurture for “not now” leads. People who said “maybe later” get one useful message a month: an example, a short guide, a seasonal reminder. Stop the moment they reply or ask you to stop.

Each one builds on the clean data from the first six steps. But none of them work if leads still arrive without a source or an owner. So add them only after the basic recipes have run cleanly for a few weeks.

A simple order to follow: leaks first, then reviews, then referrals, then nurture. Newsletters and large campaigns come last, once you know which customers you want more of.

Questions and answers