500 recent Splunk-user lookalikes to Rafael Hass and Daniel Wilson — 146 are dedicated Splunk engineers, admins or architects

Asked:

“daniel wilson of voleon, splunk customer - give me 100 more lookalikes like him. i want to go after splunk customers.”

Asked (follow-up):

“find me another 500 people like Rafael Hass | Security Information Manager BTG Pactual and daniel of voleon - both splunk users.”

500 public-web prospect records modeled on Rafael Hass’s security-information/SIEM leadership and Daniel Wilson’s hands-on senior security-engineering and Splunk-administration profile. Every record shows evidence of workplace Splunk activity in a role active during 2025 (265 records) or 2026 (235 records); similarity scores run 0.756–0.811. Rafael Hass, Daniel Wilson, BTG Pactual, Voleon, and all 25 people and organizations from the prior strict verified report were excluded. The 500 rows cover 480 distinct displayed name strings and 425 organizations — abbreviated or common names and people with multiple qualifying employer-role records account for the gap, so this is 500 prospect records, not 500 identity-resolved unique humans.

Read before outreach: LinkedIn and its regional hostnames supply 497 of the 500 rows, so the evidence is heavily single-platform: public professional-profile and event/customer-story data, not independent confirmation of a commercial Splunk contract. Similarity scores rank profile resemblance to Rafael and Daniel — they are not buying intent. Verify employment, account ownership, current production Splunk usage, and outreach suitability before contacting anyone. No contact information is included.

Where the 500 prospects sit, by role segment and activity year

Bars sorted by segment size; darker = qualified through 2026 activity, lighter = 2025. Click a bar to filter the table below; hover a slice for its top names.

The single strongest lookalike is Ali Yahyaabadi, SIEM Engineer at Iran’s Ministry of Economic Affairs and Finance (similarity 0.811), running Splunk distributed architecture for security monitoring — linkedin.com
Large regulated enterprises recur throughout: Wells Fargo, J.P. Morgan, Visa, Walmart Global Tech and the U.S. Department of Homeland Security each appear with hands-on Splunk security engineers, e.g. a J.P. Morgan engineer running 10TB+/day of Splunk ingestion — linkedin.com
Only 3 of 500 rows come from outside LinkedIn: a .conf25 session deck, a Cisco Black Hat SOC blog, and a Splunk customer story on Decathlon — conf.splunk.com, blogs.cisco.com, splunk.com
Sourcing stayed deduplicated: 480 distinct source pages back the 500 rows, 9 host strings in total, and no single URL backs more than 2 rows — linkedin.com

All 500 prospect records

Search any field; filter by segment or activity year. Sorted by similarity score, highest first.

#PersonTitle & employerSegmentSplunk use caseActivityScoreSource

Method: 500 public-web prospect records modeled on the Rafael Hass (SIEM/security-information leadership) and Daniel Wilson (senior security engineering / Splunk administration) profiles, compiled 2026. Each row holds person, title, employer, qualifying activity date (2025 or 2026), Splunk use case, explicit Splunk evidence quote, similarity score (profile resemblance, 0.756–0.811, not buying intent), and source URL. 497 of 500 rows are LinkedIn-sourced; 480 distinct source pages; no URL backs more than 2 rows. Screened out: certifications-only, training, labs, internships, migrations away from Splunk, Splunk employees, consultants, vendors, resellers, MSPs, and historical roles. Role segments were assigned from job titles for this report. Evidence quotes are truncated in the table for space; verify each record before outreach.

This report was generated automatically by Keenable SELECT at a user's request, from publicly available web sources linked herein. Keenable does not review, verify, or endorse its contents and makes no representation as to accuracy, completeness, or timeliness; AI-based extraction may contain errors. Nothing in this report is investment, legal, financial, or other professional advice. All trademarks and referenced content remain the property of their respective owners; no affiliation or endorsement is implied. To report an error, rights concern, or request removal: legal@keenable.ai.

Keenable SELECTAsk your own question
Made with Keenable SELECT