01
Describe the task
Read one week of store performance alongside a useful comparison period and identify the few changes that deserve the operator's attention.
Operate any store · Reporting
Build a weekly store performance brief
Convert the numbers you already review into a short operating brief with clear follow-ups.
The workflow
Bring the truth. Make the next move clear.
02
Provide the working context
- A current-week export, spreadsheet, or legible dashboard screenshot
- A comparable prior week or target with matching metric definitions
- Known events such as promotions, stockouts, tracking changes, or channel launches
03
Review how Claude handles it
- Normalizes labels and separates directly observed values from calculated changes
- Ranks meaningful movements by likely business impact rather than listing every metric
- Suggests plausible checks without presenting correlation as a proven cause
- Formats the findings as a brief with owners, questions, and a next-review date
What you get
A compact weekly ecommerce brief that separates facts, hypotheses, and assigned follow-up work.
Before you run it
Questions for this workflow
Can Claude build a weekly sales brief from dashboard screenshots?
Yes, when the screenshots are legible and include the metric labels, date range, and comparison values. A CSV or spreadsheet is easier to calculate from, but screenshots still support a useful read when Claude clearly separates visible numbers, calculated movement, and unproven explanations.
What context should I provide first?
Start with a current-week export, spreadsheet, or legible dashboard screenshot. Then add a comparable prior week or target with matching metric definitions. Keep the source material current, remove sensitive information that is not needed, and tell Claude which facts are verified so gaps remain visible instead of being filled by assumption.
What should I review before acting on the result?
Review the source facts, assumptions, calculations, and any marked gaps behind this deliverable: A compact weekly ecommerce brief that separates facts, hypotheses, and assigned follow-up work. Compare it with the live system or responsible teammate, and check before approving any action.
Keep moving
Related use cases
Setup
Connect Claude to the store you already run
Give Claude a trustworthy view of your store without changing platforms or pretending every stack has a connector.
Run this workflow
Product content
Turn one product truth into channel-ready copy
Build distinct product copy for each selling surface from one approved set of facts.
Run this workflow
Support
Draft grounded customer support replies
Respond faster across inboxes while keeping the answer tied to the case facts you provide.
Run this workflow