Outreach CRM for broker-dealers
Personalized outreach to investors and issuers, built for firms whose email is regulated business communication. AngelSend keeps a record of every message before it sends, holds drafts for review, and enforces do-not-contact lists across the firm.
Why outreach is hard at a regulated firm
Sales tools are built to send more email. A broker-dealer has to be able to show what was sent, who reviewed it and why a person was contacted at all.
Every outreach email is a business record
Broker-dealers have long-standing books-and-records obligations for business communications. Under SEC Rule 17a-4, firms preserve the communications they send and receive relating to their business, generally for at least three years. Outreach to prospective investors and issuers is part of that business. A sequence that goes out from a sales tool your archive never sees is a gap, whatever the tool's other strengths.
The usual fix is a BCC to the archive on each campaign, and it fails quietly. One wrong address in a bulk edit, or one send path that skips the field, and messages leave with no copy kept. Nobody finds out until someone goes looking for the records.
Supervision needs something to review
FINRA Rule 3110 expects firms to have procedures for reviewing correspondence, and Rule 2210 sets content standards for communications with the public. AI-written email makes this harder. When every message is generated per recipient, there is no single template to approve. Reviewing the template no longer tells you what each investor received.
What supervisors need is a step where the actual message, the one that will be sent, can be read and approved or rejected before it leaves.
Do-not-contact has to hold across the whole firm
An unsubscribe recorded by one rep has to stop every rep. In most outreach tools, suppression lists belong to the user or the campaign, so a request to stop is honored by the person who received it and ignored by a colleague's sequence the following week. That is a CAN-SPAM problem and a reputational one.
Reaching investors and issuers without blasting
Capital raising depends on relationships with a short list of investors, family offices and companies, and that list does not recover from being spammed. Mass email also creates offering-rule questions. Whether you may contact a given person about a given offering depends on the exemption you rely on and your existing relationship with them.
Good outreach here is narrow: verified addresses, sensible daily volume, personal messages from a real mailbox, and follow-ups that stop the moment someone replies.
How AngelSend handles it
These are the records and controls AngelSend provides today. They support your compliance program. They do not replace it.
A record of every email, written before it sends
Switch on the compliance archive for a project and AngelSend keeps its own copy of every email sent from or received into it through AngelSend: campaign steps, follow-ups, replies, one-off compose and forwards. Each outgoing message is stored as the exact bytes handed to Gmail or Outlook, captured before the send. If that record cannot be written, the email is held rather than sent.
Append-only and tamper-evident
Archived records cannot be edited or deleted, and deleting a campaign, contact or user leaves them in place. Each record carries a SHA-256 fingerprint of the stored message and a hash that chains it to the record before it, so an altered or missing record breaks verification from that point on. A Verify integrity button recomputes both.
Search, read and export
Search archived mail by subject, address or message text, filter by sent or received and by date, and open any message with its headers and attachments. Export the results as a .zip of .eml files with a manifest listing each record's fingerprint, ready to hand to an examiner or load into another system.
A copy to your existing archive
If your firm already has an archiving vendor, set its capture address as the project's external archive copy. It is BCC'd on every email the project sends, including tests and API sends. It is added at send time, so changing it also covers mail that is already queued. Saving it checks that the mailbox exists. A bounce marks it as failing and alerts the project owner, and you can choose to hold sending until it is fixed.
Channels the archive can't keep are switched off
The archive records email. For a project that keeps one, AngelSend refuses to send text messages, AI voice calls and LinkedIn messages rather than let them reach the public unrecorded.
Past mail, brought into the archive
Archive history copies earlier sent emails and replies from the connected mailbox where they still exist. Where they no longer exist, AngelSend rebuilds them from its own send log and marks them as reconstructed, so imported history is never mistaken for an original.
Review before anything goes out
A campaign can be set to generate every email up front and hold it in the review queue, where a person reads, edits, approves or rejects each one before it sends. Reply drafts written by the AI land in the same queue for approval unless you turn approval off.
Do-not-contact lists that bind the whole firm
There are three do-not-email lists: your own, the project's and the whole team's. An address on any of them is blocked. When a recipient unsubscribes, AngelSend also adds them to the team list, so nobody at the firm emails them again. Adding someone cancels anything already queued to them. Block lists keep entire domains, such as existing clients or competitors, out of campaigns.
Verified addresses, not guesses
Address verification is on by default. NeverBounce checks contacts when a campaign launches, invalid and disposable addresses are left out, and scheduled sends check deliverability again before they go. Hard bounces are suppressed automatically.
Sent from your own mailbox
Connect Gmail or Outlook and email goes out from the rep's real address, with replies landing back in AngelSend's inbox. Each campaign has its own daily sending limit and sending days, so volume stays at a level that looks like a person writing.
Two-factor on the settings that matter
For users with an authenticator app set up, changing the archive address, connecting a mailbox, creating API keys or adding team members requires two-factor verification, even through the API.
An issuer funnel for prospective mandates
Investment banking and placement teams can score prospective issuers on sector, capital need, last raise and company stage, and rank them into tranches. Each issuer moves from identified through qualified, outreach, engaged and pitched to mandated or passed, with an append-only stage history. A deal is created at mandate. You run it through the AI assistant, the MCP server or the REST API. There is no dedicated screen yet.
A typical outreach cycle
- Step 1
Turn on the archive
In Settings, under Compliance, a project owner switches on the archive and, if the firm uses an outside vendor, adds its capture address and runs Verify & save.
- Step 2
Build a narrow list
Import contacts, verify their addresses, and let the do-not-email and block lists remove anyone the firm has agreed not to contact.
- Step 3
Generate and review
Write the sequence or let AI Mode draft it from your materials. With review before sending on, every personalized email waits in the review queue for approval.
- Step 4
Send, follow up, keep the record
Approved mail goes out from the rep's own mailbox within the campaign's daily limit. Replies come back to the inbox, follow-ups stop when someone answers, and every message sent or received is archived.
What AngelSend does not do
Regulated firms should know the edges of a tool before they rely on it. These are AngelSend's.
- AngelSend is not certified or attested as compliant with FINRA rules, SEC Rule 17a-4 or any other regulation. Its archive is append-only by database rules inside AngelSend. It is not a third-party-attested WORM or Rule 17a-4(f) electronic recordkeeping system. Firms with those requirements typically keep their designated archive and use the external archive copy to feed it.
- The archive covers email that goes through AngelSend. Mail a rep sends directly from Gmail or Outlook, outside AngelSend, is not recorded by AngelSend. Text, voice and LinkedIn are disabled for archived projects rather than recorded.
- The review queue is an approval step, not a supervisory system of record. It does not assign reviews to a designated principal, apply lexicon or keyword surveillance, or produce a supervision report.
- There are no retention schedules, legal holds or e-discovery case tools. Records are kept, not managed through a disposition policy.
- AngelSend does not check FINRA BrokerCheck or the SEC for anyone's registration. It has an early data model for broker-dealer firms, CRD numbers and Series registrations, each stamped with a source and last-verified date, but it does not look anything up for you.
- It does not decide whom you may contact about an offering, verify accredited-investor status, or review content for Rule 2210 standards.
- AngelSend is in public beta.
Questions we get
Keep reading
This page describes AngelSend's features. It is not legal, regulatory or investment advice, and nothing here means AngelSend satisfies any rule for your firm. Whether these records and controls fit your obligations is a decision for your compliance team and counsel. By Will Schulz, founder of AngelSend · Last reviewed
