Primary journey
One lead, booking, signup, or checkout path tested from entry through confirmation.
Poszo partner desk
Ship the client site.
Keep the relationship.
Launch QA for agencies shipping Next.js and Vercel work without a dedicated release tester. We inspect the release, document the evidence, and hand it back privately to your team.
Stripe collects the agency name, launch URL, date, and primary journey before payment. Poszo confirms lawful scope before testing; if the launch cannot be tested safely within the published pilot, the $99 fee is refunded.
TEST → DOCUMENT → HAND OFF → RE-TEST → TEST → DOCUMENT → HAND OFF → RE-TEST →
Release coverage
A bounded acceptance pass, not an open-ended audit.
Responsive release
Up to ten representative pages checked at desktop and mobile widths.
Technical smoke test
Broken links, metadata, console errors, failed requests, HTTPS, and security headers.
Launch evidence
Timestamped findings, screenshots, severity, acceptance checks, and one re-test.
Performance snapshot
Lighthouse and Core Web Vitals evidence without promising an arbitrary perfect score.
Agency handoff
A client-safe summary plus a private technical appendix for the delivery team.
Your client stays yours
Private capacity without channel conflict.
Your agency remains the client-facing party. Poszo does not contact your client unless you explicitly invite us into the project. Findings are delivered to your team, not published as a case study.
The client-safe summary can carry your agency's name and contact details. Poszo's private technical appendix records the test evidence and remediation acceptance checks.
We use public pages or least-privilege access only after written scope. Never send passwords, private keys, customer data, or recovery codes by email.
What you receive
Evidence your team can act on.
- 01
Client-safe release summary
Scope, release status, priority findings, and re-test result without internal implementation noise.
- 02
Private technical appendix
Affected URLs, screenshots, console or request evidence, acceptance checks, and suggested owner.
- 03
One re-test
Your team implements corrections; Poszo rechecks the agreed findings once within seven days.
- 04
Optional implementation
If you want overflow engineering too, the $599 sprint covers up to three pre-agreed fixes with rollback notes.
After checkout
A clear handoff before the clock starts.
Scope confirmation
Poszo reviews the launch URL, target date, primary journey, and safe test path. If the pilot cannot be delivered within the published boundary, the $99 fee is refunded.
Two-business-day review
The turnaround starts after scope and any approved test access are confirmed. Poszo tests the agreed release and sends both handoff artifacts privately to your agency.
One re-test
Your team applies the corrections. Poszo rechecks the agreed findings once within seven days and records Passed, Failed, or Accepted-risk status.
Validate with one launch
$99paid pilot
One bounded release review and one re-test. Checkout captures the URL, target date, and primary journey; testing starts only after Poszo confirms the lawful test path.
Ask a scope question firstNeed implementation too?
$599repair sprint
Up to three pre-agreed production fixes on one client site, with staging/production QA, change notes, and rollback instructions. The checkout is issued only after you request implementation and Poszo confirms the fixes, access path, and deadline.
Request implementation scope →Boundaries
Not included
Source-code remediation in the $99 pilot, full WCAG certification, penetration testing, real purchases, complex multi-role workflows, or a full device laboratory.
Safe test data
The agency supplies approved test credentials and non-sensitive data when authentication is required. Poszo does not create or use real customer records.
No guaranteed score
The review records observable release quality. It does not guarantee conversions, rankings, security, or a perfect Lighthouse score.
One launch at a time
The pilot covers one URL set, ten representative pages, one primary journey, and one re-test. Broader programs require written scope.
A client launch is already on the calendar