If you want to find companies using Salesforce, you are already past the vague "who is in my market?" stage. You have a stack hypothesis. This guide shows how to turn that into a list, and how the same method works for HubSpot, Shopify, or Oracle.
Why technology-led lists convert better
Industry tells you the neighborhood. Salesforce tells you the operating system of revenue. A manufacturer on Salesforce is a different conversation than a manufacturer on a homegrown spreadsheet and email.
You can sell integration, cleanup, analytics, or a complementary tool. You cannot do that honestly if you do not know the CRM.
Start from the technology, then narrow
Open technology search and look up Salesforce. Then add industry and size so you are not staring at every company on earth that ever mentioned the logo.
Alternatively, start in company search and add Salesforce as a technology filter. Both paths should end in a count you can work, not a count that looks impressive in a slide.
The same workflow for HubSpot, Shopify, and Oracle
HubSpot often signals a growth-stage or mid-market motion with marketing and CRM in one place. Complementary products (data, enrichment, specialized service tools) land well. Replacing HubSpot usually does not, unless you see clear scale pain.
Shopify signals commerce operations. Pair it with size and whether you see a full stack (email, subscriptions, ERP) or a store that is still thin. Oracle often signals larger, slower organizations. Your cycle and your buyer set should change accordingly.
Do not mix these into one "uses popular software" list. The opener and the product story are different.
What to do when the list is still too big
Add country. Add employee band. Add a second technology or an exclusion. "Salesforce and not HubSpot Marketing" is a list. "Uses Salesforce" is a census.
If you sell into one vertical, use that industry first. Salesforce in real estate is not Salesforce in healthcare.
How to write the first line
Name the tool and the job it is doing. "Saw you are on Salesforce" is weak. "Saw you are on Salesforce without a MAP, which usually means campaign reporting lives in spreadsheets" is a reason to reply.
If you cannot see a second signal, keep the line short and ask a real question about the workflow. Do not invent pain.
When to use a custom list instead
If you need 2,000 accounts across several countries, with exclusions and a CRM-ready file, self-serve search can get slow. That is what custom data services is for: you describe the stack and the market, and you get a scoped export.
Use self-serve when you are testing a hypothesis. Use a custom list when the campaign is already funded and the filter logic is stable.
Check the profile before you scale outreach
Reveal a sample. Confirm the website, the industry, and that Salesforce still looks like a current system, not a job-ad mention from three years ago. Then export.
A clean 80-account Salesforce list that your team finishes is worth more than 800 rows that die in a shared drive.
Salesforce as a signal, not a trophy
Salesforce means the company invested in a CRM. It does not mean they are happy, fully implemented, or ready to buy your category. Many orgs have a half-used org, a pile of unmanaged apps, and a RevOps person holding it together with flows.
Your job is to decide which of those states you help. Integration products love messy orgs. Replacement products need visible pain. Analytics products need data that already lives in Salesforce. If you cannot name the state, you are just collecting logos.
Look at size and industry next. Salesforce in a 40-person agency is a different deal than Salesforce in a 4,000-person manufacturer. The company search filters exist so you do not mix those conversations.
Building parallel lists without losing the week
If you also sell to HubSpot or Shopify shops, keep those as separate saved searches. Do not merge them into one "uses a modern platform" export. The first line will suffer.
Run Salesforce this week, HubSpot next week, or split the team. Volume across stacks is how personalization dies.
When a campaign is approved and the logic is stable, a custom company list can produce the Salesforce cut with exclusions already applied. That is a better use of time than re-clicking the same filters every Monday.
After you have the list
Map each account to one offer. Complementary tool. Cleanup. Training. Analytics. Pick one. Then send. The companies using Salesforce that reply are teaching you which offer matches which size band. Adjust the filter. Repeat.
That loop is the whole method. Finding the companies is the start. Learning from the first thirty is the work.
Worked example: complementary tool into Salesforce shops
Search Salesforce. Add your industry. Add a size band you can implement. Exclude companies that already show your category. Save the search as the offer name.
Reveal fifteen. For each, write whether the likely pain is reporting, data quality, or a missing adjacent tool. Send only those fifteen. The replies tell you which pain is real.
Next week, keep the winning pain and add geography or a second industry. Do not add three new tools to the same list. Companies using Salesforce are not one market. They are many markets that share a CRM.
Implementation notes for Salesforce-led campaigns
Name the campaign after the offer, not after Salesforce. "RevOps reporting for mid-market Salesforce" can be measured. "Salesforce users" cannot.
Check AppExchange-adjacent competitors on a sample of accounts. If they already own the shelf, your first line must change or the account must drop.
Split enterprise and mid-market even if both run Salesforce. The security review, the champion, and the timeline are different. One sequence will serve one of them badly.
Keep HubSpot and Oracle lists in other campaigns. The how-to-find-companies-using-Salesforce muscle is focus. Mixing CRMs is how the muscle atrophies.
After thirty sends, read the objections. "We are ripping out Salesforce" is a different list. "We just bought a package" is an exclusion. Update the search the same day.
If you need the same cut in five countries, stop clicking and order a custom list. Repetition is a delivery problem, not a research problem.
Field manual for the first two weeks
Week one is a single industry and a single size band. Week two adds a country or an exclusion, not a second CRM. Finding companies using Salesforce is easy. Finding a list you can finish is the work.
Keep a running note of phrases prospects use for their Salesforce org: "our instance," "RevOps owns it," "we are in a cleanup." Those phrases become next month's first lines.
If HubSpot or Oracle is also a motion, give it its own two weeks later. Do not interleave. The how-to stays clean when the calendar stays clean.
Share three good emails in the team channel. Do not share a 40-row theory deck. Salesforce-led prospecting is taught by examples.
When you need the same cut for a partner or a region, order a custom list instead of rebuilding. The field manual ends when the search is production.
Twelve-step Salesforce list playbook
This playbook is how to find companies using Salesforce without turning the CRM logo into a junk export. Follow the order. Skipping to step twelve is how teams buy files they never send.
If you also need HubSpot or Oracle lists, run this same twelve steps on those tools in later weeks. Do not merge the exports. The first line and the buyer are different even when the motion looks similar.
- Write the offer in one sentence that includes Salesforce and the job you do next to it.
- Open technology search and select Salesforce, then add one industry only.
- Set an employee band you can implement without a six-month professional services project.
- Add one country or region your team can cover this month.
- Add exclusions for customers, open opportunities, and obvious category owners.
- Browse fifty rows and delete the search if it still looks random.
- Reveal fifteen accounts and write a reason for each row.
- Visit each website and confirm the company still looks like the industry you filtered.
- Send fifteen notes in two days, not fifty notes in two weeks.
- Log objections as new exclusions the same day they appear.
- Repeat the cut once. If it works, save it. If it fails, change the offer, not the volume.
- When the same cut is needed again, use a custom company list instead of rebuilding by hand.
Salesforce versus HubSpot versus Oracle on the same motion
People searching how to find companies using Salesforce often want the same motion for HubSpot or Oracle. The search UI is similar. The buyer is not. Salesforce-led mid-market RevOps usually owns reporting and cleanup. HubSpot-led teams often sit closer to marketing operations. Oracle-led accounts are frequently larger, slower, and more procurement-heavy.
Run each CRM as its own campaign. Keep the same size band and industry so you can compare reply rates. If you merge the three exports, you will not know which software pattern created the meeting, and you will write a first line that names the wrong system.
When you need the same cut at volume, use company search to lock industry and size, then technographic filters for the CRM. A custom company list is the right next step after the first two weeks prove the offer.
PrimoDato Editorial Team
B2B Intelligence & Prospecting Research
The PrimoDato team writes about company data, B2B prospecting, technographic intelligence, and sales strategy based on what we see across our platform and the markets we cover.