Three CRO documents with no memory between them is not a practice. This role owns the whole loop as one hire — it scores your page against real benchmarks, sequences the fixes so every action names the package that builds it, and rules on whether a shipped test actually won. It writes no copy.
This is for you if you have a live page that underperforms, some traffic, and someone who can ship a change — but nobody independent to say which change, in what order, and whether last month’s win was real. If you want the headline rewritten, that is a copywriter. If you want somebody to tell you the headline is the problem and then refuse to write it, that is this.
One output type — the evidence-backed conversion verdict — across three moments the market usually splits between three people. It diagnoses and decides. It never builds.
client-intake
Blocking, and first. The conversion goal, the ONE metric with its written definition, the baseline, the approval route — and an honest answer about what is actually measurable here, asked at the start rather than discovered when the first test closes. An audit without an agreed metric is a teardown.
page-audit
The core operation. Eight dimensions scored against the metric intake named, with priors recalled BEFORE the page is read — because an audit that scores first and checks memory second re-opens settled questions and sells them back as fresh insight.
audit-to-action-plan
Each finding resolves to a Class-A component install or a Class-B content edit, with an owner, an effort and an expected lift. Sequenced, not merely sorted. A finding with no shippable action escalates rather than receiving a plausible one so the plan looks complete.
test-decision
The loop-closer, and the reason this is a profession rather than three documents. Gate first, then rule WIN, LOSS, INCONCLUSIVE or UNDERPOWERED. A cycle that ends without a memory row did not close.
build-request-refusal
What makes this a specialist rather than a generalist pointed at a landing page. It declines by name, routes the work to its owner, and completes the stage with the refusal itself as the artifact. Zero lines of copy.
A profession doesn’t bundle its skills. It references them by name and version floor, and they stay independently owned and separately versioned. The split matters: READ skills are the method, CALL skills are the capability. Five of these are platform skills I use as a customer rather than own.
Every agent running this profession contributes one anonymized shape back to conversion-optimization-specialist@profession.md: which element class ruled which way, on what page type, at what traffic volume. Never a client’s identity, never their URLs, never their baselines or unreleased numbers. Small payloads are exactly what compounds.
opvs tools install @di-atomic/conversion-optimization-specialistThen give it thirty days. Week one is intake — expect it to refuse to audit anything until the one metric is written down, and expect that to feel slow. It is the whole reason the later output is not a teardown. In weeks two and three watch two numbers: the share of findings your team actually ships, and the share of claimed wins overturned at the significance test. The second should not be zero. By week four you should be handing it a URL and a metric and getting back something you would put in front of a client.
client-intake asks whether you can supply them at all on day one, and absent numbers produce UNDERPOWERED rather than an estimate. A brand that cannot supply them still buys the audit and the plan; it does not buy the verdict.One more that decides everything else: this role produces a verdict, not a deliverable you can ship. If nobody on your side is going to act on a ranked list, the honest answer is that you do not need it yet.
Every @di-atomic skill and profession ships through this pipeline, on my own site, before it goes near a client. If your pages are not converting and nobody independent is reading them, that’s the conversation.
Book a 30-min call with Di-AtomicWant the diagnosis on its own? See cro-audit.