Shopify growth stack guide

Name the single thing limiting revenue this quarter before adding anything.

• No traffic: fix findability and feeds before conversion tooling.
• Traffic but no sales: fix speed, product-page trust, and the mobile path before adding apps.
• Sales but no margin: fix costs visibility, returns, and operations before more acquisition.
• Sales but no time: fix operations and automation before anything customer-facing.

• You are launching, relaunching, or your category has known buying patterns a kit already encodes.
• Prefer a kit over a bare theme when you also need the app stack and settings configured — the kit is the theme plus the workflow.
• Skip custom design until the current experience is demonstrably the constraint.

• It makes or saves measurable money, or removes a recurring manual job — and you can name the number it moves.
• It replaces spreadsheet work someone actually does every week.
• Review the app list quarterly: anything unopened for a month is a candidate to cancel.

• You ship store changes at least monthly and want compounding improvements, not one-off fixes.
• You need one accountable owner across CRO, speed, SEO, and technical health.
• A project fits better when the work has a clear end state: a migration, a launch, a build.

• The workflow is core to how you win and no app models it without contortions.
• Integration glue between systems is costing real hours or causing real errors.
• You have accepted the maintenance responsibility that comes with owning code.

• Two apps solving the same problem because nobody cancelled the first one.
• Custom code where a native Shopify feature shipped last year.
• Buying analytics before fixing tracking; buying personalization before fixing search.
• Adding tools during a growth stall instead of diagnosing it — the audit is cheaper.