Insights examples
Two concrete Insights: a recruiting agency that hears about US vendors expanding into Australia in time to partner, and a support team that calls churn-risk customers before they call in.
In short
These are standing questions, not one-off chats. Each one names the agents that already hold the facts, and the feed is what a person does on Monday morning instead of rebuilding the picture by hand.
Names, companies and tickets below are fictitious, in the shape of real briefings. Use them to picture the same pattern in your own desk.
GTM Intelligence: hear the expansion while there is still a first conversation
Who benefits. A recruiting agency whose go-to-market desk lives on inbound briefs. The partners they want are overseas vendors building an Australian team. Those vendors do not start with a job ad to agencies. They register an entity, hire a country manager, and take the first three roles to whoever calls that week.
The standing question. Find overseas and US vendors that are building or expanding go-to-market teams in Australia and New Zealand. For each one, say which sales roles are coming, which people in the network fit, and the warmest way in.
What the agents already know, without anyone asking this morning:
- The market-signals agent has the public record: Ferrous Analytics (US data software) appointed Tom Okafor as GM ANZ in Melbourne six days ago; Corvid Pay (UK payments) registered an Australian subsidiary in Sydney twelve days ago, with a first-quarter launch and no Australian jobs posted.
- The GTM desk agent has the private record: Ella Novak already knows Tom from his last company. Four days ago he told her he needs two account executives and one solutions engineer in Melbourne this quarter, budget approved, no agency briefed yet. Profiles for the solutions engineer are owed this week. Josh Whitaker, in Melbourne, has said he wants to join a US vendor's early ANZ team. A firm learning sits on that desk: a new ANZ country manager briefs an agency in the first month, and the first agency they speak to usually gets the first three roles.
The insight is already saved with that standing question and those two agents. On this account it has not been run yet, so there is no findings feed to show. The detail page is the setup: the objective, northlight-market-signals and northlight-gtm-desk, and a note to click Run now.
Nobody has to search for "US companies expanding into Australia" by hand. The market-signals agent already holds the public record as claims: Ferrous Analytics, Corvid Pay, Corvid Pay Australia Pty Ltd, and others.
Open Corvid Pay and the expansion signal is dated: UK payments company, Australian subsidiary registered, launch planned for the first quarter of 2027, no Australian roles listed yet.
A run that read those claims next to the GTM desk's notes on Ferrous and Tom Okafor would put those companies on the feed: why this week, who to call, and the warmest way in. Until someone clicks Run now, the work is already in those records.
What a run should surface. Ferrous Analytics, high priority. Why now: Tom is in seat, the roles are funded, he has not briefed anyone, and the profiles are due. Recommended: Ella sends the solutions engineer shortlist this week, with Josh Whitaker on it, and offers to partner on the two account-executive seats before another firm gets the first meeting. Corvid Pay sits beside it: a new Australian entity, no jobs out yet, and the desk already knows the usual first hire is a country manager.
What they do next. Ella sends the draft, marks the finding actioned, and the next run will not nag about the same facts. If Tom later names a start date or a second city, that new claim can surface a new finding.
What it leaves alone. A company in a hiring freeze, or one restructuring rather than hiring, does not appear. A news alert based only on keywords would have dumped those on the same list. The insight does not, because the agents' records say there is nothing to partner on.
The same pattern is how a BD desk hears a Series B and already has the candidate who named that company, with one consultant owning both relationships. That is a different insight (BD Signal Matcher) over a slightly different set of agents. The product is one feed; the objectives are sentences.
Proactive outage outreach: call before they call you
Who benefits. A broadband support lead whose morning is inbound tickets. Retention knows that customers who have to chase a credit after a run of outages leave at contract end. The people with the tickets and the people with the network incidents are not the same team.
The standing question. Find customers who have had repeated broadband outages in the last 30 days and are at risk of leaving. Say who to contact before they call, what to offer, and what fix or maintenance is coming.
What the agents already know:
- The support desk has Priya Raman, Northmead, a customer since 2019. Three full outages in seventeen days. She lost a client call, asked about a credit, mentioned a competitor, and said she will cancel at contract end if it happens again. The credit callback is still open and due. A learning on that agent: three or more outages in 30 days, call first with a credit; customers contacted first renew at a much higher rate. Another: anyone who mentions a competitor during an outage is the highest churn risk.
- Network operations has node NMD-07 in Northmead failing on the same rectifier fault. Permanent replacement is scheduled as overnight maintenance in five days, which will take her premises down for another three hours. A learning there: tell affected customers about planned maintenance at least three days ahead.
What the feed shows. Call Priya Raman today, high priority. Why now: third outage, credit still owed, competitor already in the conversation, and another planned outage she has not been told about. The draft names the dates, offers the credit, and tells her about the overnight window. It does not promise a date the network agent did not give.
What they do next. The lead (or the account manager) sends the note from their own mail, Mark actioned, and stops waiting for ticket 5244. When the maintenance window completes, that new incident can refresh the picture if something else is still owed.
What it leaves alone. Marcus Lee had one 40-minute outage from a modem update and was happy with the fix. Aiyana Brooks had one outage and was already credited the same day. A ticket count would have listed all three. A successful run lists Priya.
The insight is saved with that objective and the two Kestrel agents. A run has succeeded. On Insights, then Rules, Proactive outage outreach shows succeeded, with open findings.
The feed is the output. Priya Raman is on it, high priority, from Proactive outage outreach. Why now is the maintenance window and the credit still owed. Recommended is to verify which account is hers, send the maintenance notice, and follow up the credit callback. Mark actioned is there once someone sends the note.
Other desks, same shape
The mechanism does not change when the subject does.
| Insight | Who it is for | What a good finding looks like |
|---|---|---|
| Expansion and stalled-deal follow-ups | Account executives and customer success | An expansion signal before the budget locks, or a stalled trial about to expire, with the exact follow-up and why this week |
| Contract renewal risk | Legal and procurement | A vendor agreement that will auto-renew on terms that break policy, with the notice deadline and who must act |
| BD Intelligence | A recruiting BD desk | A hiring signal at a client or prospect before a role is advertised to agencies, plus who already owns the relationship |
| Candidate rediscovery | A recruiting delivery desk | A live brief matched to someone in the network whose latest conversation changed what they would consider, with the relationship owner |
In every case the time saved is the same: nobody rebuilt a 360 from three systems, and nobody asked a question the agents had already answered last week.