A link is enough. A link and a repo is better.
Five steps from a domain you paste to a work order somebody can act on. Nothing to install, and nothing for your client to sign up for.
- 01 · Start here
Paste a domain
Any public URL. The page is fetched server-side and re-served from our own origin, so there is nothing to install on your client’s server and nothing for you to deploy first, which is what makes reviewing a site you did not build possible at all.
Pages behind a login are out of reach: we never send cookies upstream.
- 02 · Optional, and the difference
Connect the repository
A URL on its own gives you a full review of the rendered page. Point us at the GitHub repository behind it and the review also reads the source, so a finding stops being “the contrast is wrong somewhere” and becomes a file, a line, and a link straight to it.
Every plan includes repositories; extras are a per-repo add-on.
- 03 · The pass
Run the seven lenses
Each lens is a specialist with one job, and they run concurrently. They report as they land rather than behind a single spinner, because a review that finished four of seven is still worth reading.
Each finding must quote or measure something on the page. A lens that finds nothing says nothing.
- 04 · The output
Read findings on the page
Findings pin to the element they are about, carry a severity, and quote the evidence they rest on. Your client can reply on the same pin, and every comment arrives with the browser, OS, viewport and a screenshot already attached.
Clients comment without an account and without a password.
- 05 · The handoff
Send one to the client, one to the agent
The same review produces two artefacts. A frozen report under your own name and logo for the person paying the invoice, and a change brief for whichever coding agent does the work, the same brief an agent can pull over MCP rather than being pasted.