What are B2B buying signals? Buying signals are observable actions that indicate a company is actively preparing to purchase software or services. In DACH markets, job postings are the most reliable leading indicator — they represent committed budget decisions, not browsing intent.
Key factors: signal type, hiring velocity, job title specificity, tech stack mentions, combo signals
This guide covers: the six signal categories, a scoring framework, and a step-by-step outreach playbook for DACH and Scandinavia.
Why Job Postings Are the Most Reliable Buying Signal in DACH
Most intent data platforms rely on anonymous web behaviour — tracking which companies visit review sites or download vendor content. This approach has a fundamental flaw: it captures interest, not commitment. A procurement manager reading a G2 comparison page may be six months from a decision. A company hiring a Salesforce Administrator has already made it.
Job postings represent a committed budget decision. HR has approved a headcount. Finance has allocated salary budget. The tool that headcount will manage is either purchased or under active evaluation. This makes hiring data structurally superior to behavioural intent signals for predicting near-term purchases.
The Specificity Advantage
A generic "cloud job posting" tells you little. But a posting for a "Senior DevOps Engineer — Kubernetes, AWS EKS, Terraform (München)" reveals the exact technology stack, the infrastructure maturity level, and the geographic market. IntentDepth extracts these specifics from every posting using NLP, turning raw job data into actionable purchase intelligence.
The Six DACH Buying Signal Categories
Not all hiring signals carry equal weight. The following framework classifies signals by category, typical score range, and average time-to-purchase decision based on observed patterns in the DACH market.
| Signal Category | Trigger Keywords | Score Range | Avg. Decision Window |
|---|---|---|---|
| Cloud Migration | Cloud Architect, AWS, Azure, GCP, Kubernetes | 80–95 | 60–120 days |
| CRM Purchase | Salesforce Admin, HubSpot, Dynamics 365, CRM Manager | 75–90 | 30–90 days |
| ERP Rollout | SAP Consultant, S/4HANA, Oracle ERP, ERP Implementation | 75–88 | 90–180 days |
| Data Infrastructure | Data Engineer, dbt, Snowflake, Databricks, Fivetran | 70–85 | 45–90 days |
| Security Investment | CISO, SOC Analyst, NIS2, Information Security Engineer | 72–88 | 30–90 days |
| Rapid Hiring | 3+ tech roles from same company in 30 days | 70–80 | 60–120 days |
How to Score and Prioritise Signals
Raw signal detection is not enough — prioritisation separates actionable intelligence from noise. The IntentDepth scoring model combines four factors: base signal strength, combo bonuses, decay weighting, and outreach readiness.
The Signal Scoring Checklist
- Platform specificity — "Salesforce Admin" scores higher than "CRM experience required"
- Combo signal — same company posting CRM + Data Engineer = active platform transformation (+15–20 points)
- Hiring velocity — 3+ related roles in 30 days triggers a Rapid Hiring bonus
- Signal age — fresh signals (0–7 days) carry full weight; signals older than 30 days decay
- Domain resolved — company with a verified domain gets a +5 outreach readiness bonus
- Tech stack extracted — NLP-confirmed tools in job description add specificity score
Signals scoring above 85 are classified HOT. Scores between 70–84 are WARM. Below 70 are low-priority and rarely worth immediate outreach.
The DACH Market Context: Why Timing Matters More Here
DACH enterprise buying cycles are structurally longer than those in US markets. German procurement culture emphasises thorough vendor evaluation, security audits, and legal review — particularly for cloud and data tools subject to GDPR. This means the window between "early signal" and "signed contract" is often 90–180 days, compared to 30–60 days in North America.
The practical implication: reaching a DACH company at the signal stage — before they issue an RFP or engage a systems integrator — gives you a 90-180 day head start over competitors who discover the opportunity through public channels. Mittelstand companies (50–500 employees) in particular rarely publish RFPs; relationships established early in the buying cycle disproportionately determine vendor selection.
Turning Signals Into Pipeline: A 4-Step Outreach Framework
Identifying a signal is only half the work. The outreach approach must match the signal type and the company's apparent buying stage.
- Validate the signal — Check LinkedIn for supporting evidence: has the company posted other related roles? Has their team grown in this function recently?
- Identify the decision-maker — For cloud signals, target the VP Engineering or Head of Infrastructure. For CRM signals, target the VP Sales or RevOps lead. For ERP, target the CIO or CFO.
- Lead with the signal, not the pitch — "We noticed you're building out your Snowflake infrastructure" opens a conversation. "Here's our product demo" closes it before it starts.
- Set a 14-day follow-up cadence — DACH buyers rarely respond to first contact. A structured 3-touch sequence over 14 days significantly improves response rates.
2026 Update: What's Changed in DACH Intent Data
The NIS2 Directive's October 2024 implementation deadline created a new signal category that is now fully active: companies hiring Information Security Managers or CISO roles are operating under regulatory pressure, meaning budget is already approved and timelines are compressed. This is particularly pronounced in manufacturing, healthcare, and critical infrastructure sectors.
Additionally, SAP's 2027 end-of-mainstream maintenance for ECC 6.0 has accelerated S/4HANA migration hiring across the DACH region. Companies that deferred migration planning in 2024 are now in active implementation, making mid-2026 a peak window for ERP-adjacent software and consulting services.
Ready to see this week's buying signals for your target market? IntentDepth delivers ranked DACH and Scandinavia signals every Monday. Start your free 7-day trial →