What do I need to get started?

A working staging app you are authorized to test, stable test data, up to two test accounts, and sandbox access for relevant integrations. We agree the journeys, scenarios, browser, and automation budget before purchase. Share access through a restricted password-manager invitation after intake. Never paste passwords, tokens, or production data into the form.

When will I get my report?

Our target is five business days after scope and access are confirmed. We confirm capacity and a specific delivery date before you pay. Your target launch date helps us plan; it does not reserve a slot. If access or scope changes, we agree an updated date with you.

What do the three engineering hours cover?

Up to three hours in total for setup, investigation, findings review, and the included retest. Automated testing stays within the agreed scenarios and run budget. Remediation is not guaranteed or unlimited. If we reach a limit, we agree priorities with you before continuing.

What if I need more work?

We agree a separate scope and cost in writing before any extra work. The proposed standard engineering rate is $150/hour; existing customer-specific agreements take precedence. There are no automatic overages.

How does the retest work?

One retest of the original findings is included within 14 calendar days of report delivery. Provide your fixes and access in time for that window; we agree the slot and report resolved, unresolved, and blocked outcomes. New features, scenarios, browsers, or further retests need a separate scope.

When do I pay? Does it renew?

After scope, secure access, capacity, and the delivery date are confirmed, you review the approved scope and $1,000 USD total before Stripe checkout. It is one payment: no subscription, renewal, or automatic extra-work charges.

Can I cancel or reschedule?

Cancel before testing begins for a full refund. Once testing begins, the engagement fee is non-refundable, except as required by law or your written agreement. If Zof cannot deliver the agreed scope, we will offer a reschedule or refund.

Do I need a platform subscription?

No. Launch is a service for one release. The Zof platform is a separate subscription for ongoing verification, orchestration, and reporting. The enterprise Reliability Sprint is separately scoped for deeper critical-system testing and more complex environments. Neither is included in the Launch fee.

Does this guarantee I am ready to launch?

No. Your report shows what passed, failed, or could not be tested within the agreed scope. We cannot find every bug or certify the whole application. Your team makes the release decision.

Zof Launch · pre-release verification

Know what to fix.
Before you launch.

For $1,000 one time, get focused testing of your staging app and findings your team can act on. Built for founders and small product teams.

Start your launch check See a sample report

Apply first. Confirm scope, capacity, and delivery date. Then pay.

For your next release

What you get.

Ideal for a first launch, a major feature, or a small team without dedicated QA. Bring a working staging app and the journeys that matter most.

01

Focused staging tests

One app, up to 5 critical journeys and 20 agreed scenarios. Up to two roles, in one browser.

02

Hands-on engineering

Up to 3 hours total for setup, investigation, findings review, and the retest, alongside bounded automated testing.

03

An actionable report

Tested scope, findings, severity, reproduction steps, supporting artifacts, limitations, and recommended next actions.

04

One included retest

Retest the original findings within 14 days of report delivery. See what is resolved, unresolved, or blocked.

See the deliverable

Findings you can use.

Know what was tested, what failed, and what to do next. This invented example shows the report format.

Zof Launch / report excerpt

Workspace onboarding check

Illustrative report for a fictional staging application.

Illustrative only

Tested environmentStaging · build 0.9.4

Agreed coverage5 journeys · 20 scenarios

Roles & browserOwner + Member · Chromium

16Passed

2Failed

2Blocked

Every agreed scenario is accounted for, including blocked checks.

L-01 · High severityExpired invitation blocks onboardingView reproduction steps, evidence, and recommended fix

Illustrative findingL-01 · High

An expired invitation leaves a new teammate stuck.

Scenario: J02 / S08 · Join a workspace with an expired invitation as a Member.
Expected: Explain that the link has expired and offer a way to request a new invitation.
Observed: The API returns 410, but the page keeps its loading state. The user has no recovery action.
Reproduce: 1. Create a Member invitation with an expired timestamp. 2. Open the invitation URL in a fresh Chromium session. 3. Submit a valid test profile. 4. Observe the spinner after the 410 response.
Evidence: Illustrative trace: POST /api/invitations/accept → 410 INVITE_EXPIRED. Screenshot note: “Joining workspace…” remains visible after 30 seconds. All evidence shown here is synthetic.
Severity: High: blocks an agreed onboarding journey with no recovery path. It does not establish the frequency or production impact.
Next action: Handle the expired-invitation response, provide a recovery action, then retest S08 using the same role and browser.

