A screenshot roast sees one page. The Deep Roast signs up to your product.

Your homepage is not where your product loses people. It's where they arrive. The losses happen three screens later. In the signup form that asks for a card before showing anything. In the verification email that lands in spam. In the empty state that greets a new account with a blank rectangle and no next step. A tool that screenshots your homepage cannot see any of that, and no amount of model quality fixes a coverage problem.

The Deep Roast walks it. We sign up the way a customer would: complete the forms, verify the email, sit through the onboarding, connect the integrations, trigger the error states, hit the empty states, and capture every screen along the way, desktop and mobile, captured separately rather than resized. Then we read what's behind the screens, not just the pixels.

Counted, not felt

Once the capture exists, most of the analysis stops being a matter of taste and starts being arithmetic. Contrast ratios are measured, not estimated. Button variants are counted. Greys are counted. Spacing values get tallied until the number of them is its own finding.

• "CTA fails contrast at 2.8:1" is a fact. Checkable, and fixable this afternoon.
• "Consider improving visual hierarchy" is a sentence that survives in every audit ever written, because it can never be wrong.

The first kind of finding is what you're paying for. The second kind is what makes people distrust audits.

Delivered in Figma, not as a PDF

The deliverable is your product in Figma: every captured screen, in flow order, with every finding pinned to the pixel that caused it, numbered and prioritised. Each page carries its own score. You get competitor standings, the AI-visibility check that asks whether ChatGPT and Perplexity cite you or the company you're trying to beat, a recorded senior walkthrough, and a roadmap ordered by what to fix this week, this month, and before your next raise.

A PDF gets read once and filed. A Figma file gets opened by whoever is doing the work, with the finding sitting next to the screen it's about. The difference in how much of an audit actually gets implemented is not subtle.

A senior human, at the end

The tooling does the walking, the capturing and the counting. It doesn't do the judgment. Every Deep Roast gets a kill-pass from a senior designer who removes the findings that are technically true and practically irrelevant, and re-orders what's left by what will actually move the number you care about. That pass is why this takes five business days instead of five weeks, and why it costs more than twenty-nine dollars.

Two shapes: Website at $4,500 +GST, or Website + App at $7,500 +GST. The second adds everything behind the login, the error, empty and OAuth states, and editable versions of the key screens. We need a test account or, failing that, just your signup page. Test cards for payment flows. Nothing destructive, ever. Bigger product than that? Talk to us.

If you want to know what you'd get before you spend anything: run the free roast, then open the example Deep Roast file. One is about your site. The other is the whole method, in public.