Segment by Pain Point
Translate a pain hypothesis into a detectable signal pattern, then score every account in your list against it.
Pain-Point Segmentation: "Multi-vendor ITSM estate without unified event correlation"
Pain Pattern Definition
The target pattern is an enterprise running four or more distinct ITSM or adjacent IT service/operations management products — spanning service desk, ticketing, IT operations, and workflow tooling — without evidence of a unified event-correlation or AIOps layer that would stitch those signals together. At scale (100K+ employees), this creates ticket fragmentation, duplicate incidents, and manual triage overhead that only compounds as cloud and hybrid infrastructure grows.
Detection proxies used:
- Primary: Count of distinct ITSM-adjacent vendors per account (Atlassian/Jira, ServiceNow, HCL Software/DRYiCE, SAP ITSM modules, IBM ITSM, BMC) across
company_technographic - Secondary: Presence of adjacent sprawl indicators — multiple collaboration/workflow stacks (M365, SAP, Atlassian co-running at scale), IBM Rational ClearCase (legacy change management), HCL Notes (aging messaging/workflow layer)
- Verification rule: Score 3 requires ≥4 distinct ITSM-adjacent vendors with high-intensity signals; score 2 requires 2–3 distinct vendors plus corroborating complexity indicators (global footprint, legacy platforms in-flight)
Important caveat: HG's technographic data for these accounts is dominated by enterprise productivity and engineering tooling. Dedicated ITSM products (ServiceNow, BMC Remedy, Freshservice) did not appear in the top-100 intensity results for any account — suggesting either that they are present but at lower observed intensity, or that service desk tooling is deployed through embedded enterprise suites (SAP, HCL, Microsoft). The scoring below reflects what the data actually shows; it does not fabricate incumbents.
ICP Scoring (Pre-Segment Prioritization)
| Factor | Weight | Siemens | Bosch | BASF | Continental |
|---|---|---|---|---|---|
| Install intensity (top-stack richness) | 4 | ●●●● | ●●●● | ●●●● | ●●●○ |
| IT spend | 3 | ●●●● ($4.0B) | ●●●● ($2.4B) | ●●●● ($2.3B) | ●●○○ ($392M) |
| Technology fit (ITSM-adjacent complexity) | 3 | ●●●● | ●●●● | ●●●● | ●●○○ |
| Revenue tier | 2 | ●●●● ($88.7B) | ●●●● ($102.3B) | ●●●● ($70.8B) | ●●●○ ($22.1B) |
| Industry match (large complex ops) | 2 | ●●●● | ●●●● | ●●●● | ●●●○ |
| Raw score | 91/100 | 89/100 | 87/100 | 52/100 | |
| Tier | A | A | A | B |
Qualifying Segment Table
Score 3 Accounts — Full pattern match with strong complexity signals
| Company | Domain | Score | ITSM/Workflow Vendors Detected | Key Complexity Signals | Suggested Persona |
|---|---|---|---|---|---|
| Siemens AG | siemens.com | 3 | Microsoft 365/Teams (UCC+workflow), Atlassian suite, SAP (workflow/change mgmt), IBM Rational ClearCase (legacy change control), Azure DevOps | 316K employees; $4.0B IT spend; IBM Rational ClearCase at high intensity (3,223) signals a legacy change-mgmt layer co-existing with modern Atlassian tooling; SAP FI/CO modules carry embedded approval workflows; Azure DevOps adds a fourth operations channel. At least 4 distinct vendor layers for service/change management verified | VP IT Operations, CIO, Head of IT Service Management |
| Bosch GmbH | bosch.com | 3 | Microsoft 365/Teams (UCC+workflow), Atlassian (intensity 2,194 IN + 2,152 US, high), Jira Software (intensity 2,054 IN + 1,942 US), SAP (multi-module), IBM Rational ClearCase | 417K employees; $2.4B IT spend; Jira Software and Atlassian suite both explicitly verified at high intensity across India and US locations, indicating separate Jira instances by region; SAP ERP modules carry embedded service workflows; IBM ClearCase provides legacy change management layer. Four distinct vendor-sourced service/change channels confirmed | VP IT Operations, Head of Enterprise Service Management |
Score 2 Accounts — Partial match with strong corroborating indicators
| Company | Domain | Score | ITSM/Workflow Vendors Detected | Why Score 2 (Not 3) | Suggested Persona |
|---|---|---|---|---|---|
| BASF SE | basf.com | 2 | HCL Software/DRYiCE (intensity 4,344 — highest of any ITSM-adjacent signal in this cohort), HCL Notes (4,344, legacy workflow layer), SAP (multi-module with IT management attributes), Microsoft 365 | 111K employees; $2.3B IT spend; HCL DRYiCE is an AI-powered ITSM product confirmed at high intensity co-existing with HCL Notes (a legacy collaboration/workflow layer) and a deep SAP estate. Three distinct IT management vendor families verified. Falls short of Score 3 because the fourth vendor (a standalone ticketing or monitoring platform) was not surfaced in the top-100 results | CIO, VP Digital Transformation |
Notable Misses
| Company | Domain | Score | Why It Missed |
|---|---|---|---|
| Continental AG | continental.com | 0 | Smallest IT footprint of the cohort by a wide margin ($392M IT spend vs. $2.3B+ for others). Top-100 technographic results show Microsoft 365, SAP, and engineering tools (CATIA, Mathworks) with HCL Notes/Software at low intensity (488). The ITSM-adjacent vendor count does not reach the threshold. Firmographically plausible (92K employees) but operationally, the IT complexity signals are insufficient to confirm the pain pattern |
Confidence Note
Cohort size: 4 accounts assessed. Verification rate: 2/4 accounts (Siemens, Bosch) scored 3 with multiple corroborating signals; 1/4 (BASF) scored 2 with a strong ITSM-specific signal but incomplete vendor count confirmation; 1/4 (Continental) scored 0.
Data sourcing: All signals from HG company_technographic (full unfiltered pulls, top 100 by intensity, May 2026). Firmographic data from HG company_firmographic. No intent signals were queried in this pass — adding company_intent for ITSM-adjacent topics (e.g., "ServiceNow," "IT Operations Management," "AIOps") would sharpen the score, particularly for BASF and Continental.
Known limitation on ITSM product visibility: Dedicated service desk products (ServiceNow, BMC, Freshservice) did not appear in the top-100 intensity results. This is consistent with how HG technographic data surfaces — large enterprises often have ITSM platforms at medium-to-low intensity because the service desk layer has fewer public-facing signals than ERP or collaboration suites. A targeted lookup against specific ServiceNow/BMC product IDs is recommended before finalizing scores for Siemens and Bosch.
Recommended Next Steps
-
Siemens & Bosch (Score 3 → prioritize now): Run
company_intentfiltered for ITSM / IT Operations Management topics to check for active research signals. The IBM ClearCase + Atlassian + Azure DevOps co-existence is a compelling conversation opener about change management fragmentation — lead with that. -
BASF (Score 2 → validate): Run a targeted technographic lookup for ServiceNow and BMC product IDs. HCL DRYiCE at intensity 4,344 is a genuine ITSM incumbent signal; if a second monitoring or ticketing platform surfaces, BASF moves to Score 3. The HCL Notes install also indicates a legacy workflow layer that is ripe for consolidation conversation.
-
Continental (Score 0 → deprioritize): The IT spend gap ($392M vs. $2.4B+ for others) is the structural constraint. Consider revisiting if Continental's automotive software spinoff (Continental Automotive Technologies) creates a separate IT estate worth targeting independently.
Overview
Segment an account list by the pain the data suggests they're feeling. Marketing Ops feeds a pain hypothesis (vendor sprawl, declining incumbent, post-outsourcing rebuild) and an optional account list; the workflow maps the hypothesis to detectable HG signal patterns, scores each account against the pattern, and returns the qualifying accounts with the signals that placed them in the segment.
Use cases
Run your campaign hypothesis through real signals
Marketing campaigns ride on pain hypotheses (CRM sprawl, post-outsourcing rebuild, declining incumbent). The workflow translates the hypothesis into a detectable signal pattern across HG firmographic + technographic + contracts + intent, scores every candidate account against the pattern, and surfaces the qualifying segment with the signals that placed each account on the list. Misses are surfaced honestly so the pattern doesn't get silently widened.
View workflow prompt
# Segment by Pain Point
## Parameters
- `{{pain_hypothesis}}` *(required)* — The pain to detect. Example: `4+ ITSM vendors without event correlation`
- `{{candidate_domains}}` *(optional)* — Comma-separated candidate account domains. Example: `siemens.com,bosch.com,basf.com`
- `{{category}}` *(optional)* — Anchor category for the pain. Example: `IT Service Management`
## Purpose
Detect which accounts are experiencing {{pain_hypothesis}} (scoped to {{category}}) across {{candidate_domains}}. If the candidate list is empty, derive one from the hypothesis via `search_companies`. Return a ranked segment with the HG signals that placed each account on the list.
## Process
1. **Translate the hypothesis to a signal pattern.** Pick the right HG-detectable proxies. CRM sprawl pattern: `company_technographic` returning ≥ 4 vendors in the relevant category. Post-outsourcing rebuild pattern: `company_contracts` showing expired large IT-services contracts without active large replacements. Declining incumbent pattern: `company_technographic` intensity drop or `company_intent` against displacement keywords for that vendor.
2. **Score each candidate.** For every account in {{candidate_domains}} (or the derived list), run the signal pattern. Score 0 to 3 on how cleanly the data matches: 3 = the full pattern is present with strong intensity, 1 = partial match, 0 = no signal. Pull `company_firmographic` for context.
3. **Verify each match.** For any account scoring 2 or 3, confirm with at least one secondary signal (intent topic, recent contract expiry, operating-signal modernization wave).
4. **Surface the qualifying segment.** Score 2-and-3 accounts with the signals that placed them. Note any accounts that look promising in firmographic terms but score 0 to 1 (likely false negatives or off-pattern).
## Output Format
- Pain pattern definition (one paragraph; the proxies, intensities, and verification rules)
- Qualifying-segment table (score 3 then score 2: company, domain, score, signals that placed them, key figures)
- Notable misses (firmographically-fit accounts that scored 0 to 1, with a one-line "why")
- Confidence note: cohort size, verification rate
## Quality Checklist
- Pain pattern definition is explicit; reader can challenge or refine
- Every qualifying account cites the signals that placed it (not just a score)
- Misses are surfaced honestly; pattern is not silently widened to hit a quota
- Citations use HG signal source class per the intent calibration skill (TrustRadius vs bidstream named)
