The right research depth is the one that resolves the decision your team cannot already make. StackShortlist basic Stack leads already include fit scores. The practical choice behind the phrase basic versus scored leads is therefore how much additional company research and seller-specific interpretation you need. A general company brief helps explain unfamiliar businesses; offer-specific research connects their evidence to your own services.
More text does not automatically create more value. This guide compares levels of depth through a fictional account and an original reviewer decision log. It shows when a brief changes prioritization, when a score adds little, and when a general rubric cannot answer the seller's actual question.
What you’ll be able to do
- Choose depth according to the decision left unresolved by the basic list.
- A general company score summarizes a shared rubric; it does not establish buying intent.
- A company brief should explain evidence and unknowns, not merely expand a description.
- Offer-specific fit requires seller context and can differ for the same target account.
- Measure whether research changes a useful action before ordering more detail everywhere.
List the decisions a representative must make
Before comparing packages, write the decisions between receiving an account and choosing an appropriate next step. A representative may need to confirm identity, understand the business model, decide whether the service applies, choose an initial role, and prepare a relevant question. Some decisions require only structured fields; others need explanation.
Mark each decision as already supported, cheaply checked internally, or unresolved. If the team has deep knowledge of a narrow market, a general overview may repeat what it already knows. If the list contains unfamiliar hybrid companies, a short description may leave substantial work before anyone can route the account.
Distinguish a decision from curiosity. Knowing every product page is not necessarily useful if the campaign concerns one service line. Conversely, a single distinction between outsourced delivery and an in-house product can materially change the account's relevance. Research depth should follow those consequential distinctions.
Assign a user to each requested output. A manager may need sortable eligibility fields, while a representative needs a concise approach brief. Buying a long narrative for a decision that depends on one categorical field can create reading work without improving consistency.
Start with the campaign specification Identify required decisions before selecting the depth of the order.
Understand what basic lead data does well
A basic list gives the team an organized starting population with the company and contact information defined in the accepted scope. Its value is not that it explains every account. Its value is that the team can identify the business, understand why it was selected at the agreed level, and begin its own review.
Basic data can work well for a tightly defined service with straightforward eligibility. Suppose a fictional support firm serves one named platform and offers a standard configuration review. If platform evidence and account identity establish the necessary starting condition, a long general narrative may not change the first review action.
That does not eliminate verification. The team still needs to apply exclusions, inspect contact suitability, and choose a lawful, relevant approach. A completed new lead from StackShortlist requires a named founder or administrator with business email; it does not guarantee that the named person owns every possible buying decision.
Basic data becomes insufficient when the representative repeatedly opens the same kinds of pages to answer the same missing question. Record that question explicitly. It may justify one additional structured field, a general brief, or offer-specific research. Do not assume the only choices are no research and the longest available dossier.
Do not choose a deeper tier merely to obtain a score: basic Stack leads already include fit scores. Company intelligence adds research depth and company context, while Your-offer intelligence evaluates the relationship to the seller context. Review the meaning of each score and the accompanying evidence rather than assuming that a score first appears in the more detailed package.
What a general company brief should add
A useful general brief explains the company well enough for a reader unfamiliar with it to make a grounded account judgment. It can cover the advertised products and services, business model, stated audiences, visible customer evidence, operating context, and important uncertainties. The precise modules should match the accepted research scope.
The brief should distinguish observations from interpretations. A product page can show that the company advertises an integration service. It does not establish the quality of delivery, internal staffing, or willingness to change suppliers. A clear unknown can be more useful than a confident sentence based on indirect evidence.
A general score should have an understandable purpose. It might summarize completeness or a shared qualification rubric, but the buyer needs to know which criteria contribute and how missing information is treated. Without that explanation, a numerical score can create an appearance of precision without helping the user understand the account.
The brief earns its place when it reduces repeated reconstruction. A representative should be able to read the summary, follow a relevant source when necessary, and decide whether the company belongs in the next review queue. If the brief contains only a longer version of the homepage tagline, the added depth has not resolved much.
Choose depth with a decision table
The table below is an original selection tool, not a rule that every campaign must buy a particular package. Start in the left column with the missing decision. Then choose the smallest output that can support it reliably.
If several decisions are unresolved, separate them. A team might need general context for all accounts and seller-specific research only for a shortlisted subset. A staged scope can be ordered as two packages: the broader research first, then an own-list order for the shortlisted subset. The point is to make the reason for each research task visible.
Do not upgrade depth simply because the target account appears prestigious. A familiar large organization can still have an obvious fit decision, while a small hybrid business can require careful interpretation. Complexity comes from the relationship between the offer and the target, not from brand recognition alone.
Use an explicit stop condition for each task. If the research cannot establish a required fact publicly, the output should identify the unresolved question and the next appropriate validation step. A deeper package does not turn private information into a guaranteed public finding.
| Unresolved decision | Useful output | Depth to discuss | What it does not prove |
|---|---|---|---|
| Which businesses meet a clear public condition? | Company and contact list with accepted eligibility fields | Basic lead data | Interest or readiness to buy |
| What does this unfamiliar company actually do? | General company brief with evidence and unknowns | Company intelligence | Fit for every seller offer |
| Does our specific service apply here? | Seller-context criteria and a target dossier | Your-offer intelligence | Budget or approved project |
| Which role should explore the issue? | Observed role evidence and a routing question | Agreed role research scope | Final purchasing authority |
| Is a private operating problem present? | Clearly framed validation question | Conversation after research | A confirmed pain point from public context alone |
Worked example: the same account at three depths
Consider a fictional company, HarborDesk, with a website describing scheduling software for field service businesses and implementation support. A basic record identifies the company, its website, the accepted selection condition, and a named founder or administrator with business email. A representative can find the account and begin review, but may still wonder whether HarborDesk is primarily a software provider or a consultancy.
A general brief adds that HarborDesk advertises subscription plans, publishes product documentation, and offers onboarding services. It distinguishes the software product from the implementation service and notes that the website does not disclose the relative revenue from each. This context supports a clearer business-model classification without pretending to know the internal economics.
For a seller of product documentation services, offer-specific research examines whether HarborDesk's public documentation covers the workflows that seller supports. The resulting dossier could identify a relevant capability match and a question about documentation ownership. It should also record counterevidence, such as a detailed and recently maintained help center.
For a seller of on-site warehouse equipment, the same account may be a poor fit unless there is separate evidence of an operating need. A high general company score would not repair that mismatch. The example illustrates why depth is useful only when it remains connected to a particular decision.
Record exactly what changed after reading
Use a reviewer decision log to evaluate the extra research. Before reading the general brief, record the intended action and the uncertainty. After reading, record whether the action changed and which evidence caused the change. This makes the test concrete.
For HarborDesk, the initial action might be “hold for business-model review.” After the general brief, the action becomes “eligible software business; route to product-services queue.” The source-backed distinction between subscription product and onboarding service is the reason. The change is useful because it resolves a routing decision.
For the documentation seller, the offer-specific dossier may change “contact immediately” to “review documentation maturity before approaching.” A counterexample or disqualifier can therefore be valuable research even when it lowers enthusiasm. Research should improve decisions, not merely justify the purchase of more accounts.
Keep the log short enough to use consistently. Suggested fields are account ID, initial action, unresolved question, evidence added, revised action, and remaining uncertainty. Do not record invented time savings or projected revenue as if they had been measured. If you want to evaluate reading time or downstream outcomes, collect those observations separately under a defined process.
Worked example: when more general context changes little
A fictional seller, Eastbank Merchant Support, offers one narrowly defined platform configuration service. Its team already understands the typical merchant models in the niche. The accepted list includes operating merchants with the relevant platform observation and excludes agencies, demo sites, existing customers, and unsupported configurations.
The team reviews a general brief for a candidate and learns that the merchant sells outdoor products, offers shipping, and publishes a returns policy. These facts may be correct, but they do not change eligibility, routing, or the service the team can offer. The brief is readable without being decision-changing for this campaign.
A more useful addition might be a specific structured observation about the relevant checkout configuration, if it is within the accepted research scope and can be supported. Alternatively, the team may decide that basic data plus its own short review is sufficient. The decision is not that general research is bad; it is that this team's missing question is narrow.
Eastbank records that conclusion and retains the basic scope for similar accounts. If it later introduces a complex operations advisory service, the depth decision should be revisited. The value of research depends on the current offer and workflow, not a permanent label attached to the company or buyer.
Read the score as a model summary
A score is meaningful only in relation to a rubric. Ask which criteria it summarizes, whether there are eligibility gates, how weights work, and how unknowns affect the result. Two accounts with the same total can have very different strengths and weaknesses.
Keep confidence separate from fit. A company might look highly relevant on the limited evidence available, while the evidence itself remains incomplete. Another company may be well documented but clearly outside the offer's scope. Combining those ideas into one unexplained number makes it harder to choose the correct next action.
Do not interpret a high score as buying intent. A public company profile can support relevance, compatibility, or the presence of a contextual observation. It generally cannot establish an approved project, internal dissatisfaction, or willingness to purchase from you. Those questions remain open unless direct evidence supports them.
Use the score to order review when the rubric serves your purpose, and use the brief to understand exceptions. If a mandatory condition fails, a high total from optional criteria should not override the failure. A transparent decision rule is more useful than a ranking that cannot explain why an account appears near the top.
The W3C Data Quality Vocabulary, published as a Working Group Note, distinguishes a quality dimension from the metric used to measure it. That distinction provides a useful reference for asking what a score measures. The account-scoring recommendations in this guide are an original operating method, not a prescribed W3C sales rubric.
References: W3C Working Group Note: Data Quality Vocabulary ↗
Know when general research reaches its limit
General research reaches its limit when the target decision depends on your own service model. A business may be attractive to a managed service provider and irrelevant to a software implementation partner. The same public facts can produce different implications for different sellers.
Describe the capabilities that matter, the customers you can serve, the dependencies your delivery requires, and the accounts you should avoid. Include actual exclusions such as unsupported project types or direct competitive overlap. A broad marketing slogan is not enough to guide a target-specific assessment.
StackShortlist's Your-offer intelligence work uses the buyer's website and a brief of up to three thousand words, supplied as PDF, DOCX, TXT, or pasted text. The brief should resolve decisions that the website leaves ambiguous. It should not require the researcher to infer an unadvertised service or choose among conflicting offers.
The resulting dossier should make the connection visible: observed target fact, relevant seller capability, fit implication, counterevidence, and a question worth validating. If the same recommendation could be pasted into every seller's dossier unchanged, the research has probably remained too general.
Connect dossiers to your offer Determine which seller-specific questions require additional context.
Research the seller before the target Clarify capabilities and exclusions before assigning offer-specific fit.
Compare the cost of the accepted task
For one hundred new companies, StackShortlist's starting prices are $19 for Stack leads, $39 for Company intelligence, and $79 for Your-offer intelligence. For an existing list, the corresponding starting prices are $15, $35, and $69. The minimum is one hundred, and each requirement after the first adds $0.10 per company under either All or Any matching.
Use these prices only alongside the exact scope you order; the price is charged at checkout. A catalogue category is not a guarantee that a requested quantity is available, and a higher research depth is not a promise that every public field can be found.
Compare the added price with the specific work it replaces or enables. If representatives repeatedly reconstruct the same company context, a brief may centralize that task. If the research does not change any decision, extra reading can become a cost rather than a benefit. Avoid inventing a universal monetary value for a saved minute or an assumed response improvement.
Keep contact acquisition separate from own-list research. An existing-list task can improve company understanding without guaranteeing new contacts. If missing contacts are the main obstacle, treat that as the problem to solve rather than choosing a deeper dossier and expecting the contact problem to disappear.
Compare complete research scopes Normalize company quantity, depth, contact obligations, and requirements before comparing price.
Run a small depth comparison with real decisions
Choose a manageable set of accounts spanning clear matches, borderline businesses, and likely exclusions. Use the same accepted criteria for each account. Have reviewers make an initial decision from the basic fields, then reveal the general brief, and finally reveal seller-specific analysis where relevant.
Record changes without forcing an upgrade to win. A useful result may be that general context resolves business-model ambiguity but offer-specific analysis is only valuable for one service line. Another result may be that structured eligibility fields are sufficient for most accounts. Both findings can improve ordering decisions.
Inspect whether the added research is readable at the point of use. A representative should not need to search through several pages to find the observation that matters. Detailed evidence can remain available while the immediate decision summary stays concise.
After the comparison, choose a depth policy and the exceptions to it. For example, use general briefs for unfamiliar business models and seller-specific dossiers when an account's service compatibility is unclear. Treat this as an internal operating method, not a promised product feature or automatic upgrade workflow. Confirm the available delivery scope in the quote.
Package each output for its next user
Keep sortable fields separate from the narrative. Company identity, eligibility state, score, and review priority belong in fields that can be filtered. A detailed explanation, source context, and counterargument belong in the brief. Link them through the same company identifier.
Give representatives a short reading order: understand the business, inspect the fit reason, read the counterevidence, then choose a question. This reduces the temptation to copy a generic opening line from a long dossier. The brief should support judgment, not replace it with an unsupported claim about the prospect's pain.
Assign a refresh trigger. A changed seller offer, a rebranded target, or contradictory new evidence can invalidate an earlier fit decision. Preserve the original research date and criteria version so the team knows what was evaluated. More depth does not make a record permanently current.
Review the depth policy after the team has used it. Ask which fields were repeatedly ignored, which questions still required manual work, and which research changed routing or priority. Use that feedback to improve the next accepted scope. The objective is a usable account decision with an appropriate evidence trail.
Common questions
Are scored leads always better than basic leads?
They are useful when the rubric and company context support a decision your team needs to make. A narrow campaign with clear eligibility may work well with basic fields. Evaluate whether the added research changes routing, priority, or preparation rather than treating a score as an automatic quality upgrade.
Can a general score be used for my specific offer?
Only to the extent that its documented criteria match your actual requirements. A general score may summarize the company without evaluating your service dependencies or exclusions. If the same account would fit differently for different sellers, use a seller-specific rubric and preserve the general score as a separate concept.
Should the team read every dossier in full?
Give each user the level of detail needed for the next decision. A manager may use sortable fields to assign accounts, while a representative reads the fit reason and counterevidence before contact. Preserve the full evidence trail for review, but make the immediate action easy to find.
What should happen when added research finds a disqualifier?
Record the disqualifier and change the action. Research that prevents an irrelevant approach can be useful even when it reduces the shortlist. Do not judge a dossier by how enthusiastically it recommends the account; judge whether the conclusion follows from the accepted criteria and evidence.
How can I tell whether the brief is too generic?
Ask which decision would change if you removed it. If the text mostly repeats homepage claims, offers compliments, or recommends the same approach for every seller, it may not add enough context. A useful brief identifies specific observations, relevant uncertainty, and a defensible next question.
Sources & further reading
Primary references support the technical details. Worked examples are illustrative; workflows and checklists are practical methods to adapt to your own process.
Something changed? Tell the editorial team.