The problem this solves
The accounts that matter most are the ones nobody has time to watch. A named-account program picks 25 companies, and the plan is that each owner stays current on theirs; in practice the owners are selling, and the account that announced a new CEO on Tuesday is discovered in the following month's pipeline review. The information was public on Tuesday.
A weekly digest fixes the attention problem by concentrating it: one post, one line per account, only the accounts that changed, and a link for every claim. Read in two minutes on Friday, it tells the team which conversations to open on Monday and gives the leadership review a record of what moved across the whole program rather than what each owner happened to notice.
How the mission runs
- Read the 25 accounts. The Company Intelligence Agent loads list <name> and the baseline for each account from the previous digest - latest news items, funding state, leadership, open senior roles - so changes can be detected rather than restated.
- Check news, funding and leadership. Funding and news data are read for announcements since the last digest - rounds, acquisitions, partnerships, product launches - and people data is checked for executive appointments and departures, each with its source.
- Check for notable job posts. Hiring data supplies new senior or strategically relevant postings since the last digest - the roles you name, such as RevOps or Marketing Operations, plus any VP-level role - with title and posting date.
- Write and post the digest. One line per changed account is written - the account, what changed, why it matters in a few words - with source links, and the digest is posted to #accounts on Friday. Accounts with no change are listed in a single closing line so the team knows they were checked.
The prompt
This is the exact objective the agent receives. Swap the obvious placeholders for your own domain, segment or channel and run it as-is from the console, Slack, or the API.
What comes back
A Friday post in #accounts with one line per account on list <name> that changed during the week - news, funding, leadership changes, notable job posts - each with a source link and a short note on why it matters, and a closing line naming the accounts with no change. The digests accumulate into a week-by-week record of the named-account program.
Make it yours
- Send the digest by email to account owners with only their accounts included.
- Add intent surges on your category as a fifth change type.
- Post mid-week as well for a program with fast-moving accounts.
- Include a suggested action per change, drafted from the evidence, for teams that want the next step written.
Frequently asked questions
Why only 25 accounts?
Because a digest is read when it is short. The mission works for any list size; for larger lists, split into several channels or ask for the top changes only.
What if nothing changed at any account?
The post says so in one line with the check date, which is useful evidence that the accounts were watched and quiet.
Can the owner be tagged on their account's line?
Yes. Provide the owner mapping or read it from the CRM, and each line mentions the owner in Slack.
Can I ask follow-up questions in the thread?
Yes. Reply under any account's line and the agent answers in the thread with the full detail and the sources, keeping the digest itself short.
Does it include competitor news about the accounts?
Ask for it and the digest adds a line when one of the accounts is named in a competitor's announcement, such as a partnership or a case study.