“Find ten relevant companies” and “find every relevant company” are different assignments. A system can finish the first while barely beginning the second.
Ten good results establish that ten good results were found. They say little about the size or shape of the missing market. If a sales leader uses that list to assign territories, estimate opportunity or decide a segment is too small, the difference matters.
Research needs to explain what finished: a requested shortlist, a bounded directory, or a search that stopped finding new candidates. Those outcomes deserve different language.
Start with the Boundary
A list of exhibitors in a particular event's official directory has a defined source and edition. Subject to the directory's own accuracy, the work can be checked against its entries and pagination.
“All regional manufacturers likely to need a new scheduling system” has no comparable boundary. Some companies have poor websites. Some do not describe the relevant operation publicly. Need may be private. Search engines and commercial databases expose different slices of the market.
Before research begins, ask what “all” can reasonably mean. It might mean every entry in a named directory, every match returned by specified sources under a documented query, or a broad search with explicit coverage limits. Do not let the answer switch between those meanings after the work is done.
For open-ended market discovery, a candid partial result is more useful than a confident but undefinable completeness claim.
Separate Finding from Qualifying
Imagine a synthetic research task covering three regional industry directories. The first lists 80 organizations, the second 50 and the third 40. After resolving overlap, the sources contain 120 distinct organizations.
Research has identified the directory population, not 120 qualified prospects. Suppose 45 meet the seller's criteria, 55 clearly do not, and 20 lack decisive evidence. The result should keep all three groups visible.
Now suppose only the first page of the third directory was read. The same 45 accepted prospects might still look useful, but the coverage claim has changed. The team has not completed the stated source set.
These are illustrative counts. Their purpose is to show why a result count cannot serve as a completion check. Qualified rows, excluded rows, unresolved rows and unread source material answer different questions.
Record the Work That Remains
Fama's development research implementation represents a plan as tasks with statuses and recorded activity. The inspected code distinguishes successful calls from failures and records continuation information such as additional pages or truncated results. The final answer format also carries unresolved parts of the plan.
Those mechanisms are useful because a source failure should remain a source failure. It should not turn into “no matching companies” merely because the agent has nothing to show.
They are not a proof that an entire market has been searched. Recording work accurately and defining the correct search space are separate problems. Even a perfectly completed plan can omit an important source or use a narrow query.
A useful completion note explains both: what the plan covered and whether the planned work actually finished.
Give “No Match” a Specific Meaning
There are several reasons a search produces no accepted prospect. The query may return nothing. The source may be unavailable. The candidates may all fail the criteria. The evidence may be too weak to decide. The process may have reached its time or cost limit.
Only one of those is a completed examination that found no qualifying entries within a defined scope. The others contain an unresolved question.
For a sales team, the next action depends on that distinction. Rewriting a query can help with terminology. A different source may help with missing coverage. A clearer brief may resolve ambiguous qualification. Waiting for the same unavailable source to return a result is a different operational decision again.
The output should name the reason without forcing the reader to inspect an execution log.
Treat Saturation as a Stopping Rule
Repeated searches that stop producing new candidates can be a reasonable reason to stop spending. They do not prove that no more candidates exist.
Search saturation depends on the routes used. Ten queries that all rely on the same directory can exhaust that directory while missing a different part of the market. A new regional term or industry association can reveal a separate cluster.
Before stopping, review source diversity and the distribution of results. If almost every account comes from one country or one familiar vocabulary, the missing regions deserve an explicit note. If the brief only asked for an initial shortlist, further exploration may have little value and should not continue indefinitely.
The stopping rule should fit the business decision. An exploratory campaign does not need the same coverage as a territory-allocation exercise.
Report Coverage in Words the Team Can Use
A useful report for the directory example might say:
Reviewed the complete published entries in two directories and the first available page of a third. Found 45 qualifying organizations across the material reviewed. Twenty candidates still need evidence. Additional entries in the third directory remain unreviewed, so this is not a complete list for the requested source set.
The statement is longer than “45 companies found,” but it protects the next decision. The team can use the verified subset for a bounded task while assigning the unfinished research separately.
For an open-web search, describe the regions, source types, key exclusions and remaining gaps. Avoid a percentage-complete figure when the total population is unknown.
A sales team should know whether it received a useful starting point or a defensible account of the search space. Those are both valuable deliverables. They deserve distinct labels.