Marketing Automation Specialists: The Brief to Send Them

A marketing automation specialist builds and runs campaign workflows inside a platform you already chose: email sequences, segmentation, lead scoring, the CRM sync and the reporting on top. It is an execution role, not a strategy role, and the published job listings say so plainly. What you get back depends almost entirely on the brief you write before the first call.

The brief to send

Here is the whole thing. The platform, the invoicing product, the event name and the email count are placeholders, not a job I ran; replace them with yours.

Platform: HubSpot Marketing Hub, my portal, already connected to my product.
Scope: four lifecycle workflows for a solo SaaS trial.

What I supply before you start
- The activation event, already arriving in the platform: "first invoice sent"
- Final copy for the four emails
- The exit condition for each one, written out
- Two test contacts on addresses I control

What I am buying
- The four workflows built and enrolled against those conditions
- Suppression so no contact receives more than one of these in a day
- One saved report: sends, exits and errors per workflow
- A written note on any condition the platform cannot express as I wrote it

Access
- One user, Marketing email and Workflows at Edit, Publish left off
- I publish after acceptance, then the user is removed

Acceptance test
- Enroll test contact A, fire the activation event, then show me which
  email sent, which three did not, and which workflow the contact left
- Repeat with test contact B, for whom the event never fires

Out of scope: copy, the offer, pricing, and choosing the platform.

Three lines do most of the work. "What I supply" is the honest part: if you cannot fill it in, you are not ready to hire. The acceptance test is a demonstration on a contact you own, not a screenshot of a canvas. And "out of scope" stops the quote from quietly growing into a strategy engagement priced by the hour.

What the job listings actually ask for

Coursera's career guide for the role lists the day job: design and build email campaigns, manage lead generation and nurturing while developing a lead scoring system, monitor campaigns and report on return, troubleshoot the software, and work inside HubSpot, Marketo Engage or Salesforce Account Engagement (career guide). Robert Half's role page compresses the same thing into three duties: create and execute campaigns and workflows and test performance, report findings and recommend improvements, and run lead scoring and segmentation.

The sentence worth reading twice is on Robert Half's careers page. Specialists "build, launch and maintain programs so campaigns run flawlessly"; managers "own the overall strategy, platform management and team coordination" (marketing automation careers).

That has a direct consequence for your search. If what you need is someone to decide what gets sent and to whom, the word "specialist" is pointing you at the wrong half of the market. Search for a manager or a consultant instead. Same skill family, different purchase, different rate.

“

A specialist will build exactly the sequence you describe. The event that means a customer got value still comes from you.

”

What one costs

The same Robert Half page puts a US marketing automation specialist at $70,500 for someone new to the role, $82,750 mid, and $97,250 for extensive experience, from its 2026 Salary Guide. That is an employment number, and it is not the one you need for four workflows.

For contract work, goLance's 2026 rate guide lists roughly $20 to $40 an hour at zero to two years, $40 to $80 at two to five with a $60 average, and $80 to $140 at five to ten (hourly rate guide). Upwork maintains a live cost page for the same role, worth opening for today's figure rather than trusting a number printed in any article, including this one.

Then ask for a fixed price against the acceptance test rather than an hourly estimate. You cannot audit hours spent inside a platform you do not operate. You can audit whether test contact A got exactly one email and test contact B got none.

Give access you can take back

HubSpot's permissions are granular enough to hand over the build without handing over the button. Under Automation, Workflows splits into View, Edit, Publish, Enroll and Delete, and Marketing email splits into View, Edit and Publish (user permissions guide). Grant Edit, leave Publish off, and the work arrives finished but inert until you accept it.

The harder question is whose account the automation acts in once it reaches your other apps. It is the same question as connecting an agent to your apps: the answer decides whether a personal token is quietly holding your CRM sync together. Settle it before anyone wires the integration, because moving it afterwards means rebuilding what you just accepted.

The two things this brief does not buy

The first is the event that means someone got value from your product. Not a signup, not a click. The four triggers worth building first all hang off that one name. Someone with access to your usage data can help you find it, but that is analysis, and it is not what a build engagement pays for. On this brief the name arrives from you, or the workflows get hung on a proxy like a login.

The second is the offer, which is to say the reason any of these emails deserve to arrive. A specialist can build a nurture sequence for a product they do not understand, and it will run correctly and convince nobody.

Supply neither, and what comes back is the templated setup, which fails in the same predictable ways as the eight mistakes solo stores make with their first automations. The build was fine. Nobody had decided what should happen.

One item on the job listings does not belong in an hourly brief at all. Scheduling social posts and ads appears in the task list, and it is the part most cheaply replaced by a product rather than a person: ReadyToPost writes and schedules posts and handles the replies. Buy hours for the work that touches your own data.

FAQ

Should I insist on a certification?

It tells you which platform someone has operated, not whether they will read your exit conditions. Adobe expects "approximately 18 months of experience" before its Marketo Engage Business Practitioner Expert exam, AD0-E559, which puts 46% of its weight on campaign management (exam page). On Marketo or Salesforce that credential is a real filter, because the build is hard to fake. On HubSpot the acceptance test tells you more than the badge.

What if I already have a working program?

Then the framing flips and a specialist is the right hire. With a strategy already running, most of what you buy is genuine build and maintenance work, the scope runs well past four workflows, and the brief becomes an ordinary statement of work. What does not change is the acceptance test: still a named contact, still a fired event, still you pressing publish.