Selling a redesign is easier with evidence than with taste. An outside report that separates measured facts from opinion turns an argument into a scope document.
Run a roast on a prospect or on your own delivery before handover, and hand the client something they can verify themselves.
What you get: measured facts separated from human judgement.
Start an auditWhat we check
Objective baseline
Performance, accessibility and metadata measured before and after your work, with a score you can compare.
Independent human feedback
Testers who are not you and not the client, reporting what confused them with screenshots.
Findings ready for scope
Each finding carries severity, so it maps directly to a line item in your proposal.
Pre-handover check
Catch the breakpoint bug before the client's marketing lead does.
Shareable report
A public or private report link, plus a badge if the client wants to show the result.
Typical findings
- Client-side arguments about taste replaced with measured contrast failures.
- Handover bugs found on tablet widths nobody tested.
- Stale metadata carried over from the previous site.
- Forms that stopped delivering after a DNS change.
Questions
Can I resell this to clients?
You can run audits on client sites and include the findings in your own deliverables.
Can reports stay private?
Yes, a roast is private by default and only public if you publish it.
How many sites can I audit?
As many as your balance covers; each audit is paid per run.
See also
A roast is an automated audit plus reports from real testers, with evidence attached.