Agency launch workflow
Agency website QA: a buyer's guide
Launch Ready helps agencies check multiple client sites, prioritize launch blockers, and hand clients a clear QA report. Keep code changes, task ownership, and delivery decisions in your existing tools.
Use it alongside your issue tracker, not instead of one: Launch Ready reports scan findings but does not create or export implementation tickets, perform fixes, or automatically approve or block a production release.
Last reviewed
A repeatable workflow for each client launch
1. Organize sites by client and launch
Keep each website as a project, associate it with a client, and use environment and tags to distinguish production, staging, and preview work.
2. Run QA at the agreed checkpoint
Start a scan before a release review. Pro and Agency can schedule daily or weekly scans; scans are discrete runs, not continuous uptime monitoring.
3. Triage blockers with evidence
Review readiness, severity, affected pages, and captured evidence. Start with critical launch risks, then check what was not measured before drawing conclusions.
4. Fix work in the tools your team owns
Create or update implementation tasks in your issue tracker and assign owners there. Launch Ready does not sync findings into tickets or make code changes.
5. Review exceptions and rescan
Pro and Agency include rule tuning to document an accepted exception or adjust a finding; scan again to see the current result. Keep the reason and client approval in your normal delivery record too.
6. Hand over a client-ready report
Share the findings, remaining blockers, exceptions, and unmeasured checks. Agency adds your logo and colours; retain the issue tracker as the source of truth for fix ownership and completion.
Portfolio view
See which client site needs attention first
This preview uses the current portfolio heat-map component and its real readiness ordering. Every name is fictional: the first tile uses the AV-12 synthetic report, and the second is explicitly unscanned, with no invented score or findings.
Heat map
Worst first: 1 blocked.
- Pre-launch websiteFictional client35Blocked
- Next launchFictional client—Never scanned
The heat map is an Agency feature. This illustrative portfolio is not customer data or a claim that every plan includes the portfolio view.
Report evidence
Show the client what was found and what was not checked
The report below is a live rendering of the synthetic AV-12 fixture using the current scoring, finding, and badge components. It is fictional; no site was scanned, and no customer data or share link is used.
launch-ready-example.example
Critical blocker detectedScore and readiness are calculated from the fixture findings with the production scoring rules.
1 critical, 1 high, and 1 medium findings.
- Block Launch
Homepage returns noindex
<meta name="robots" content="noindex, nofollow">
- Important
Contact form submits to a staging URL
<form action="https://forms.staging.example/lead">
- Improvement
Images without alt text
4 image elements on this page have empty or missing alt attributes.
The full report shows page coverage, category coverage, Not measured states, exceptions, and plan requirements.
Open the full synthetic reportAlternatives
Replace fragmented review artifacts, not your whole delivery stack
Spreadsheets and screenshots are useful for human context and bespoke checks. They become harder to keep aligned across many sites and repeat scans. Launch Ready adds repeatable automated findings and coverage; your team still decides what to fix and where to track it.
| Approach | Useful for | Trade-off / boundary |
|---|---|---|
| Spreadsheet checklist | Client-specific manual checks, sign-off steps, and context outside automated scans. | The agency must keep status, evidence, and repeat checks consistent across sites. |
| Screenshot bundle | Visual context for a reviewer or a point-in-time design decision. | A still image is not a crawl, does not establish page coverage, and can lose the URL or review context when separated from the checklist. |
| Launch Ready | Repeatable scan findings, page-level evidence, coverage, and client report sharing. | Automated checks can miss inaccessible or dynamic behavior; they do not submit forms, fix code, export tickets, or gate releases. |
| Your issue tracker | Owners, implementation work, due dates, and delivery status. | Keep it as the source of truth; Launch Ready does not imply issue export or ticket synchronization. |
Plan fit
Match the plan to the agency workflow
This comparison reflects current code entitlements, not a verification of production overrides. In-app share links are available on every plan. API/MCP share-link creation and the deploy hook are Agency-only; a deploy hook starts a scan but does not judge its completed results or block a release.
| Capability | Free | Pro | Agency |
|---|---|---|---|
| In-app share links | Available | Available | Available |
| Report branding | Launch Ready branding | Neutral, unbranded report | Your agency logo and colours |
| Full scan categories | Core checks | Included | Included |
| Scheduled scans and monitoring | Not included | Daily or weekly scans; alerts depend on configured delivery | Daily or weekly scans; alerts depend on configured delivery |
| Portfolio heat map | Not included | Not included | Included |
| API/MCP scan and read access | Included | Included | Included |
| API/MCP share creation and deploy hook | Not included | Not included | Included |
Plan limits come from current code entitlements and may be configured differently in production. Check pricing for current commercial terms. API/MCP scan and read access is on every plan; Free scans are limited to one site. In-app sharing is available on every plan.
Limitations
What to keep in the client handover
- Coverage depends on reachable pages, scan limits, captured markup, and rendering; read the report's coverage and Not measured states.
- Static form checks do not submit forms or confirm that leads are delivered. Test important workflows manually.
- Automated accessibility and compliance signals are not specialist audits, legal advice, or proof of conformance.
- A scan is a review input, not a production approval gate. Your team owns the release decision.
- Use the tracker for owners, fixes, accepted client exceptions, and due dates; Launch Ready does not export tickets.
- Confirm every finding against the client site and record what was manually reviewed before handover.
For implementation detail, see how we scan, the API reference, and pricing. Launch Ready is a QA aid; the agency remains responsible for technical fixes, client approval, and release decisions.