High-Intensity Location Decline Watch
For platforms that land site-by-site, location attrition is the leading indicator. Catch it.
Sample output for this workflow will appear here once it is captured.
Run the workflow in Claude, ChatGPT, or Phoenix Playground using the buttons below to see real output.
Overview
If your platform lands site-by-site (industrial, security, point-of-sale), the leading churn signal is high-intensity locations falling. `company_technographic.productLocations` is a current snapshot only, so this workflow REQUIRES a prior_location_count parameter from your CRM or prior brief. Output is a delta + the intensity_momentum context — so you know whether the location drop is a deployment pullback or just attrition.
Use cases
For platforms where attrition lives in the location count
If your product lands per-site (a security agent, a POS terminal, a sensor), the location count IS the adoption signal. Intensity averaging across sites hides per-site attrition. This workflow surfaces the count delta plus the momentum context — so a 47→42 drop reads as 'real, plus adoption momentum is negative, escalate' rather than 'maybe noise'.
Honest about the data limit
`company_install_time_series.data_points` only carries intensity, not locations. So this workflow requires `prior_location_count` from your CRM. Better than fabricating a per-month location series — your CSMs trust outputs that say 'we don't have monthly granularity, here's the prior vs current'.
View workflow prompt
# High-Intensity Location Decline Watch
## Parameters
- `{{domain}}` *(required)* — Customer company domain. Example: `acme.com`
- `{{your_product}}` *(required)* — Your product (the per-site product whose location count is the leading indicator). Example: `Cisco Umbrella`
- `{{prior_location_count}}` *(required)* — Baseline location count from a prior brief or CRM. REQUIRED — company_install_time_series.data_points only carries intensity, not locations.. Example: `47`
## Purpose
For platforms that deploy site-by-site (industrial, security, point-of-sale), high-intensity locations dropping is the earliest churn indicator. Compare today's `productLocations` for {{your_product}} at {{domain}} against the CRM-supplied {{prior_location_count}} baseline. Surface delta + adoption context.
**Important data limit**: `company_install_time_series` `data_points[]` returns `{ date, intensity }` only — no per-month location count. `company_technographic.productLocations` is a current snapshot only. The {{prior_location_count}} parameter is the only baseline.
## Process
1. **Resolve product id** — call `get_vendor_information` for {{your_product}} to get its canonical product/vendor id (exact-product filtering in `company_technographic` requires this; passing a free-text name can miss the product if it's not in the unfiltered top results). Optionally also call `list_product_categories` to confirm the category.
2. **Current snapshot** — `company_technographic` for {{domain}} filtered by the resolved product id. Capture today's `productLocations` and `firstVerifiedDate` (when the product was first detected at the customer).
3. **Adoption context** — `company_install_time_series` for {{domain}} filtered to {{your_product}}, `timeRange: last_12_months`. Capture `intensity_momentum` and `current_intensity`. Location decline + negative intensity momentum is a much louder signal than location decline alone.
4. **Customer context** — `company_firmographic` for {{domain}}: any customer-enrichment context. For explicit event detection (office closures, divestitures, M&A that explain a real-estate footprint contraction), route through `web_search` since `company_firmographic` exposes static fields only, not event streams.
5. **Delta + verdict** — `delta = current productLocations − {{prior_location_count}}`. Verdict:
- Delta ≥ 0 → No decline (Watch).
- Delta < 0 AND `intensity_momentum` ≥ 0 → Footprint contraction, adoption holding (likely organic office change — Yellow with firmographic context).
- Delta < 0 AND `intensity_momentum` < 0 → Coordinated deployment pullback (Red — escalate).
## Output Format
- `# 🏢 {{domain}} — Location Decline: <Watch|Yellow|Red>`
- `Prior: {{prior_location_count}} sites | Current: <N> sites | Delta: <±N>`
- `## Adoption context` — `intensity_momentum` + `current_intensity` + first detected at `firstVerifiedDate`
- `## Customer context` — any firmographic event that explains the delta
- `## Verdict reasoning` — one paragraph tying the delta + momentum + context to the verdict
## Quality Checklist
- {{prior_location_count}} is the baseline — never derive a delta from `data_points` (it carries intensity only)
- Verdict cites both location delta AND intensity momentum
- Customer context is non-judgmental — flagged separately from the verdict
- Cap tool calls at ~6