Skip to main content
Home/Recipes/Client-branded audit report
Audit & Compliance

Client-branded audit report

AgencyPM

Overview

Run an audit of any site, then render the findings as a document that looks like it was made by your client — using their own colors, fonts, and voice. Two extractions, one polished deliverable.

An audit report that looks generic undermines the work it contains. This recipe produces a report that is visually and tonally aligned with the client receiving it — so when Nike's brand team opens the document, it looks like it belongs in their world. The workflow has two parts: extract the site being audited (a competitor, a campaign microsite, a legacy property), then give the agent your client's brand guide — either as a PDF or as a second Dembrandt extraction of their own site — and ask it to render the findings using that visual language. The agent applies the client's primary color, typeface, spacing personality, and tone of voice to the output HTML. No manual design work, no Figma. The result is a document that feels considered rather than automated.

Extract the site being audited

Terminal
dembrandt prospect.example.com --wcag --crawl 10 --save-output

Extract your client's own site for brand context

Terminal
dembrandt client.example.com --brand-guide --save-output
Agent prompt: render audit in client's brand
You have two inputs:
1. A Dembrandt extraction of the site being audited (audit-target.json)
2. Either a Dembrandt extraction of the client's own site (client-brand.json)
or a brand guide PDF attached to this conversation.
Write a concise audit of the first site — what the data shows about their color
discipline, typography consistency, spacing system, and WCAG compliance. Quote
specific values when they reveal something concrete.
Then render this as a self-contained HTML document styled with the client's brand:
use their primary color for headings and accents, their font stack, their border
radius and spacing rhythm. The document should look like it came from their design
system, not from a generic report template.
Tone: match the voice in the client's brand guide if one is provided. Otherwise
infer it from their site — formal or conversational, technical or editorial.
Output

A self-contained HTML audit report styled with the client's own brand tokens — ready to send without further design work.

Browse all

All recipes →

56 workflows