Propensity Scorer (Signal-Weighted)
Rank your campaign list by propensity using a confidence-weighted composite of HG signals — TrustRadius high, bidstream capped, contracts and modernization signals separated and cited.
Observability Propensity Scorer — German Industrial Tier
Campaign category: Observability | Window: May 2026
Tier 1 threshold: ≥ 7 | Tier 2 threshold: ≥ 4 | Tier 3: < 4
Score Legend
| Signal Class | Max Weight | Rationale |
|---|---|---|
| TrustRadius buyer intent (TR) | 0–3 | First-party, verified vendor/category browsing. High confidence per intent calibration skill. |
| Bidstream intent (BS) | 0–1.5 | Directional only; capped. Never allowed to drive a displacement claim alone. |
| Operating signals (OS) | 0–2 | Cloud depth, AI maturity, and modernization posture from company_operating_signals. |
| Technographic intensity (TI) | 0–2 | Adjacency installs (DevOps toolchains, monitoring-adjacent, cloud infra) that create observability pull. |
| Contract within 122 days of expiry (CT) | 0 or 2 | Binary; active infra/cloud contract expiring ≤ 122 days = decision window open. |
| Max composite | 10.5 |
Calibration note: No "Observability" or "APM" named-category installs surfaced in the filtered technographic pull for any of the four accounts — the category filter returned adjacent DevOps/database/cloud infra products. This is expected for large German industrials who often run custom or OT-centric stacks. Technographic scoring is therefore based on adjacency strength (CI/CD pipeline depth, cloud footprint, DevOps toolchain breadth), not a confirmed Observability install. The absence of a confirmed install also means no displacement claim is warranted for any account; these are whitespace or expansion plays.
Per-Account Signal Detail
1. Siemens AG (siemens.com)
Firmographic context: 316,000 employees · ~€88B revenue · ~$4B IT spend · Forbes Global 2000 #62 (HG, May 2026)
Intent (TR): Active TrustRadius buyer activity across 50+ events in the 30-day window. No Observability-specific product pages, but notable signals: AWS Security Hub vs. SentinelOne comparison (May 12–15), Playwright vs. Postman API testing comparison, ManageEngine vs. Microsoft System Center endpoint management, Tanium reviews, security tooling pricing pages. Bidstream shows 743 active topics including IaaS (High, Evaluating), Migration (High, Evaluating), Terraform (High, Researching, Complementary to cloud infra), and SAP HANA TDI data platform signals. "iaas" and "Terraform" together are a strong pull signal for cloud-native observability needs. TR score: 1.5 (active but not directly Observability-named; cloud/infra tooling adjacent). Bidstream: 1.0 (IaaS + Migration + Terraform signals, directional).
Operating signals: AI leader accelerating (maturity score 77.3, +3.2 delta); cloud-native depth (AWS 4,126 + Azure 4,578 + GCP 1,253); automation stage: autonomous; network: next-gen. Full-stack cloud modernization in progress. OS score: 2.0.
Technographic: Extremely broad DevOps and infra footprint — Jenkins (intensity 2,096–1,948 across US/IN), Azure DevOps Server (2,424), Git SCM (2,937), HCL Software incl. HCL AppScan/BigFix (2,282), VMware Cloud DRaaS (2,363), Qlik (2,102), Apache Hadoop (1,823), MongoDB (1,795). Deep CI/CD pipeline + cloud data infra = strong observability pull. Last verified across all products within 12 months. TI score: 2.0.
Contracts: Two active HCLTech cloud transformation contracts expiring 2026-09-07 (110 days from scoring date) — inside the 122-day window. CT score: 2.0 (binary trigger met). HG-modeled contract value: ~$5.3M + ~$0.8M annual run-rate.
Composite: 1.5 + 1.0 + 2.0 + 2.0 + 2.0 = 8.5 / 10.5 → TIER 1
2. Bosch (bosch.com)
Firmographic context: 418,000 employees · ~€102B revenue · ~$2.4B IT spend (HG, May 2026)
Intent (TR): ⚠️ Intent API returned HTTP 404 for bosch.com — upstream data gap. No TrustRadius or bidstream intent data available for this scoring cycle. Per the intent calibration skill, this is flagged for manual verification in the HG platform UI before any SDR prioritization. TR score: 0 (no data). Bidstream: 0 (no data). ⚠️ Flag: bidstream-silent; this account may have suppressed domain matching or a data gap — manual HG platform check recommended before deprioritizing.
Operating signals: AI leader accelerating (maturity 56.8, +4.0 delta — highest 6-month delta in this set); cloud-native (AWS 2,320 + Azure 2,865 + GCP 725); automation: autonomous (32,142 intensity — highest in set, driven by Computer Vision 3,157, Deep Learning 3,273, NLP 2,001, XAI 1,159); IoT: advanced-industrial (IoT 4,070 + Autonomous Vehicle 2,412 + Smart Home 2,939). Bosch is running the most intensive AI/automation program in this peer group by signal volume. OS score: 2.0.
Technographic: Rich DevOps stack — Jenkins (2,010–1,599 across IN/US/DE), Git SCM (2,363–1,477), Atlassian Bitbucket (1,147–902), Red Hat Ansible (946), GitHub (913), Apache Hadoop (1,181–910), MongoDB (1,224), Oracle DB (1,229). Automotive-specific: CANalyzer (2,653) confirms embedded/OT environment requiring specialized observability. TI score: 1.5 (strong DevOps depth, automotive OT adds complexity that may favor niche observability vendors — slight reduction from max).
Contracts: All 7 contracts are expired; none active. No renewal trigger. CT score: 0.
Composite: 0 + 0 + 2.0 + 1.5 + 0 = 3.5 / 10.5 → TIER 3
(Intent data gap is the dominant downward driver. Manually verify in HG platform — if even moderate TR activity exists, score would move to Tier 2.)
3. BASF SE (basf.com)
Firmographic context: 111,822 employees · ~€70B revenue · ~$2.3B IT spend · Forbes Global 2000 #305 (HG, May 2026)
Intent (TR): 45 TrustRadius events in the 30-day window. Notable signals: AWS Systems Manager product pages viewed on Apr 28–29 (2 separate events — cloud ops tooling, directly adjacent to observability); OpenText ArcSight product details (May 3, security/monitoring adjacent); Rackspace Managed Hosting reviews; Metabase analytics; Darktrace vs. n8n comparison. Bidstream: 544 active topics; "Check Point" expansion signal, "Open JDK" expansion, Insider Threat research. The AWS Systems Manager signal is the most relevant — it indicates someone is researching cloud operational management tools, a direct gateway category for observability. TR score: 1.0 (AWS Systems Manager is adjacent, not Observability-named; activity volume is lower than Siemens). Bidstream: 0.5 (directional, no strong observability-adjacent topic).
Operating signals: AI leader (plateau — maturity 34.3, -1.0 delta, weakening); cloud-native (AWS 1,576 + Azure 1,287); automation: autonomous (6,039 intensity, lower than peers); cloud posture: no-signal (no private/hybrid cloud mentions detected). Weaker modernization posture vs. Siemens/Bosch. OS score: 1.0.
Technographic: SAP-heavy stack (SAP QM, SAP BW, SAP SD, SAP HCM, SAP SuccessFactors) — deep SAP dependency with moderate cloud data tools. OSIsoft PI / AVEVA (last verified Oct 2025 — borderline fresh) indicates industrial process data infrastructure where observability tools are relevant for plant operations. HCL Software (4,344 intensity, fresh May 2026) includes HCL BigFix for IT ops management. OpenText Documentum active (Dec 2025). TI score: 1.0 (SAP-centric; process data tools suggest operational monitoring need, but CI/CD depth is thinner than peers).
Contracts: Two active SAP S/4HANA Cloud contracts (both started May 27, 2025; expire May 27, 2028 — 738 days out). One active OpenText contract (expires Jul 2028). No contracts within 122 days. CT score: 0.
Composite: 1.0 + 0.5 + 1.0 + 1.0 + 0 = 3.5 / 10.5 → TIER 3
4. Continental AG (continental.com)
Firmographic context: 92,653 employees · ~€22B revenue · ~$392M IT spend · Forbes Global 2000 #585 (HG, May 2026)
Intent (TR): 59 TrustRadius events in the 30-day window — second-highest TR event count in this set. Key signals: Beats (Elasticsearch/Elastic Stack) product details viewed Apr 26 and May 4 — Elastic Beats is a direct observability/log-shipping component; Google Analytics vs. HeapAnalytics vs. Google Cloud Operations Suite three-way comparison (Apr 26) — Google Cloud Operations Suite is an explicit observability/monitoring product; AWS Systems Manager product details (Apr 26 and Apr 29); F5 NGINX vs. Azure Front Door comparison (May 9 — application delivery/infrastructure monitoring adjacent); Apache Cassandra vs. Teradata Vantage database comparison. Elastic Beats + Google Cloud Ops comparison together are the strongest observability-adjacent TrustRadius signals in this entire account set. TR score: 2.5 (Elastic Beats + Google Cloud Operations are directly in the observability stack; high confidence per TrustRadius signal classification).
Bidstream intent: 559 active topics; 7 displacement signals (highest in set) and 21 complementary; Data Science (High, Evaluating), SAP HANA TDI (Complementary/Expansion), Citrix expansion, Skype displacement (bidstream only, not asserting a switch). The displacement signals indicate active vendor evaluation motion generally. Bidstream: 1.0 (directional; Data Science + displacement activity suggests active buying cycle).
Operating signals: AI leader (plateau — maturity 30.8, -1.7 delta); cloud-native but lighter footprint (AWS 472 + Azure 220 + GCP 43 — smallest cloud depth in this set); automation: ai-exploring (intensity 1,320 — lowest); cloud posture: no-signal. Significantly lower modernization maturity than Siemens/Bosch. OS score: 0.5 (plateau + smallest cloud depth — constrained budget signal consistent with Continental's restructuring phase).
Technographic: Light stack per HG data — TYPO3 CMS, CANalyzer (automotive ECU), Jenkins (reduced verifications, some stale to Aug 2025), Git SCM, Adobe Creative Cloud, SAP BW. Importantly, Qlik (intensity 144, last verified Mar 2026 — fresh) and SmartRecruiters are recent. The CANalyzer presence confirms automotive embedded environment. TI score: 0.5 (thinner install base vs. peers; Qlik and Jenkins provide some adjacency, but overall footprint is lighter).
Contracts: All 3 contracts expired (T-Systems SAP migration expired Sep 2025; AWS automotive platform expired Apr 2024; Cognizant IT support expired 2012). No active contract renewal trigger. CT score: 0.
Composite: 2.5 + 1.0 + 0.5 + 0.5 + 0 = 4.5 / 10.5 → TIER 2
Ranked Composite Table
| Rank | Company | Domain | TR | BS | OS | TI | CT | Composite | Tier | Top Driving Signal |
|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Siemens AG | siemens.com | 1.5 | 1.0 | 2.0 | 2.0 | 2.0 | 8.5 | 🔴 Tier 1 | HCLTech cloud contracts expiring in 110 days + IaaS/Terraform bidstream + autonomous AI posture |
| 2 | Continental AG | continental.com | 2.5 | 1.0 | 0.5 | 0.5 | 0 | 4.5 | 🟡 Tier 2 | TrustRadius activity on Elastic Beats + Google Cloud Operations Suite comparison (direct observability stack) |
| 3 | BASF SE | basf.com | 1.0 | 0.5 | 1.0 | 1.0 | 0 | 3.5 | ⚪ Tier 3 | AWS Systems Manager TR signals; SAP + process data infra creates latent need |
| 4 | Bosch | bosch.com | 0 | 0 | 2.0 | 1.5 | 0 | 3.5 | ⚠️ Tier 3* | Intent data gap (404); strongest AI/automation posture in set — manual platform verify required |
*Bosch score is structurally suppressed by intent data unavailability. See disagreement flag below.
Tier Distribution
| Tier | Count | Accounts |
|---|---|---|
| Tier 1 (≥7.0) | 1 | Siemens |
| Tier 2 (4.0–6.9) | 1 | Continental |
| Tier 3 (<4.0) | 2 | BASF, Bosch |
Notable Disagreements & Flags
🚨 Flag 1 — Bosch: Bidstream silent but operating signals are anomalously strong
Bosch returned a 404 on the intent API, yielding zero TR and bidstream contribution. Yet its operating signals are the highest in the peer set: fastest-accelerating AI maturity (+4.0 delta), highest automation intensity (32,142), strongest NLP/computer vision/XAI stack — exactly the telemetry complexity that drives observability demand. This is the most likely false deprioritization in the set. Action: verify in the HG platform UI before routing Bosch to Tier 3. If any TR signal on cloud ops, monitoring, or infrastructure tooling exists, composite would move to 5.5–6.5 (Tier 2).
🟡 Flag 2 — Continental: High TR signal, weak operating posture — a divergence
Continental carries the highest TrustRadius signal quality (Elastic Beats + Google Cloud Operations Suite — directly in-category), but its operating signals and technographic depth are the weakest in the set. This is a known divergence pattern: a single motivated buyer or small team driving research that hasn't yet propagated to organizational investment. Interpret as: a real buying signal from a specific team or initiative, not a company-wide modernization wave. SDR motion should be narrow and team-specific (likely a platform/DevOps team), not a C-suite pitch.
🟡 Flag 3 — Siemens: Contract trigger is the decisive differentiator
Siemens would score ~6.5 without the HCLTech contract trigger — respectable Tier 2. The 110-day contract window pushes it firmly into Tier 1. The HCLTech contracts ($5.3M + $0.8M annual, cloud transformation scope) are the renewal-cycle entry point: the conversation is already "live" on cloud transformation, and observability is a natural adjacent ask. The 110-day figure should be validated for precision — HG models contract expiry dates with variable confidence; treat as approximately inside the 122-day decision window.
⚪ Flag 4 — BASF: No observability installs confirmed; bidstream-only for most signals
BASF's relevant TR signals (AWS Systems Manager) are adjacent but not confirmed Observability. Its operating signals show a plateau trajectory (AI maturity declining). The OSIsoft PI / AVEVA install (process data historian, stale Oct 2025) is the most natural hook — AVEVA customers frequently need telemetry/observability layers for industrial data pipelines. This is a whitespace play (no existing observability vendor confirmed), best suited for discovery messaging tied to industrial operations monitoring, not a competitive displacement.
Displacement Claim Guardrail Check ✅
Per the intent calibration skill: no displacement framing is used in this output. The technographic pull returned no confirmed Observability or APM vendor installs for any account. All plays are framed as whitespace or expansion. The displacement signals in Continental's bidstream (7 flagged contexts) are noted as directional only; no incumbent is confirmed to be at risk without a specific technographic confirmation. (HG, May 2026)
Overview
Rank an account list by propensity using a confidence-weighted composite of HG signals. Marketing Ops feeds a campaign list; the workflow scores each account on TrustRadius buyer intent (high confidence), bidstream intent (medium, capped), operating-signal modernization, technographic intensity in the relevant category, and contract-expiry proximity, then returns a tiered output with the signals that drove each score.
Use cases
Rank your ABM list by propensity, honestly
Feed in a 500-account campaign list. The workflow scores each account on TrustRadius buyer intent (high weight), bidstream intent (medium, capped), operating-signal modernization, technographic intensity in the campaign category, and contract-expiry proximity. The output is a tiered ranked list with a per-class breakdown so the SDR-priority cohort is defensible and the marketing-only nurture cohort is honest about why it didn't make Tier 1.
View workflow prompt
# Propensity Scorer (Signal-Weighted)
## Parameters
- `{{account_domains}}` *(required)* — Comma-separated domains of the accounts to score. Example: `siemens.com,bosch.com,basf.com,continental.com`
- `{{category}}` *(required)* — The product category your campaign is selling. Example: `Cloud cost optimization`
- `{{tier_threshold_t1}}` *(optional)* — Composite score threshold for Tier 1. Example: `7`
- `{{tier_threshold_t2}}` *(optional)* — Composite score threshold for Tier 2. Example: `4`
## Purpose
Rank {{account_domains}} by propensity for {{category}} using a confidence-weighted composite. Tier above {{tier_threshold_t1}} is SDR-priority; tier above {{tier_threshold_t2}} is marketing-only nurture. Every score traces to its signal class.
## Process
1. **Gather signals per account.** `company_intent` (TrustRadius and bidstream, source-class noted), `company_technographic` (intensity in {{category}} and adjacencies), `company_operating_signals` (modernization wave in the relevant axis), `company_contracts` (renewal proximity in {{category}}), `company_firmographic` (for context only).
2. **Score each signal class with the right weight.** TrustRadius buyer intent: high weight (0 to 3). Bidstream intent: medium weight, capped at 1.5. Operating-signal modernization in the right axis: medium weight (0 to 2). Technographic intensity in {{category}}: 0 to 2. Contract within 122 days of expiry: 0 or 2 (binary). Sum into composite (max 10.5).
3. **Apply the cross-reference rules.** Displacement framing requires `company_technographic` confirming an incumbent install. "Evaluating" claims are bounded to "engaging with [vendor]-comparison content" per the intent calibration skill.
4. **Tier the output.** Composite above {{tier_threshold_t1}} = Tier 1 (SDR-priority). Above {{tier_threshold_t2}} = Tier 2 (marketing-only nurture). Below = Tier 3 (deprioritize this cycle).
5. **Surface the ranked CSV-shaped table.** Each row: company, domain, composite score, per-class breakdown (TR / bidstream / operating / tech / contracts), tier, top driving signal.
## Output Format
- Score legend (weights + the rationale per class, citing the intent calibration source)
- Ranked table sorted by composite descending
- Tier distribution (count per tier)
- Notable disagreements: accounts where bidstream is high but TrustRadius is silent (likely false positives; flag for manual review)
## Quality Checklist
- Bidstream-only displacement claims are flagged, not asserted
- Every composite score has a per-class breakdown the reader can challenge
- TrustRadius signals are cited with topic + recency; bidstream signals are cited as directional only
- Tier thresholds {{tier_threshold_t1}} and {{tier_threshold_t2}} are stated explicitly