Your client's compliance breaks when your stack updates. Know first.

None of this is bad workmanship — it's the normal physics of maintained websites:

• Theme and plugin updates rebuild footers and widget areas — the exact places the SRA number and digital badge embed live.
• Consent managers and security headers silently block the SRA badge script, so the badge stops rendering while the embed code sits untouched in the template.
• Content edits by the client trim VAT wording or delete a disbursements table from a pricing page you built correctly.
• Migrations and relaunches change URLs, and the complaints procedure link in the footer starts returning 404 — discoverable only by clicking it.

Each of these is invisible in your deployment pipeline, because nothing “failed”. The only way to catch them is to check the rendered public pages the way the SRA does — regularly.

• Weekly automated checks of each client site against the SRA Transparency Rules — SRA number, digital badge rendering, complaints information and its Legal Ombudsman / SRA content, price-page signals — with the exact page and excerpt for every finding.
• Regression detection: when something that passed last week stops passing, that's flagged as its own finding — the “what did the update break?” answer, per site, without manual QA sweeps.
• Instant re-scan after a fix, so you can close the loop in the same maintenance window and show the client the dated before/after.
• Evidence your clients can use: each firm gets a dated monitoring history and monthly statement — useful to their COLP, and a genuinely differentiating line in your care-plan proposals.
• White-label reports: coming soon. Agency-branded monitoring statements are on the roadmap; tell us if that's the piece you need and we'll shape it with you.

The boundary is deliberate: FirmProof reads public pages only — no CMS access, no client credentials, no client-matter data. Results are automated monitoring checks, not certification; judgement calls are labelled for human review, which in practice means you or the firm's COLP.

We're onboarding a small number of agencies while multi-site tooling matures, and pricing for portfolios is straightforwardly per-site. The fastest way to evaluate the engine is to run the free scan against a client site you maintain (it's the same checks the weekly monitor runs, public pages only). For portfolio setups, white-label interest or anything else, email dantasdeveloper@gmail.com — a short note with how many law-firm sites you look after is plenty.