nicks-demand-report
Produce an executive demand and growth report for Nick's Tire & Auto by reconciling the strongest available evidence across Google Search Console, Google Business Profile/local visibility, website lea
SKILL.md.claude/skills/nicks-demand-report/SKILL.md
GitHubNick's Demand Report
Measure whether Nick's is creating and capturing more qualified local demand, not whether vanity metrics moved.
Core outcomes
Prioritize evidence that connects to:
- phone calls and qualified call outcomes
- direction requests and local discovery
- tire/service inquiries and orders
- booked appointments
- cars arriving at the shop
- repeat customers
- review volume/quality
- revenue and gross-profit proxies when available
- durable local brand recognition
Workflow
- Define the exact reporting period and an equal prior comparison period. Add year-over-year when available and comparable.
- Inventory data sources before analysis. Use connected systems, exports, files, dashboards, or verified production receipts. Mark each source as available, stale, partial, or missing.
- Build the demand chain:
- visibility -> engaged demand -> lead/contact -> booked/committed -> arrived/completed -> revenue -> repeat/review.
- Reconcile channels rather than summing incompatible metrics.
- Organic search and GBP can overlap.
- Calls may include existing customers, vendors, spam, or non-marketing traffic.
- Platform conversions can be modeled or duplicated.
- Find the biggest positive and negative movements, but weight them by business value and confidence.
- Identify leakage between stages: high visibility with weak clicks, strong calls with weak booking, bookings with weak arrivals, traffic with poor conversion tracking, or revenue changes unsupported by demand metrics.
- Surface local competitive or platform changes only when current external evidence materially explains the numbers.
- Distinguish causation, plausible contribution, and simple correlation.
- Read
references/report-contract.mdand follow its output structure.
Rules
- Never call growth successful based on followers, impressions, traffic, or calls alone.
- Never combine counts from different systems unless definitions and deduplication are understood.
- Use exact dates and identify timezone/cutoff mismatches.
- Prefer a small number of high-leverage actions with measurable receipts.
- Flag any area where tracking uncertainty is large enough to undermine the report.
Useful triggers
Examples: "give me Nick's monthly report", "how are we actually doing?", "is demand growing?", "what moved the shop this month?", "where are we leaking customers?"