How Installed Base Marketing Boosts B2B Success
Marketing Strategy · Published 2026-10-12
Installed base marketing works when you run it as a targeted campaign against a defined list of existing accounts. Treat it as account-based marketing aimed inward. The accounts already using your product have cleared the hardest part of a buying decision, which is trust in the vendor, so the campaign built for them should look like ABM with a warmer start, with a named owner, a segmented list and a weekly cadence.
Most programmes stall before they start because nobody owns the list. Customer success owns the relationship, sales owns the renewal, and marketing owns no account in particular, so the expansion opportunity sits in a CRM field that nobody campaigns against. Fixing that starts with treating the installed base the way a full-funnel demand generation programme treats a target account list: segmented, prioritised and worked in sequence.
Why installed base marketing needs its own campaign
New-logo campaigns answer one question: does this account have the problem at all. An installed base account answered that when it signed the first contract. The questions that matter now are narrower. Is there a second problem the same product solves? Is there a second team in the account that has not adopted it? Does the usage pattern show the account is ready to expand?
Running acquisition messaging at an existing customer wastes the one advantage you hold there, which is that nobody needs convincing the category is real. A new-logo campaign leads with the problem. An installed base campaign can lead with what the account already gets, and what a second team or use case would add.
Build the list from usage, structure and health
Three checks decide whether an account belongs on an active expansion list. Run all three before any campaign touch goes out.
- Usage signal. An account running at or near capacity, or across more seats or workflows than it was sold on, is pulling for more. That beats tenure: a five-year account that never grew its usage is less ready than a six-month account pressing against its plan ceiling.
- Account structure. If the team that signed the original deal is one team inside a larger organisation, the rest of the company is a new-logo motion running inside an existing contract. It needs the same call you would make for a new target list, covered in when to run ABM and when to run broad demand generation: a few high-value accounts with several buyers justify individual treatment, and many smaller single-buyer accounts suit a lighter campaign.
- Health. Open support tickets, a departed champion or flat usage rule an account out of expansion, however long it has been a customer. Campaigning into an unhappy account turns curiosity into complaint.
An account that passes on usage and structure but fails on health moves to a retention motion first. Expansion messaging sent to an unhappy account is how installed base marketing gets its tone-deaf reputation.
A rulebook for routing each account
The list is only useful if every account lands in exactly one motion. A simple rulebook keeps the weekly review short.
- Health flag open: retention owner acts, marketing pauses all sends to the account.
- Usage above 80 percent of plan for two consecutive months: upgrade note from the account owner, with marketing supplying the usage-specific copy.
- New domain or department appearing in product logs: second-team campaign, mapped as a fresh buying committee.
- Champion changed in the last 30 days: re-introduction sequence, written as if the new contact never saw the original sale.
- Renewal inside 120 days with no expansion conversation logged: flag to the account owner, because after that point the talk is only about the renewal price.
- None of the above: stay on a light content cadence and review again next month.
The 80 percent threshold above is a starting placeholder. Set your own from the point where accounts in your product tend to hit friction.
What the campaign contains
An installed base campaign has three parts, run together.
The first is account-specific messaging built from the usage data. A note that names the workflow an account already runs reads as attentive. A note that could have gone to any customer reads as automated, and gets treated that way.
The second is a handoff between the campaign owner and the account owner, usually customer success or an account manager. Agree it before the first send. A campaign that produces interest while no rep knows it is running sends the reply to an inbox nobody is watching.
The third is its own measurement. Expansion revenue, net revenue retention on the touched accounts and the usage change that followed are the numbers that show the programme works. Blending expansion pipeline into the new-logo report hides whether either motion is functioning.
Timing the first touch
Fire the first expansion touch from a trigger, not a date. An account that hit its usage ceiling in month four is ready in month four. Waiting for the renewal cycle to prompt a check-in leaves a ready account untouched for months while a less ready one receives the same generic outreach on schedule. Log the trigger that fired next to every send, so the next review can show which triggers led to conversations and which led to silence.
Where installed base programmes go wrong
Four failure modes show up repeatedly in these programmes.
- Calendar-driven sends. An anniversary email fires on schedule whether or not the account has done anything. A usage threshold crossed or a new team added is a better trigger because it describes something that happened.
- One message for the whole list. Batch-and-blast performs the same on customers as on prospects. Low relevance in, low response out.
- Marketing sends, nobody follows up. The email exists to start a conversation. If customer success does not book the call, the reply goes cold and the account learns that responding does nothing.
- Expansion pipeline mixed with new-logo pipeline. The blended number looks healthy while one motion carries the other.
A worked example, with made-up numbers
Take a hypothetical software vendor with 400 customer accounts. A review of product data flags 60 above the usage threshold. Health checks remove 14 of them, and account structure shows 21 of the remaining 46 are single-team deployments with an untouched second department. That gives two lists: 25 accounts for an upgrade note and 21 for a second-team campaign, each with a different message and a different owner.
Nothing in this example is a result. It shows the shape of the work: a list of 400 becomes two lists totalling 46 in one review, and the 14 removed accounts avoid an expansion send they would have disliked.
What this replaces
Most of what gets called installed base marketing today is a quarterly newsletter and a renewal reminder. The newsletter has no target account logic behind it, and the reminder defends revenue you already have. A real programme looks like any other full-funnel campaign aimed at a specific list, and the list happens to be the accounts that already trust you. For the wider structure this sits inside, read the full-funnel demand generation framework.
To see how account tiering, usage-based targeting and campaign sequencing fit together, open the B2BinDemand library.