First customer validation packet
Use this packet when onboarding one of the first 10 accepted StoreFix AI customers. It keeps the validation run focused on the live Shopify App Store flow, the saved report workflow, one carefully approved update, undo evidence, and the support questions that decide what to improve next.
Validation goal
Confirm that a real Shopify merchant can install or open StoreFix AI, run Catalog QA, save a report, understand approval-ready versus review-only findings, apply one selected low-risk field, confirm saved undo evidence, and know exactly how to contact support if anything blocks.
Do not batch-approve updates during the validation run. One selected field is enough to prove the workflow without risking broad catalog changes.
Current offer boundary
| Item | Validation stance |
|---|---|
| Access | First 10 accepted customers use the $5/month Founding plan while the app validates install, scan, saved report, approved update, rescan, undo, and support load. |
| Billing | Recurring subscription checkout remains paused until first-customer workflows, support expectations, refund handling, and pricing are proven. |
| Writes | StoreFix AI can update only selected product description, search listing title, search listing description, and image alt text fields after merchant approval and saved snapshots. |
| Claims | Position as catalog QA, approval workflow, accessibility/metadata cleanup support, report evidence, and saved undo logs. Do not promise ranking, traffic, sales, or passive income. |
Merchant run script
- Open the StoreFix AI Shopify App Store listing and install or open the app from the target Shopify store.
- Inside Shopify Admin, confirm the store domain shown in StoreFix AI matches the store the merchant intended to scan.
- Open Catalog QA and confirm the overview says the scan does not edit products.
- Choose Run Report and review fixes, then open the saved report.
- Use filters for High priority, Needs review, and Looks good. Inspect at least 3-5 representative products.
- Separate approval-ready fields from review-only warnings using the report review guide.
- If the merchant approves, select one low-risk field for one product and apply only that field.
- Return to Applied updates, confirm saved undo evidence, then use Undo if the merchant wants to verify restoration immediately.
- Run a new report only after the merchant understands what changed. The new report is the before/after evidence point.
After the run, score each stage in the install conversion checklist. The lowest-scoring stage should become the next product or support task.
Evidence to save
| Evidence | Capture | Decision it supports |
|---|---|---|
| Install/open proof | App Store listing state, selected Shopify store, and embedded app first screen. | Whether the public App Store path is usable for a first merchant. |
| Catalog QA overview | Shop domain, product count, score, issue counts, and no-edit scan copy. | Whether the merchant trusts the app is scanning the intended store. |
| Saved report review | Report ID, filters used, affected product, issue label, recommended next step, and review-only warnings. | Whether report language is clear enough without live support. |
| Approved update | Selected field, confirmation summary, success or error message, and applied-update status. | Whether field-level approval feels safe enough for merchant use. |
| Undo evidence | Saved snapshot status, Undo result, and restored Shopify product value when tested. | Whether saved undo evidence is credible before broader adoption. |
| Support question | Exact merchant confusion, blocker, or requested feature in their own words. | Which onboarding, support, or product copy should be improved next. |
Revenue-validation readout
- Strong signal: merchant installs from the public listing, saves a report, approves one field, understands undo, and asks how to keep using StoreFix AI.
- Usability signal: merchant likes the report but needs clearer copy, better filtering, or guided review before approving a write.
- Support-load signal: merchant needs hands-on help to identify the correct store, understand report labels, or recover from a failed update.
- Pricing signal: merchant says the report/update/undo workflow is useful enough to keep paying for after the first-10 Founding validation period.
- Stop signal: merchant does not trust the recommendations, cannot complete install/open, or cannot understand what StoreFix AI changed and how undo works.
Questions to ask after the run
- Did StoreFix AI find product issues you already suspected were real?
- Which finding or label was most confusing?
- Would you approve more fields after seeing one selected update and saved undo evidence?
- What would you expect to happen after a rescan?
- Would this be worth keeping after the first-10 Founding-plan period, and why or why not?
Send support this packet
Shopify store domain: Approximate product count: Installed/opened from Shopify App Store? Yes / No Saved report ID: Product title or handle: Selected field: Latest StoreFix AI message: Undo tested? Yes / No Merchant question or confusion: Screenshot attached? Yes / No