The 3 Evolutions of Outbound: Signal-Led, Scenario-Led, Relationship-Led

Signal-based selling was the GTM edge of 2024. By mid-2026 it's the floor. Cam Wright at Grafana Labs argues the new edge is scenario-led, signal stacks evidencing buying scenarios. He's right, and he stops one evolution short. Here's the 3-stage evolution of outbound, why scenarios aren't the end state, and what relationship-led actually looks like at scale.
Shankar Ganapathy
Co-Founder, Boomerang

Signal-based selling was the edge in 2024. By the middle of 2026 it's the floor. That's not a knock on signals. It's just what happens to any edge once everyone has it.

Cam Wright at Grafana Labs has the sharpest public take on what comes next: scenario-led outbound, where you treat signals as evidence of a specific buying scenario instead of triggers to spray against. He's right. He also stops one evolution short. The full stack is three layers: the signal tells you when, the scenario tells you why, and the relationship tells you who can actually get you in the room. The teams compounding outbound in 2026 run all three.

Let me walk the evolution, because the order matters.

Where signal-based selling came from

The 2022-to-2024 tooling wave sold one promise: detect the signal, time the outreach, win the meeting. Common Room, 6sense, Bombora, Demandbase, UserGems, Champify, Apollo's intent tier, Clay's signal stacks. Each got a turn on the funding podium.

The logic held. Cold-into-random accounts has terrible economics. Detect when an account is actually in market, a hiring spike, a funding round, a champion job change, and you sidestep the bad-timing problem. For the first teams to adopt it, the math worked. Some shipped 30 percent of pipeline through signal-triggered plays at peak.

Why signal-led plateaued

Two things happened.

First, the signal stack got commoditized. Every competitor now pulls the same job-postings feed, the same G2 alerts, the same intent flags, the same change-detection layer. When everyone in your category gets the same trigger at the same moment, the signal stops being a differentiator and becomes a queue. The buyer's inbox fills with nine vendors writing "noticed you're hiring an SRE" inside 48 hours of the post going live.

Second, the math reversed. Commsor's 2026 Warm Intro Gap Report (n=1,305 sales leaders) found outbound touches to book one meeting up 5x in five years, now at 1,400, with only 23.6 percent of leaders hitting their number in 2025. The buyer isn't ignoring you because the signal is wrong. They're ignoring you because the signal is in nine inboxes at once and the outreach reads as synthetic. The signal is real. The reply isn't.

