At a glance
If your ABM programme is active but accounts are not moving, find the first point where useful progress stops. These seven checks cover account selection, workload, messaging, buying-group gaps, channel coordination, lead handover and measurement. Choose one repair, give it an owner and agree what evidence would show it helped.
The campaign is running. People are downloading the content, the account list is getting attention and the dashboard has plenty to report. Yet the sales conversation still ends with the same question: what should we do differently next month?
Adding another channel is one answer, but it is an expensive way to investigate a problem you have not identified. Start with a few accounts you expected to progress. Look at what actually happened, where the next step stalled and whether the same obstacle appears elsewhere.
This guide is for improving an existing programme. If you are still deciding how to organise ABM, our ABM strategy guide covers the initial planning decisions.
1. Are the accounts still worth this level of attention?
An account can remain a good fit for your product while becoming a poor use of this month’s campaign effort. Its relevant initiative may have paused, the owner may have changed or your team may have lost its route to the people involved.
Take the original reason for selecting the account into the review. Which part is still supported? Which part was an assumption? If the reason has changed, decide whether the account needs research, lighter nurture or a pause.
Our account-prioritisation approach brings commercial fit, evidence and delivery feasibility together. The useful output is a reason to keep, change or defer the work. A high score without that explanation leaves the team guessing.
2. Can the team deliver the treatment each tier promises?
A tier is only useful if it changes the work. Ask an account owner to describe the research, content and follow-up planned for one account in each tier. Then compare that with the time the team actually has.
If every account needs bespoke preparation, your supposedly scalable programme has an individual workload. Either reduce the number receiving that treatment, reuse more of the work or fund the capacity it needs. Quietly dropping the research while keeping the same promise will make the programme harder to explain.
Shared work makes sense when accounts face a sufficiently similar problem. Keep the parts that genuinely differ visible, so the team knows when an account needs more attention.
3. Does the message help with a recognisable decision?
Read the invitation without the company name or job title. Does it still explain something the intended reader needs to understand, assess or change? Personalisation fields cannot rescue an unclear offer.
For example, a generic invitation to “explore transformation” leaves a lot of work to the reader. An invitation to compare who owns the handover between regional teams gives the conversation a more specific purpose, if that responsibility is relevant to the account.
Check the evidence for that relevance before writing as though you know the buyer’s situation. A public announcement can give you a sensible question to investigate without proving that the company has the problem you sell against.
4. Whose unanswered question is holding things up?
Several contacts in the same account can still leave a critical gap. You may have an enthusiastic user and a supportive manager, while nobody has addressed the technical team’s implementation concerns.
Ask the account owner what the next decision requires and who needs to be comfortable with it. That could mean finding another stakeholder, but it could also mean helping an existing contact explain the proposal internally.
Do not assume silence means opposition. Mark the missing view as unknown and agree a suitable way to learn more. Our buying-group coverage guide helps distinguish finding people from understanding their part in the decision.
5. Does the next interaction follow naturally?
Look at the sequence from the buyer’s side. An advert introduces a planning issue, a guide helps examine it, and then a salesperson asks for a product demonstration without referring to either. All three activities happened, but the connection is weak.
Before adding another touchpoint, write the reason someone would welcome it. What useful question does it answer after the previous interaction? Who will deliver it, and will they know what the person has already seen?
Our experience-planning methodology connects the desired change with the interaction and follow-up. You can apply that thinking to a simple content sequence as well as a larger experience. Sometimes the best repair is a clearer follow-up, rather than another channel.
6. Can the receiving person use the response?
Pick a recent lead and ask the receiving colleague what they understood from it. Could they see the relevant account, what the person did and why that mattered? Did they own the next action, or assume somebody else would take it?
A valid content response can need nurture. A direct request to talk needs a different response. Neither is helped by a handover that hides the original interaction behind a qualification label.
If the record met the delivery brief but went to the wrong owner, fix the routing. If the brief never asked for information needed to choose the next step, revise the brief. Tightening targeting will not solve either problem on its own.
7. Does the report tell you what to do next?
Separate delivery, engagement and commercial progress. Reaching an account, holding a conversation, starting a pilot and winning a contract are useful but different events. Your report should make the latest supported step clear.
For each important account, ask what changed, what evidence supports it and what remains unresolved. If the answer is simply “engagement increased”, look at the underlying interactions before assigning more budget.
Our ABM measurement guide goes into the reporting detail. Here, the test is whether the report leaves someone with a justified action. Another chart is unlikely to help if nobody owns the existing exceptions.
Choose one repair for the next review
These are diagnostic questions, so you do not need to turn every answer into a new project. Choose the earliest obstacle that prevents the next useful action, then check whether resolving it changes what happens.
| What you find | A sensible first repair | What to review next |
|---|---|---|
| Suitable responses have no clear owner | Agree routing and acknowledgement with the receiving team | Whether the next comparable responses reach an owner and receive the intended follow-up |
| A technical question repeatedly delays evaluation | Prepare the relevant explanation with the technical team | Whether the buyer can assess it and identify any remaining concerns |
| The same research work is rebuilt for similar accounts | Identify a shared component and document what still needs checking individually | Whether account owners can use it without losing the context they need |
These examples are starting points, not reported client outcomes. Agree the owner, change and review date before making the repair. If it does not help, revisit the explanation rather than treating the original diagnosis as settled.
If you would like help reviewing an existing programme, bring the account list, a recent report and a few examples of stalled follow-up. We can use those to discuss where an account-based programme needs attention before expanding the work.
