Tiny Shop Metrics Map — 28 Weekly Signals for Digital Download Sellers
A weekly decision map for digital download sellers who want useful metrics without dashboard overwhelm.
The five-shelf map
Most tiny shops drown in numbers because every platform offers a different dashboard. This ebook uses a five-shelf map instead: Reach, Trust, Product, Delivery, and Cash. Reach tells you whether the right buyers can find the product. Trust tells you whether the page removes doubt. Product tells you whether the offer is specific enough to buy. Delivery tells you whether customers can receive and use the file without friction. Cash tells you whether the work is worth repeating. Review the shelves once a week, not every hour.
Reach signals
1. Qualified visits: count only visits from places where your target buyer would plausibly come from. 2. Search phrase clarity: list the top three phrases a buyer might type and compare them to your title. 3. Referrer quality: mark each traffic source green, yellow, or red based on fit, not volume. 4. Gallery first-slide comprehension: ask whether a stranger can name the product in five seconds. 5. Freshness touch: note the last meaningful improvement to copy, assets, or positioning.
Trust signals
6. Promise specificity: replace broad claims with exact jobs the download helps complete. 7. What-is-included clarity: confirm the buyer can see file types, page counts, and usage format before buying. 8. Doubt removal: write the top objection and answer it visibly. 9. Refund/support boundary: make support available for access issues while avoiding impossible outcome promises. 10. Proof of care: include an honest preview, sample page, or process note that shows real craft.
Product signals
11. Buyer moment: name the situation that makes the buyer need this today. 12. Starter outcome: define the first useful result they can get in under 20 minutes. 13. Reuse depth: score whether the file is one-time, monthly, weekly, or daily useful. 14. Differentiator: write one sentence explaining why this product exists instead of another generic template. 15. Bundle fit: note the neighbouring product that would naturally sit beside it.
Delivery signals
16. Download test: open the buyer ZIP as if you were the customer. 17. First-open path: check the README says exactly what to open first. 18. Device reality: confirm the main file works on a normal browser without paid software. 19. Naming clarity: file names should explain themselves without internal shorthand. 20. Support trigger log: record any customer question that means the product needs clearer instructions.
Cash signals
21. Price confidence: compare price to the time saved or confusion removed. 22. Margin calm: ensure the product does not require custom support to be profitable. 23. Conversion floor: if visits are qualified but no one buys, improve trust before making more products. 24. Update cost: estimate whether maintenance will be light, moderate, or heavy. 25. Repeatability: decide whether this product teaches a pattern you can turn into a series.
The weekly scorecard
Use a 30-minute weekly review. Give each shelf a 0, 1, or 2: 0 means unclear or broken, 1 means usable but weak, 2 means clear and strong. Pick one shelf only for the coming week. The goal is not to optimise everything; it is to remove the biggest current bottleneck without destroying your attention.
Decision rules
If Reach is low and Trust is strong, improve distribution or keywords. If Reach is high and Trust is weak, fix the page before making new products. If Product is weak, narrow the buyer moment. If Delivery is weak, improve the ZIP, README, preview, and file names. If Cash is weak, raise price, reduce support burden, bundle smarter, or stop repeating that product type.
Mini case studies
A printable planner with many visits but few sales found its Trust score was 4/10: the gallery looked pretty but never showed what pages were included. A script pack with low traffic but strong conversion found its Reach score was weak: the product solved a real problem but used cute names instead of buyer search language. A micro-app that sold twice then created support emails found its Delivery score was weak: customers did not know which file to open first. Small fixes beat new dashboards.
30-minute ritual
Minute 0-5: open product page, preview, buyer ZIP, and last traffic notes. Minute 5-15: score the five shelves. Minute 15-22: choose one bottleneck and write the smallest fix. Minute 22-28: make or schedule the fix. Minute 28-30: write one sentence for next week: what changed, why, and what to check next.
28 weekly signals checklist
- Qualified visits
- Search phrase clarity
- Referrer quality
- Gallery first-slide comprehension
- Freshness touch
- Promise specificity
- What-is-included clarity
- Doubt removal
- Refund/support boundary
- Proof of care
- Buyer moment
- Starter outcome
- Reuse depth
- Differentiator
- Bundle fit
- Download test
- First-open path
- Device reality
- Naming clarity
- Support trigger log
- Price confidence
- Margin calm
- Conversion floor
- Update cost
- Repeatability
- One-shelf focus
- Next tiny fix
- Next review date
Disclaimer
Educational business-planning material only. Not financial, legal, tax, or platform-policy advice. No income or sales outcome is guaranteed.