Public Claims Methodology

1. Figures currently covered

• More than 60 completed store audits.
• 749 distinct issues recorded across those audits.
• About 55% of those issues classified as potentially resolvable through an agentic workflow, subject to connector capability, permissions and human approval.

2. Definitions

A store audit is one completed audit of an agreed store scope. An issue is one distinct finding recorded in that audit. Potentially agentically resolvable means the finding was classified as suitable to progress through software within defined guardrails. It does not mean the issue was automatically completed or that every store supports the required write, staging or rollback capability.

3. Calculation

The issue total is the count of distinct findings in the included internal audit records. The percentage is the number classified as potentially agentically resolvable divided by the total issue count, rounded to an approximate whole percentage.

4. Evidence and confidentiality

The source is an internal historical audit snapshot assembled before August 2026. Merchant-level records are not published because they may contain confidential operational information. Named customer outcomes require separate permission and measurement context.

5. Limitations

• The sample is not a controlled market study and may not represent every merchant.
• Issue mix depends on store size, platform, connected systems and audit scope.
• Classification does not guarantee completion, saving, revenue uplift or payback.
• Availability depends on the connector, plan, permissions and workflow.
• Revenue uplift is excluded from the core ROI calculator unless the store provides verified inputs.

6. Review cycle

Marketing and Product review volatile claims quarterly. A figure is qualified or removed when its source, date, calculation, limitation or owner cannot be confirmed.

7. Organic traffic: 1,400% at one merchant

Figure: one large Shopify merchant recorded a 1,400% increase in organic traffic following deployment of the Vortex IQ SEO and GEO engine.

• Source: the merchant's Google Analytics property, read with the merchant's permission.
• Calculation: organic sessions in the measurement period after deployment compared with the equivalent period before deployment, as recorded in Google Analytics.
• Scope: one merchant deployment. The measurement period and baseline are held in the internal record for that merchant and will be published with the merchant's name once publication approval is received.
• Limitations: one deployment, not a controlled study. Seasonality, other campaigns and platform changes in the same period are not isolated. The figure describes traffic, not revenue or conversion.

8. Deployments: The Revere Group with StagingPro

Figure: The Revere Group recorded 100% incident-free deployments and a 65% shorter development cycle using StagingPro.

• Source: the published customer story, agreed with the customer.
• Scope: the customer's use of StagingPro, one of the Vortex Apps, on its BigCommerce store. The figure does not describe the other five crews.
• Calculation: incident count across deployments made through StagingPro in the period covered by the story, and development cycle length compared with the customer's own prior process, as reported by the customer.
• Limitations: customer-reported comparison against its own previous process. Not independently audited.

9. Catalogue optimisation: 10,549 product records

Figure: the Beacon crew has processed SEO enhancements across 10,549 product records as of 10 September 2026.

• Definition: a product record is counted once when the SEO and GEO engine has generated an enhancement for it, regardless of how many fields were enhanced.
• Distinction: generated means the engine produced a proposed enhancement; approved means a person on the merchant's side accepted it; published means it reached the live store. The headline figure counts generated enhancements. Approved and published counts are held per merchant and are not aggregated publicly.
• Source: the engine's own run records across merchant stores, aggregated on 10 September 2026.
• Limitations: a count of work prepared, not a claim about traffic or revenue. Merchant-level detail is confidential.