Customer research

Interview transcripts in, themes out.

## Active study

- **Question:** What are we trying to learn?
- **Status:** Recruiting / In flight / Synthesizing
- **Target:** N interviews

## Interview log

Use the **Interviews** surface: one row per conversation. Columns: date, name, role, company, transcript link, key themes.

## Quote bank

Use the **Verbatim quotes** surface. Pull the most-charged 1-3 sentences from each interview, tag with theme. This is the raw material every later artifact (decks, blog posts, internal pitches) reuses.

## Themes

The synthesis lives below. Update as themes solidify. Argus can draft the cross-cut from the quote bank when you ask.

### Theme 1: [name]

### Theme 2: [name]

## What we're not pursuing

Theme threads we noticed but explicitly aren't following. Documenting prevents rediscovery.

Fork to next cycle

When you're done, fork the workspace for the next cycle. The new workspace will be seeded with your structure, your customizations, and this cycle's retro as your agent's first Status entry — so it picks up context-aware from where this one left off. Same template, next cycle, no manual setup.