News Manager Use Cases
Three concrete workflows so you can see how the same News Manager pipeline fits different kinds of work.
What you'll learn
- How a solo creator aggregates a single industry.
- How a small news team triages a busy queue.
- How to run a competitive or market watch.
The concept: same pipeline, different rhythm
Every workflow below uses the same four stages — Scout, Extract, Evaluate, Generate — and the same controls: brand-scoped sources, categories, excluded topics, scheduling, and selection-only AI. What changes is the rhythm: how many sources you follow, how often you scout, and how much you lean on the AI steps. All three assume you've set the brand's primary locale and added an AI key for the brand.
Workflow A: the niche content creator
You run a brand around one industry and want a steady stream of post ideas without reading a dozen sites each morning.
- Add a handful of trusted sources in that industry with Adding a News Source, labelling them all with one category so the queue stays focused.
- Schedule scouting daily. Each morning, new articles are waiting, deduplicated by the dedup mechanism. Run Extract so the full text is ready.
- Skim and select. Tick the few articles you find genuinely interesting, run Evaluate to confirm relevance, then Generate to get drafts.
- Edit and publish the drafts that earn it. The AI only touches the rows you picked, so a quiet day costs almost nothing in tokens.
Sharpen the brand's Positioning and the evaluation prompt over the first week so approvals match your taste.
Workflow B: the small news team
You cover a beat and need to move faster than the queue fills up. (Team accounts are live — invite members and split the beat between them, or run it solo across categories.)
- Add many sources and split them across categories — one per sub-topic — so you can filter the queue by area.
- Set excluded topics for subjects outside your beat. Evaluate hard-rejects those before anyone spends time on them.
- Scout on a frequent schedule so the queue stays current through the day.
- Triage by selection. Filter to a category, select the stories worth covering, and run Evaluate and Generate on just those.
- Polish the drafts. Generated drafts land in Content in a planning state, where you finish and publish them.
Workflow C: competitive and market watch
You want to track what competitors and the wider market are saying, without turning every mention into a post.
- Add competitor blogs and market-news feeds as sources, grouped under a category like "watch."
- Lean on Evaluate, not Generate. Run Scout and Extract to gather everything, then Evaluate selected items to see what's actually relevant — and read the skip reasons for the rest to understand the landscape.
- Generate selectively. Only when something is worth a public response do you run Generate to start a draft.
- Use excluded topics to cut recurring noise — promotions, hiring posts, or any subject you never want to react to.
Here the value is mostly in the filtered, scored reading list. Drafting is the exception, not the default.
FAQ
Can my team share a News Manager queue with separate logins? Yes. Members with access to the brand see the same queue under their own logins. There is no per-row claim marker yet, so split the work by category to avoid double-handling.
Which workflow uses the least AI spend? The competitive watch — it leans on Scout and Extract (no AI) plus selective Evaluate, and rarely runs Generate. Evaluate and Generate only ever run on rows you select.
Can one brand mix workflows? Yes. Categories let you run a daily-creator flow and a competitive-watch flow in the same brand by filtering to different categories.
How do I keep a high-volume queue fast? Use Cleanup to slim aged and skipped items, and lean on categories and status filters. Cleanup keeps the dedup fingerprints, so cleared stories don't return.
What's next
- Review the pipeline in The News Manager Concept.
- Set up your first feed with Adding a News Source.
- Tune relevance in The Evaluate Stage and drafting in The Generate Stage.