What has to be on a signal card before a rep should work it?
Five parts, and a card missing any of them is not ready. One, the trigger, stated as a label a human can read. Two, the source link and the date it happened, which are two attributes and one part because neither is useful alone. Three, the consequence: one sentence naming the operation that gets harder in the next thirty to ninety days. Four, the person who feels it, as a role at minimum. Five, the angle: what this means you would actually say.
The rule that makes it work is what happens when a part is missing. The card does not ship with a blank field and a note that it needs research, because that card ends up worked anyway by whoever is behind on activity. It goes to a separate needs-work queue with the missing part named, so the stack a rep opens in the morning contains only complete cards. A partial card in the main stack is worse than no card, because it teaches the team that the stack is not trustworthy.
The five parts and what each one prevents
Each part exists because of a specific way outbound research fails. Read the failure column first. If you have watched a team work signal alerts for a quarter, you will recognize all five, and you will probably recognize which one your current process is missing.
| Row | Part | What it is | The failure it prevents |
|---|---|---|---|
| 01 | 1. The trigger, labeled | A short human-readable statement of what happened, at a named company. | Raw feed items that a rep has to interpret before deciding whether to care. If the label does not survive being read out loud, it is not a trigger yet. |
| 02 | 2. The source link and the date | The URL where it was read and the date it happened, not the date it was found. | Two failures at once. Without the link, a rep cites something they cannot verify and a buyer corrects them on the call. Without the date, the stack cannot be ranked, because ranking a week is mostly a freshness problem. |
| 03 | 3. The consequence | One sentence: because of this, that operation gets harder in the next thirty to ninety days. | Congratulations emails. The consequence is the connective tissue between an event and a reason to write, and it is the part that makes the same event a strong reason for you and a nothing event for the vendor next to you. |
| 04 | 4. The person who feels it | The role that absorbs the consequence, plus a name when one is actually available. | The CEO receiving every email. If the only owner you can name is the founder, the card is telling you the function does not exist yet, which is useful information and not a send. |
| 05 | 5. The angle | What this means you would say, tied to the mechanism linking trigger to consequence. | A card that is correct and unusable. A rep who agrees with all four earlier parts and still does not know how to open the note will default to a template, which discards the work. |
Drop rules, which matter more than scoring
Most of the quality in a signal stack comes from what never appears in it. Scoring decides the order of what survives; drop rules decide what survives at all, and they are the cheaper lever by a wide margin. A stack of eight complete cards beats a stack of forty where a third are thin, because the second one costs a rep judgment on every row and judgment is the scarce thing in a morning.
- Undated: dropped. A development with no date cannot be ranked and cannot be referenced without sounding like you found an old article.
- Source link not traceable to something actually read: dropped. A citation must point at the specific page the claim came from, or it is decoration.
- Weak consequence: dropped. They will need better tooling is a product description, not a consequence. The sentence has to name an operation, a direction, and a window.
- No role that feels it: dropped. An event nobody owns is news.
- Below the confidence bar: dropped rather than shown with a caveat. Caveats get skimmed and the account still ends up in the queue.
The last one is worth sitting with, because it is the rule teams find hardest to adopt. Showing a weak card with a warning label feels generous and is not. It moves the judgment onto the rep at the exact moment they are least equipped to make it, which is first thing in the morning with a number to hit.
How to rank what survives
Once only complete cards are in the stack, ranking is a small problem. Four factors are enough: how well the account fits what you sell, how fresh the trigger is, how well this kind of trigger has worked for you before, and how confident the judgment is. Multiply rather than add, because a zero on fit should not be rescued by a very fresh trigger, and freshness should not rescue an account you would not want as a customer.
- Fit
Does this account look like the ones you win? This is the slow-moving factor and the one you probably already have an opinion about.
- Freshness
Decay per trigger type, not with one global cutoff. Acquisitions stay useful for a couple of quarters; a product launch is stale in weeks.
- Efficacy
How this trigger type has performed for you specifically. Start with a flat prior and let your own replies move it. Do not import a benchmark, including from a page like this one.
- Confidence
How sure the judgment is that the consequence follows from the trigger. Low confidence should mostly have been a drop, so this factor is a tiebreak among survivors.
Cap the daily stack at a number a person can actually work, and let the cap do the arguing. If eleven cards clear the bar and the cap is eight, three wait until tomorrow. That is a better outcome than a rep skimming eleven and working four at random.
Close the loop with dismissal reasons
A card that gets dismissed is the most valuable feedback in the system, and most teams throw it away by making dismissal a single button. Make the rep pick a reason from a short fixed list, because the reasons map cleanly onto different fixes and an unlabeled dismissal maps onto none.
- Wrong person: the who step is misfiring. Fix role mapping before you touch anything else.
- Too old: your freshness windows are too generous for that trigger type.
- Not a trigger: your drop rules are too loose, and this is the one to act on fastest.
- Bad fit: the fit definition is wrong, or the market description is too wide.
- Already working it: not a quality problem at all, a deduplication problem against the CRM.
Read the distribution monthly, not the individual dismissals. If one reason is most of the volume, you have found your next fix and you did not have to run a survey to get it.
This is what the category calls signal cards, why-now briefs, and account research.
Vendors call this unit different things: a signal card, a why-now brief, an account snapshot, a play. The name does not matter. What matters is whether the unit is complete enough that a rep can act without doing a second research pass, because the second pass is where the time savings the tool was bought for quietly disappear.
The useful way to evaluate any of them is to ignore the count of signals and ask for ten real cards. Check each one for the five parts. A tool that shows you thousands of signals and hands over cards missing the consequence has moved the hard part back onto your team and charged you for the easy part.
Questions people ask next
Is five parts not a lot to ask for every account?
It is, and that is why the honest output is a small stack rather than a long list. If your tool or your process can only produce complete cards for eight accounts a day, the right answer is eight cards, not forty with gaps. The gaps do not disappear when you ship them, they just move onto the rep.
What goes in the needs-work queue, and who works it?
Cards with a trigger and a source but no stated consequence, or no role that owns it, with the missing part named. Someone who knows the market can often close the gap in two minutes, and they will do it far more reliably when the queue is separate and the gap is labeled than when the card is sitting in the main stack looking almost finished.
Do you need a named person, or is a role enough?
A role is the minimum and is often better than a purchased contact, because a rep who knows the account will pick the right person faster than a database will. Put a name on the card when your own CRM already has one or when the cited source names them. Buying contact resolution to fill the field adds cost and a hard dependency on a part your team usually knows better.
How do you stop the same account appearing every day?
One card per account per day, and a check against what is already being worked in the CRM. Repetition is the fastest way to train a team to stop opening the stack, and it is usually a deduplication bug rather than a signal problem.
Where to check this yourself
Primary records and published research, not vendor blog posts. Every link was checked on September 1, 2026.
- SEC EDGAR full-text searchsec.gov
A primary record you can cite on a card: filings including 8-K item disclosures and Form D notices, with filing dates.
- SEC list of filing formssec.gov
Which form carries which corporate event, useful when you want the label on the card to be precise about what happened.
- USAspending.govusaspending.gov
Federal award data with dollar values and periods of performance, a dated public source that supports a consequence sentence directly.
- US Department of Labor, WARN Actdol.gov
The federal notice requirement that makes layoff notices public and dated, and the basis for state notice lists.
- The Bridge Group, SDR Models and Metrics researchblog.bridgegroupinc.com
Published survey research on sales development structure and activity, useful for sizing a realistic daily card cap.
This is the shape of what Intakra prepares: a labeled trigger with its dated source, the consequence, the role that feels it, and the angle. Anything missing a part lands in a needs-work queue with the gap named, rather than in the stack you work on Monday.
Free scan, no signup, no card