"Codex in Practice" — @LauraEntis
Why this is in the vault
Real-team Codex playbooks from Every's own staff — concrete use cases in CRM enrichment, inbox management, and personal ops that map directly to the RDCO agent-as-COO operating model.
⚠️ Sponsorship
Self-promotional: Every gates the full team-setups section behind a paid subscription and promotes its own software bundle (Sparkle, Cora, Spiral, Monologue). No paid third-party sponsor. The free email portion contains the Natalia Quintero use cases in full; the Dan Shipper / Katie Parrott / Austin Tedesco / Kieran Klaassen setups are paywalled.
Issue contents
Framing: Codex is versatile enough to reshape itself around any workflow — but that flexibility creates onboarding paralysis. Every's answer: show concrete team use cases rather than capability lists.
Natalia Quintero (head of consulting) — AI & I episode:
- Codex as lower-friction Claude Code. Natalia previously spent significant time manually architecting folder structures in Claude Code. Codex builds those structures automatically as she works. "I can just trust it to make good decisions and build solutions for me." Workflow: open the day's priority Codex project and work from it; the app maintains its own context.
- Codex as direct report. She prompted Codex to "set up my CRM to accurately reflect what happened in my emails and conversations with existing and prospective clients." Codex had access to her inbox, meeting transcripts, and the sales-pipeline logic in Attio and enriched hundreds of records overnight. "I woke up to a CRM that was fully set up — work that would have taken weeks otherwise."
- Codex as care operating system. Managing her father's multi-nurse healthcare — appointments, follow-up protocols, family information flow — through a single Codex project. "Codex helped me create an operating system for how, as a family, we could triage my dad's care."
Paywalled team setups (preview only):
- Katie Parrott: prompt for storing voice, style, and column ideas
- Austin Tedesco: goal + sources → AI drafts deliverables
- Kieran Klaassen: personal folder synced from meetings and voice notes
Fable 5 sidebar: Brief note that Anthropic's Fable 5 (Mythos-grade) was returning the same day; Every's Mike Taylor attended AI Engineer World's Fair where Anthropic's Thariq Shihipar gave the keynote "A Field Guide to Fable."
Mapping against Ray Data Co
Strong on three axes:
Ray = Natalia. The overnight CRM enrichment case is a near-identical pattern to the Ray COO agent: autonomous, asynchronous, context-rich execution while the founder is away. This is a practitioner validating the agent-as-COO thesis from the nontechnical-user side, which is useful framing when explaining RDCO's model to clients or prospects.
phData DSA role. CRM enrichment from meeting transcripts + email context is a data pipeline problem — exactly the kind of use case that surfaces in RevOps or sales-ops discovery conversations. The Attio → inbox context → enriched records pattern maps to any client data-layer modernization pitch.
Codex vs. Claude Code positioning. Natalia's "lower-friction Claude Code" framing is a clean analogy for tiering AI tooling: Codex for business users who don't want to architect prompts, Claude Code for engineers who do. The DSA role straddles both tiers; knowing this distinction helps frame recommendations during client scoping.
Related
- [[2026-05-26-every-codex-for-knowledge-work-power-user-guide]]
- [[2026-06-25-every-codex-for-everything-and-everyone]]
- [[2026-05-03-every-context-window-codex-goes-to-work]]