Section 1
Key takeaways
• Only ~5% of buyers in a category are in-market in a given quarter and ~20% in a year, the other 95% literally cannot buy today, so timing beats message volume . • A contact who has previously sat on a buying committee converts at nearly 3x the baseline (49% win rate), making the "champion move" the single highest-yield trigger to detect . • Buying windows are rare by design: roughly 80% of companies change banking services only once every five years, so any given account is buyable in a thin slice of time . • A purchase decision opens for a committee of 6 to 10 stakeholders, not one person, trigger detection has to find the account, not chase a single contact . • Never fire on one signal. Treat the first trigger as the window cracking and a second, confirming signal as the window opening, the discipline that separates noise from a real buying moment.
Section 2
Why your best message still gets ignored
Here is the uncomfortable math behind most outreach. In any category, the share of buyers actively in-market is small, about 5% in a given quarter, around 20% across a full year, which leaves 95% out-of-market at the moment you reach them . That isn't a deliverability problem or a copy problem. It's a calendar problem. You're knocking on doors where, by definition, almost nobody is home. Professor John Dawes of the Ehrenberg-Bass Institute puts it plainly: "If I'm chasing clients in commercial banking then it's useful to realise that in any given year only one in 10 of them will be looking to appoint a new bank or switch their lead bank." One in ten, in a year. That is the structural reality of selling to businesses, and it's why activity metrics lie to you. A rep can send 400 emails a week and feel productive while spraying almost entirely at accounts that have no open window. The reason windows are this rare is purchase frequency. Categories renew on multi-year cycles: roughly 80% of companies change banking services only once every five years, and about 75% buy new computers only every four years . Substitute your own category, managed IT, fractional CFO work, an agency retainer, a SaaS platform, a recruiting partner, and the cycle length is similar. Most of your market is mid-cycle on a decision they already made. They are not bad prospects. They are simply not due. This reframes the whole job. If the binding constraint is timing rather than persuasion, then the highest-leverage skill in outbound isn't writing, it's detection. You want to know which of the out-of-market 95% just became part of the in-market 5%. That's the entire premise of the 95-5 rule and its consequences for how you build demand, and it's why a Trigger Map outperforms a bigger send list.
Section 3
What actually flips a buyer in-market?
The academic name for "a situation that puts a buyer in-market" is a Category Entry Point, the trigger that makes someone go looking in the first place. For a service business, these aren't mysterious. They cluster into a small, recognizable set. Name them, and you can hunt them. Consider a fractional CFO practice. The accounts that close fast almost never arrive because the founder admired the pitch deck. They arrive because something happened: a board started asking for a real forecast, a fundraise put unfamiliar money on the balance sheet, a bookkeeper quit, a bad quarter spooked the CEO. Each of those is a different door opening. The pitch barely changed between the deals that closed and the ones that ghosted, the timing did. That's the core idea. Buyers don't flip in-market for abstract reasons; they flip because a concrete event made the status quo unacceptable or impossible. Your task is to enumerate those events for your category, then wire each one to a signal you can actually observe from the outside. Vendor guides that catalogue operational signals, pricing-page visits, leadership changes, funding, hiring surges, technology shifts, renewal timing, competitive research, are useful precisely because they translate fuzzy "intent" into things you can detect . A broader taxonomy groups roughly two dozen triggers into financial, organizational, market, operational, and digital-behavior buckets, which is a helpful way to make sure your own map isn't missing a category . But you don't need 24 triggers. You need the five-to-seven that actually drive your deals, in priority order. That's the Trigger Map.
Section 4
The seven triggers worth mapping
1. Renewal / contract clock. The incumbent solution is up in roughly 90 days. This is the most predictable window of all because it's literally on a calendar. The catch is that it's invisible from the outside unless you've captured it, which is why "when does your current contract end?" belongs in every discovery call, even with prospects who say no today. A "no" with a renewal date is a scheduled "maybe." 2. Bad result. A missed number, a churn spike, a failed launch, a public stumble, a compliance miss. Something made the current approach unacceptable. For an agency, the trigger is the client whose competitor just out-marketed them; for managed IT, it's the outage that made the board ask hard questions. Bad results are powerful because they convert a low-urgency "someday" into a high-urgency "now." 3. New hire / champion move. A new VP, CRO, or CMO arrives wanting to make a mark in their first 90 days, new leaders re-evaluate vendors as a matter of course. The higher-yield version of this trigger is the champion move: a past buyer or champion who already bought from you (or someone like you) lands at a new account. This is the strongest trigger in the entire map. Champify's analysis found that a contact who has previously sat on a buying committee is almost 3x more likely to buy again, converting at a 49% win rate . On a larger cut of the same data, 230,000 former champions across 7,000 opportunities, opportunities carrying prior buyer experience won at 37% versus 19% without, roughly double . When someone who knows your value changes jobs, a warm window opens at a brand-new logo. We go deeper on operationalizing this in the warm-network outbound playbook. 4. Funding / financial event. A raise, a strong quarter, an acquisition, a new credit facility, anything that unlocks budget that wasn't there last month. Funding is a classic trigger, but it's also the most over-played: every vendor emails the company the day the round is announced, which is exactly why funding alone is a weak signal (more on that below). 5. Launch / expansion. A new product, a new market, a new office, or a hiring surge that creates a fresh job-to-be-done. When a company opens a second location or spins up a new product line, it inherits problems it didn't have before, and often needs to buy its way out of them. A hiring surge in a specific function is one of the cleaner expansion signals because job postings are public. 6. Competitive / compliance pressure. A rival's move that raises the bar, or a new regulation with a hard deadline. Deadlines are gold because they remove the "do nothing" option, the buyer must act by a date, which compresses the sales cycle and kills the usual stall. 7. Research spike. Pricing-page visits, comparison searches, demo requests, repeat visits to your case studies, digital body language that says someone is actively shopping right now. This is the latest-stage trigger: by the time you see it, the window is already open and a committee is likely forming. Notice what these seven have in common: each is an event, not a trait. "Mid-sized SaaS company in fintech" is a trait, it tells you nothing about timing. "Mid-sized SaaS company in fintech that just hired a new CRO and posted four sales-ops roles" is an event stack, it tells you the window may be open. Good targeting filters on traits; great targeting fires on events. That distinction is the spine of how intent signals turn a flat prospect list into a ranked queue.
Section 5
When a window opens, it opens for a committee
A trap worth flagging: triggers tempt you to chase a single person, the new VP, the champion who moved, the founder who tweeted about a bad quarter. But the decision rarely belongs to one person. Most B2B purchases involve 6 to 10 stakeholders . So when you detect a trigger, the unit of work is the account, not the contact. Practically, that means a detected trigger should kick off account-level motion: map the likely committee, identify the economic buyer and the likely champion, and shape outreach for several roles, not one inbox. The champion-move trigger is so valuable precisely because it hands you a head start on that committee, you already have one member who's pre-sold. But you still have to win the other five to nine. Treating a trigger as a one-to-one event is how promising windows die in a single ignored email. Mapping the committee the moment a trigger fires is the bridge from LeadOS into the multi-threaded deal mechanics of ConvertOS.
Section 6
The detection problem: signal vs. noise
Here's where most trigger programs fall apart. The triggers are real, but a single trigger is noisy. A funding announcement gets blasted by every vendor on earth the same morning. A new executive's LinkedIn post might mean nothing. Reacting to one signal puts you in a crowd, shouting at a window that may have only cracked an inch. The fix is discipline, not more data. Salesmotion documented a case where a team saw a spin-off announcement, an obvious opening signal, and waited roughly three weeks to confirm a hiring wave before reaching out, then closed the biggest deal of the year . The lesson isn't "be patient" in some vague sense. It's that the first trigger told them a window might open; the second signal told them it actually had. The same source frames a tight response window once a real signal is confirmed: speed matters, but only after confirmation . This is the difference between a trigger and a confirmed buying moment. A funding round is an opening signal; the new "VP of RevOps" role posted three weeks later is the confirming signal that the money is being deployed against the exact problem you solve. A renewal date is an opening signal; a pricing-page visit from that account 75 days out is the confirmation that they're actually looking. Stacking two independent signals does two things at once: it filters out the noise that wastes your reps' time, and it tells you the window is genuinely open rather than merely possible.
Section 7
The BGA framework: the Trigger Map (and the Two-Signal Rule)
The Trigger Map is a one-page operating document plus a single firing rule. Build it once, wire it to detection, and your reps stop guessing who to contact today. 1. List your 5-7 triggers, in priority order. Use the seven above as a starting menu and cut to the ones that actually drive your deals. Rank them by yield. For most service businesses the champion move sits at or near the top because the data says prior-buyer relationships convert at roughly 3x baseline . Renewal and bad-result usually round out the top three. 2. Pair every trigger with a detectable signal. A trigger you can't observe is useless. For each row, write down the opening signal (what tells you the window cracked) and at least one confirming signal (what tells you it's open). Renewal → "contract end date captured in CRM" → "pricing-page or case-study visit inside 90 days of that date." Champion move → "tracked contact changes jobs to a target account" → "they post about hiring on your team or accept a connection." Funding → "round announced" → "relevant role posted within 30 days." 3. Assign a source and an owner to each signal. Job-change and hiring data, funding databases, website-visitor tracking, news alerts, and your own CRM renewal dates. If no one owns the feed, the signal won't get seen. Cheap beats nothing: a saved LinkedIn search and a CRM renewal report cover three triggers before you spend a dollar on tooling. 4. Apply the Two-Signal Rule before any rep touches the account. No outreach fires on a single trigger. One signal moves an account to a "watch" status; the second, independent signal promotes it to "contact today." This is the rule that turns a noisy list of events into a clean, ranked queue, and it's the single highest-ROI line in the whole framework. 5. Score and route, then move at the account level. When a window confirms, the unit of work is the committee of 6 to 10, not one name . Map the roles, identify economic buyer and champion, and route to the rep with the right relationship, the moved champion if you have one. You can pressure-test where your own pipeline leaks to see whether timing or targeting is your real constraint. 6. Review the map quarterly. Triggers drift. A regulation passes its deadline; a new competitor changes the pressure map; a channel that surfaced champion moves dries up. Re-rank by which triggers actually produced closed revenue last quarter, and retire the rows that didn't earn their place. The fully built-out version, with signal sources and routing templates, lives in the LeadOS playbook, and the ready-to-use detection checklists are in the template pack. A worked example. A 12-person managed-IT firm builds its map with three triggers: renewal (contract dates captured on every discovery call), bad result (monitoring news and local breach disclosures in their region), and expansion (job-board alerts for IT and ops roles at target accounts). They apply the Two-Signal Rule: a posted IT-manager role (opening signal) only becomes "contact today" when paired with a second office address appearing on the company site (confirming signal, they're expanding and short-staffed at once). Reps stop sending 300 cold emails a month and start sending 30 timed ones. The send volume collapsed; the meeting rate didn't, it climbed, because every email now lands on an account where a window is demonstrably open.
Section 8
You're running the Trigger Map right when…
You're running the Trigger Map right when a rep can answer "why this account, why today?" in one sentence, and the sentence names two signals, not a hunch. You're running it right when your outbound volume is down and your meeting rate is up, because you've stopped paying postage to the 95% who can't buy . You're running it right when a champion changing jobs triggers an alert the same week, not a discovery three months later . You're running it right when no rep fires on a lone funding headline, because the map says funding is an opening signal that has to be confirmed before anyone reaches out . And you're running it right when a confirmed trigger spins up account-level motion across a 6-to-10-person committee, rather than a single email to a single inbox that goes nowhere . If your team still measures itself by emails sent rather than windows detected, you don't have a Trigger Map yet, you have a send list.