An account targeting strategy decides which companies your team will pursue, which it will exclude, and how much attention each eligible group can receive. Define the serviceable account universe and exclusion conditions before messaging rules; then reserve research for uncertain fit and allocate sales capacity among eligible accounts.
Define the Account Universe Your Team Can Serve
“We will learn who fits by talking to the market.” That is a reasonable objection to defining exclusions early. Conversations can reveal a use case your existing customers never raised. But you still need to distinguish a question worth investigating from a constraint your current offer cannot satisfy.
Product fit and market constraints
What can you actually deliver today? Start with that business. You'll need to name the product, the problem it addresses, the buying entity, and the markets your delivery model supports. You'll want to decide whether this strategy concerns new customers, expansion within existing customers, or a particular product entering a new segment. Without that scope, two colleagues can approve the same company for entirely different reasons.
A useful account universe is broader than this quarter's active sales workload. It contains companies that could plausibly be served under the defined offer. The active portfolio is the subset you're able to pursue now. Keeping those concepts separate lets you defer a suitable account without declaring that it is a bad customer.
Geography shows why the distinction matters. Stripe's availability page separates supported merchant countries from the worldwide customers those merchants can sell to. A business's need to collect global payments does not, by itself, establish an available direct onboarding route for its location. That is a product availability question before it is a messaging question.
Targeting strategy versus building the list
Demandbase describes targeting as selecting and prioritizing accounts, with personalized ABM following that selection. Your strategy therefore needs to explain what belongs in the portfolio and why. Building the target account list is the later work of finding and checking records against that policy. Account mapping then examines relationships inside a selected company; outreach develops an approach to its people.
You can research accounts in OKKI Go while developing the policy. Keep the policy decision in your planning notes: which business problem, delivery constraint and commercial objective make this company worth considering? You can use a populated company record as material for that judgment, not the judgment itself.
Specify Inclusion and Exclusion Criteria Separately
“Our fit score already handles that.” It may handle preferences well. The harder question is whether it distinguishes a preference from a condition that makes your present offer unsuitable. Those deserve different consequences. Ask your team to explain which rules reduce priority and which rules stop pursuit.
Positive fit indicators
You can define inclusion around observable reasons to consider an account: the problem you solve, a compatible operating environment, a plausible purchasing route and enough potential value to justify the proposed sales effort. You'll need to choose the evidence you'll need for each reason. A company description may suggest a relevant use case while leaving procurement or implementation requirements unresolved.
Can you separate interest from suitability? You'll want to see both before approving pursuit. HubSpot documents distinct company fit and engagement scores, as well as a combined score. That separation is useful for your policy: activity can help determine attention, but it doesn't explain whether you can deliver the requested product. You'll want to inspect both dimensions before letting a total score stand for eligibility.
Your inclusion criteria should also identify the unit being assessed. A subsidiary buying independently may need a different assessment from its parent. Record whether the policy concerns the contracting entity, a business unit or the corporate group. Otherwise, a parent's apparent fit can quietly substitute for facts about the actual purchase. This is a proposed planning rule, not a claim about automatic entity resolution in a particular tool.
Conditions that rule an account out
You need independent exclusions: an unsupported delivery location, a required capability the offer lacks, or a purchasing condition the business has decided it cannot meet. Can you explain the scope and the reason? Be precise. “Not enterprise” is too vague if the actual issue is an implementation requirement; “small company” says little if the real constraint is the economics of a specific service package.
HubSpot's scoring documentation provides an instructive distinction: exclusion lists can remove selected records from scoring. That is different from assigning fewer points. It is also only a scoring control; don't assume it automatically suppresses every campaign or sales action. Your targeting policy must say how a disqualifier affects the actual sales portfolio.
When a positive indicator and a hard exclusion conflict, apply the hard exclusion for that offer unless an authorized exception changes the underlying constraint. Strong engagement cannot create a missing capability. A soft preference can be outweighed; a condition necessary for delivery needs resolution. Keep “excluded,” “deferred for capacity” and “unresolved” as different decisions.
Balance Coverage Against Sales Capacity
“Strict exclusions will make us miss the next valuable segment.” Here the objection wins a round: missing evidence is not evidence of incompatibility. A policy that rejects every unknown will prevent the learning that could justify a new market. Give that uncertainty a bounded research route.
Borderline accounts and strategic exceptions
You can reserve a research allocation for plausible accounts outside the established pattern. You'll want to give that work a question to answer, such as whether the purchasing unit can use the existing implementation model. Keep it separate from the committed sales portfolio. A research exception authorizes learning; it does not authorize a salesperson to promise an unsupported feature.
How much attention can you promise? Budget the eligible portfolio. Demandbase's published tier model distinguishes individual-account treatment, small-group treatment and broader treatment of accounts that still fit the ICP. You'll want to treat tiers as different commitments of effort. A prestigious logo should not become a top-tier account unless someone can provide the corresponding attention.
For your own capacity estimate, multiply the number of accounts in each tier by the planned time per account over the same period. Add shared campaign work and a reserve for follow-up, existing opportunities and research. You can compare that total with the team's available time. These are planning inputs to supply from your operation, not industry benchmark numbers.
If the plan doesn't fit, reduce the active portfolio, reduce the promised treatment, or add real capacity. Don't quietly assign an individual-account sales motion to everyone and hope automation closes the gap. Eligible accounts can wait for a later review without being removed from the serviceable universe.
When the available data cannot settle fit
You can make uncertainty visible by naming the missing fact. “Procurement route unknown” gives research a task. “Low fit” conceals whether the evidence is negative, absent or simply old. Attach a review date and decide how much effort the unresolved question merits before it consumes more sales time.
Demandbase reports revisiting its own target list quarterly. That is a documented practice, not proof that every team should use the same cadence. You'll want to choose a regular review suitable for your sales cycle, and allow an earlier review when product availability, account structure or a relevant delivery constraint changes.
The compromise is deliberate: stable exclusions for known constraints, a limited route for uncertain opportunities, and a portfolio that fits the attention available. You preserve the ability to learn without treating every attractive account as an immediate sales commitment.
Approve the Targeting Policy Before Personalizing Outreach
“Why not write the messages now and settle these questions later?” You can explore wording early. What you shouldn't approve is a campaign whose audience assumes answers the business has not agreed to. The audience promise and the product promise need to describe the same offer.
Record why an account belongs or does not belong
Stripe supplies a concrete test of that rule. Its page says that merchants in supported countries can sell to customers worldwide, while the notice for businesses outside supported regions says Payments is not yet supported there. Global customer reach therefore does not erase merchant eligibility conditions. This is a published product boundary, not a hypothetical rejected customer.
The page also offers other routes, including Atlas. That is a reason to investigate the relevant route, not to assume the original direct Payments offer applies unchanged. Your account policy should distinguish an eligible route, a route requiring separate assessment, and an offer that cannot currently be delivered. The inference is narrow: need and enthusiasm cannot substitute for the particular eligibility fact.
You can approve a short targeting policy with the following content before launching the outreach program:
- Offer and objective: the product, buying entity and commercial purpose this policy covers.
- Account universe: required fit evidence and the markets or operating conditions you can serve.
- Exclusions: disqualifying conditions, their scope, and who can approve a justified exception.
- Capacity: the active tiers, treatment promised, deferred accounts and research allocation.
- Review: the missing facts, review triggers and evidence needed to change an account’s status.
Sales should accept the workload; product or delivery should confirm the constraints; marketing should understand which audience is authorized. A policy disagreement should remain visible until those responsible resolve it. Personalization can then address the needs of a defined audience instead of making eligibility decisions by implication.
You'll want to review performance by the cohorts the policy actually created. Track eligible-to-active coverage, progression into qualified opportunities, and reasons accounts are excluded or deferred. Examine research accounts separately so their uncertain fit does not disappear inside the main portfolio. These are suggested measures for evaluating your choices, not promised improvements.
You don't need perfect market knowledge before outreach. You'll still need a defensible account universe, an honest treatment of unknowns and a sales commitment your team can deliver. That is where the skeptic and the planner can agree: learn from the market, while being explicit about which offer you are able to deliver.
Frequently asked questions
How is account targeting different from building a target account list?
Targeting sets the policy: which companies qualify, which conditions exclude them and how eligible accounts receive attention. List building finds and checks company records against that policy. Messaging and relationship mapping use the selected accounts for different, later tasks.
What should happen when an account meets both inclusion and exclusion criteria?
Apply a hard exclusion to the relevant offer unless an approved exception resolves its underlying constraint. Treat soft preferences differently. If evidence is missing, mark the case unresolved and define the research needed; do not automatically classify uncertainty as disqualification.
How many accounts should a sales team target at once?
Use the attention available over a defined period and the treatment promised to each tier. Budget account work, shared programs, existing opportunities and follow-up. Keep eligible accounts outside the active portfolio when capacity is unavailable, and review them later rather than labeling them unsuitable.
