# Signal-based outbound examples: 9 worked from signal to message. Each example goes from the signal, to the person worth messaging, to why now, to the message that went out. The companies and people are fictional; the patterns are the ones that work. **The short answer:** **A signal-based outbound example** has four parts: the signal (what the prospect or their company did), who to contact (the person who owns the problem), why now (what the signal implies about their situation this week), and the message (a short note about their problem, not about the signal). Public trigger events can be mentioned; private behaviour like a profile view or website visit should not. ## Every good example follows the same rule: the signal picks the person, the message is about them. Read the examples below with one question in mind: could the message have been sent without the signal? Usually the answer is yes. The signal did its work earlier, by deciding that this person gets a message today. That is the whole trick, and it is the part most vendors get wrong when they tell you to "reference the trigger". The exception is a public event about the prospect: a funding announcement, a job they posted about, a job ad. Mentioning those is ordinary conversation. Mentioning that you watched them is not. ### 1. Profile viewer, Head of Sales at a fit company - **Signal:** Priya, Head of Sales at Northwind (90 people, B2B logistics software), viewed your profile yesterday. - **Why now:** She was curious about you, and Northwind just launched a mid-market tier on its website. > Hi Priya, the new mid-market tier at Northwind looks like a different buyer from your enterprise accounts. Is the team prospecting that segment from scratch, or starting from accounts you already know? Built on one public fact about her company. The view is invisible. ### 2. Commenter on your post about SDR ramp time - **Signal:** Dana, VP Sales at Plotline, commented "our new reps lose the first month to research" on your post. - **Why now:** She described the problem in public, this week. > Hi Dana, your point about new reps losing their first month to research stuck with me. Is that account research, or working out who to go after in the first place? They need quite different fixes. Her comment was public and hers, so picking it up is natural. ### 3. Engager on a competitor's launch post - **Signal:** Tom, RevOps lead at Ledgerly, liked and commented on a competitor's product launch post, asking whether it works with their CRM. - **Why now:** He is comparing options this week. > Hi Tom, Ledgerly's US expansion probably means a lot more accounts for the same team. How are you deciding which accounts reps work first? Happy to share how a few finance software teams handle it. No mention of the competitor or the comment. The question meets him where he already is. ### 4. Identified website visitor on the pricing page - **Signal:** Brightline (fits your ICP) visited pricing twice this week. Company-level match only. - **Who:** Anna, the sales leader who owns the problem, found by normal prospecting. Not whoever the tool guessed. - **Why now:** Brightline opened a second office last month, publicly. > Hi Anna, congrats on opening the Austin office. New regional teams usually take longer to ramp than HQ, because nobody local knows the accounts yet. How are you getting the new reps up to speed? The visit set the priority. The message uses only public information. Check privacy rules before identifying visitors. ### 5. New VP of Revenue, week four - **Signal:** Sofia started as VP of Revenue at Fernway a month ago and posted about it. - **Why now:** She is diagnosing what to change, inside her first 90 days. > Hi Sofia, a month into the role I imagine you've seen where Fernway's pipeline really comes from. Most new revenue leaders find outbound looks fine until they check how many replies are real conversations. Is that on your list? The new role is public and mentioned in passing. The question is about what she is likely working on. ### 6. Past champion moves company - **Signal:** Marcus, who ran your product at his last company, just became Head of Growth at Brightline. - **Why now:** Champions bring tools they trust in their first weeks. > Marcus, great move to Brightline. If you want the same setup you had before, I can have it running in a week. If the team's different, tell me how and I'll be straight about whether it fits. Short, warm and honest. He already knows the product. ### 7. Hiring four SDRs - **Signal:** Plotline posted four SDR roles for EMEA; the ad says reps will "build their own prospect lists". - **Who:** Raj, the sales director the roles report to. Not the recruiter. > Hi Raj, saw Plotline is hiring four SDRs for EMEA, and the ad says they'll build their own lists. That's usually what slows new reps most. Will each rep research their own accounts, or is someone setting that up centrally? The job ad is public. The message reads it properly and asks about the problem behind it. ### 8. Series A, three weeks later - **Signal:** Ledgerly announced a Series A "to move into mid-market banks". - **Who:** Lena, Head of Sales, who owns that plan. - **Why now:** Week three: the congratulations wave has passed, and budgets are being set. > Hi Lena, the Series A note said mid-market banks are next for Ledgerly. That usually means procurement and risk teams in the deal, not just one finance lead. How are you mapping who to reach at each bank? It uses the announcement for its plan, not its money. ### 9. Stacked: competitor follower + new leader + hiring - **Signal:** Jordan follows two competitors, started as Head of Sales at Northwind six weeks ago, and Northwind is hiring three AEs. - **Why now:** Three weak signals add up to one strong one: new leader, building a team, already looking at the category. > Hi Jordan, six weeks into running sales at Northwind and already hiring three AEs, you're building fast. When new AEs start, where will their first pipeline come from: inbound, their own prospecting, or something you're setting up? Mentions the public facts (role, hiring), never the follows. ## Here is what a bad signal-based message looks like, and why it fails. *Don't:* > Hi Priya! Our tracking shows you visited our website and viewed my LinkedIn profile this week, and you also follow two of our competitors. Sounds like you're in the market! Can we book 30 minutes? Every fact in it is about your surveillance, none is about her. It tells her she was watched and assumes a decision she has not made. ## The pattern behind all nine. | Signal type | Mention it? | What the message is about | | --- | --- | --- | | Profile view, website visit | Never | A public fact about their company and the problem it implies | | Like on your post | No | The post's topic, through their situation | | Comment on your post | Yes, their words | What they said | | Competitor follow or engagement | Never | The problem both products solve | | New role, job ad, funding | Yes, briefly | The plan or problem the event creates | For how long each of these signals stays worth acting on, see [signal decay](https://signalbasedoutbound.com/signal-decay/). In Valley's 2025 data, warm and signal campaigns got 2.3x the reply rate of cold ones; messages like these are why. ### Should a signal-based message mention the signal? Only if it is a public event about the prospect, like a new role, a job ad or a funding round. Never mention private behaviour such as profile views or website visits. ### How long should a signal-based outbound message be? Short: two to four sentences, one specific observation and one question they can answer easily. Next: [the step-by-step playbook](https://signalbasedoutbound.com/playbook/), or [the profile viewers guide](https://signalbasedoutbound.com/signals/profile-viewers/). --- Source: https://signalbasedoutbound.com/examples/ Written by Zayd Ali, Founder & CEO of Valley (https://www.linkedin.com/in/zayd-syed-ali-4201101a9/). Published by Valley (https://joinvalley.co/?utm_source=signalbasedoutbound). Last updated 2026-10-27.