Three mornings a week
On Monday, Wednesday and Friday a research agent scans your markets and returns a short list. It carries a brief specific to your facility: where you are, what you can physically handle, and which public events imply demand for it. Larger terminals run several agents in parallel across different market clusters, and the results are merged and deduplicated.
It hunts for the events that precede a cargo booking. Engineering and construction awards, plant expansions and turnarounds, refinery, petrochemical, power and manufacturing phase transitions, transformer and turbine procurement, over-dimensional movements, and site congestion or laydown constraints.
Each run returns a handful of signals at most, and only those that clear a scoring floor. Fewer strong leads beat a long list of generic mentions.
What a signal contains
| Field | What it holds |
|---|---|
| Headline | One line naming what happened. |
| Narrative | Two or three sentences on the event and its logistics implication. |
| Why now | The urgency or timing that makes this worth a call this week. |
| Cargo types | What would actually move. |
| Use case | The terminal-side service the event implies. |
| Best target | Who to call: role, title and company. |
| Priority | A score from 0 to 100 from the agent’s own scoring model. |
| Confidence | A score from 0 to 100 based on source quality. |
| Category | Immediate outreach, research more, or monitor. |
| Sources | The specific pages the agent actually read. |
Why the sourcing matters more than the research
Anything can generate plausible leads. The failure mode for a product like this is confident, unsourced, or quietly fabricated research, and a terminal only has to be burned once to stop trusting the whole feed.
So sourcing is enforced rather than requested. A signal that cannot point at a real, specific, working page does not reach you: it is discarded rather than delivered with a caveat. Every link is fetched and checked before the signal lands, so a dead link or a vague gesture at a publication’s homepage does not survive the run.
The live link check exists because a customer told us a link was dead. That is the correct thing for a customer to care about, and it is now a machine step rather than a promise.
Encyclopedia entries are never acceptable as the support for a signal, and the agents are barred from handing your own terminal’s activity back to you as a lead.
Working the list
Signals land in a briefing view alongside your prospects and open opportunities. Each one can be marked in progress or followed up, with a note.
Two things about that are worth stating plainly, because people assume otherwise. There are only those two states: there is no passed or rejected status. And tracking is per user rather than shared, so two people at the same terminal do not see each other’s marks.
The digest
Anyone who wants it can opt in to an email digest on the same schedule, about an hour after the scans land. It covers everything new since your last send, so nothing is duplicated and nothing is skipped, and it goes to one recipient per send.