Seven services, seven receipts: what a marketing engineer's service list should let you check

A service list is worth nothing if you cannot check it.

Most "what I do" pages are a list of nouns: strategy, campaigns, funnels, growth. Nothing on them can be opened, dated or verified, so the buyer's only option is to trust the adjectives. I write mine the other way around — seven deliverables, and each one ends in a URL that returns 200.

Here is the list, plus the part that matters more: what each line lets you check before you spend anything.

01 · Capture — the page that has to convert

One question answered in the first 60 words, prices stated as numbers, Service/Offer and FAQPage markup, readable without JavaScript.

Receipt: the offer page itself. Open it, count the prices, disable JS, read it again.

02 · Machines read — schema, sitemap, llms.txt, IndexNow

Answer engines do not guess. They read structured data, a sitemap, and a file that states what the site actually answers. Every new URL gets pinged the day it goes live and archived so there is a dated snapshot.

Receipt: llms.txt, sitemap.xml, and the free 23-point readiness checklist.

03 · Demand — outbound and lifecycle email

List, sequence, deliverability, suppression. Sending domain and volume are stated up front, and the test size is calculated before the first send instead of argued about after the replies.

Receipt: the done-for-you lead generation page and the free test-size planner.

04 · Plumbing — 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.

Receipt: the automation engineer page and the scope document.

05 · Decisions — measurement and kill rules

The part most engagements skip: one event that matters in your own property, the sample size each test needs before a result counts, and a written rule for what gets killed and when.

Receipt: the free kill-rule calculator.

06 · Production — agent skills instead of one-off prompts

The operating file an agent loads every single time: what to do, what never to do, and which numbers are floors rather than opinions. Versioned and published, not pasted into a chat.

Receipt: the skill repo on GitHub, the same method as a CLI on npm.

07 · Trail — distribution that leaves a public record

Work shipped where the next buyer and the next model already read: registries, repos, articles, archived snapshots. Nothing is a "case study" without a URL.

Receipt: the proof page — every artifact, with a date.

The rule that keeps the list honest

If a line in the table cannot be opened, it does not belong in the offer.

That rule has a consequence most agencies would rather avoid: it applies to the service page itself first. So the receipts are not screenshots or logos — they are the artifacts. A page that returns 200. A package on a public registry. A repository with a commit history. A free tool that runs in your browser with no account.

This is also why there are no strategy decks in the offer. A deck tells you what is wrong; it does not change a conversion rate. If the honest answer is that you only need a document, the free tools on the site cover it at no cost — sizing a channel before you fund it, checking whether the site is even readable by answer engines.

What a buyer can check before the first call

Four checks that take about ten minutes and cost nothing:

1. Do the prices exist as numbers on the page? If pricing needs a call, the scope is undefined.
2. Is the machine-readable layer real? Fetch llms.txt and sitemap.xml. A site that sells AEO without them is selling something it does not run.
3. Does the proof page carry dates and links? Claims without URLs are decoration.
4. Is the exit written down? Mine is fourteen days' notice on the monthly block. A retainer you cannot leave is a lease.

The packages, publicly

Sprint — $900, one path built, instrumented and live in a week.
Engine — $1,900/month, build, measure, kill the losers, scale the survivor.
Full build — $2,900, everything handed over running, including documentation, so the system survives without the operator.

Pages, sending domains, analytics property, CRM and repositories stay in the client's accounts from day one. Ad spend and subscriptions stay on the client's cards with no markup.

The service list lives here: marketing engineer services, each line with a receipt.

If your bottleneck is on that list, one line about it is enough to get a straight answer — including "this is not in scope":

Start with a description of the broken path →