DEV Community: StackShortlist

Evidence on the row beats a sales claim

StackShortlist — Fri, 16 Oct 2026 15:39:56 +0000

A sales page can say a list is verified. That word means different things to different sellers.

What I want on each row is quieter: a source URL I can open, a date for when that page was checked, and a named person with a business email when one was found. If any of that is missing, the row should say so. Unknown is fine. A filled cell that cannot be checked is not.

I built https://stackshortlist.dev around that shape. One-time research lists by technology, with evidence and contacts, $19 per 100 companies, no subscription.

If you buy lists, what do you open first on a new row?

Written with AI assistance, edited by me.

Write the exclusions first

StackShortlist — Fri, 16 Oct 2026 15:37:33 +0000

Most lead lists I've seen go wrong in the same spot. Somebody picks the tool, picks a country, and hits go. Then half the rows are companies they'd never call anyway.

Agencies that resell the tool. Your own customers. A competitor's partner. Companies too small to have a person who'd own the decision.

So now I write the "not these" list before anything else. Takes ten minutes. It's usually five to eight lines, and it cuts more junk than any extra filter I've tried.

A few I keep reusing:

current customers (paste the domains, don't trust memory)
agencies and freelancers building for clients
anyone already in an open deal in the CRM
companies you lost in the last six months, unless something real changed on your side

Then the requirement itself can stay simple. One tool, maybe a second one with "all" if it really matters.

That's how I set up orders on https://stackshortlist.dev too. Exclusions go in the order, and the list comes back without the rows you'd have deleted by hand. One payment per list. Pricing is on https://stackshortlist.dev/pricing.

What's on your exclusion list that most people forget?

Written with AI assistance, edited by me.

When a startup database is the wrong first step

StackShortlist — Fri, 16 Oct 2026 05:16:29 +0000

A lot of people start with a big startup database. Thousands of companies. Funding stage. Headcount. Industry tags.

That is fine if you sell something every startup needs. Most of us do not.

If you sell around Shopify, HubSpot, Stripe, or some other concrete tool, the first filter is simpler: who already runs it.

A generic startup list makes you guess. A stack list gives you a reason to write the first line. You can point at the evidence page and ask a real question about their setup.

I built StackShortlist for that. One-time research. Companies using a technology you choose, with sources and a named contact. No subscription. No claim that they are ready to buy.

https://stackshortlist.dev

If your offer only fits people on one platform, start there. Save the broad database for later.

Coverage is not the same as a usable row

StackShortlist — Fri, 16 Oct 2026 03:17:43 +0000

People ask how big the database is. Wrong question for a one-time list.

What matters is whether each row has enough to start a conversation: which tool, where you saw it, and who to write to.

Gaps stay gaps. Unknown stays unknown. That is more useful than a padded file.

More on how we ship lists: https://stackshortlist.dev

The contact row is the product

StackShortlist — Fri, 16 Oct 2026 03:17:36 +0000

A spreadsheet of company names is homework. What you actually need on each row is a person who can answer mail: a founder or an admin, with a work email you can attribute.

Stack evidence helps too. A source page and a date beat a vague "they use X" claim when you write the first line.

That is what we build at https://stackshortlist.dev : pick a technology, get companies running it, with a named contact. One payment. No subscription.

One payment is enough for a stack list

StackShortlist — Fri, 16 Oct 2026 02:30:53 +0000

I got tired of another monthly seat for lists I only need once.

StackShortlist is a one-time order: pick a technology from 3,500+, get companies that run it today with evidence and a named contact. Launch price is $19 per 100.

Order on https://stackshortlist.dev

Evidence on the row beats a sales claim

StackShortlist — Fri, 16 Oct 2026 02:30:20 +0000

When I buy or build a lead list, I want the proof next to the company name. Source URL, what was observed, and when.

A named founder or admin email beats info@ every time. Unknown stays unknown.

That's how StackShortlist rows are built. https://stackshortlist.dev

Pick the tool before you pick the company

StackShortlist — Fri, 16 Oct 2026 01:33:41 +0000

Most prospecting starts with a company filter. Industry, headcount, country. Then you stare at the list and try to think of something relevant to say.

I've had better luck flipping the order. Pick the software first, then go after the companies that already run it. A list of 100 companies in "SaaS, 10 to 50 people" tells you nothing about whether they'd care. A list of 100 companies running the tool your product plugs into tells you your first question before you've written a word.

It also changes who you write to. The person who set up the tool, often a founder or an admin at a small company, knows its gaps. They'll answer, or tell you plainly it's not a problem for them. Both save time. Mention the tool, ask the question, stop.

If you'd rather skip the research, StackShortlist has lists of companies by the technology they use, across 3,500+ technologies: https://stackshortlist.dev

What I check before trusting a lead list row

StackShortlist — Fri, 16 Oct 2026 01:33:02 +0000

Before I write to anyone on a lead list, I look at each row and ask four boring questions.

First, is there a source URL? If a row says a company uses some tool, I want to click through and see where that claim came from. A page I can open beats a confident label every time.

Second, when was it observed? A stack note from last month is useful. One from two years ago is a guess dressed up as data. If there's no date, I treat the row as unverified.

Third, is there a named person? Not a role, not info@, an actual founder or admin with a name. If I can't say who I'm writing to, I'm not ready to write.

Fourth, are the unknowns left blank? I trust a list more when it says "unknown" than when every cell is filled. Filled cells that nobody checked are how you end up opening an email with the wrong tool, the wrong title, or a person who left in 2023.

None of this is clever. It just stops me from sending 200 emails that start with a wrong assumption. If a row fails two of the four, I drop it and move on. Fewer rows, better first lines.

This is roughly the checklist I built StackShortlist around, if you want to see how the rows look: https://stackshortlist.dev

Unknown is a useful answer in a lead list

StackShortlist — Fri, 16 Oct 2026 01:02:06 +0000

Every lead list I've bought had every column filled in for every row. Industry, size, tech, email. Looked tidy. A lot of it was guessed.

I'd rather see "unknown" than a confident wrong value. Unknown tells me to check it myself or skip it. Wrong, I find out after the bounce, or after a reply saying "we don't use that".

So when I build a prospect list now, every claim needs a source and a date. No source, the cell stays empty.

How do you handle guessed fields? Clean them out, or live with them?

Why a named contact beats a generic inbox

StackShortlist — Fri, 16 Oct 2026 01:00:21 +0000

I've sent a lot of cold email to info@ and hello@ addresses. Most of it went nowhere. Those inboxes are a queue, and whoever reads them is sorting support tickets and invoices before anything else.

When I started writing to the founder or the admin who actually set up the tool I was asking about, replies went up. Not by magic. The person reading it could answer without forwarding it to anyone.

Before I write now, I check two things. Is there a real person whose role touches the tool? And can I see they actually use it, with a source I can point to?

If I can't find a named person, I'd rather skip the company than send to info@ and hope.

That's part of why I built StackShortlist. You pick a technology and get a one-time list of companies running it, each with stack evidence and a named founder or admin email. https://stackshortlist.dev

Ever had a generic inbox actually turn into a deal?

Start your B2B lead list from the tools a website runs

StackShortlist — Fri, 16 Oct 2026 00:25:01 +0000

Most B2B lead lists start with industry and headcount. That tells you a company exists. It doesn't tell you if your product fits.

I'd start from the software a company already runs instead. If you sell around one tool, the companies using it are the ones who'll understand your email in the first line. The fit is usually much tighter than any broad filter.

Keep it to one technology per list so the message can be specific. Write to a named founder or admin, not a generic inbox. And start small, around 100 companies, so you learn from the replies before scaling up.

If you'd rather skip the research, StackShortlist has lists of companies by the technology they use, across 3,500+ technologies: https://stackshortlist.dev