The blog · GTM Systems · From The Demand Compass · 7 min
Why does my intent tool show no intent in my market?
A quiet intent tool rarely means a dead market. It means only capture was built, with nothing on the awareness side to create the signal it is waiting to catch.
An intent tool that stays quiet almost never means the market went cold. It means the system that feeds it only has one of its two jobs built. Capture finds a signal that already exists and acts on it; creation builds the awareness that makes a signal appear in the first place. A team that buys an intent feed, wires up routing and waits for accounts to light up has built capture alone, and a radar with nothing moving toward it reads as silence no matter how good the vendor is.
Why does an intent tool show no intent when the market is fine?
The market is usually fine. The team's Signal Radar, the part of the system that reads every account's activity across both axes, has nothing to read because too few accounts have crossed from cold into aware. Almost nobody tries to measure awareness on purpose; almost everybody assumes readiness is already solved once an intent tool is switched on. The tool is real and does what it says. The reading falls apart because a signal has to exist before any tool, however good, can catch it.
A quiet radar is usually a confession that only half the system exists, not a finding about the market.
Refuse "there's no intent in our market" as a conclusion. It is close to always a description of an incomplete system: the sensor is on, and the motions that would give it something to sense were never built.
What is the difference between demand capture and demand creation?
Demand capture finds a buying signal that already exists in an account and acts on it; demand creation builds the awareness that makes a signal appear at all. An intent tool, a signal radar, a routing rule, every one of these is capture. None of them makes a single new account start reading your pricing page, starring your repository or asking about you in a community thread. That has to come from somewhere else, and the somewhere else is demand creation, the deliberate work of moving an account from never having heard of you to knowing you exist. Skip creation and demand capture has nothing arriving to catch.
What are the four motions that keep the Market Map current?
Four motions keep the Market Map, the single account-level view of where every company in your addressable market sits and which way it is moving, honest and current. Three of them build awareness, the axis a team has to develop on purpose. The fourth converts.
- Outbound. Reaches cold accounts directly and makes them aware for the first time.
- Inbound. Attracts accounts in, pulling them toward you rather than reaching out.
- Nurture. Keeps an aware but not-yet-ready account warm until its readiness rises on its own schedule.
- Activation. Fires when the Radar catches an already-aware account starting to move on either axis, and closes it fast.
| Motion | Builds or converts | What it does |
|---|---|---|
| Outbound | Builds awareness | Reaches cold accounts, makes them aware |
| Inbound | Builds awareness | Attracts and pulls accounts in |
| Nurture | Builds awareness | Keeps the aware but not-ready warm |
| Activation | Converts | Acts fast the moment the Radar catches movement |
Only the fourth motion converts. Outbound, Inbound and Nurture exist to fill the Map with accounts the Radar can then watch. A team with strong Activation and nothing upstream of it is running a radar over an empty sea.
What happens when a team builds only capture?
Picture a marketing leader doing everything that looks right: a webinar series pulling in four hundred registrants, content getting traction, paid campaigns producing leads. Every quarter-end pipeline review still feels like a guess, a good month followed by a quiet one, because campaign-based demand generation is effort-dependent by nature. Pipeline stays proportional to whatever activity is running right now, so the moment the team is short-staffed or the budget tightens, pipeline follows it down. That is not a worse campaign. It is the same structural problem as a single point of failure, wearing a marketing costume, and no amount of tuning the intent tool fixes a structural gap upstream of it.
The same instinct that skips creation shows up as a preference for renting over owning. When automate rev.ops. needed that new landing page, Marcos built it himself with AI and a designer friend's feedback for about fifty dollars, instead of paying out the thousand-dollar quote to outsource the same job. Owning the capability instead of renting it is the same discipline as building the awareness motions instead of only buying the sensor that reads them: a rented capability, like a bought signal with nothing feeding it, is a dependency wearing the costume of a solution.
How do you diagnose which half of the system is missing?
Draw the Map, then list every tool and activity currently running under the motion it actually serves: Outbound, Inbound, Nurture or Activation. Two things tend to jump out immediately. Most of the spend clusters into a single motion, usually Activation or Outbound, and at least one of the other three sits nearly empty. If the empty one is on the awareness side, that gap is the reason the Radar feels quiet: nothing is moving accounts from cold to aware, so almost nothing ever crosses into the readiness the tool was bought to catch.
A win is not the end of the wheel, either, and this is where teams that do build both halves still leave signal on the table. A closed account does not drop back to cold Outbound; it stays in Nurture, warm and watched, because the same Radar that caught the first deal keeps reading the account afterward. When a new signal fires inside it, a new team standing up, a fresh burst of product usage, Activation runs again, this time toward expansion. The cheapest readiness a team will ever detect is inside an account that already bought, and a system built only for new-logo capture throws that away by design.
Why does the flywheel compound once both halves exist?
Once creation and capture both run, they stop being additive and start compounding. The awareness the three building motions create makes the readiness the Radar catches convert at a higher rate, because an account that already knows you answers differently than a stranger. The deals Activation closes fund more Outbound, Inbound and Nurture, and the loop turns again, each pass stronger than the last. A checklist gives back only what was put in. A flywheel raises its own baseline every turn.
Related questions
Could my market genuinely have no buying activity right now?
It happens, but rarely, and only after the awareness motions have actually been running for a while. Check the Map first: if most accounts are still marked cold because nothing has ever reached them, the tool has nothing to report regardless of what the market is doing.
How long should I run an intent tool before concluding it isn't working?
The tool itself works the moment it is switched on; what takes time is the awareness that gives it something to read. Judge it against how many accounts have moved from cold to aware, not against how many weeks have passed.
Which motion should a team with only Activation build first?
Whichever one is cheapest for that business to stand up, usually Outbound, because it does not depend on someone else finding you first. The point is coverage across all three awareness motions eventually, not picking a permanent favorite.
Do Inbound and Outbound compete for the same budget?
They do at any given moment, but they are not substitutes. Outbound reaches accounts that would never have found you on their own; Inbound catches the ones already circling. A market fully covered by one still leaves the other's accounts invisible.
Does a Signal Radar replace the need for a Market Map?
No, they are two halves of the same system. The Radar is what reads each account's activity; the Map is where every account's resulting position lives. A radar with no map just produces alerts nobody can place in context.
