Case study · In-house builds · Before this practice had a name
These predate Welnack. They're employer work across a broadcast and B2B career, which is why no employer is attached to any number — a boundary I hold, and the same discretion your business would get. What they share is the sequence. Every result landed after the system got built, not after the ideas got better.
Build 01 · Global B2B manufacturer
I inherited a marketing function with almost no pipeline contribution. The instinct everyone expected: launch campaigns, buy demand, show activity fast.
Instead, infrastructure first — a CRM built from zero across three brands, lead scoring, lifecycle stages, attribution. Months of work with almost nothing to show a status meeting. Then, on top of it, demand.
Growth in marketing-sourced qualified leads, eighteen months after the build started. Not creativity. Sequence — held at the exact point where skipping a step would have looked faster.
The uncomfortable lesson: the months of "nothing to show" were the result being built. Demand generation on top of no infrastructure produces activity. On top of infrastructure, it produces a number nobody argues with.
Build 02 · Brand governance, encoded
A brand standard that lived in a document had the usual problem: it was only as enforced as the memory of whoever was writing that day. AI raised the content volume, and governance by memory stopped scaling entirely.
So the style guides got encoded — voice, terminology, claims rules, formatting standards — into custom AI skills any team member could invoke on any draft. The rules stopped depending on recall and started running in the system.
Drop in content production time — while brand consistency went up, because the standards were enforced by the system instead of by memory. Faster and more consistent isn't the usual trade. It's what governance buys.
This build is the one that convinced me the failure was never talent. It was a governance problem wearing a creativity costume — and it's now sold as its own engagement.
Build 03 · Regional broadcaster
A regional broadcaster's site drawing 500 monthly visitors — effectively invisible. The build: figure out what the audience was actually asking, structure every page so a machine could extract the answer, and get cited in places that weren't our own domain.
500 to 50,000 monthly visitors in six months. The search era's version of the exact mechanics that decide AI visibility now — the machine changed, the method didn't.
And in the same discipline: a B2B email program's open rate, doubled by maintenance rather than a rewrite — list hygiene, authentication, segmentation, month over month. Click-through up two to three points.
Employers appear in my bio, where naming them is a fact about a career. They don't appear next to numbers, where naming them would turn in-house work into implied client engagements — and would attach specific results to companies that never agreed to be marketing material.
That's the standard this practice runs on, and it's the one your numbers would get.
The sequence is the product. Measure, encode, build, maintain — the same order every time, sold now as four engagements you can read plainly on the services page.
Before any build, find out what the engines already say about you. One page, forty-eight hours, no pitch inside.
I run a limited number each month, so there may be a short wait.
Takes about a minute. The more precise the last two answers, the sharper the report.
I'll only use this to run and send your snapshot. No list, no sequence you didn't ask for, and you can tell me to delete it at any time (see the privacy policy). I run a limited number each month, so there may be a short wait.