Account Tiering for Marketing Programs
Tier your accounts for ABM 1:1, 1:few, and broad nurture — combining firmographic fit, FAI reach, and momentum signals.
Account Tiering — Observability Campaign
Accounts: siemens.com · bosch.com · basf.com · continental.com
Target revenue band: $500M–$5B (firmographic reach floor)
Data sourced: HG, May 2026
Note on revenue band: All four accounts are large-cap German industrials well above the $500M–$5B sweet spot (revenues range from $22B to $102B). The band is applied as a floor — any company within or above the band earns full fit credit for revenue; companies materially outside (i.e., dramatically smaller) would lose fit credit. Since no account is below the floor, the revenue band does not downgrade any account here; it is called out explicitly per the quality checklist.
Bosch intent data note: The HG V2 intent API returned a 404/422 for bosch.com regardless of lookup method. Intent signals for Bosch are unavailable and treated as absent (0 momentum sub-credit) with a risk flag.
Score Legend
| Axis | Max | Scoring Rules |
|---|---|---|
| Fit | 3 | 1 pt: industry relevance to Observability (tech-intensive manufacturing/industrial) · 1 pt: revenue ≥ $500M · 1 pt: IT spend ≥ $1B (proxy for infrastructure scale) |
| Reach | 3 | 1 pt: Observability products detected in FAI · 1 pt: multiple departments or roles touching Observability installs · 1 pt: decision-maker or influencer flags present in FAI records |
| Momentum | 4 | 1 pt: cloud posture = hybrid or above · 1 pt: network/automation stage = next-gen or autonomous · 1 pt: active IT contracts indicating transformation spend · 1 pt: Observability-adjacent intent signals (bidstream OR TrustRadius) |
| Composite | 10 | Sum of the three axes |
Tier rules:
- Tier 1 (ABM 1:1): Fit ≥ 2 AND Reach ≥ 2 AND Momentum ≥ 2
- Tier 2 (ABM 1:few): Composite ≥ 5 AND Fit ≥ 2 (firmographic floor holds)
- Tier 3 (Broad nurture): Fit ≥ 1, all else below threshold
Axis Scoring Detail
Fit Axis (0–3)
| Account | Industry | Rev ≥ $500M? | IT Spend ≥ $1B? | Fit Score |
|---|---|---|---|---|
| Siemens AG | Instruments/Process Control Mfg (NAICS 334513) — high-relevance industrial | ✓ ($88.7B) | ✓ ($4.0B) | 3 |
| Bosch | Motor Vehicle Electrical & Electronic Mfg (NAICS 336320) — high-relevance industrial | ✓ ($102.3B) | ✓ ($2.4B) | 3 |
| BASF SE | Organic Chemical Mfg (NAICS 325199) — moderate relevance; large process-industrial ops | ✓ ($70.8B) | ✓ ($2.3B) | 3 |
| Continental AG | Other Motor Vehicle Parts Mfg (NAICS 336390) — moderate-high relevance | ✓ ($22.1B) | ✗ ($392M) | 2 |
Continental's IT spend at $392M misses the $1B threshold; all other three are solidly above.
Reach Axis (0–3)
| Account | Observability Products in FAI | Departments Touching | DM / Influencer Flags | Reach Score |
|---|---|---|---|---|
| Siemens AG | Splunk Observability (strength 9), Elastic Observability (strength 21) — both in Engineering 100% | Engineering: Data Scientist, Software Architect, Software Engineer, DevOps Engineer | Influencers present (Software Engineer, DevOps Engineer) — no DM flags | 2 |
| Bosch | Splunk Observability (Engineering 100%, strength 19), Elastic Observability (Engineering 40% / IT 60%, strength 2–3) | Engineering + IT — two distinct departments | No DM or influencer flags | 2 |
| BASF SE | No Observability products detected in FAI | — | — | 0 |
| Continental AG | No Observability products detected in FAI | — | — | 0 |
FAI: Engineering 100% / Splunk Observability & Elastic Observability (HG, May 2026) — Siemens. Engineering+IT split / Elastic & Splunk Observability (HG, May 2026) — Bosch.
Note on Reach = 2 for Siemens/Bosch: Reach earns 1 pt for products detected and 1 pt for multiple roles/departments; the third point requires decision-maker flags, which are absent from FAI records for both accounts. This is flagged as an orchestration risk below.
Momentum Axis (0–4)
| Account | Cloud Posture | Network/Automation Stage | Active Transformation Contracts | Intent Signals | Momentum Score |
|---|---|---|---|---|---|
| Siemens AG | Private-first (hybrid elements, VPC, edge) ✓ | next-gen / autonomous ✓ | HCLTech cloud transformation expiring in 110 days ✓ | 743 active bidstream topics; TrustRadius: IaaS, migration, security research activity — no Observability-specific topic but transformation-adjacent ✓ | 4 |
| Bosch | Hybrid ✓ | software-defined / autonomous ✓ | No contracts returned (API gap — see risk flags) — scored 0 for this sub-credit | Intent unavailable (API error) — scored 0 | 2 |
| BASF SE | No cloud signal (no-signal stage) ✗ | microservices-oriented / autonomous (automation moderate) — partial ✓ | SAP S/4HANA + OpenText contracts, 738–775 days to renewal — active transformation spend ✓ | 544 active bidstream topics; TrustRadius: data pipeline (Striim pricing), automation research, visual collaboration — transformation adjacent but no Observability-specific topic; scored as 1 sub-credit | 3 |
| Continental AG | No cloud signal ✗ | no modernization signal / ai-exploring only ✗ | No contracts returned | 559 active bidstream topics; TrustRadius: F5 NGINX vs Azure Front Door comparison (network-adjacent), SAP HANA TDI, Citrix expansion — mixed signals; scored 1 sub-credit (partial) | 1 |
Intent source classes: all signals above are bidstream (HG source) unless noted as TrustRadius (verified buyer activity). Per intent-data-calibration rules, bidstream signals are directional context only — they inform momentum but do not independently trigger a commercial trigger. No TrustRadius Observability-category signals were found for any account in the 30-day window; all TrustRadius activity cited is adjacent/contextual.
Composite Scores & Tier Assignments
| Company | Domain | Fit | Reach | Momentum | Composite | Tier | Program |
|---|---|---|---|---|---|---|---|
| Siemens AG | siemens.com | 3 | 2 | 4 | 9 | Tier 1 | ABM 1:1 |
| Bosch | bosch.com | 3 | 2 | 2 | 7 | Tier 1 | ABM 1:1 |
| BASF SE | basf.com | 3 | 0 | 3 | 6 | Tier 2 | ABM 1:few |
| Continental AG | continental.com | 2 | 0 | 1 | 3 | Tier 3 | Broad nurture |
Ranked List by Tier
🥇 Tier 1 — ABM 1:1 (Fit ≥ 2, Reach ≥ 2, Momentum ≥ 2)
1. Siemens AG · siemens.com · Composite: 9/10
- Fit (3/3): NAICS 334513 (Process Control Instruments) is a direct Observability use case — industrial telemetry, distributed systems, edge deployments. $88.7B revenue; $4.0B IT spend.
- Reach (2/3): Both Splunk Observability (signal strength 9) and Elastic Observability (signal strength 21) confirmed installed in Engineering. Roles include DevOps Engineers and Software Engineers (influencers flagged). FAI: Engineering 100% / both products (HG, May 2026). No decision-maker titles surfaced — see orchestration risk.
- Momentum (4/4): Cloud-native depth (AWS $4.1B intensity, Azure $4.6B intensity), next-gen network + autonomous automation stage. HCLTech cloud transformation contract ($18.4M combined) expires in 110 days — inside the renewal window. Bidstream: 743 active topics including IaaS (High, Researching), Migration (High, Evaluating), and security stack comparisons via TrustRadius (AWS Security Hub vs SentinelOne, Palo Alto reviews). AI trajectory: ai-leader-accelerating (maturity score 77.3, +3.2 6-month delta).
- Top signal per axis: Fit → NAICS 334513 + $4B IT spend · Reach → Elastic Observability Engineering 100%, signal strength 21 · Momentum → HCLTech renewal in 110 days + IaaS/Migration intent (bidstream, HG)
2. Bosch · bosch.com · Composite: 7/10
- Fit (3/3): NAICS 336320 (Motor Vehicle Electrical & Electronic Manufacturing); IoT-heavy, embedded systems, edge computing — strong Observability affinity. $102.3B revenue; $2.4B IT spend.
- Reach (2/3): Splunk Observability in Engineering (signal strength 19, 100% usage share); Elastic Observability split Engineering 40% / IT 60% (strength 2–3). Two departments touching Observability installs (Engineering + IT). No DM or influencer flags in FAI records (HG, May 2026).
- Momentum (2/4): Hybrid cloud posture; software-defined network + autonomous automation (IoT intensity 11,039 — highest of the group, driven by Autonomous Vehicle 2,412 and Smart Home 2,939 signals). AI trajectory: ai-leader-accelerating (maturity 56.8, strongest 6-month delta +4.0). No active contracts returned; intent API unavailable — both capped at 0, which is why Bosch scores 2 rather than 3–4 on momentum. These are data gaps, not confirmed absences.
- Top signal per axis: Fit → $2.4B IT spend + NAICS 336320 edge/IoT · Reach → Splunk Observability Engineering 100%, strength 19 · Momentum → autonomous stage + highest IoT intensity in cohort
🥈 Tier 2 — ABM 1:few (Composite ≥ 5, Fit ≥ 2)
3. BASF SE · basf.com · Composite: 6/10
- Fit (3/3): NAICS 325199 (Organic Chemical Manufacturing). Process-industrial ops at global scale — plant performance monitoring, distributed pipeline telemetry, and safety instrumentation are all Observability use cases. $70.8B revenue; $2.3B IT spend.
- Reach (0/3): No Observability products detected in FAI. No department-level signal for Splunk or Elastic Observability categories. This is the key gap for BASF — installs may exist below FAI detection threshold or under subsidiary domains.
- Momentum (3/4): Active SAP S/4HANA Cloud (two contracts, ~$35.6M combined, 738 days to renewal) and OpenText supply chain contracts ($13.7M, 775 days) — major digital transformation underway. Bidstream: 544 active topics; TrustRadius: Striim (data streaming pricing viewed), DigitalOcean Droplets pricing, Camunda vs OpenText Magellan comparison — data pipeline and integration research context. No cloud-posture signal detected (no-signal stage); cloud depth shows AWS + Azure active (intensity 1,576 / 1,287) despite no posture declaration. AI maturity plateau (score 34.3, −1.0 delta) — the one drag on momentum.
- Top signal per axis: Fit → $2.3B IT spend + process-industrial NAICS · Reach → no signal (zero score) · Momentum → active SAP/OpenText transformation contracts + Striim/Camunda TrustRadius activity
🥉 Tier 3 — Broad Nurture (Fit ≥ 1, below Tier 2 threshold)
4. Continental AG · continental.com · Composite: 3/10
- Fit (2/3): NAICS 336390 (Other Motor Vehicle Parts Manufacturing) — relevant but lower IT spend ($392M), which misses the infrastructure-scale threshold.
- Reach (0/3): No Observability products detected in FAI.
- Momentum (1/4): No cloud posture signal; no network modernization signal; no contracts. AI trajectory plateauing (maturity 30.8, −1.7 delta — declining). Partial credit for bidstream activity: F5 NGINX vs Azure Front Door comparison (TrustRadius, network infrastructure-adjacent), SAP HANA TDI research, and Data Science / Citrix expansion signals — broadly suggestive of infrastructure interest but no Observability-specific signal. Automation stage is ai-exploring, the weakest of the group.
- Top signal per axis: Fit → NAICS 336390 + $22B revenue · Reach → none · Momentum → F5 NGINX/Azure Front Door TrustRadius comparison (network-adjacent, directional only)
Tier Counts & Recommended Program Mix
| Tier | Count | Accounts | Program |
|---|---|---|---|
| Tier 1 — ABM 1:1 | 2 | Siemens, Bosch | Dedicated sequences: direct outreach to Engineering VP / Head of DevOps at each account; custom Observability ROI messaging anchored to Splunk/Elastic installed base |
| Tier 2 — ABM 1:few | 1 | BASF | Cluster play with 2–4 peer process-industrial accounts; focus on SAP modernization journey and data pipeline observability angle |
| Tier 3 — Broad nurture | 1 | Continental | Digital/content nurture; revisit in Q3 when cloud posture or contract signals develop |
Notable Risks & Flags
1. Tier 1 Orchestration Risk — No Decision-Makers Surfaced (Siemens & Bosch)
FAI confirms Engineering-led Observability deployments at both accounts, but no decision-maker flags appear in any FAI record (isDecisionMaker = false across all 17+ rows per account). The working buyer is clearly the Engineering VP / VP of DevOps / Head of SRE — but no named DM title has been confirmed by the data. Action: Use FAI influencer roles (DevOps Engineer, Software Architect) as warm entry points; escalate to Engineering Director / VP level based on org chart research. Do not cold-call a CIO on these accounts — FAI shows Observability is an Engineering-owned workload, not a central IT purchase.
2. Bosch Data Gaps — Contracts & Intent Unavailable
Bosch's momentum score of 2/4 is constrained by two API gaps (contracts returned 0 records; intent returned HTTP errors). If contracts or intent signals are present in the HG platform UI, Bosch's composite could rise to 8–9, potentially matching Siemens. Action: Verify Bosch contracts and intent in the HG platform before finalizing SDR prioritization within Tier 1. Treat Bosch as a co-equal Tier 1 candidate pending verification, not as a lower-priority account.
3. BASF Tier 2 Escalation Candidate — Strong Fit + Transformation Underway, Zero FAI Reach
BASF carries a 3/3 Fit score and active digital transformation spend ($49M+ in confirmed contracts), but FAI returns zero Observability product signals. This may indicate: (a) Observability installs exist under a subsidiary domain not in scope, (b) installs are present but below the FAI detection threshold, or (c) Observability is genuinely a whitespace opportunity — BASF is investing in SAP/supply chain but has not yet instrumented its operational stack. Action: Run a subsidiary-level technographic check (BASF Catalysts, BASF Corp.) before treating this as whitespace; if confirmed whitespace, the SAP S/4HANA transformation timeline is the entry angle.
4. Revenue Band Assumption Note
The $500M–$5B fit band was applied as a floor; all four accounts exceed it (lowest: Continental at $22B). No account was penalized for being above the band. If the campaign converts specifically on mid-market accounts and these enterprise-scale accounts represent a stretch segment, the composite scores here may overstate actionability — flag for campaign owner to confirm enterprise motion is in scope.
Overview
Tier an account list for marketing programs. Marketing Ops feeds the universe; the workflow combines firmographic fit (revenue, employee count, industry match), reach (FAI department coverage), and momentum (recent operating-signal modernization, intent activity, contract proximity), then returns tier assignments — Tier 1 for ABM 1:1, Tier 2 for ABM 1:few, Tier 3 for broad nurture — with the signals that placed each account in its tier.
Use cases
Tier your ABM book without a manual sort
Marketing Ops feeds the campaign universe. The workflow scores each account on firmographic fit, FAI reach (departments touched, decision-makers identified), and momentum (modernization, intent, contract proximity), then assigns Tier 1 (1:1), Tier 2 (1:few), or Tier 3 (nurture). The ranked output cites the three axis scores plus the top signal per axis, so program leads can defend the tier mix.
View workflow prompt
# Account Tiering for Marketing Programs
## Parameters
- `{{account_domains}}` *(required)* — Comma-separated domains of the accounts to tier. Example: `siemens.com,bosch.com,basf.com,continental.com`
- `{{category}}` *(required)* — The product category the campaign is selling. Example: `Observability`
- `{{target_revenue_band}}` *(optional)* — Revenue band where the campaign converts best. Example: `$500M-$5B`
## Purpose
Tier {{account_domains}} for marketing programs in {{category}}. Reach is anchored on the {{target_revenue_band}} when provided. Tier 1: ABM 1:1 (high fit + reach + momentum). Tier 2: ABM 1:few (fit + reach OR momentum). Tier 3: broad nurture (firmographic fit only). Every tier assignment cites the signals.
## Process
1. **Fit score.** `company_firmographic` across {{account_domains}}: industry match, revenue band match against {{target_revenue_band}}, employee band. Score 0 to 3.
2. **Reach score.** `company_fai` scoped to {{category}}: departments touched, decision-maker flags, contact density. Score 0 to 3 (3 = decision-makers identified, multiple departments, dense contact graph).
3. **Momentum score.** `company_operating_signals` (modernization wave in the relevant axis), `company_intent` (TrustRadius topics in {{category}}, source-class noted), `company_contracts` (renewal proximity). Score 0 to 4 (max).
4. **Tier with rules.** Tier 1: fit ≥ 2 AND reach ≥ 2 AND momentum ≥ 2. Tier 2: total composite ≥ 5 with fit ≥ 2 (so firmographic floor holds). Tier 3: fit ≥ 1, everything else below threshold.
5. **Surface the ranked list.** Each row: company, domain, tier, fit / reach / momentum scores, top signal per axis, recommended program (1:1 vs 1:few vs nurture).
## Output Format
- Score legend (weights + how each axis maps to tiering)
- Ranked table grouped by tier (1, then 2, then 3)
- Tier counts + recommended program mix
- Notable risks: Tier 1 accounts with low FAI reach (orchestration risk), Tier 2 accounts with strong momentum but firmographic-floor miss (escalate review)
## Quality Checklist
- Every tier assignment cites the three axis scores AND the top signal in each
- FAI-derived contacts cite the department and role (not just count)
- Intent signals carry source class (TrustRadius vs bidstream)
- {{target_revenue_band}} is used in the fit score when provided; otherwise call out the assumption