Stage 2: Scenario-led (Cam Wright's framework)

Cam's argument: a signal is just a data point, useful only if it points to a reason to buy. Single signals are ambiguous. A job opening could mean growth, churn, or backfill. A bad G2 review could mean they're shopping alternatives, or that they just switched and feel fine sharing.

His fix is to build a scenario library before a signal library. For each scenario, write the current state, the negative consequences, the desired future, and how you uniquely help. Then watch for signal stacks, combinations that together evidence a specific scenario.

His Grafana example is precise. Hiring an SRE is weak alone. Hiring an SRE plus running three observability tools plus a recent public outage plus customer complaints about downtime is a strong stack. The four together evidence the buying scenario Grafana actually sells into.

Scenario-led works because it raises the precision floor. You stop reacting to every job posting and start reacting to the ones that, in context, evidence a motion you can win. Cam's right. And he stops one evolution short.

Stage 3: Relationship-led (where the next edge lives)

Scenario-led tells you why now. It doesn't tell you who can get you in.

Same Commsor data makes the point: 77.8 percent of sales leaders believe their team would be ready if cold outbound vanished overnight, but only 18 percent have a reliable warm-intro system. The market knows where this goes. It just doesn't have the system. That space, between wanting the warm motion and actually running one, is where relationship-led selling lives.

Be precise about what relationship-led means, because it's not what your VP of Sales asks for at QBR. A rep copying a Slack thread to a customer they half-remember, a founder pinging an investor every six weeks for a favor, that's random acts of intros. It's vibes. It doesn't scale, it isn't measurable, and it doesn't compound.

Relationship-led at scale is orchestration: a system that maps every warm path from your team, customers, investors, and advisors into your target list, scores each path, and routes the right ask to the right Super Connector for the specific deal. Signal-and-scenario tells you the motion is live. The relationship layer tells you who in your graph can put you in front of the buyer with credibility intact. Both required. Neither sufficient alone.

Why relationships are the next moat (when signals can't be)

Cam wrote one of the best sentences of 2026 on this: "A signal everyone has access to cannot, by definition, be an advantage. The only thing that can be proprietary is what you do with it." His extension: borrowed logic can't be an edge.

Here's the next extension, and it's the one Boomerang is built around. Borrowed relationships can't be an edge either, but yours can.

The team you spent years building. The customers who bet on you over the alternatives. The investors with portfolio overlap into your ICP. The board members you share with three other companies in their pipeline. Those are proprietary. A vendor can't scrape them and a competitor's feed can't replicate them. They compound when you orchestrate them and atrophy when you don't. That's the moat, and it's why scenario-led plus signal stacks is the second-to-last chapter of outbound, not the last.

The bigger shift: prospecting has been an SDR problem. It should be an executive one.

This is the part most teams miss, and the one most worth getting right.

For two decades we've treated the closing side as an executive priority. The AE executes, but the whole company shows up: sales engineers on the call, RevOps on the close plan, marketing on the case study, CS on the reference, the CRO late-stage, the CEO on the seven-figure deal.

Now look at prospecting. The SDR runs the motion. Who supports them? A manager, sometimes. A RevOps dashboard, occasionally. No executive sponsor. No CRO mapping her network into the target list. No CEO opening doors for the top 50. No board offering intros into their portfolio. No VP-level customer vouching to a peer.

That's why the prospecting team runs the same cold sequences as everyone else. Not a talent gap. A support gap.

The shift is to give prospecting the same executive backing closing already gets. The CRO's network is a prospecting asset. The CEO's investor relationships are prospecting assets. Customer champions at VP and C-level are prospecting assets. The board's connections are prospecting assets. All of it should feed the rep running outreach, the way sales engineering and RevOps feed the AE running discovery. Relationship-led activation is, structurally, that executive support layer for prospecting, and Boomerang is the system that turns it from a QBR talking point into a routed warm path the rep can use this week.

Which is also why orchestration beats data here. The CRO already knows she has a network. Getting it into the rep's daily workflow is the hard part. The data is the easy half. The orchestration that adapts to who's making the ask, on behalf of whom, to which type of Super Connector, is the half that's actually hard.

The four Super Connector types

The Warmbound motion has two halves, signals plus credibility, and the credibility half runs through Super Connectors. Four types, each different. You don't ask an investor the way you ask a customer.

Customer (fellow buyer): the highest-converting category. Someone who bet on you, signed, and made it work, vouching to a peer with the same risk profile. 50 to 75 percent on qualified intros. Use them when the receiving buyer is structurally similar.

Investor (favor economy): your investor, board member, or operating partner. The buyer takes the meeting to bank goodwill. Meetings happen reliably, then stall without real intent, so pair investor intros with strong signals and spend that goodwill like the finite budget it is.

Partner, OEM split (AWS, Salesforce, Shopify analog): credibility from technical co-positioning inside the buyer's stack. Use in deal positioning more than sourcing.

Partner, reseller split (SIs, channel, agencies): often vouching inside a paid relationship the buyer knows about. Real credibility, interpreted differently. Use in deal sourcing with co-sell economics baked in.

Orchestration that flattens these four into "ask for an intro" misses the point. The agentic layer adapts the ask, framing, and timing to how each type actually works.

The full stack

Signal-led plus scenario-led plus relationship-led, in sequence:

  1. Detect the signal stack. First-party (web, in-app, champion job changes) plus credible third-party (G2, named funding, BuiltWith). Skip generic intent unless it confirms something stronger.
  2. Match the stack to a scenario. Which motion in your library does this evidence? None, deprioritize. One, run that playbook.
  3. Find the warm path. Map the account against your graph, identify the highest-quality Super Connector path, score on credibility, accessibility, freshness.
  4. Match the ask to the type. Customer: peer endorsement, signal in the body. Investor: favor first, signal as the timing reason. OEM: stack positioning. Reseller: co-sell economics.
  5. Orchestrate end to end. Draft in the connector's voice, route for one-click approval, close the loop when the meeting books.

Boomerang is built for steps 3 to 5. Signal tools like Warmly (web de-anonymization), Clay (broader orchestration), and Claude Cowork (lighter) cover step 1. Step 2 lives in your scenario library, the proprietary GTM context Cam argues every team should own.

How to make the shift

Three moves, in order.

Audit your signal layer. What share of your outbound fires off generic third-party intent versus first-party plus credible third-party? If generic is over 40 percent of trigger volume, you're running an expensive cold motion with a signals story. Cut it, reinvest in scenario definition.

Build a scenario library. Three to five core scenarios, written the way Cam recommends: current state, negative consequences, desired future, how you uniquely help. Map each to the signal stack that evidences it.

Wire the relationship graph as the activation layer. Map team, customers, investors, advisors against your target list. Score the paths. Stand up the orchestration so the right ask flows through the right Super Connector per scenario. Doing this by hand at scale is exactly what produces random acts of intros, which is why the Commsor numbers look the way they do: 66.8 percent of sellers cite fear-based barriers to asking, and 48.5 percent call themselves relationship-led while only 18 percent have a reliable system.

Bottom line

Signal-based selling worked. Then everyone got the same signals. Scenario-led is the current edge, and Cam Wright has done the clearest writing in the category on how to run it. He's right about scenarios, signal stacks, and the context layer.

The next evolution sits on top of his framework. The signal stack tells you why now. The scenario tells you why this account. The relationship layer tells you who can put you in the room. Run all three and you compound. Stop at signals or scenarios and you plateau.

Borrowed signals can't be an edge. Borrowed logic can't be an edge. Borrowed relationships can't be one either. But the team you built, the customers who bet on you, the investors with portfolio overlap, the board you share with three other companies, that's yours. It's the one thing AI can't scrape, buy, or replicate. Orchestrate it.

For the relationship graph and activation layer, Boomerang is built for it. For the full Warmbound motion, see the Warmbound primer. For the strategy above it, see What is Go-to-Network. For the vendor landscape, see the warm-introduction software buyer's guide.