How Barie drafts personalised outreach emails for 10 prospects based on each company’s recent news — then sends them via HubSpot
Barie researches each of the 10 prospect companies from the live web simultaneously, identifies the most relevant, recent development for each, drafts a personalised email anchored to that specific context, and sends each email through HubSpot via Connector. Ten research threads, ten personalised emails, ten sends. One prompt, zero tab-switching.
Why personalised outreach at scale collapses into templates with a name merged in
A sales rep has a list of 10 prospects to contact this week. She knows that personalised outreach outperforms templates by a factor of 3 to 5 on reply rate. But true personalisation requires research — what has the company been doing recently, what did the decision-maker say publicly, what trigger event makes this the right moment to reach out? That research takes 20 minutes per prospect. Ten prospects is over three hours of research before a single word of the email is written.
So she does what every rep does when facing three hours of research for a single outreach cycle: she uses a template with the company name merged in and calls it “personalised.” The recipient reads the first sentence and immediately recognizes it as a template. The response rate is below 2%. The issue is not that the rep failed to personalise — it is that true personalisation at scale was not humanly achievable in the available time. Barie makes it achievable because it researches all 10 in parallel.
Your prompt
Step 1: Four connectors activated — research, draft, and send in a single execution chain
Step 2: Two of the 10 drafted emails — each anchored to a specific, current, verifiable hook
unique per company
tracked
Sarah Chen · CISO · Velosync AI
Hook: RSA Conference API auth statement
Hi Sarah,
I caught your session at RSA last month where you mentioned Velosync is managing authentication consistency across 400 APIs — and that inconsistent patterns across the codebase are the current hard problem for your security team.
That exact scenario is where our customers were before implementing [Product]: multiple API authentication patterns, no central enforcement layer, and a sprawling codebase that made auditing painful before every compliance review.
We recently helped a SaaS company at a similar scale — 360 APIs post-Series B — get from scattered authentication patterns to a consistent, auditable layer in under 60 days without requiring changes to existing API code.
Would a 20-minute call make sense this week? I would be happy to show you how that implementation worked.
Marcus Rivera · VP Engineering · Clarifio Analytics
Hook: EU expansion announcement + DevSecOps hiring
Hi Marcus,
Congratulations on the EU expansion announcement last week. I noticed Clarifio is currently hiring three DevSecOps engineers — which typically signals either a compliance push or a significant infrastructure scaling initiative, often both when an EU launch is involved.
GDPR-compliant API security documentation and authentication audit trails are the two areas that tend to catch engineering teams off guard in EU market entry. They are also the two areas we see the most traction with SaaS teams at your stage.
I do not want to assume that is your current pain point, but if it is, I have a short case study from a RevOps SaaS company that went through exactly this during their European launch that might be worth 10 minutes of your time.
