Key points
- Define mid-market from the offer and serviceable operating environment
- Map relevant responsibilities without fixed committee sizes or assumed authority
- Review contacts and coordinate next actions around one account plan
A useful mid-market decision-maker list connects a defined account use case with the people responsible for the affected work. Start with your team's serviceable account definition and the decision you want to understand.
There is no universal employee or revenue band that reveals a company's buying process. Titles help you discover candidates; actual responsibilities and account evidence determine which contacts belong in the plan.
Define mid-market for this campaign
Write down the company conditions that matter to implementation and commercial fit. These may include operating markets, industry, supported systems, location complexity or company scale.
If you use size or stored revenue bands, document why the boundary matters. It should reflect the offer and operating constraints rather than a claim that every company in the band buys in the same way.
| Discovery input | Useful purpose | Follow-up research |
|---|---|---|
| Employee-size band | Scope a candidate cohort | Relevant team, entity and operating footprint |
| Stored revenue band | Apply a documented company criterion | Source meaning, entity scope and commercial fit |
| Industry or company description | Find a plausible operating environment | The actual workflow your offer affects |
| Person or company location | Support the appropriate geographic constraint | Location of the work and decision responsibility |
Map the decision as tasks
Describe the problem owner, day-to-day users, evaluators and approval or purchasing responsibilities relevant to your offer. Some tasks may belong to one person; others may not matter for a particular account.
- Who owns the outcome the project would change?
- Who operates the affected process?
- Who needs to evaluate compatibility, security or implementation?
- Who can explain purchasing and approval requirements?
- Who coordinates the existing relationship with your company?
Do not force a fixed number of contacts or assume every VP is a budget owner. A founder, director or specialist can be relevant for a different part of the same decision.
The buying-group planning guide provides a wider account framework.
Search candidate responsibilities in separate passes
Use role titles, seniority and department criteria according to their documented meaning. Separate searches can help inspect which title variants produce useful candidates.
Retain qualifiers such as region, division and customer segment. “Director of Operations” at a subsidiary should not automatically become the group-wide operational sponsor.
Decision-maker contact discovery can support candidate research. It cannot establish private approval chains, current buying intent or a complete account organisation chart.
Review an illustrative operating change
Example: a provider offers scheduling software for service businesses with several operating locations.
| Question | Candidate to investigate | Evidence needed |
|---|---|---|
| Who owns scheduling outcomes? | Operations or service-delivery leader | Actual remit for the affected locations |
| Who understands the daily process? | Scheduling or local operating manager | Workflow context and practical constraints |
| Who evaluates system compatibility? | Relevant IT or systems responsibility | Involvement in this kind of change |
| Who explains approval requirements? | Project owner or appropriate purchasing contact | The company's actual process |
This is a research plan, not a prescribed committee. The investigation can show that one person covers several questions or that another function belongs in the discussion.
Preview scope before retrieving contacts
Free count preview measures matching contacts, not unique mid-market companies or approved buying-group members. Compare filter variants while preserving the campaign's actual fit requirements.
Retrieve a bounded set using applicable credits. Review account identity, person-company association and the responsibility hypothesis before extending the search.
Use the empty-segment diagnostic if a restrictive search returns little usable scope. Do not broaden criteria just to hit an invented minimum campaign size.
Create an accepted account handoff
Carry the researched account, relevant contact, supporting evidence, unresolved question and next action into the handoff. Include source context and the owner of further research or outreach.
Keep missing data separate from a rejected account. An absent email may call for another permitted route; an irrelevant responsibility calls for different research.
The contact-quality workflow helps separate identity, field availability and address checking.
Coordinate outreach around one account plan
Assign an owner who can see existing conversations and exclusions. Give each relevant person a reason connected to their work, without inventing internal problems or sending conflicting promises.
Review channel readiness, preferences, stopping conditions and the applicable requirements before activation. A provider record does not establish permission for every form of communication.
When a response reveals the actual decision process, update the responsibility map. Use referrals and factual answers as evidence rather than treating the original title-based hypothesis as fixed.
Evaluate the list by decisions it supports
Track accepted account fit, supported responsibilities, unresolved gaps, relevant responses and research effort. Distinguish booked meetings from qualified opportunities and later commercial outcomes.
A useful mid-market list lets the team explain who belongs in the conversation and what remains unknown. Expand the cohort when that evidence and the team's capacity support the next step.



