Account-based LinkedIn prospecting: map the decision before outreach

Account-based prospecting on LinkedIn starts with a company you have a reason to pursue and the decision you want to understand. It does not mean collecting as many employees as possible and putting them into the same sequence.

Build a working picture of who experiences the problem, who evaluates a solution and who can authorize the change. Treat the first version as a hypothesis. Use public information and conversations to improve it, coordinate contact across your team and keep unresolved responsibilities visible.

Start with the decision inside one account

Suppose you sell software that changes how a service company approves completed work before invoicing. The operations team may experience the delay, finance may care about the billing process, and IT may need to assess access and integration. These are possible responsibilities in an illustrative example, not a standard committee you can infer at every company.

Write the decision in operational language: “Would this account benefit from changing how completed jobs reach billing, and who would need to participate in that change?” That question is more useful than “How do we reach the CFO?” because it leaves room for the actual process to differ from your assumptions.

Choose the account for a defensible reason. Record the relevant business conditions, the source that supports them, the kind of work your product can handle and the conditions that would make the account a poor fit. Otherwise an attractive logo can absorb research and outreach effort without a plausible buying situation.

Create a map of responsibilities, not a collection of titles

Use a simple table before you add names:

One person can hold several responsibilities. Several people can share one. “Director” or “VP” is not enough to fill the approval column, and a missing name is more honest than an invented decision maker.

LinkedIn's multithreading guidance discusses building relationships across an account rather than relying on a single contact. For your process, the reason to add a relationship should be a question that person can help answer, not a contact-count target.

Find plausible people and mark your confidence

If you use Sales Navigator, an account list can hold the target companies while you search for relevant roles. Its filter definitions describe current company, title, function, seniority and account-list filters. Review the results rather than treating the combination as verified authority.

For each potential contact, record the profile, apparent remit, source, review date and confidence. Use plain labels such as “public title suggests,” “confirmed by contact” or “unknown.” Do not allow a score to hide the difference between a public inference and something the buyer told you.

The OutreachGenie company employee finder can help collect accessible profiles associated with a company. The buying-group mapper can organize user-supplied records against chosen roles. Neither should be treated as proof of the company's reporting lines or purchasing authority.

LinkedIn also offers its own Relationship Map within Sales Navigator. Check current plan availability and what information the product actually provides before selecting it as your account-mapping tool.

Choose one opening that can improve the map

An initial contact should have a plausible connection to the problem and a reasonable question to answer. You do not need to present the full proposal or ask for introductions to an entire committee.

For the illustrative billing workflow:

Hi [name], your role appears connected to service operations at [company]. We work on the handoff between completed jobs and billing. Is that handoff owned by your team, or does another group coordinate it?

If the person is not the owner, they can correct your map. If they are, the next conversation can establish whether the process needs attention. Do not interpret a helpful routing reply as sales interest.

Once there is a substantive conversation, explain why another stakeholder may need to be involved:

You mentioned that any change would need finance to confirm the approval rules. Would it help to include the person who owns those rules in the next discussion, or would you prefer to check internally first?

This lets the buyer shape the process. Contacting a colleague secretly to get around an unfavorable answer is a different behavior from involving a necessary participant.

Coordinate before a second sender acts

Account work creates a team problem: two sellers can each send a reasonable message that becomes unreasonable when the buyer receives both. Decide who owns the account conversation and how others check its status before contacting another employee.

Keep an account-level note with the current question, active contacts, commitments, next date and contact restrictions. A person-level opt-out must be respected. A broader instruction from the organization should be reviewed for its actual scope; do not automatically treat it as a personal objection to be bypassed through another employee.

Before adding a new contact, ask what uncertainty the conversation should resolve and whether an existing contact can help route it appropriately. Do not enroll the whole map into parallel campaigns merely because the tool can store the profiles.

Give each stakeholder the evidence relevant to their decision

The operational owner may need a workflow example. A technical evaluator may need actual integration and access information. A commercial approver may need scope, cost assumptions and implementation responsibility. Sending each person a slightly reworded version of the same general pitch does not address those different questions.

Keep the evidence consistent. If one person is told a feature is available and another is told it is on the roadmap, the account will eventually discover the discrepancy. Mark product limitations and decisions still open in a shared record.

If the buyer identifies a requirement you cannot meet, update the opportunity rather than looking for someone who might overlook it. The purpose of mapping the decision is to understand whether the offer fits, including when it does not.

Measure the quality of account progress

Useful progress includes confirming the process owner, discovering a necessary evaluator, identifying an implementation dependency or agreeing that the project is not appropriate. Counting new contacts alone misses these outcomes.

Use an account review with a few concrete questions:

• Is the original business problem still supported by evidence?
• Which responsibilities are confirmed, inferred or unknown?
• What decision is the buyer currently making, and what information is missing?
• What has your team promised, and who owns each next action?
• Is further contact appropriate under the responses already received?

An account can contain many LinkedIn connections and no qualified opportunity. It can also contain one useful conversation that reveals exactly why the project should stop. Preserve both kinds of evidence.

For outreach execution, use the relationship-sequence guide and current campaign controls to keep later actions consistent with the conversation. LinkedIn's automated-activity policy applies regardless of how carefully an account has been mapped.