Definition · deliverables · published prices
What is a marketing engineer?
A marketing engineer runs acquisition the way a software team runs a product: scope is written down, work ends as artifacts at public URLs, a test states in advance how much volume it needs, and everything is built inside the client's own accounts. Marketing is the judgement; engineering is what makes it checkable.
The job in one sentence
Decide what to build, build it so it can be measured, and kill it when the number says so — with the files left in your hands.
Decide
Offer, audience, exclusions, the smallest difference worth detecting. Written before anything is built, because that decision sets the volume and the price.
Build
Landing page, source pages, a free tool, sending domains with SPF/DKIM/DMARC, tracking events. All under the client's logins.
Read and kill
Interpretation happens against a pre-declared floor: cold email reply-rate tests need roughly 1,500–2,000 sends per variant before a difference means anything. Below the floor, a verdict is noise.
How it differs from the three usual options
Agency retainer
You rent attention and activity. Accounts and files stay with the agency, so the asset leaves when the contract does.
Freelancer by the hour
Cheap per hour, unpriced per outcome. Scope drifts, and nothing forces the work to end at something you can open.
Marketing engineer, fixed scope
Fixed package, published scope page, artifacts live at URLs you can point at, ownership from day one. The cheapest way to find out whether a channel works at all.
What you can point at
Judging this page is not the point — judging the work is. These are the live artifacts from the same engine, published with their links:
- Proof page — every shipped artifact with an openable link.
- What shipped — the artifacts this method produced, with dates.
- Scope of work — what is inside each package and what is deliberately not.
- Pricing — packages, and the comparison against agency and hourly work.
- Fractional marketing engineer — the part-time seat: senior build, fixed packages, everything handed over.
- Marketing automation engineer — the machinery behind the marketing: capture, routing, suppression, alerts.
- Marketing engineer cost — the three published packages and what each one buys.
- Growth engineer for hire — the path built, instrumented and measured, with the packages published up front.
- AI marketing engineer — the machinery marketing runs on: agent skills, quotable pages, automation and kill rules.
- Marketing engineer services — the seven deliverables, each with something you can open before paying.
- How to become a marketing engineer — five steps, each with something you can open: one channel, a measurement stack, three dated public artifacts.
- Marketing engineer vs freelancer — what you are actually buying: who owns the number, how the work is checked, and what you keep at handover.
- Marketing engineer vs growth marketer — what each role owns by default, the first readable result, and four signs that decide the hire.
- Marketing engineer for agencies — an agency cannot pool its clients' traffic, so every client needs its own floor and its own read-out date: 13,914 per arm (27,828 total), 14 months for a client at 2,000 contacts a month, and 4,638 contacts a month as the smallest client readable inside 6 months. li>Marketing engineer for marketplaces — two funnels that must be readable at the same time, liquidity as the readable unit, why each side needs its own floor (13,914 per arm; 27,828 in total; 70 months for a 400-seller-a-month supply side) and the four decisions taken before the first contact.
- Marketing engineer interview questions — the six questions that separate an engineer from a marketer with tools, what each answer really measures, the volume a verdict needs (13,914 contacts per arm; 27,828 in total), and the four things the interview cannot decide. li>Marketing engineer for devtools — why the readable unit is the first successful call rather than the signup, the volume a verdict needs, and the stop rule that has to exist before the spend.
- Marketing engineer for fintech — why the readable unit sits after identity and funding, the volume a verdict needs, and the stop rule that has to exist before the spend. li>Marketing engineer retainer — the invoice line by line, the four decisions a retainer cannot make for you, and how many honest tests a month can actually hold at your volume.
- Marketing engineer job description — the four decisions and six lines to write instead of a tool list, the artifact due each week, the volume a strict test needs, and a free generator. li>Marketing engineer for B2B — the lead, source and reply definitions that decide whether a channel can be judged, the five things that exist before the first send, and the floor an honest test needs. li>Marketing engineer for SaaS — the five numbers most plans are missing, what gets instrumented first, and what ships in a $900 Sprint.
- Marketing engineer for startups — the three routes a seed-stage team compares, what the first 30 days produce, and the floors the numbers have to clear.
- Marketing engineer for ecommerce — why last-click revenue is not a verdict, the spend gate, and the traffic floors a store test has to clear.
- Test-size calculator — free, runs in the browser, no signup: how much volume a test needs before you may judge it.
Questions people actually ask
Is a “marketing engineer” just a growth hacker with a better title?
No. The difference is what you can inspect. A growth hacker sells experiments; a marketing engineer hands over files: a page on your domain, a calculator, a sending setup that passes a deliverability checklist, a tracking event in your own analytics property. Every claim here can be opened, and if it cannot be opened it is not counted.
What does it cost and how is it sold?
Three fixed packages, published before you talk to me: Sprint $900 one-time, Engine $1,900 per month, Full build $2,900 one-time. Scope for each is written on the pricing and scope pages, so there is no discovery phase used to size the invoice.
Do I have to hand over my accounts?
Only as a seat inside your own accounts. Nothing is built under my logins — pages live on your domain, analytics lives in your property, sending lives on your domains. Handover is not a migration, because there was never anything to migrate.
What happens if nothing ships in a month?
The month is free. That term is on the offer page, not buried in a contract: deliverables are files on the internet, so “shipped” is not a matter of opinion.
Which parts are technical, and which are marketing?
The seam is the point of the job. Copy, offer and positioning decide what gets built; the engineering decides whether it is crawlable, measurable, deliverable and repeatable. Holding both halves in one person removes the usual week of hand-offs between an agency and a developer.
Next step
Send what you sell and what you have already tried. You get back a fixed scope and a price, not a request for a discovery call.