Every engagement starts as a diagnosis.

How to choose between them

The eight engagements are not eight products. They are eight places a publisher's revenue commonly goes missing, and most engagements end up touching two or three of them — a render rate problem turns out to be a wrapper timeout problem, a reporting discrepancy turns out to be a trafficking one. Picking the closest fit is enough; the diagnosis stage finds the rest.

If you already know which number moved, start from the engagement that owns it. If you do not, start anywhere: programmatic & ad stack strategy, video monetization, revenue operations & yield management and adtech evaluation & implementation are the four most publishers arrive through, and data, audience & brand safety; ad operations & campaign management; mobile & emerging formats; strategic advisory & executive support are the ones that usually turn up during the work rather than before it.

What every engagement has in common

Each runs in four stages, and the first stage is always an inventory rather than a recommendation — "Full stack inventory", "Capture real requests" and "Reconcile the sources", and so on. Nothing is proposed before the current state is written down, because the current state is almost never what the last runbook says it is.

Each ends in named deliverables rather than a report: an as-built map, a scorecard built from partners' own numbers, and a change log sequenced so every item is measurable on its own. Working sessions run with your engineering and AdOps teams so the changes survive the engagement.

The scope, in numbers

Between them the eight engagements list 53 distinct areas of scope. The widest is video monetization at 7; the narrowest is programmatic & ad stack strategy at 6, which is not a smaller engagement so much as a more sharply defined one. Every area is listed in full on the page it belongs to — open an accordion below to see the scope before you email about it.