Windows App 
MacOS (sillicon) How Barie finds decision-makers at a target company — titles, professional profiles, recent public statements, and role context — with source links for personalised outreach
Barie researches the target company’s decision-makers from live professional networks, press releases, conference speaker lists, and company announcements simultaneously. It delivers a structured contact intelligence report — role title, LinkedIn profile, area of responsibility, recent public statements, and the source URL for each — giving you the context to personalise outreach from a position of demonstrated knowledge, not generic cold contact.
Why contact research from static databases produces outreach that reads as generic to informed buyers
An AE identifies a high-priority account and wants to reach out to the CISO. She searches ZoomInfo, finds a contact record with a title and email, and sends a templated cold email. The email addresses the CISO by name but is otherwise a category-level message about cybersecurity that could have been sent to any CISO at any company. The CISO receives 40 emails like this per week. Response rate: below 2%.
The reason the email is generic is not that the AE did not want to personalise it. It is that she had no raw material to personalise with. A ZoomInfo contact record contains a name, title, email, and phone number. It does not contain what the CISO said at a security conference six weeks ago, what blog post she published about her team’s approach to zero-trust architecture, what security incident she publicly addressed in the company’s investor materials, or what she recently endorsed on LinkedIn. Barie surfaces that raw material.
Barie retrieves recent public statements and professional context that make personalisation possible, not just name-insertion personalisable: An outreach email that opens with “I read your talk at RSA Conference on zero-trust implementation and noticed you mentioned API authentication as your current priority” is not a template. It is a conversation started from a specific, verified piece of public information that the decision-maker said. Barie finds those hooks.
Your prompt
Task prompt
“Find decision-makers at [Target Company], titles, professional profiles, recent public statements.”
1
Connectors Activated
Step 1: Connectors activated — each sourcing the specific intelligence type this task requires
Barie Research Stack · Live Intelligence
Parallel execution
Apollo.io
Queries Apollo’s database for current decision-maker profiles at the target company — CISO, VP Engineering, Head of IT Security, CTO, and any recently-hired security roles. Retrieves verified name, current title, LinkedIn URL, and email where available. Apollo’s real-time database is updated continuously from live professional network signals, meaning the title and role data reflects current employment, not a data refresh from three months ago.
Current titles · verified profiles
Firecrawl
Crawls the target company’s website for executive team pages, blog posts authored by identified decision makers, press releases quoting key leaders, and any published thought leadership content. Executive quotes in press releases are gold for outreach personalisation — they reveal what the decision-maker considers important enough to put their name on publicly.
Executive pages · authored content
Web Research
Searches for the identified decision-makers in conference speaker databases (RSA, Black Hat, InfoSecurity Europe, CISO XChange), industry publications (Dark Reading, TechCrunch, Fortune, CNBC), podcast appearances, and panel discussions from the last 12 months. Conference appearances and published interviews are the richest sources of recent public statements — the specific opinions, priorities, and concerns the decision-maker has voiced in their own words.
Conference talks · press · podcasts
Deep Research
Cross-references all retrieved information per decision-maker to identify the most relevant personalisation hook for your specific product. A CISO who spoke at RSA about API authentication complexity at scale, recently hired three DevSecOps engineers, and has a LinkedIn post about SOC 2 preparation provides three distinct, relevant, timely outreach angles. Deep Research identifies which of the available hooks is most aligned with your product’s value proposition.
Outreach hook identification
2
Output and Analysis
Step 2: The structured output — every finding sourced, every contact verifiable
6
Decision-makers identified with
context
context
3
Recent public statements per
contact
contact
100%
Claims sourced to live URLs
5 min
From prompt to full contact brief
Role context
CISO for 14 months. Joined during Series A. Oversees a security team of 8. Reports to CTO. Previously Head of Security at Cloudflare for 4 years. Owns vendor selection for security tooling with a known preference for developer-first tooling that does not create friction for the engineering team.
Recent public statements
“API authentication is the hardest part of our security posture right now — we have 400 APIs and the authentication patterns are inconsistent across the codebase.”
Recommended outreach hook
Open with the RSA Conference API authentication quote — she said this publicly and it maps directly to your product’s core value proposition. Reference the 400-API scale problem specifically. This is not a generic hook. She made the problem statement; you are responding to it.
3
Delivered to Your Tools
Step 3: Contact intelligence delivered to your sales and outreach tools
Apollo.io
Contact records created or enriched in Apollo with all retrieved data fields and outreach hook notes added.
HubSpot
Contact records created in HubSpot linked to the Company record with role context and outreach hook populated in the contact notes field.
Notion
Full contact intelligence report with all 6 decision-makers, role context, public statements, and outreach hooks documented.
Slack
Account team digest with the top 3 decision-makers, their recent statements, and the recommended outreach hooks.
Gmail
Draft personalised outreach email for the primary decision-maker using the specific hook identified in the contact brief.
Google Sheets
Contact intelligence spreadsheet with all 6 contacts, role context, outreach hook, source URLs, and outreach status.
Asana
Outreach tasks created for each decision-maker with the specific hook and the source URL for verification before sending.
Airtable
Contact intelligence database for the account with outreach stage, last contact date, and intelligence freshness tracking.
The Verdict
A generic cold email sent to a CISO’s name and title is not personalised outreach. It is a template with a field merged. Personalised outreach requires raw material — specific, current, verifiable things the decision-maker has said or done that make the opener specific to them rather than to the category. The CISO’s RSA Conference statement about 400 inconsistent API authentication patterns is not something that appears in ZoomInfo. It appears in a conference session recording that Barie found and surfaced as the opening hook for an outreach email that no other vendor will have written. That is the difference between a 1.8% response rate and a 14% response rate.
Barie features used in this task
Feature
ChatGPT
ZoomInfo
Barie
Recent Public Statement Retrieval — Conference talks, podcast appearances, and press quotes from the last 12 months surfaced with direct URLs for verification
✗
✗
✓
Cross-Referenced Outreach Hook — Best personalisation angle identified per contact from the intersection of their recent statements and your product value proposition
✗
✗
✓
Live Apollo.io Profile Data — Current title, LinkedIn URL, and verified contact data from Apollo’s continuously-updated database
✗
✗
✓
