Examples
These walk-throughs show Signal Outreach in action across the kinds of signals your firm sees most often. Details are illustrative; the steps reflect actual behavior.
Example 1: A Position Step-Up at a Mid-Tier RIA
Scenario: A signal posts to the signals channel reporting that an RIA in the Midwest stepped up a holding in one of the ETFs your firm distributes from roughly $4M to roughly $16M over the most recent quarter. Three advisors at that firm are mapped to your wholesaling team.
Step 1: Request. A wholesaler reads the signal post, recognises the firm from a meeting last quarter, and clicks "Draft Outreach Emails" on the post.
Step 2: Confirmation. A reply appears in the post's thread.
@Alpheous
Drafting outreach for 3 contacts at the firm.
Drafts will appear in your Gmail Drafts folder
as each one finishes. I will summarise here when
the batch is done.
Step 3: First draft lands. Within a minute, the first draft is in the wholesaler's Drafts folder. The opener cites the specific size move (the step-up from the earlier holding level to the current level); the middle ties the move to the recipient's channel and what their book is doing; the close offers a short call without naming a day or time.
Step 4: Batch complete. A second thread reply confirms the batch.
@Alpheous
3 drafts written to your Gmail Drafts folder.
All cleared compliance review on the first pass.
Step 5: Review and send. The wholesaler opens Gmail Drafts, reads each one, tightens a sentence in the second draft, and sends all three over the next ten minutes. Each recipient sees a different opener despite all three being tied to the same filing.
Example 2: A New Form D from a Sleeve Competitor
Scenario: A Form D signal posts: a competitor just filed a new fund in a sleeve that overlaps with one of your firm's products. Two advisors at a wirehouse branch are flagged because their book has historically allocated to that sleeve.
Step 1: Request. The wholesaler covering that wirehouse clicks "Draft Outreach Emails" on the post.
Step 2: Confirmation. Drafts queued for two contacts; thread reply confirms.
Step 3: Compliance pass needed. Each draft is written and reviewed. One draft mentions a specific category-flow figure that triggers a compliance rule hit. The agent rewrites it with the figure removed and the framing changed to a neutral observation about the sleeve. The rewrite clears review.
Step 4: Batch complete. Both drafts are in Drafts.
@Alpheous
2 drafts written to your Gmail Drafts folder.
1 needed a compliance rewrite (now resolved).
Read both before sending.
Step 5: Review and send. The wholesaler reads the rewritten draft carefully, tweaks one phrase to sound more natural, and sends both. The recipients see a short, plain note about a new competing product in their sleeve and an offer to walk through the comparison; neither email names the underlying filing type.
Example 3: A Regulatory Window Affecting Plan Coverage
Scenario: A regulatory-window signal posts noting a compliance review cycle that affects retirement plans of a certain size band. Five advisors with plan-related books at four different firms are matched.
Step 1: Request. The wholesaler reads the signal in the morning, recognises that this is the kind of timing trigger that calls for outbound, and clicks the button.
Step 2: Confirmation. Drafts queued for five contacts; thread reply confirms.
Step 3: Drafts trickle in. Over the next few minutes, five drafts land in Gmail Drafts. Each opener leans on the timing of the review cycle; the middles are different because the recipients are at different firms with different book profiles; the closes vary across a short call ask, a one-pager offer, and an offer to share a benchmark.
Step 4: Batch complete.
@Alpheous
5 drafts written to your Gmail Drafts folder.
All cleared compliance review on the first pass.
Step 5: Review and send. The wholesaler reads the first three carefully, sends them, and decides the fifth contact is too cold for a regulatory-window angle. They discard that draft in Gmail; nothing else needs doing.
Example 4: A BrokerCheck Update on a Long-Tail Advisor
Scenario: An IAPD update signal posts noting a new disclosure on the BrokerCheck record of an advisor who is mapped to a wholesaler's territory but has had no recent activity in the system.
Step 1: Request. The wholesaler decides this is worth a careful, low-pressure touch and clicks the button.
Step 2: Confirmation. A single contact in scope; one draft to write.
Step 3: Thin briefs. The advisor has minimal context in the firm's records: a name, a firm, a title. The agent does not invent specifics. It writes a 70-word draft that names the change in business language, references the advisor's channel without inventing AUM figures, and closes with an open question rather than a meeting ask.
Step 4: Batch complete.
@Alpheous
1 draft written to your Gmail Drafts folder.
Cleared compliance review.
Step 5: Review and send. The wholesaler reads the draft, finds the tone right for a long-tail advisor with thin history, and sends it without edits.