Findings in one side, a client deliverable out the other
The document on the right is not an image. It is live HTML in the Labate SEO report system, with the typefaces self hosted and the structure driven entirely by which findings are selected. This is the same pipeline that produces client PDFs.
Findings in, branded deliverable out
Engagement
Findings to include
Toggle any finding and the document rebuilds: the counts, the severity distribution, the thesis line, and the roadmap all derive from what is selected. In the production pipeline this same HTML is rendered to PDF through headless chromium, which is why the layout is built in print units and page break rules rather than as a screen first design.
The deliverable is part of the argument
A findings list in a spreadsheet gets forwarded once. A document that a stakeholder can read end to end without a translator gets circulated, quoted in a budget meeting, and acted on.
Severity has to be visible at a glance
An executive reads the pill colours before the prose. If the distribution is not legible from six feet away, the prioritisation is not communicating.
Method up front, not in an appendix
Scope and assumptions stated before findings is what stops the first reply being a question about how the numbers were reached.
Templated but not generic
The system is fixed so that the thinking gets the attention. Consistent typography, palette, and section rhythm across every deliverable, with the analysis different every time.