Ciwi
Back to topic
Spark playbook scenarios · Spark: AI Store Assistant

Assess the size and direction of a target ecommerce market

Before entering a market, the merchant needs to know whether demand records show a trend or just a short favorable window. In this case, the immediate task is to assess the size and direction of a target ecommerce market. The workflow should produce a market assessment stating what the records support, listing the gaps that would need better data.

Topic
Product Research and Market Opportunities
Target keyword
ecommerce market research tool
Copyable AI prompt

A prompt you can drop directly into Spark

First replace every [bracketed] placeholder with real store scope and constraints, then add any actual records or data you have, and paste it into your preferred AI assistant or Spark agent. Spark will follow this page's workflow to produce structured output and verification steps.

ai-prompt.txt
Act as a Shopify operations specialist.
Help me assess the size and direction of a target ecommerce market.
My store context is [describe the business, products and target audience].

My scope is [specify the affected products, pages, customers or reporting period]. Use these inputs: [target market definition with geography and audience boundaries, dated demand evidence with sources, competitor presence and pricing, and stated sourcing or regulatory limits]. Read the direction of demand strictly from the dated records, stating which periods the evidence covers and whether growth or decline is actually evidenced, while separating overall market size from active buyer demand signals.
Return a market assessment stating what the records support and the gaps that would need better data for the specified task.
Show the relevant evidence or before-and-after examples and explain how I can verify the result.
If essential data is missing, ask for it and mark unsupported conclusions as unknown.
Do not invent metrics, product claims or customer facts.
For any publication, message, account or store change, use only connected tools within my explicitly authorized scope and report success only after verification; otherwise provide the draft or proposed steps.
Use in Spark
How to solve

A recommended resolution workflow

Split the work into input, judgment, and deliverable phases. Verify each step's output before moving to the next.

01

Step 1

Collect the target market definition with its geography, audience and product boundaries, dated demand evidence with sources, competitor presence and pricing in the market, and any stated sourcing or regulatory limits.

02

Step 2

Read the direction of demand strictly from the dated records, stating which periods the evidence covers and whether growth or decline is actually evidenced, while separating overall market size from active buyer demand signals.

03

Step 3

Deliver a market assessment that names each conclusion the records support, each conclusion they do not, and the data gaps that would need filling, then check every figure quoted in the assessment back to its dated source record.

FAQ

Common questions when running this scenario

Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.

Why are market size and demand signals reported separately?

Size describes the whole market while demand signals show what buyers actively seek, and conflating them makes a large market look like ready demand; the assessment states both with their own sources, and a conclusion that mixes the two is rewritten before delivery.

How far can historical records support a direction claim?

Only as far as the periods they cover, so the claim is stated as an indication over named dates rather than a forecast; the boundary case is a short evidence window, which supports at most a description of what happened inside it and nothing about persistence.

What if the market definition keeps drifting during the work?

The geography, audience and product boundaries are fixed at the start and any proposed change restarts the comparison, because a moving definition silently compares unrelated products; changes are recorded with the reason so the assessment's scope stays auditable.

Related scenarios

Continue with adjacent or same-topic scenarios

Start with scenarios under the same topic, then expand into cross-topic matches suggested by similarity.

Next step

Want these AI scenarios embedded directly into daily operations?

Ciwi Spark builds Shopify-native AI tools and agents around the workflows merchants actually run: research, ads, translation, and customer support. Stop rewriting the same prompts by hand.

Open Spark product pageBack to Spark scenario library