What does an AI-native marketer actually do?

Switching the models off should stop the work

An AI-native marketer runs a system in which models do the repeatable production, while a person owns the buyer, the message, the quality bar, and the result. Switch the models off: if the loop merely slows, the work is assisted.

CXL’s 2026 guide names three levels and sells training on the last. Assisted is a tool for one task, then a manual handoff. Integrated connects tools. Native means the model is the default engine. In its B2B survey, 55% are beginners at workflow redesign and only 10% call that a top skill, 65% are beginners at building systems, 42% name generic output as the top content failure, and 37% name hallucinated data as the top AI failure. Its June 2026 benchmark put 57% of marketers at assisted, 34% at integrated, and 9% at native. Improvado, writing about its customers, draws the cut on the work: assisted means people still execute, and native means the default path runs through an agent.

fdpm.ai, last checked by its authors on 9 August 2026, scores you on what the system achieves, not on assets you typed. You keep judgment, taste, and distribution. Their doubling test: if volume doubled at the same quality, would results double? If not, production is not the constraint. That is a different buy from a traditional digital marketer who adds a chatbot to an old process.

Three human functions fit in one startup seat

A startup seat holds two or three of the human functions, not six jobs. Diego Lomanto, CMO at Writer, on 23 July 2026 says most people do that from one seat. Writer sells the software. He keeps four functions with people and two with agents. He calls this a rebalancing of who does what, not a reorg, and says what changes is where the time goes. An AI lead next to an unchanged team does not change how the rest of the team works. He cites a reported gap: 70% of CMOs call AI leadership a critical goal, and only 30% report the readiness to scale it.

Function	Who holds it here	Done when you can point at this
Strategy	You, with a recommendation	Buyer, offer, the bet, and why
Architecture	Specialist exception: one workflow	One workflow a colleague can run
Curation	The marketer	Voice, allowed claims, banned phrases, one yes and one no
Orchestration	The marketer	A goal, a review, and a kill
Execution	The model	Drafts, variants, reformatting, first-pass research
Sensing	The model, if connected	A flag in time to act, not a decision

He treats architecture as the specialist exception. One marketer holds a single workflow only after the buyer and the bar are written. A second hire, if there is one, builds that workflow. Curation has to be text an agent can follow.

He describes a content manager who used to write 10 posts a month and now curates a system that writes 50, and a campaign manager who used to build one campaign and now directs five at once. He says he watched that on his own team and on customer teams. It is his observation, not a benchmark.

SaaStrix, in August 2026, cites ads at Stripe, Toast, and CrowdStrike: map the work, decide what to automate, and keep a person on governance. Stripe’s ad also says build the agents. They are not a template for a team of six.

Friday should show a loop, not a chat log

The job is real when a second person can run one recurring output without the author present. A chat log is not that artifact; a written bar and a known failure are.

CXL’s five places: one brief into a set of assets, research checked against more than one source, a process retired rather than prompted, an experiment loop that must not invent the total (42% in that survey call themselves beginners), and approval plus notes a team can run. A private prompt library fails the last.

What you are shown	What it proves	What it does not prove
A polished draft	They can edit	That a system exists
A bar and a loop with a failure note	The work can outlast the author	That the bet was right
A tool list and a volume chart	Fluency	Judgment

Improvado treats prompt fluency as baseline literacy. The failure in those customer notes is confident garbage: formatted, safe, and average. Ask for a refusal with a reason, such as a stale segment, a claim absent from the proof file, or a voice already killed. See an AI-native marketer at seed and where to hire one.

One scored output, then a second

A week is one named loop, scored on work you already trust. Before you read a draft, write the claim that has to be true and the buyer it is for. SaaStrix, on 31 May 2026, says fluent prose is not evidence once a model is in the loop. Notice whether you are lightly editing or rewriting. Keep writing some of the craft yourself so that ear does not die.

