SCOPE BEFORE ACCESS

A clear promise is safer
than a broad one.

We define coverage before invoicing. If a requested state cannot be tested safely or honestly, it appears as an exclusion—not a silent assumption.

AREAFOUNDING PILOT INCLUDESNOT INCLUDED BY DEFAULT
Storefront coverage

One named store or preview, one release window

Additional stores or unrelated releases

Viewports

One current desktop and one mobile viewport

Every browser, device, OS or assistive technology

Critical paths

Up to three agreed paths

Exhaustive catalog, account or localization coverage

Evidence

Screenshots, short video, console/network detail and reproduction

Raw credentials, customer data or production exports

Delivery

Next workday after access and scope are ready

24/7 incident response or emergency on-call

Closure

One written revision and one focused retest

Unlimited revisions, fixes or development work

01

Public storefront

No account is required. We stop before payment and never submit a real order.

02

Preview or password page

Share temporary, least-privilege access through an agreed secure channel—not plain email.

03

Shopify admin

Excluded from the standard pilot. If essential, access and actions require a separate written scope.

THE SERVICE PROMISE

Evidence within scope.
Transparency outside it.

Release Assurance reports observed behavior during a stated window. It is not legal, tax, accessibility, security or accounting certification.

A pass means the agreed checks passed in the tested states. It does not prove that every possible shopper, geography, experiment or third-party service will behave identically.

We report findings; we do not make production changes unless a separate development engagement is agreed.

READY FOR A BOUNDED PILOT?

Confirm the release before access.

Build a pilot brief