Marketing engineer services · priced before the call
Marketing engineer services: seven deliverables, each with a receipt
A service list is worth nothing if you cannot check it. So this one is written as seven deliverables and every one of them ends in something openable — a live page, a published package, a repository, a free tool, an archived snapshot. Packages are public before we speak: Sprint $900, Engine $1,900/month, Full build $2,900.
The seven services
Offer page built to be quoted
The page that has to convert: one question answered in the first 60 words, prices as numbers, Service/Offer and FAQPage markup, no JavaScript required to read it.
Schema, sitemap, llms.txt, IndexNow
Answer engines do not guess: they read markup, a sitemap, a file that says what the site answers. Every new URL gets pinged and archived the day it goes live.
Outbound and lifecycle email
List, sequence, deliverability, suppression. Sending domains and volume are stated up front, and the test size is calculated before the first send, not after the replies.
Automation, routing, failure alerts
The unglamorous half: where a lead lands, who gets notified, what stops the sequence, and what happens when the webhook dies at 3am.
Measurement and kill rules
One event that matters in your own analytics property, the sample size each test needs before a result counts, and a written rule for what gets killed and when.
Agent skills instead of one-off prompts
The operating file the agent loads every time: what to do, what never to do, which numbers are floors and not opinions. Published, versioned, reusable.
Distribution that leaves a public record
Work shipped where the next buyer and the next model already read: registries, repos, articles, archived snapshots. Nothing here is a case study without a URL.
Same list, as a receipt table
| Service | What you get | The receipt you can open |
|---|---|---|
| 01 Capture | A page that answers one question in the first 60 words and states prices as numbers | the live offer page |
| 02 Machines read | Schema, sitemap, llms.txt, IndexNow ping, archived snapshot | llms.txt · sitemap.xml |
| 03 Demand | List, sequence, deliverability, suppression, test size calculated first | lead-gen page |
| 04 Plumbing | Routing, notifications, stop conditions, failure alerts | automation page |
| 05 Decisions | One event, sample-size floors, a written kill rule per test | kill-rule calculator |
| 06 Production | Reusable agent skills, versioned and published | GitHub repo |
| 07 Trail | Public artifact list with dates and links | proof page |
If a line in this table cannot be opened, it does not belong in the offer. That rule is applied to this site first: the proof page lists every artifact with a date on it, including the free tools and the npm packages.
How the engagement works
One path, live in a week
Pick the broken or unmeasured path — usually the offer page or the machine-readable layer. It gets built, instrumented and running, and you keep it.
The continuing block
Build, measure, kill the losers, scale the survivor. Fourteen days notice to cancel — a retainer you cannot leave is a lease, not a service.
Handed over running
Offer, pages, outbound, automation, measurement and documentation, so the system survives without the operator.
Not sure which service you need?
Then start with the free tools, they answer the two questions that decide it: is the site even readable by answer engines, and does the channel you are funding have enough volume to be judged yet. Both run in the browser with no account. The third one sizes the test before you send it.
Questions people actually ask
What services does a marketing engineer actually sell?
Seven things, in this order: the offer page that has to convert, the machine-readable layer (schema, sitemap, llms.txt, IndexNow), outbound and lifecycle email, the automation and routing underneath, measurement with kill rules, agent skills that produce the work, and distribution that leaves a public record. Each one ends in an artifact you can open, not a slide.
Do you do strategy decks or audits?
No. An audit tells you what is wrong; it does not change your conversion rate. The cheapest thing here is a Sprint: one path built, instrumented and live in a week. If the honest answer is that you only need a document, the free tools on this site cover it at no cost.
Can I buy one service and not the others?
Yes. Most engagements start with service 01 or 02 because those two are measurable within days. Automation and measurement are usually added once the first path converts, since instrumenting a path that does not exist yet is decoration.
Is the work done in my accounts?
Yes. Pages, sending domains, analytics property, CRM, repository: all yours, from day one. Ad spend and subscriptions stay on your cards with no markup. When the engagement ends, the machinery is still there and still running.
How is it priced?
Three published packages, no hourly rate: Sprint $900 one-time, Engine $1,900 per month with 14 days notice to cancel, Full build $2,900 one-time. The comparison against a freelancer, an agency and a full-time hire is on the cost page.
What is explicitly out of scope?
Ad spend management, content volume promises, hiring, and anything requiring a paid licence paid for by me. The written line is on the scope page; if a request falls outside it, you get that answer in the first message rather than in month two.