

When I started outbound, the job lived in two browser tabs, LinkedIn Sales Navigator in one and a Google Sheet in the other.
The first emails I opened with “Congrats on the new role!” beat everything else I was sending by a wide margin. Today, a newly appointed CMO gets 200 to 500 emails a day that open with those exact words.
We call this the wrong-signal problem. Funding rounds, executive hires, and job posts are still true signals, but every competitor sees them the same morning you do and writes the same email about them. The signals worth watching show what an account is living through right now, like a headcount ratio that doesn’t add up, something missing from a website, or a purchase approved in a school board’s minutes. They take work to find, which is why they still get a reply.
Below is a sample of our own library of non-obvious signals, how we read each one, an email built from a stack of them, and a 40-minute exercise to start your own. Treat our library as an example. The real advice is to build your own.
One reply I still think about was four words long: “certainly piqued my interest.” It came from a digital leader at a Fortune 500 manufacturer, and the email that earned it didn’t mention a new role or a funding round.
It pointed out the one place their website stopped letting customers buy on their own.
Obvious signals are the events any team can see with the same tools, like funding rounds, new executive hires, job posts, pricing-page visits, tech-stack changes, and layoffs.
They are real. A new leader reviews vendors, and a company that just raised spends.
In the early days, these signals worked because few teams were tracking them, and the ones that did found them by hand, one profile at a time. Every new platform made the same signals easier to find and act on, until tracking them took one click. According to Gong, a typical executive receives hundreds of cold emails each day.
Shared signals also come with shared blind spots. DemandScience’s own 2026 research found that 87% of intent signals never reach qualified pipeline.
At JumpSeat, we often explain this with a story from the California gold rush. George Hearst arrived in California in 1850 and, like almost everyone else, panned for gold near Sutter's Mill with meager results.
He switched to quartz mining, learned to read the veins in the rock, and in 1859 bought a one-sixth interest in the Ophir Mine in 1859. Flakes in the creek are visible to everyone. Veins take work to find, which is exactly why they pay.
A non-obvious signal is a concrete, current fact about what an account is living through that never shows up as an event in a standard data feed.
You find it by cross-referencing sources, calculating something, or knowing exactly where to look, like a ratio between two headcounts, a feature missing from a website, an item buried in public meeting minutes. A quick way to tell them apart is to ask who else can see it. If any competitor with the same tools would get the same alert, it’s obvious. If you had to go looking for it, it’s non-obvious.
That kind of digging used to cost an afternoon per account. Research workflows built in Claude or Clay now run it across a whole list, which is what makes this practical at scale.
My own test for telling a signal from trivia is simple. If I can’t say in one sentence why this fact makes the account more likely to buy now, it’s not a signal.
Here is a sample from our library. Each signal starts with who it’s for, then what we saw, what it may mean and why it isn’t in your intent feed. The first three also include an example from our own work. The reading matters more than the signal itself, because the same fact can mean different things for different offers.
Who it’s for: Web development and e-commerce agencies.
Signal: A manufacturer lets customers order some products online, while they can buy the rest of its catalog only through a sales rep.
What it may mean: The company already knows its customers will buy online, because they do it for part of the catalog. Bringing the rest of the catalog online is a specific, well-scoped project, and that gives a web development partner something concrete to propose.
In practice: For a web development client, we wrote to a digital leader at a global scientific manufacturer. The site had best-in-class online buying for consumables, while complex instruments still ran through sales. The email named that one gap. The leader replied with interest, and our client’s rep turned the conversation into an opportunity.
Why it isn't in your intent feed: It’s an absence, and you only see it by using the site. Intent data tracks what happens, not what’s missing.
Non-Obvious Signal: Sales, marketing, and business development add up to less than 5% of total headcount.
What it may mean: The company has grown faster than the team built to drive growth, so it is more likely to buy that capacity from outside: a marketing agency or an outsourced growth partner.
In practice: We call this one GTM Capacity Gap. Across 257 industrial, power and logistics accounts we scored in recent runs, it fired on 79, nearly one in three. One 1,000-person power equipment maker had four people across sales, marketing and BD.
Why it isn't in your intent feed: It's a ratio you calculate from two numbers. Nothing happened, so nothing fires an alert.
Who it’s for: Companies that sell to K-12 districts, like device management software, Wi-Fi and network infrastructure, and classroom tech accessories.
Signal: A public school board approves 400 new Chromebooks three weeks before a scheduled budget cut.
What it may mean: The district is spending ahead of a deadline, and 400 new devices create their own needs, like management software, cases and charging carts, and more wireless capacity. A vendor that reaches the technology director before the cut lands can offer the next purchase while the budget is still open.
In practice: In a Provo, Utah, school district, five minutes in public records turned up an approved 400-unit Chromebook purchase, a budget reduction scheduled for a later date, an upcoming wireless refresh, and a recently hired technology director.
Why it isn't in your intent feed: It lives in board meeting minutes, far from the web activity intent data measures.
Who it’s for: Companies that sell to K-12 districts, like device management software, Wi-Fi and network infrastructure, and classroom tech accessories.
Signal: 225 open job reqs concentrated in one function, alongside a new pricing model on the website.
What it may mean: The company is changing how it sells, and the team behind the new model has to grow fast. Every new hire also has to learn a pricing model the company hasn’t used before. A firm that can fill those seats quickly, or get new hires productive sooner, has a clear reason to reach out now.
Why it isn't in your intent feed: Each fact looks ordinary alone. The meaning is in the combination.
Who it’s for: Consultancies, training providers, and software vendors whose offer supports the way the company says it wants to work.
Signal: A CEO mentions a new internal methodology eleven times on a recent podcast.
What it may mean: Leadership has committed publicly to a way of working, so projects that help it take hold are likely to get priority and budget. A vendor that frames its offer in the CEO’s own words is pitching into an already-set priority.
Why it isn't in your intent feed: It’s spoken on a podcast, and intent data only measures what people search for and read.
A single signal rarely earns a reply on its own. As we put it in our Sunrise newsletter: "One signal is noise. Three correlated signals pointing in the same direction are intelligence." The work is finding signals that point the same way, then saying what they mean together.
Here is a real one. We reached out to the founder of a family-run trucking company in Chicago about our Signal Intelligence work. Two kinds of signal went into the email.
About the company
In its market
Every carrier read about the reclass, which makes it the obvious signal. A mattress plant across town is easy to miss. Put the two together, though, and they point to a local shipper that may be taking a fresh look at its freight, and possibly at its carriers. The email puts that shipper in front of the founder as a lead their own sales team could act on.
Here are the two paragraphs of the email that carry the signals, exactly as we sent them.
Reason for my outreach: saw you hit the 40-year mark this winter and are still hiring. Not many people start a truck line in Chicago and run it for four decades. Congrats.
We’ve already surfaced a few buying triggers in your market. Some are obvious, like the NMFTA’s density-based reclass going live and low-density shippers watching their freight classes jump. Others are non-obvious, like {{target_company}} running the old {{plant_name}} plant right here in Chicago. Mattresses are textbook low-density freight.
The founder forwarded it to the company’s VP of Sales, who reached out to ask whether we’d be a good fit for their business. That’s close to the best outcome a cold email can get, because the person you wrote to handed it to the person who owns the problem. And notice it still opens with a congrats. Not on a new role, but on forty years of running the same truck line.
The takeaway: build every stack in two layers. Signals about the company tell you why to reach out now. Signals in the company's own market give the reader something to act on, and that's what earns the reply.
Everything above came from our work, for our clients' offers. Copy it as is and you are back in the creek with everyone else, just a little further upstream. The teams that win build their own signal library, calibrated to their own wins. Three shifts get you there.
Calibrate against closed-won. Pull your last twenty closed deals and write down what was true about each account in the months before it bought. The signals that keep showing up become your library. The ones that never show up are noise, however clever they look. Expect to end up with fifteen to forty signals that actually track with revenue in your category.
Turn every signal into an implication. A signal is a fact. The implication is why it matters now. “Hired a new CRO” is a fact. “A CRO who scaled their last company 3x just joined one that has been flat for 18 months, on tooling that won’t get them there” is a reason for the call. Write the implication next to every signal, because that sentence is what ends up in the email.
Let signals change the list, not just the email. Signals should decide which accounts you work, who you contact, and in what order. Used this way, they shrink the list. Expect to prospect into 10% to 50% of the accounts you used to, with far more conviction about each one.
All you need to start is one account and 40 minutes.
Before you send it, try one test. Put a different company’s name into the opening lines. If they still make sense, go back to step 2 and dig further. If they fall apart, you’ve written an email only you could send.
Doing this for one account takes around 40 minutes of manual work. Doing it across every account on your list, week after week, takes a system. Signal Intelligence is a structured system that identifies, prioritizes, and activates the signals most relevant to a company’s revenue motion, so GTM teams can make shared, evidence-based decisions about who to target, when to engage, and what to say.
Curious which non-obvious signals sit behind your own closed-won deals? Start a Signal Audit, and we'll help you find them.
The obvious signals will keep filling inboxes. The non-obvious ones are still out there for the teams willing to look.
Martin Kriletich is a Senior GTM Engineer at JumpSeat, a B2B growth agency and advisory built around a signal-led approach to go-to-market. He designs and ships the outbound infrastructure behind that approach (signal frameworks, Fit and Conviction scoring, agentic workflows, and platforms integration), turning buying signals into pipeline for clients.