1. Name one recurring output. A launch is the same shape: buyer questions, one message, variants, a claim check, a small test, then stop or continue.
2. Write voice, banned phrases, and one yes and one no before the prompt. fdpm.ai’s point is that this file, not the prompt, is the asset.
3. Score it on past examples. Fix the failure that repeats.
4. Run it where the team already works, with notes and a failure alert.
5. Schedule it only after that. Faster mediocre work is a liability.

SaaStrix retells two shortcuts that failed in the one public transition it reviews. Handing out tools stayed personal and did not change how campaigns moved. A fully autonomous system failed because it did not know what good looked like. The order is tasks, then workflows, then agents, built by marketers. Results in that account are company-claimed, and the firm sells the work.

That account says workflow redesign is the trait McKinsey’s 2025 survey most associated with reported impact, and only about 21% of organizations using generative AI had redesigned any workflow. There is still no controlled study that this operating model beats a conventional team. A field experiment on ad production found human-AI teams more productive per person, with better copy and worse images, and similar campaign results overall. The UK ICO’s staff policy, first published in August 2025, requires a person to review outputs unless its approval body agrees otherwise, and it names no share that may skip review. A claim, a customer email, and the choice of buyer stay with a person. Automating repetitive work is that first loop, not permission to send.

Each craft keeps a different decision

The model takes a craft’s production first. The person keeps the call that compounds. fdpm.ai’s map is a field guide, not a measurement.

Craft	The model takes first	The person keeps
Content	Drafting, repurposing, SEO variants	Editorial judgment, original reporting, voice
Product marketing	Collateral, release notes, deck production	Positioning, customer insight, narrative
Growth	Ad variants, landing pages, test setup	Channel strategy, economics, experiment design
Field	Event logistics, follow-up content	Customer proximity, industry fluency, proof
Brand	Asset production, adaptation	Taste, distinctiveness, the thing AI averages away

The table does not retire specialists. See whether one person replaces specialist freelancers, and hire a fractional growth marketer who builds automations when the gap is one growth workflow. fdpm.ai calls the forward-deployed marketer title embryonic, including posts at Cognition and Hightouch.

Refusing a draft is the actual craft

Kill bad output, then use the hours for conversations and distribution you own. Hand the model the strategy note, the voice file, and the success test, or it fills the gap with an average. Improvado’s layer of three to seven seniors is an enterprise shape. If you cannot say why a draft is wrong, leave the loop off.

Walk away when:

• They show drafts and no workflow that ran last week without them.
• They cannot name a draft they killed, or why.
• Output is up and pipeline is not. SaaStrix calls that the faster-content trap.
• The bar is only in their head, or the prompts live in a personal login.
• They will not say where the system fails, or they want the model to pick the buyer.

A go-to-market engineer is a different hire. In that SaaStrix account, hiring clusters at Series A to C B2B SaaS, and the usual path in is sales development or revenue operations. Most other AI marketing reqs are an existing job plus a tool requirement.

Keep this operating model parked

Leave the models in a supporting role when the offer is blank, when more output would not move results, or when nobody will review a line a buyer could see.

1. You cannot name the buyer and one proof point. Fix the words first.
2. More assets would not create more conversations. The doubling test fails.
3. Nobody can refuse a bad line this week. Do not automate the send.
4. You are copying a transformation director into a team you do not have.

Where I start when you hire me for this

I am Piet Baudoin, an AI-native growth marketer for startups. Poldermarketing is my one-person practice. I offer an all-in GTM solution, marketing, AI, and automation together, for freshly funded startups anywhere, fully remote, from first message to first customers. I work in Dutch and English, and you can hire me freelance or for a few days a week. I build and execute. I do not only advise.

I build the loop in your accounts. Notes and access stay in your name. 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 to scale a large paid program.

If the site does not yet say the offer, the loop will not repair it. The free growth scan shows how the current site reads. How I work is the shape of an engagement. Positioning and messaging is where I start when the words are the constraint.