Nordic SAP doesn't buy on a champion — it buys on a coalition. CFO, CIO, Enterprise Architect, Process Owner. Each cares about something different, each can kill the deal silently if missed. Below: how to talk to each of them, what to avoid, the question that opens the door, and how to hand off cleanly between personas inside the same account.
The research on Nordic SAP buying is consistent: deals close on a coalition, not a champion. The CFO needs the cost case, the CIO owns platform fit, the Enterprise Architect signs the migration risk, and the Process Owner has to believe operations get simpler. A great cold email to the CIO is operationally worthless if the other three aren't aligned. So this playbook is built for landing two-to-three personas concurrently in the same account, then quarterbacking them toward a shared decision.
Increasing scrutiny on SAP spend. Worried about migration cost overruns, support-cost cliff post-2027, and being sold a cloud bill they can't predict. Wants timing certainty more than speed.
"We're not budgeting for this until 2027." Reframe: the question isn't budget timing, it's risk timing. Phase Zero is consulting — opex, not capex — and de-risks the 2027 capex case by quantifying it. Most Nordic CFOs we work with would rather spend a small opex amount in 2026 to walk into the 2027 budget cycle with a defended number than walk in cold.
"I'd love your CIO in this room — most of these conversations end up needing the platform-fit perspective alongside the financial one. Want me to pull them in for the next session, or would you prefer I open that thread separately?"
Owns the 2027 deadline. Stuck between rigid Big-Four proposals (expensive, slow) and tiny boutique offers (limited, risky). Wants a partner who'll de-risk the platform without owning their team. Increasingly responsible for the AI strategy, often without budget for it.
"We already have an SI." Don't compete. Position the Stuck-Program Diagnostic — a free audit on whether the current program is on-track, conducted by the only consultancy in the Nordics that's both AI-first in production AND multi-hyperscaler. Most CIOs say yes because the audit costs them nothing and gives them a second-opinion artifact for their board.
"Before we go further on the platform fit, I'd want your Enterprise Architect in the next conversation — they'll have the integration questions I can't answer at this level. Who would that be?"
Has to translate ECC migration into a feasible roadmap. Cares about integration debt, master data, and standardization vs customization debate. Often the most technical voice — and the one most likely to kill a deal silently if the architecture story doesn't hold up.
"You don't know our landscape well enough to have a view." Agree. That's exactly the point of the Stalled-Program Audit — a 90-minute walkthrough where they show us, not the other way around. We listen, ask the architectural questions Big Four won't, and write up what we heard. No pitch.
"This conversation is going to need someone from the business side — not because we're missing technical depth, but because the customization decisions you're describing have business-process roots. Who's the operations or supply chain voice we should pull in?"
Their team uses SAP every day. They're terrified of disruption to close cycles, plant operations, or supply chain visibility. They've usually been burned by a big SAP project before. They have veto power but rarely use it openly — they kill deals through quiet inertia and absent stakeholders in critical workshops.
Silence and non-attendance. Most dangerous Process Owner objection isn't a "no" — it's a missed workshop. Counter by asking the CIO or sponsor to designate one Process Owner as a named participant with explicit accountability. If they won't, the deal is already in trouble — surface it now, not at signing.
"The operational savings we're describing here — the reduced manual work, the faster close — are usually the line items the CFO wants quantified for the business case. Want to loop them back in for the next conversation?"
A starter sequence designed to get two coalition members into a conversation within 21 days, then triangulate to the others. Run it concurrently against the persona pair you have the strongest data on per account (CFO+CIO is the highest-leverage starting pair for most Nordic SAP accounts). Ignite Studio's reply-handling principles apply — every doc in the sequence either earns a meeting or qualifies the account out.