Most Nordic SAP buyers in 2026 are stuck choosing between two bad options — full big-bang replatforming (expensive, risky, slow to value) or do-nothing-and-pay-the-extended-support-premium. There's a third path nobody is publishing about: selective transition, with Joule activated progressively as each domain migrates. Forefront can credibly publish this — Joule is already running in production for one of your customers. This is the published version of that POV.
The default Nordic conversation in 2026 is binary: big-bang RISE or slow ECC death. Both are wrong for most mid-market accounts. Selective transition — what SAP and BCG sometimes call smartfield or selective data transition — sits between the extremes and is what wins in markets like Sweden where consensus buying, cost discipline, and operating-model continuity all matter more than speed. Forefront can credibly publish this position because (a) the team has the multi-hyperscaler depth to deliver it, and (b) Joule is already running in production for a Forefront customer. Nobody else in the Nordic SAP space owns both. This doc is the published version of that position — a POV Daniel can post under his own name.
The framework below is the simplification we'd publish. Three columns — Big-Bang RISE, Selective Transition, Do-Nothing — scored across the variables that actually drive the Nordic decision. Customer profile inputs determine which column fits; in our experience roughly two-thirds of mid-market Nordic SAP accounts land in the middle column, and the framework defends why.
The opinionated claim of the Method: if you're not in the bottom 20% (genuinely about to be acquired or shut down), you should not be choosing between Big-Bang and Do-Nothing. Selective transition is the rational path. The reason most accounts don't already see it that way is that their existing partner doesn't sell it — Big Four push big-bang because that's their billing model, small boutiques push lift-and-shift because that's their capability. Forefront's position: we sell selective because it's the right answer, not because of our cost structure.
Most "AI on SAP" stories are aspirational — a slide that says you'll get to Joule "after the migration." The Joule-Native version inverts that: Joule activates on each domain as it migrates, so the customer sees AI value in the first phase, not in year three. This isn't theoretical for Forefront — base Joule for Digital Manufacturing is already running in production for a customer. The Method documents how that gets repeated: the data access pattern, the BTP integration plane, the hyperscaler-native services that make it work without a full landscape replacement.
First domain selected based on highest pain × lowest disruption. Migrate process to S/4HANA Cloud (PCE if private cloud needed, public if not), activate base Joule for that domain, integrate via BTP back to ECC for the remaining landscape. Customer sees AI value in 4-6 months.
Sequenced through procurement, supply chain, or HR depending on customer priorities. Each phase activates Joule for that domain. The migrated portion of the landscape grows Joule-native; the un-migrated portion stays on ECC, integrated via BTP.
By the time the last domain migrates, the customer is mostly on S/4HANA, mostly on Joule, and the ECC sunset is a clean operational decision rather than a forced cliff. Total elapsed time: 18-24 months in three phases vs 24-36 months for big-bang.
BTP as the integration plane (non-negotiable). Hyperscaler-native services (Azure or GCP) for data, identity, AI extension. Clean-core S/4HANA — customizations live in BTP extensions, not in S/4 itself. Joule data access scoped per domain so AI doesn't cross-contaminate ungoverned data.
A starter set of LinkedIn posts you can publish in your own voice over the next 6-8 weeks. Each is designed to do two things at once: stake the Joule-Native Selective Transition position publicly so Forefront SAP starts owning it, and build Daniel's individual category profile in the Nordic SAP conversation. Edit freely.
Skeleton outline for a Joule-Native Selective Transition talk. The Poznan Joule talk Björn-Henrik already gave is the seed; this is the version positioned for a CFO/CIO audience at SAPSA, an industry event, or a customer roundtable. Forty-minute talk, 20 of those for Q&A.
The reason this position is defensible — and the reason it's an asset and not a marketing claim — is that Forefront has actual proof. Joule running in production. Multi-hyperscaler delivery (Azure migration of 70+ servers, GCP Partner of the Year for Sweden via the parent group). 20+ years of transformation depth across the wider Forefront ecosystem. The Joule-Native Selective Transition Method is a published interpretation of work the team is already doing. Other Nordic SIs would need 18-36 months to credibly claim this position. By the time they get there, Forefront should already own the category.