Email Marketing Automation Freelancer: A 25-Point Scorecard

A 25-point scorecard for hiring an email marketing automation freelancer: sending domain, warm-up, list and consent, flows, tests and handover, with sources.

By Carlos Familia, CRM & AI automation expert. Updated October 15, 2026. 6 min.

Before I trusted my own email system, I ran a pilot on one demo account: 12 test journeys through the email workflows, 260 executed steps, 12 of 12 passed. Building and testing those demo accounts taught me how much a green result can hide. GoHighLevel keeps writing "condition: success" rows while a contact waits, so the newest log row is not the state of anything. Workflows triggered by a tag can start late when the account is busy. And a failed publish can leave behind a draft with the same name.

None of that shows in a screenshot, so the scorecard below is built around what a freelancer can prove.

How do you pick an email marketing automation freelancer? Give each of the 25 items below one point, but only when they show you proof, not when they say yes. A score of 23 or more is a hire. A score of 19 to 22 is a hire with the gaps written into the scope. Anything under 19 means they build emails, not systems.

Sending domain and authentication (5 points)

Mailbox providers set the floor. Google's sender guidelines require SPF or DKIM from every sender and ask for spam rates under 0.3% in Postmaster Tools. Above 5,000 messages a day to Gmail, they require SPF, DKIM and DMARC, an aligned From domain and one-click unsubscribe for marketing mail. Most small lists sit below that line, but a freelancer who builds to the strict standard saves you a rebuild.

• Mail goes out from a dedicated sending domain, kept apart from your staff mailboxes. On my own sub-account I set one up with SPF, DKIM, DMARC and MX records.
• SPF and DKIM pass, and the From domain aligns with at least one of them.
• A DMARC record exists. Starting at p=none with reporting is acceptable, and Yahoo's sender requirements list p=none as the minimum.
• The freelancer shows you the verified status in your sending settings and a result from an outside checker.
• Google Postmaster Tools is connected, so the spam rate is something you can see.

Warm-up and volume (4 points)

HighLevel's warm-up guide describes fixed stages, starting at 1,000 emails a day and moving up one stage only after the domain sends the full daily limit. Warm-up starts on its own for new domains, and existing domains need it turned on by hand. Missed days pause progress without a penalty.

Warm-up matters most when email is your only channel. A roofing contractor in Kentucky had no texting registration yet, so email was the only channel its follow-up had. A new domain that blasts a full list on day one burns the one channel you still have.

• Warm-up is switched on, and the plan names the first stage's daily limit and the date you can expect to reach full volume. HighLevel's email sending guide puts warm-up at about four weeks.
• The first campaign goes to a validated list. HighLevel's email sending guide offers first-send validation at $2.50 per 1,000 validations, with a re-check every 90 days.
• Hard bounces are removed at once.
• There is a sunset rule for contacts who never engage. The same guide suggests slowing to weekly after one to two weeks without engagement, and stopping after two months of weekly sends with none.

List, consent and unsubscribes (4 points)

• Every email has a visible unsubscribe link, and Yahoo asks senders to honor unsubscribes within 2 days.
• The freelancer has tested what each Do Not Disturb action really does. In one of my builds, the workflows meant to stop email after a bounce or a complaint switched email Do Not Disturb off instead.
• You can see where and when each contact opted in.
• Form sign-ups confirm by double opt-in wherever the list matters. HighLevel's email sending guide says double opt-ins significantly boost domain reputation.

Flows that should exist (5 points)

For a service business, the core list is a first reply to a new lead, appointment confirmations and reminders, no-show recovery, a review request and old-lead reactivation. My niche demo accounts carry an email system of 34 workflows each, and a script checks the 48 emails per niche for errors. The scorecard asks for something smaller and checkable.

• A written map of the flows, with the trigger of each one.
• Every flow has an exit: a reply, a booking or an unsubscribe.
• Re-entry is decided on purpose. A workflow that blocks re-entry never confirms a returning customer's second appointment.
• If you serve two languages, both branches are tested, not just the English one.
• Shared templates get a test send before any edit goes live, because in GoHighLevel an edit to a saved template reaches every published workflow that uses it.

Tests you can see (4 points)

• A test contact with Do Not Disturb on and no real address walks each path, and you get the execution logs.
• Loops are proven with real one-minute waits. Force-resuming a loop more than about four times hits GoHighLevel's loop lock, so the shortcut cannot prove a loop.
• Open rates are not used as proof. Gmail loads the tracking pixel when it delivers the message, so an unread email can still show as opened.
• The tester reads the whole log, not the last row.

Handover and balances (3 points)

• You hold the logins for the sending domain, the DNS and the account.
• Someone owns the wallet. Premium workflow actions skip silently when the agency wallet is empty, and on that same Kentucky build an empty email wallet blocked sending altogether.
• There is a named alert for silence, such as no sends in a day when sends are expected.

How do I run the scorecard on a call?

Ask the freelancer to share a screen and open four things, in this order: the sending settings with the verified records, the execution log of a test contact from a recent build, the list of email templates with the workflows that use each one, and the wallet or usage page. Score as you go and write the number next to each item.

Someone who has worked in an account opens all four in a few minutes. Someone who needs a day to pull it together is describing work they have not seen. Treat "I'll send you screenshots tomorrow" as a zero for those items, and ask again for the live version.

How do I score a freelancer?

Two items are automatic fails, whatever the total: no evidence of SPF, DKIM and DMARC, and no test logs. Without the first, mail lands in spam. Without the second, nobody knows what the flows really do.

What does a passing score mean?

A passing score means the freelancer has already hit the usual failures somewhere else. It does not mean the emails will convert. Copy, offers and your list decide that.

Whatever the score, start with one flow in your own account: a welcome email for a single form, a test contact with Do Not Disturb on, the execution log, and a deliberate failure so you see the alert fire. Pay for that test before the full system. For the wider scope, read my guide to hiring a marketing automation consultant, and for the text-message side, SMS marketing automation specialist. When texting is waiting on registration, email goes first, and GoHighLevel A2P explains the wait.

My testing method is in how I test GoHighLevel workflows, and the usual build traps are in GoHighLevel workflow mistakes. If you want a second pair of eyes on a proposal, book a call and bring your scores.

About the author

Carlos Familia, CRM & AI automation expert. GoHighLevel, n8n, AI agents, servers. Full-stack developer.

I build CRM systems in GoHighLevel, n8n automations on my own servers and AI voice and chat agents for service businesses. Full-stack developer: I write the workflow, the API integration, the database and the server it runs on, and I test every build with real journeys before handoff.