sb-demand-capture
Diagnostic over three terms: the destination's demand, the searches on the property's own booking engine, and actual Back Office reservations. Says whether a property captures its destination's demand and, when it doesn't, which leg loses it — visibility or conversion. Orchestrates sb-revenue-lens (area demand, availability, restrictions, parity) and sb-reservation-insights (pickup, channel mix, markets, lead time), and owns first-party demand directly. Use ALWAYS for: "am I keeping up with the market", "I have demand but I'm not selling", "do they even find me", "searches that found nothing", "requests I turned away", "who searches vs who books", "am I opening sales too late", "which property captures demand best". Do NOT use for: a single metric in isolation (sb-reservation-insights); demand, availability or price without sales (sb-revenue-lens); the fixed weekly brief (sb-monday-brief); direct booking provenance (sb-direct-attribution).
Pinned to revision 9620e2a7d550, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/sb-demand-capture/SKILL.md
- skills/sb-demand-capture/agents/openai.yaml
- skills/sb-demand-capture/config/defaults.yaml
- skills/sb-demand-capture/references/cross-lenses.md
- skills/sb-demand-capture/references/orchestration.md
- skills/sb-demand-capture/references/property-demand.md
- skills/sb-demand-capture/scripts/verify.py
- skills/sb-demand-capture/templates/sb-demand-capture-example-questions.html
Every link opens the file at its source, pinned to the revision this page describes.