StackShortlist

A job title tells you who to email. The tools a company already runs tell you what to ask. A Shopify store on Klaviyo already pays for email, so "who builds your flows?" is a fair first line. Pick from 3,500+ technologies at stackshortlist.dev

Before writing a single cold email, pick 100 companies that already run the tool your product works with. That one filter does more for replies than any subject line test. If you'd rather not build the list by hand, we do it as a one-time CSV, $19 per 100: stackshortlist.dev

Small tip for founders doing outbound: write the first line about the tool they already run. "Saw you use X, we make X easier" beats any clever opener.

We built StackShortlist to make that easy: B2B company lists filtered by the software they use, 3,500+ tools covered. stackshortlist.dev

If your product plugs into a specific tool, your best customers are the companies already using that tool. Start your list there, not with a generic industry filter.

Building a lead list by technology used to mean hours of checking job posts and page source. We built StackShortlist so you can pull companies by the software they use, across 3,500+ tools. It's ours, happy to hear feedback: stackshortlist.dev

Quick tip for founders doing outbound: start from the stack, not the job title. If your product plugs into Salesforce, a list of companies already on Salesforce is a far warmer starting point than a generic industry list.

If you sell B2B software, one of the easiest ways to find good-fit customers is to look at the tools they already run. A team on HubSpot and Stripe tells you a lot before you ever send a message. That's why we built StackShortlist: stackshortlist.dev

Building outreach around a CRM integration? Pull companies that already use that CRM, then reach the admin, not a generic inbox. The admin is usually the one who installs integrations. stackshortlist.dev

Selling a Shopify app? The best first list is stores already running an app next to yours, like a reviews app if you sell upsells. They have shown they will install and pay for apps. Filter by that app in a list of 3,500+ technologies here: stackshortlist.dev

Another lead tip: filter by two tools together, e.g. Shopify plus a specific email platform. The overlap is usually a much tighter, more relevant list than either tool alone.

Tip for finding leads by tech stack: start from a tool that pairs well with your product, then list the companies already using it. They have the budget and the workflow problem you solve.

Need a list of companies by the tools they use? Search 3,500+ by tech stack, then export. stackshortlist.dev

Starting a cold email list? Begin with companies already running the tool your product plugs into. Shopify app, start with Shopify stores. 100 companies with stack evidence and a named contact, $19 one-time: stackshortlist.dev

Emails to info@ and support@ rarely get read by the person who decides. A named founder or admin, with an email you can trace to a source, usually does better.

Question for people who sell plugins or integrations: do you build your first list from the platform (everyone on WooCommerce) or from the customer type and check the stack after? I go platform first. Not sure it's always right.

Every row on a lead list should answer one question: why this company? 'They were in a database' is a weak opener. 'They run Shopify and you sell a Shopify app' is a real one.

Knowing who runs a tool gets you a conversation, not a sale. Open with one good question about how they use it, then listen.

Pick one tool your buyers already run. Shopify, Stripe, Webflow

If reply rate fell after you rewrote the copy, check the list before another rewrite. Same offer, worse list, worse replies.

If you sell to Shopify stores, or Stripe users, or anyone on a specific stack, start from who already uses it. StackShortlist builds that list once: stack evidence, fit score, named contact. stackshortlist.dev

Most lead lists are a pile of domains and a best-guess email. What I want is simpler: companies that already run the tool I sell around, plus a named founder or admin with a work email, and the evidence that got them on the list. $19 for 100. One payment. No subscription.

This is the kind of small tool I like. One annoying problem, one job, no logins. Warranties are a perfect fit for it.

Before I build any lead list I write the "not these" lines first. Current customers, agencies building for clients, open deals, recent losses. Ten minutes, and it cuts more junk than any extra filter. What do you always exclude?

Closing the loop from RFQ back to the ad platform is the part most teams skip. Same on the outbound side. If you know which companies already run HubSpot, you can start with them instead of guessing. stackshortlist.dev

Most lead lists go stale because nobody wrote down where each row came from. So every company on StackShortlist has its source URL next to it. Check it yourself before you email. stackshortlist.dev

A stack match tells you why a company is relevant. It doesn't tell you they're ready to buy. Good first line, not proof of need.

Most cold lists fail before the first email. Wrong companies, generic inboxes. Start from the tool they already run and a named person who can say yes. stackshortlist.dev

info@ addresses almost never reply. A named founder or admin, with an email you can trace back to a source, usually does. That's most of why every row we deliver has a named contact.

Cold email habit worth keeping: before writing the first line, check what the company actually runs. If they're on Shopify and you sell a Shopify app, you've got a real opener. If you can't tell, say so and ask. Lists by technology: stackshortlist.dev

info@ rarely answers. A named founder or admin with an attributed work email is a better first hello. Launch price is $19 per 100 companies. stackshortlist.dev/pricing

Your next customer already runs a tool you sell around. Pick that stack and get 100 companies with a named founder or admin email. $19, one payment. stackshortlist.dev

Built StackShortlist for exactly that: a one-time list of companies running the technology you pick, with stack evidence and a named contact. Launch price is $19 per 100 companies. stackshortlist.dev

If you sell an add-on for a specific platform, the best first list is companies already running that platform today. Start there, then sort by size and fit before writing a single email.

I built a small local recording desk for GitGlow. It prepares real changes and tests in a disposable Git repo, so I can repeat a staging or review scene. No footage yet; this week's work was making the setup repeatable. #buildinpublic

Developer workflow: Backend state confusing. Solution A: fix backend. Solution B: add six frontend conditions. Guess which one feels faster today and hurts more tomorrow. #buildinpublic #indiedev

Asked my coding agent to find every place my side project trusts the client. Found 4: a price sent from checkout, a user_id in a hidden field, a role flag, a coupon checked only in JS. All passed testing. None should exist. #claudecode #security #indiehackers #buildinpublic

Cold email is infrastructure before it's copywriting. Warmed domain, low bounce rate, clean list — get these right and average copy will still land. Miss them and brilliant copy goes straight to spam.

An AI agent named Cosmo runs this shirt shop. I still approve every design before it ships. We have until Dec 20 to make 5 sales or the store closes. Following along is allowed. Heckling is also allowed. #buildinpublic

💥 Cold email tips: Let AI scrape each prospect's website before you write. Grab: - Team members - Recent blog posts - Case studies Then reference one in your first line. Reply rate jumps because it reads like real research 🔥

the whole asset pipeline runs on a 1 cpu server with 2gb ram and no gpu. not because it's clever. because it does one thing at a time and frees memory explicitly. cheap hardware rewards discipline. #BuildInPublic #IndieHackers i made the Pipeline Starter Kit for this.

If several screens need different workarounds for the same state, fix the state model. UI patches age badly. #buildinpublic #indiedev