ABM case study: how Backbase built an AI-native ABM motion
Backbase has 3,000 addressable accounts worldwide and an 18-24 month sales cycle.
Backbase CMO Tim Rutten took the seat in 2025 knowing the lead-volume playbook wouldn't work. What he built instead: a full-funnel, AI-native ABM motion that started with a single US pilot, generated six enterprise discovery calls, and triggered his CEO to ask one question: how fast can every region run this way?
Backbase built an AI-native ABM motion by reorganizing marketing around strategic accounts rather than channels, running a small-scope pilot in a single region to prove the model, and using a five-stage account velocity framework to track pipeline contribution. The motion required tight sales-marketing alignment across six regions and a deliberate choice about what to automate versus what to keep human. The pilot produced six enterprise discovery calls and created internal demand from other regional teams to replicate the approach.
Why a narrow TAM forces different thinking
Backbase sells an AI-native banking operating system to mid-to-large banks globally: retail, commercial, private banking, and wealth management institutions modernizing their full operations. The product is strong. The market is not wide.
When the number of possible accounts worldwide fits on a long spreadsheet, every coverage decision matters. Broad content programs, paid traffic optimized for volume, and field marketing that chases event attendance all look different when you have 3,000 accounts and need meaningful relationships across all of them.
The marketing function Tim inherited was built the way most enterprise marketing functions are built. Brand had its KPIs. Content had its KPIs. Digital and field each had their own interpretation of what ABM meant and their own view on how marketing should work. The result was a collection of well-run sub-functions with no coherent view of the account.
Tim wanted one system: brand, demand, sales, and client success unified around strategic accounts, with every region running the same motion and reporting the same way.
The pilot design
Rather than rolling out globally and hoping each region would adapt, Tim and the team at Fullfunnel started with a tight scope: the US wealth management team. The logic was straightforward.
Backbase had strong presence and credibility in Europe. In the US, particularly in wealth management, they were building recognition from scratch. The US team was relatively small, was already building a new sales motion, and had the kind of people who would become amplifiers if the pilot worked.
The full pilot design rested on five decisions.
Pick the right person to lead it. The ABM lead is a program driver, not a campaign manager. As Tim describes this role: "You know the type of talent that will pull through, will unblock it, will give you the right phone call at the right moment in time to make progress. Critical." Without someone whose job is to push the motion forward and remove friction, the program stalls between functions.
Pick the right region. The US wealth management team had the right sales talent in place and was already building a new motion, which meant ABM could integrate rather than interrupt. Tim knew that if the pilot worked, those people would carry the model into other regions organically.
Build the right cross-functional team. Tim's selection process was deliberate: identify who is needed at each stage of the account flow and ask them directly. ABM programs fail most often not because the strategy is wrong but because the wrong people are accountable at the wrong stages.
Align on a shared account list. In most organizations, sales and marketing disagree on which accounts matter. One of the first artifacts the team produced was a jointly owned account list that both functions had signed off on. This sounds simple; it is not common.
Define progress with a stage-based framework. The team implemented a five-stage account velocity model to measure ABM progress and pipeline contribution at each stage. This gave the CMO, the regional VP, and the sales team a shared language for where each account stood, not just whether pipeline had been created.
What the AI-native operating system actually does
The phrase "AI-native" is doing a lot of work in B2B marketing right now, and most of it is padding. In Backbase's case, Tim was already building a GTM AI system before the ABM motion started. The pilot had to integrate into that system rather than run alongside it.
The relevant question for any operator building a similar motion is not "what did we automate?" but "what did we keep human, and why?"
From what the Backbase case shows, the human layer stayed on three things: account selection judgment, cross-functional relationship management, and any communication that required reading an individual stakeholder's situation at a specific bank. These are judgment calls that require context accumulation over 18 months. Automating them produces noise, not pipeline.
The AI layer handled research aggregation, account signal monitoring, content personalization at scale, and reporting. Across a 3,000-account TAM with six global regions, manual execution of those four functions would consume more headcount than most B2B marketing teams have.
Human judgment stays at the relationship layer; AI handles data and personalization. The distinction matters operationally: the first category requires 18 months of context accumulation; the second doesn't.
What the pilot produced
Six discovery calls with enterprise wealth management accounts. On its own, that number could mean anything. What matters is the downstream effect: internal demand from other regional teams to run the same motion.
When Tim described the CEO's reaction, he quoted the exact question the pilot triggered: "How fast can all of my teams, all of my regions, all of our territories work this way, report this way, and basically play the game this way?"
That question is the actual outcome, not the six calls. The pilot created a proof of concept credible enough that the top of the organization wants it everywhere — that is organizational change driven by evidence, not a successful campaign.
What B2B founders and marketing leaders can take from this
Some of this is specific to Backbase — narrow TAM, fintech, long enterprise cycles. Several patterns apply broadly.
The pilot-to-scale structure works. Starting with one region, one product line, or one segment and building internal demand is more reliable than building a global program that depends on every region buying in before there is evidence. The Backbase pilot worked partly because the US team knew their success would be visible to peers in other regions.
Shared account lists are not a given. The fact that sales and marketing separately owning account selection is still common in 2025 enterprise companies explains a lot of ABM program failure. Getting joint ownership of the account list before you build anything else removes one of the most persistent failure modes.
Reporting language has to be the same across functions. The five-stage account velocity framework is not just a measurement tool. It is a shared language that lets a CMO, a regional VP, and a frontline sales rep describe the same account's progress without translation. When functions report differently, leadership has to manually reconcile views, which means they stop doing it, and the program loses executive attention.
The ABM lead role is distinct from campaign management. Operators who assign ABM responsibility to an existing campaign manager and expect the same output are building for disappointment. The skills are different. Program driving requires cross-functional authority, tolerance for ambiguity, and the ability to escalate and unblock without creating organizational friction.
The harder point about LinkedIn's role in ABM
For founders with a narrow TAM and a long sales cycle, every post that reaches a decision-maker at a target account does pre-pipeline work that no BDR sequence can replicate — it arrives through their own network feed, not a vendor-initiated channel. The operators we work with consistently find inbound signals from LinkedIn reaching the same accounts their ABM motion is targeting. Treating LinkedIn as separate from ABM leaves one of the cheaper awareness tools unused.
If you want to see how other founders are building LinkedIn presence to support exactly this kind of tight-account motion, the patterns we track across top LinkedIn creators and the inbound signals they generate are worth comparing to your own account list.
Frequently asked
An AI-native ABM motion uses AI for research aggregation, account signal monitoring, personalization at scale, and reporting, while keeping human judgment at the relationship and account selection layer. Traditional ABM typically relies on manual research and segment-level personalization. The distinction matters because at a TAM of 3,000 accounts across six global regions, manual execution of data and personalization tasks is operationally unsustainable. An AI-native system is designed from the start with AI handling high-volume, lower-judgment work. Retrofitting AI onto a manual process leaves the structural bottlenecks in place.
