Before you buy a list
How to validate a technology lead list
Check a sample before buying. Match each company to the recorded website, inspect the technology claim, and separate the source date from what is true today. Record supported, unsupported and unknown findings before deciding whether the package fits your work.
Download the blank audit worksheet
A CSV with 11 columns and 10 empty rows. Open it in a local spreadsheet app, fill one row per company and property claim, and add rows as needed. Your entries stay in your file; WhosBuilt does not receive them.
Download blank worksheet (CSV)The download contains no company examples or completed checks. The worked example below is separate.
What to enter in each column
- company
- Name the company the seller associates with the record.
- domain
- Copy the listed domain; keep the checked property separate.
- claimedTechnology
- Copy the technology claim you intend to check.
- websiteOrPropertyScope
- Record the website, subdomain, product or workload the claim covers.
- publishedSourceClass
- Record the source type the seller publishes, such as website configuration or a customer story.
- recordedCheckDate
- Copy the source observation date. Keep the package date in your notes if it differs.
- buyerCheckedSourceURL
- After checking a source, paste its URL here. Leave blank until you check it.
- buyerCheckDate
- Record when you checked that source, using YYYY-MM-DD and a timezone where relevant.
- assessment
- Enter supported, unsupported or unknown for the claim and scope you checked.
- reason
- Explain what the source supports, contradicts or leaves unanswered.
- unresolvedBuyingRequirement
- Write the requirement you still need resolved before buying or using the list.
Check a sample in four steps
- Set the buying requirement. Write down the technology, property and freshness you need. A company homepage, recruiting portal and client project can belong to different scopes. Ask how the seller chose the sample; a curated preview cannot establish the accuracy of the full file.
- Copy the recorded claim and date. Keep the source class and observation date beside the company and domain. A package date describes the package; it does not refresh every source in it.
- Inspect the supporting source. Check that the source refers to the listed company, technology and property. Record the URL you checked and your check date. If the preview gives only a homepage, ask for the supporting source before treating the claim as checked.
- Record the finding and remaining question. Mark each claim using the definitions below. Keep unanswered requirements beside the finding so a historical match does not become a claim about current use or buying intent.
For source definitions, use the technographic data guide. To build a candidate list yourself, see how to find Shopify stores.
Choose supported, unsupported or unknown
- Supported
- The source you checked supports the stated technology, property and date. Record that scope; other requirements may still be unresolved.
- Unsupported
- The checked source contradicts the claim or refers to a different company or property. Write down the mismatch.
- Unknown
- You have not checked, cannot access the source, or the source cannot answer the claim. A missing signal alone does not prove non-use.
Keep the three counts separate. Do not count unknown rows as passes or turn a small selected sample into a whole-list accuracy rate.
Worked example from Lattice / Webflow
Filled from the published package; no fresh site check.
The public October 5, 2026 Webflow package lists Lattice with a website-configuration signal observed October 4. This example transcribes that published record. It leaves the buyer's check fields empty and the audit assessment unknown because no fresh source check was performed.
- company
- Lattice
- domain
- lattice.com
- claimedTechnology
- Webflow
- websiteOrPropertyScope
- Attributed website or workload only; company-wide deployment unverified.
- publishedSourceClass
- Website configuration signal
- recordedCheckDate
- 2026-10-04
- buyerCheckedSourceURL
- Not checked; leave this cell blank in your own audit.
- buyerCheckDate
- Not checked; leave blank.
- assessment
- unknown
- reason
- The October 5, 2026 package records the historical signal. No fresh site check has been made for this example; current use, execution and paid status remain unknown.
- unresolvedBuyingRequirement
- Confirm whether the recorded property and its current technology fit the intended work. Purchase intent remains unknown.
Start from the listed Lattice homepage when doing your own check. The homepage link alone does not support the technology claim. The package's website configuration signal does not establish current execution, a paid subscription or company-wide deployment.
Download the existing public Webflow preview (CSV)Decide what still needs checking before purchase
Compare the findings with your buying requirement. Keep supported rows that fit your scope, set aside mismatches, and ask the seller about unknowns. Confirm permitted use, included fields and delivery terms separately; a public technology signal cannot answer those questions or establish outreach permission.
View Webflow package and enquiry