The cheapest quote is difficult to identify when the quotes describe different work. One may count contacts, another companies. One may include a general company brief, while another evaluates fit against your own offer. A price comparison becomes useful only after those differences are made explicit.
This guide builds an original normalization worksheet for lead data and company research purchases. It includes two fictional buying scenarios, a worked StackShortlist scope calculation, and a review process that separates known prices from uncertain downstream effort. The goal is a defensible choice about the task being purchased, not a universal ranking of providers.
What you’ll be able to do
- Align the company unit and completion rule before comparing per-record prices.
- Separate contact coverage, research depth, evidence, and output usability into distinct comparison fields.
- Treat unclear inclusions as unresolved scope rather than assuming the cheapest interpretation.
- Calculate additional requirements using the accepted quantity and matching logic.
- Keep actual quoted cost separate from unmeasured review effort and hoped-for campaign outcomes.
Establish whether the quotes describe the same task
Begin with the campaign specification and place it beside each quote. Highlight the target population, company boundary, quantity, contact requirement, research depth, exclusions, evidence expectations, and delivery structure. A blank in the quote is a question to resolve, not an automatic inclusion.
Ask whether the supplier is discovering new companies or researching a list you provide. These tasks can have different obligations. A quote for company context on an existing list should not be compared directly with a quote that also supplies a new company population and required contacts.
Check whether the proposal uses your terminology. The word lead can mean a company, a person, or an appointment in different commercial conversations. Do not allow that ambiguity to survive into the comparison. Rewrite the quoted unit in plain language and confirm it with the supplier.
Create a common scope column before looking at price rankings. If one proposal includes work you do not need, record it without automatically assigning it value. If another omits a required task, mark the gap. The comparison should reflect your accepted campaign need rather than whichever proposal contains the most impressive feature list.
Use a common purchase specification Give every quote the same campaign, counting unit, and acceptance basis.
Build the normalized quote worksheet
Use one row per comparison dimension and one column per quote. Keep a final column for the buyer's required position. This layout makes omissions visible without requiring a single composite score that hides tradeoffs.
Record the source of each answer: written quote, sample, public product description, or supplier clarification. If an answer comes from a conversation, put the confirmed wording into the decision record. Avoid relying on a salesperson's casual phrase when the formal scope says something different.
Use explicit statuses such as included, excluded, optional, subject to review, and unclear. These are more useful than check marks when the offer contains conditions. A feature can exist without being included in your particular order.
The worksheet is a comparison artifact, not an attempt to standardize every provider's business model. Suppliers may legitimately package work differently. Your job is to identify the work needed for the campaign and the implications of choosing each proposal.
| Dimension | What to record | Why it affects the comparison |
|---|---|---|
| Quoted unit | Distinct company, contact, input row, or other stated unit | Determines the denominator |
| Company boundary | Group, entity, operating business, brand, or location | Changes apparent account coverage |
| Contact obligation | Required person, role, address, and association | Changes completion and review work |
| Research depth | Basic fields, general brief, or offer-specific dossier | Changes the decisions supported |
| Evidence | Claim support, observation dates, unknown handling | Changes reviewability |
| Exclusions | Suppression matching and business-rule exclusions | Changes usable population |
| Requirements | Count and All or Any interpretation | Changes price and availability |
| Delivery and corrections | Format, identifiers, exceptions, and correction process | Changes operational usability |
Use a denominator that matches the decision
Per-record cost is only meaningful when record is defined. Divide the quoted total by the number of accepted companies when comparing company-based tasks. Keep contact quantities in a separate field. A quote for two hundred contacts may cover fewer than two hundred companies.
Do not substitute a delivered raw row count for the quoted company quantity. A flattened contact file can repeat company details many times. Likewise, a supplied list can contain aliases that map to one research target. Ask how duplicates and unresolved matches affect the accepted processing scope.
Calculate more than one descriptive ratio when it helps, but label each clearly. Cost per distinct company and cost per company with the required contact coverage answer different questions. If the latter coverage is unknown at quote stage, leave the calculation unresolved rather than inserting a hopeful estimate.
Avoid using a small selected sample's acceptance rate as if it were a guaranteed denominator for the full order. A sample can reveal failure modes and clarify definitions. Unless the sampling method supports a broader inference, it should not be used to manufacture a precise adjusted unit price. Keep demonstrated facts and planning assumptions in separate columns.
Separate company and contact counts Prevent a contact-heavy file from appearing to cover more accounts than it does.
Compare contact requirements independently
Specify what makes a company complete for the campaign. A named person, a business email, a current company association, and a relevant public role are distinct pieces of information. A proposal that includes only a generic mailbox does not satisfy the same task as one requiring a named contact.
For StackShortlist, completed new leads require a named founder or administrator with business email. Phones are optional. Own-list research does not guarantee new contacts. Include those distinctions in the comparison rather than assuming that a more detailed company dossier automatically adds new contact coverage.
Ask what validation and status labels mean in the particular quote. Do not equate a populated email field with an appropriate person-to-company relationship. A technically plausible address attached to the wrong company still creates a practical problem.
Keep role authority separate from role identity. A verified title can support a routing hypothesis, but it does not prove that the person approves your specific purchase. A quote promising decision makers should explain the evidence and scope of that description. The buyer should not compare an observed role with an unsupported authority claim as though they were equivalent deliverables.
Compare depth through the questions it resolves
Basic Stack leads already include fit scores. The relevant distinction is additional research depth: Company intelligence adds general company context, while Your-offer intelligence assesses the relationship to the buyer's own offer. A score by itself should not be used as the dividing line.
For a general brief, ask which company modules are included and how the evidence is presented. For an offer-specific dossier, ask what seller inputs are used and how the output distinguishes observed facts, fit implications, counterevidence, and open questions. A longer narrative is not automatically a more customized task.
Review the same fictional or appropriately sourced account across sample formats when possible. Identify which decision the added information changes. If a deeper brief only repeats a homepage summary, its marginal value to your campaign may be limited. If it resolves a critical service compatibility question, the difference may matter.
The UK Government Data Quality Framework uses fitness for purpose as a way to understand data quality. In this original buying method, the corresponding practical question is whether each proposed output supports the specific account decision your team must make. Do not award extra value merely because a field exists.
Choose depth by decision value Identify whether general context or seller-specific interpretation is the missing work.
References: UK Government: The Government Data Quality Framework ↗
Worked example: two unequal proposals
A fictional buyer, Wren Service Design, wants to identify one hundred eligible operating businesses and understand whether its onboarding advisory service applies. Proposal A describes one hundred company records with a named contact and a general company overview. Proposal B describes one hundred company records with a seller-specific dossier based on Wren's website and brief. The example does not assign invented market prices to either supplier.
The buyer initially treats B as the expensive version of the same list. The worksheet shows a more important difference: A explains what the targets do, while B is scoped to interpret those observations against Wren's delivery model. Wren's team must decide whether it can perform that interpretation itself.
During sample review, the general overview correctly describes a target's services but does not address whether onboarding is delivered centrally or separately by each branch. The custom dossier identifies that question, explains why it matters to Wren's service, and preserves the uncertainty. It does not claim the target has a problem.
Wren records two viable options. It can purchase general research and perform the seller-specific review internally, or purchase the accepted custom scope. The comparison should include that unperformed internal task without assigning an invented cost to it. If Wren wants a monetary estimate, it should measure its own review effort rather than borrowing an unsupported industry assumption.
Worked example: a lower headline price uses a different unit
A second fictional buyer, Ashgrove Systems, receives one proposal for two hundred contacts and another for one hundred companies. It wants to expand coverage across distinct businesses. The lower headline amount for the contact proposal initially looks attractive, but the account distribution is not stated.
Ashgrove asks for the company count and learns that the contact proposal is designed to provide several people at each of a smaller set of accounts. That could be useful for coordinated research within strategic accounts, but it does not match the current goal of covering one hundred different companies.
The company proposal also needs scrutiny. It includes one company row per account, but the buyer must confirm the required contact coverage and the treatment of subsidiaries. If ten rows are branches of one centrally managed business, apparent quantity may still differ from the intended operating-company population.
The buyer normalizes both proposals to the desired company boundary and asks each supplier to quote the same required scope if available. It does not declare one provider better merely because the original packages differ. The lesson is to align the task before calculating unit prices. A contact-rich proposal and an account-breadth proposal can both be reasonable products while serving different buying decisions.
Work through an accepted requirement calculation
StackShortlist's starting prices per one hundred new companies 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 companies.
Each requirement after the first adds $0.10 per company under either All or Any matching. Consider an illustrative request for three hundred new companies with Your-offer intelligence and three requirements. The base calculation is three groups of one hundred at $79, which is $237. Two additional requirements across three hundred companies add $60. The resulting arithmetic is $297 before applicable tax.
This calculation explains the stated pricing structure; it is not an availability promise. StackShortlist charges the price shown in its builder at checkout and starts the research after payment. If the requested population then cannot be delivered as written, the buyer should be contacted to agree a change or other resolution rather than receive a silent substitution.
Notice that All and Any have the same additional-requirement charge under this rule, but they create different populations. All requires every selected condition. Any allows alternatives and may create several segments. Price arithmetic does not replace a review of what those logical choices mean for the campaign.
For the same illustrative quantity and requirement count on a supplied list, the Your-offer intelligence base would be three times $69, or $207, plus the same $60 requirement addition, producing $267 under the stated arithmetic. The lower total describes an own-list task and does not carry an unstated promise to discover new companies or add new contacts. Keep those scope differences beside the two totals so the team does not choose an unsuitable starting point merely to reduce the quoted amount.
Review delivery conditions and correction handling
A useful quote states when the delivery clock begins and which inputs must be complete. For StackShortlist, the stated windows begin after the accepted, paid order has complete inputs: up to one thousand leads within twenty-four hours, 1,001–10,000 within seven days, and larger orders within fourteen days.
Compare those conditions with your own dependencies. If the seller brief is incomplete or a suppression file is still being assembled, the project is not ready merely because a payment date has been chosen. Leave time for buyer-side acceptance after receipt.
Ask how findings against the accepted specification will be handled. The useful answer names the correction process and the information the buyer should provide. Do not infer a replacement guarantee, refund entitlement, or service level that the quote does not state.
Keep scope changes separate from corrections. A wrong company match may be a correction. A newly requested customer segment is a changed task. The quote comparison should show how each proposal handles both situations, but the buyer should not label a changed preference as a defect in work that followed the accepted rules.
Agree the acceptance basis Compare correction handling against explicit requirements rather than subjective impressions.
Write the purchasing decision as a short argument
After normalization, write a decision record that explains why the selected proposal fits the task. Include the campaign goal, accepted company unit, required contacts, research depth, important evidence obligations, quoted price, unresolved conditions, and the person responsible for acceptance.
State the tradeoff plainly. You might choose a simpler output because the team can perform the remaining interpretation, or choose a deeper dossier because the seller-specific work is otherwise unassigned. Do not justify the choice with unmeasured claims about guaranteed reply rates or revenue.
Record why alternatives were not selected without attacking the providers. A proposal can be unsuitable because its unit, population, or depth differs from the current need. That does not make it poor quality in every context. Keeping the reasoning specific makes the record useful for a future campaign with different requirements.
Attach the final clarification messages or accepted wording to the order record. A comparison worksheet is only as reliable as its current inputs. If the quote changes after the decision, update the worksheet and the approval rationale rather than leaving the team with a stale cost or scope assumption.
Make future comparisons easier
Retain a reusable blank worksheet, the accepted specification, and a list of questions that revealed important differences. Over time, remove comparison dimensions that never affect your decisions and strengthen those that repeatedly expose ambiguity.
Review actual delivery against the purchasing assumptions. Did the files preserve identifiers? Did the contact scope match the accepted wording? Did representatives use the extra research? Did the correction process resolve specific findings? These observations improve future decisions without requiring a fabricated provider ranking.
Keep campaign results in a separate evaluation. A good data delivery can still support a weak offer or an inappropriate approach. A successful reply does not prove every field was correct. Feed back specific evidence about data usefulness rather than treating all commercial outcomes as a direct measure of list quality.
Before the next order, confirm that the seller offer and company boundary are still the same. A reusable worksheet helps only if the underlying task remains comparable. The goal is a transparent purchasing method that makes scope, price, and remaining work visible to everyone involved.
Common questions
Should I compare price per lead?
Only after lead has an agreed definition. Use the same company or contact unit, entity boundary, and completion rule for each proposal. Keep raw rows separate from distinct companies, and avoid treating additional contacts at one account as additional company coverage.
How do I value extra dossier detail?
Identify the decision the detail changes and the internal work it replaces or enables. A longer brief is not automatically more useful. If you want a monetary estimate, measure your own review effort and state the assumptions. Do not assign a universal value to more paragraphs or a higher score.
Can a sample acceptance rate adjust the quoted price?
A sample can reveal defects and clarify scope, but a selected demonstration may not support a population-wide estimate. Keep the sample's method and limits visible. Do not divide the quote by a projected accepted quantity unless the assumption is justified and clearly labeled.
Does Any matching cost less because it is broader?
Under StackShortlist's stated pricing, each requirement after the first adds $0.10 per company under either All or Any matching. The logical choice affects the population, not that additional-requirement rate. Choose the final criteria before checkout, because the order is paid at checkout.
What is the most important unresolved quote question?
Ask what exactly counts as a completed purchased record under your scope. That question connects company identity, eligibility, required contacts, and evidence. If completion remains unclear, a per-record comparison can be mathematically precise while describing different commercial tasks.
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.