Skip to main content

Use Cases

Research

For strategy consultants, policy analysts, academic researchers, expert-network operators, journalists — anyone whose work is gather many sources, hold them in your head, synthesize on demand.

If your day looks like this​

  • You're juggling five-plus engagements or research threads at once, each with its own source library.
  • You read 30+ documents a week — PDFs, papers, transcripts, news articles, expert call notes.
  • You build market maps, briefs, and synthesis decks from a sprawling pile of inputs.
  • You'd love a memory that retrieves "who said this and where" without you tagging anything.

Set up first​

  1. One project per engagement or research thread — keep source bodies tight and unambiguous.
  2. A Methods project — your interview guides, frameworks, prior research designs, scoring rubrics.
  3. Forward every PDF, transcript, and article into the right project as you read it.

Use cases worth setting up​

Sourced answers across a project​

Forward 30 PDFs into a project. Then: "what does the literature say about [X]? Cite specific documents."

Deck answers with references back to the source. Useful for first-pass synthesis before you read deeply. See How to engage with your assistant.

Expert-call recap and theme extraction​

Forward transcripts from Fireflies, Granola, or your own notes. Ask: "across the eight expert calls I've done on [topic], what do experts agree on? Where do they disagree?"

The bigger your project gets, the more this pays off.

Market maps from inputs​

Drop company profiles, news articles, and analyst notes into a project. Ask: "give me a market map of [category]: who's a leader, who's a challenger, who's a fast follower. Cite the documents."

A starting structure your team refines, not a finished deliverable.

Weekly engagement digest​

For each active engagement, a weekly scheduled task: "summarize everything new in [Engagement] this week. Group by theme. Flag anything that changes a prior conclusion."

A discipline that's hard to maintain by hand becomes effortless.

"Where did I read that?"​

Two weeks into a project: "I remember reading that [vague claim] — which document was that in?"

The thing search engines are bad at and a good assistant is great at.

Synthesis drafts​

End of project: "draft a one-page executive summary of [Engagement] in my voice. Use the structure in Methods/exec_summary_template."

You edit — but you start with structure and citations already in place.

Standing literature watch​

Subscribe Deck to relevant arXiv alerts, Google Scholar alerts, SSRN feeds, journal table-of-contents emails. Weekly: "which new papers this week are relevant to my active research threads?"

You stop missing the paper that matters.

What good looks like after two weeks​

  • Every source is filed against the right project as you read it — zero tagging.
  • "Where did I read that?" is a sentence away from an answer.
  • Engagement digests are written automatically; you read and reshape.
  • New literature shows up in your inbox, filtered to what's relevant.