The list you sent us was from a 2023 SAP user-group event. Names, titles, and emails accurate as of then. We re-verified all 812 contacts against Apollo and rolled the changes up to the company level. What came back is more than a clean list — it's a Stuck-Program signal map across the Nordic SAP universe. Here's what moved.
Six numbers that explain why the list was worth washing. None of these would have surfaced from the spreadsheet alone — they all required matching every contact back to a current source of truth. Apollo was that source.
Of the 340 contacts who moved, the ones that matter most are the C-suite and Director-level departures — they take SAP decisions with them. Below is a sample of the more notable moves we surfaced from the wash. Names and destinations are public via LinkedIn; we didn't dig into anything sensitive.
When we scanned the open job postings of the top 13 highest-drift companies, one role jumped off the page. It's the cleanest demonstration of the Stuck-Program pattern we could have asked for.
ABAP is the proprietary programming language for SAP ECC's customizations — the bespoke extensions that grew up around the core ERP over the years. Hiring an ABAP developer in 2026 is, definitionally, an investment in maintaining custom ECC code. Not a migration. Not a transition. A maintenance hire.
"If you're hiring people to maintain your custom ECC code in 2026, you've effectively chosen ECC over RISE/Joule for now. That's the diagnostic in one job posting."
Combine that single posting with what the wash already shows about Fora AB — CFO departed, CIO departed, 71% of the original contacts have moved on — and you have an account where the leadership conversation about SAP modernization hasn't happened yet, but the operational signal says it's overdue. That's a Stuck-Program Diagnostic conversation waiting to happen.
Different shape from Fora AB. Telia is actively building out SAP capability — three open roles, all senior, spanning the parts of the platform that matter for a transformation: identity/auth, integration, finance.
These three roles read together as the core operating team for an in-progress SAP program — someone owning identity and access, someone owning the integration layer between SAP and the rest of the stack, someone owning the finance modules. You don't post these roles unless SAP is a strategic platform you're investing in.
Telia's drift score is also 7/10 — CIO has departed since 2023. The combination — new IT leadership stepping into an active SAP investment — is the textbook moment for an outside POV like Forefront's Joule-Native Selective Transition to land in the inbox of whoever just inherited the program.
Combined priority = drift score + SAP signal weighting. These five sit at the top of the account map. Each one has a specific, evidence-backed reason to lead with the Stuck-Program Diagnostic right now — not next quarter.
The full account list (Nordic-SAP-Account-List.xlsx) sits in this package — link's on the index page. It's got everything you need to start working the top 13: enriched contact rows, the Drift_Per_Company sheet, the SAP_Signals sheet, the Priority_Targets list. Tier-rebalanced, sorted, ready to ship into whatever cadence tool the team uses.
The two playbook docs in here — the Stuck-Program Diagnostic and the 4-Buyer Coalition — were written before any of this evidence existed. Now it does. The diagnostic in particular reads differently when you can name three live signals at the account it's being sent into.
If you only do one thing with this: open the Priority_Targets sheet and send Fora AB the Stuck-Program Diagnostic email this week. The ABAP role is the hook. The diagnostic offer is the close. We'd love to hear how it lands.
Open the Account Map→