Invented example · illustrates the report format · not a customer outcome

Also in this example

L-02 · Medium: profile changes save without confirmation (S14). Reproduce: as Owner, update the display name and select Save. The synthetic API trace returns 200, but the page gives no success message. Add visible and screen-reader feedback, then retest the save journey.

Limitations & next actions

S19 and S20 are blocked by the email sandbox outage. Restore the sandbox and agree follow-up coverage. Production, other browsers, security penetration tests, and load tests were not tested.

Limits in this example: two scenarios are blocked by an email sandbox outage. Restore access and agree follow-up coverage. A report supports your release decision; it does not certify a bug-free application.

Six simple steps

How it works.

Start your launch check

01
Submit your application
Share your app and critical journeys. No payment yet.
02
Confirm scope & access
Agree scenarios, browser, secure access, capacity, and the report date in writing.
03
Review & pay
Approve the scope and $1,000 total, then pay once through Stripe.
04
Run the tests
We test the agreed staging scope and capture evidence.
05
Review your findings
Receive your report and discuss priorities and next actions.
06
Retest your fixes
One retest of original findings within 14 days of report delivery.

A focused scope

Need more coverage?

We scope deeper work separately before it starts.

Additional engineering: proposed $150/hour, agreed in writing. Existing customer-specific agreements take precedence.

Outside the $1,000 engagement

Production testing
Private or air-gapped deployment
Custom integrations
Formal penetration testing
Extensive load testing
Unlimited remediation

Ongoing verification

The Zof platform is a separate subscription for continuous verification, orchestration, and reporting.

Platform pricing

Deeper enterprise testing

The Reliability Sprint is separately scoped for critical systems and more complex failure modes.

Reliability Sprint

Before you apply

Common questions.

Tell us what you are launching

Start your
launch check.

Apply now. We confirm your scope, secure access, capacity, and report date before checkout.

$1,000one time · no payment with this application

Questions? launch@zofai.com

Your applicationNo payment now

Full name

Our contact for scope and findings.

Email address

Use an address you monitor.

Company or product name

Solo founders are welcome.

Target launch date

Dates use Pacific time. We confirm our delivery date before purchase.

Staging application URL

HTTPS only. Do not include passwords, tokens, query parameters, or production access.

Critical user journeys

One journey per line, up to five. Describe the outcome a user needs to complete.

Test user roles

One or two roles, one per line. No account credentials.

Browser to verify

One browser engine. We agree the version during scoping.

Relevant integrations (optional)

Names and context only. Existing integrations can be tested within the agreed scope; building custom integrations is separate.

Keep test access private. After intake, invite Zof to a restricted password-manager item or vault using the recipient on your private engagement page. Use staging accounts, least privilege, and an expiry date. Do not paste secrets into this application.

I am authorized to request testing of this staging application. I understand the $1,000 engagement is limited to one application, five journeys, 20 agreed scenarios, two roles, one browser, and three engineering hours, with one retest. Scope and capacity must be confirmed before payment.

Required to submit the application.

No subscription. No automatic charges.

We use these details to scope and deliver your engagement. Privacy policy.

Know what to fix.Before you launch.

What you get.

Focused staging tests

Hands-on engineering

An actionable report

One included retest

Findings you can use.

Workspace onboarding check

Also in this example

Limitations & next actions

How it works.

Submit your application

Confirm scope & access

Review & pay

Run the tests

Review your findings

Retest your fixes

Need more coverage?

Outside the $1,000 engagement

Ongoing verification

Deeper enterprise testing

Common questions.

What do I need to get started?+

When will I get my report?+

What do the three engineering hours cover?+

What if I need more work?+

How does the retest work?+

When do I pay? Does it renew?+

Can I cancel or reschedule?+

Do I need a platform subscription?+

Does this guarantee I am ready to launch?+

Start yourlaunch check.

Know what to fix.
Before you launch.

Start your
launch check.