What should I look for in a marketer who can also build automations?
Screen one person who defines a qualified lead, the failure path, and one number showing the workflow earned its place. A tool list is not evidence. Draw the route, consent, and retry. Add engineering skill when a retry would duplicate people, or when a model classifies or drafts and a person still approves. Keep accounts and keys in your name.
Judge the handoff, not the logo row
Hire the person who can say what to automate, what stays manual, and which recorded outcome would show the workflow earned its place.
Three purchases hide in one title. A growth marketer chooses the buyer, the message, and which test stops. A marketing operations manager, as Pedowitz Group describes the seat, runs intake, taxonomy, platform admin, launch checks, and training for other people. Hire that title when routing and reporting are the pain and a marketer is already shipping campaigns. A connector only moves records between apps. You want the growth marketer only if that same person also ships the workflow. Splitting the hire is for when the crafts do not sit together. The seed freelance screen is the marketing half on its own.
Markampus states the operations test: explain what a field means, which system owns it, what should happen when it changes, and how you would know the process worked.
Four grades of builder
Name the grade the work needs before you name the person.
| Grade | They can show | Stop when |
|---|---|---|
| Sender | One sequence, and the message | The job crosses tools, or a blank must not be guessed |
| Connector | Trigger, branch, exclusion, approval | No retry rule, so a rerun would duplicate or resend |
| Integrator | Field map, webhook or API, alert, a note | The step needs code, a model test set, or a reshape |
| Engineer | Code or an agent, logged prompt, a gate before send | The tool you already run can do this step |
Pedowitz wants this person configuration-heavy and code-aware, and says to call an engineer for custom development. Markampus says coding is not required on every operations role. SQL, APIs, and scripting matter when the integration is deeper. Custom agents are the fourth grade. A marketer versus an automation consultant is owning the motion versus only wiring tools.
Write the definitions before any branch
Do not automate a stage nobody can define. Keep four ideas apart: who the buyer is, what qualified means, what they did, and whether you may message them.
Sitecore puts the tool last, after the buyer, the journey, the goal, and the count. It never screens the person.
HubSpot, updated 17 July 2026, lists default stages: Subscriber, Lead, Marketing Qualified Lead, Sales Qualified Lead, Opportunity, Customer, Evangelist, and Other. Subscriber means opted in. Lead means a conversion past that signup. Qualified is yours to define. You may replace the labels, and default tools only move a stage forward. Markampus says a default label is not universal. A contact, a company, and a deal are different records: two people at one company are not necessarily duplicates, and one person at three events is not necessarily three leads.
A form fill is interest. Fit is the match to the buyer. Engagement is what they did. Permission is separate. Markampus says a promising enquiry is not a reason to change subscription status, and unused fields add maintenance and privacy risk. Braze (January 2026) separates a scheduled blast from a flow that reacts. Cart and loyalty examples are a consumer stack, not one B2B lead path.
The failure path is the work sample
A workflow is finished when the ugly cases are written, not when the happy path creates a row. For the motion you are hiring for, the lead route, onboarding, or a report, not a cart recovery, the diagram stores consent, applies your rule, routes who passes, parks the rest, alerts when intent changes, and names one outcome you defined.
It has to cover the five rows of the Markampus test matrix:
- One valid in-region request, one owner, one task.
- A support request never enters prospecting.
- A missing region goes to review and is not guessed.
- A second submission follows a written rule and creates no unintended second task or message.
- An unavailable owner leaves the record in a queue someone can see.
Do not invent a company from the email domain. Markampus warns a full replay can send the acknowledgement again, so the candidate must say whether the retry sends it.
Debug one named record: did it arrive, did the values match, which branch ran, was an owner set.
A campaign tag names a referrer
Judge measurement by a definition they can re-run. Ask for a baseline, one conversion event, and whether you mean sourced, influenced, open, or won.
Google’s URL builder guide says utm_source, utm_medium, and utm_campaign show which campaigns refer traffic, and that values are case sensitive. Markampus draws the line those parameters do not cross: tags show where a visit came from, and they do not prove a touch caused a sale. Do not add one opportunity, touched by several campaigns, and call the sum unique revenue.
Refuse personal data in a URL, and name the number that turns the workflow off. Pedowitz’s data prompt starts from a messy field map. Ask them to propose a normalized schema, the lifecycle stages, a minimal attribution model, and how they would check that the model is right.
Permission, keys, and a note
The company stays responsible for the send, including when a freelancer builds it. Put the consent check in the workflow and keep the login in your name.
The UK Information Commissioner’s guide to electronic marketing limits unsolicited email and text under PECR. Rules are stricter for individuals than for companies. Sole traders and some partnerships count as individuals. Consent, where required, is a positive act for your organisation and that channel. A pre-ticked box does not count. Record what was agreed and when, and make withdrawal easy. You remain responsible if a freelancer sends, and that person works under a written contract. Messages sent outside the UK must also follow the destination’s law. Some EU rules are stricter than the UK, especially when the recipient is a company, so do not copy the UK sole-trader rule onto a company elsewhere. For the workflow, keep a suppression list, collect only fields the route uses, and ask which field stores the opt-in.
Albato’s chief marketing officer says complex CRM and triggered-email flows need a written note, or it is easier to rebuild them. On that page, automated copy misses nuance, an unattended flow goes stale, bad inputs produce bad sends, and a model does not fact-check the subject or the claims. The note names the owner, the trigger, the exclusion, and the off switch.
Markampus adds the rule for the test itself: practice on fabricated records, and do not export a live list to a personal spreadsheet. The instance, the keys, the prompts, and the notes sit in your workspace before a real record is in scope.
Engineering skill starts past the connector
Hire AI engineering skill when a step you already understand cannot live in the connector, the native sequence, or a reviewed template.
Two cases earn an engineer, or a marketer who can do that work. The connector drops fields and a retry would duplicate people. Or a model must classify, extract, or draft, and you hold wrong answers plus a rule for when a human still reads the output. Braze keeps eligibility, compliance, and fatigue as rules, and puts the model inside them.
Skip it when the tool already has the action, when you have not run the motion by hand, or when there is no trigger, no exit, and no recorded outcome. When automation makes sense for a small company comes first.
Gumloop’s 2026 roundup says basic setup that needs an AI engineer means the wrong tool. That is a shopping rule. The failure path, the consent record, and a custom step sometimes do need the engineer.
Run this screen on one diagram
Pay for that diagram, on fabricated records, in a workspace you own. Pass means they write the message in the company’s voice for your approval, keep judgement, negotiation, and bad news manual, and bring one workflow that went wrong.
They ask where leads come from, what qualified means, which fields exist, and who may be messaged. Fit stays apart from engagement. Before go-live they write the suppression list and the exit, such as a reply, an unsubscribe, or an existing customer, and they say when sales can send a lead back and force the rule to change. They name the field owner, volunteer at least three of the five ugly cases, and name one number and the off switch. Ask how they noticed the failure and what they changed.
Stop if they promise growth from AI, talk only about tools or a migration, show only the successful record, would mail a scraped list, keep logins personal, or start with outbound, ads, and a CRM replacement. Count a stage you defined, not posts and sends.
Pedowitz calls process design, plus aligning other people, the skill with the most reach. A fractional growth marketer who also builds automations is the contract after this screen.
Keep the seat empty for now
Keep the search closed when you cannot define a qualified lead, when the build is only a form and a chat ping, when nobody can approve the message, when the offer is the gap, when the job is a large paid media program, or when a marketing operations manager was offered and nobody is shipping campaigns yet.
I take the definition and the build
I write the buyer, the qualified rule, and the consent field, then one path into the CRM, with a failure alert and a check before a prospect sees anything.
I am one person, trading as Poldermarketing, working remote in Dutch and English. Hire me freelance for a bounded build, or for a few days a week. I am an AI-native growth marketer who advises, builds, and runs the work in your accounts, and I am strong in AI, content, automation, and workflows. Google Ads and Meta Ads are newer for me: I can set them up and review them, and I am the wrong person when the job is scaling a large paid media program.
For a freshly funded startup, anywhere, this is one remote engagement: marketing, AI, and automation, from the first message to the first customers, without a separate specialist for each part. The point is to move from invisible to a conversation with the person who decides. Keys and prompts stay in your name.
If the offer is still hard to say, routing will not fix it. The free growth scan shows how the site reads now. How I work is the shape of an engagement. Positioning and messaging is where I start when the words are the constraint.
Questions people ask
Do they need to code?
Not for the usual brief. Markampus says some operations roles start with configuration, spreadsheets, and testing, and that SQL or APIs matter only when the integration is deeper. Pedowitz describes the operations manager as configuration-heavy and code-aware, and says to call an engineer for custom development. Ask which step in your flow a connector cannot do. If they cannot name one, you do not need code. If they name three and still want to replace your CRM, shrink the scope.
Should they already know our CRM?
They should know objects, not a certificate. A contact, a company, and a deal are different records. HubSpot's lifecycle labels are defaults you can replace, and its tools only move the default stage forward unless you clear it. A strong candidate asks which system owns each field and what a missing value should do. A weak one lists product names and offers a migration. Name your stack. Accept an equivalent they have run if they can map your fields.
What should the paid test produce?
One diagram and one small build in a workspace you control, using fabricated records. The diagram names the trigger, the consent check, the route, one exclusion, and the retry. Markampus warns against moving a live customer list onto a personal sheet to prove skill. You are done when a colleague can follow the note and a failure alert fires on a record you break on purpose. Do not trade CRM access for an unpaid trial.
When is a marketing operations manager the wrong title?
When you do not yet have a team shipping campaigns. Pedowitz's manager owns intake, taxonomy, platform admin, launch checks, and training for other people. That is a function on top of a motion. A company with one motion needs the person who also chooses the message and runs the test, then automates the repeat. Hire the operations title when routing and reporting are the only pain and a marketer is already in the seat.