Top 10 uses for Codex at work

Top 10 uses for Codex at work

Try these 10 prompts to move real work forward with dashboards, decks, workflows, and more.

You’ve seen what Codex can do. Now it’s time to put it to work. These use cases show how to use Codex to do real work: create deliverables, pull together context from multiple tools, take action on real inputs, and move tasks forward faster. Start with the generic prompt if you want something you can use right away, then use the customization suggestions and example to make it your own.

You start the day by bouncing between your calendar, messages, email, and notes, trying to figure out what matters most. Codex can pull that context together, keep watch for changes, and turn it into one clear brief so you spend less time triaging and more time acting on priorities.

Swap in your real tools and follow-up sources. Set when the brief should start and how often Codex should check back. Tell it what to include in the brief and when to draft replies.

Suggested plugins: Google Calendar, Gmail, Slack, Google DriveSuggested skills: Google Calendar Daily Brief, Gmail Inbox Triage, Slack Notification Triage, Google Calendar Meeting Prep

Example:

Set up a weekday heartbeat called “Morning Work Brief” that starts at 8:30 AM local time and keeps checking throughout the workday. At 8:30, use today’s calendar, unread Slack DMs and mentions from the previous 24 hours, unread Gmail from the previous 24 hours, my Google Doc “Open Follow-Ups,” and any recent context that affects today. Create a brief with priorities, meeting prep, messages needing reply, decisions I owe, and FYIs. Then check every hour until 5 PM for new replies, meeting changes, or follow-ups I need to handle. Only update me when something changes or needs my attention. Draft replies only when the next step is clear. Flag missing access or uncertainty.

You end the week trying to remember what you finished, what changed, and what your manager actually needs to know. Codex can pull together the week across your calendar, docs, messages, and trackers so writing the update feels less like a memory exercise and more like a quick review.

Suggested plugins: Slack, Gmail, Google Calendar, Google Drive, NotionSuggested skills: Slack Daily Digest, Slack Channel Summarization

Example:

I’m writing my Friday update for the week of April 20. Use my calendar, Google Docs I edited, Slack messages I sent in #launch-planning and #sales-enablement, “Q2 Workstream Tracker,” and anything else that looks relevant to my week. Write a manager-ready summary with work finished, decisions, important changes, blockers, follow-ups, and next week's priorities. Include source links. Separate confirmed facts from inferences.

You may already have the content for the deck, but turning scattered notes, metrics, and source docs into something presentation-ready takes too long. Codex can work across those materials, draft editable slides, and help catch layout issues so you get to a usable deck much faster.

Swap in the real brief, metrics, and template. Set the audience, slide count, and sections. Tell Codex what not to invent and what layout issues to fix.

Suggested plugins: Google Drive, Notion, Figma, CanvaSuggested skills: PowerPoint, Google Slides, Google Docs

Example:

I need a draft deck for the April 23 customer onboarding review. Use “Customer Onboarding Brief,” “Top Customer Onboarding Issues,” “April Onboarding Metrics,” the attached “Simple Company Template.pptx,” and related onboarding context. Create a 7-slide PowerPoint with an exec summary, customer problem, top issues, example workflow, adoption signals, improvement plan, and open decisions. Keep text editable. Add speaker notes. Render the slides and fix overflow, crowded layouts, or unreadable charts. Do not invent metrics. Flag missing data.

Important decisions are usually spread across old recaps, planning docs, budget inputs, and whatever you can learn from current research. Codex can gather those pieces in one workflow, separate internal evidence from external research, and turn the result into a memo that is easier to act on.

Replace the decision and supporting files. Tell Codex what outside research to gather. Specify how to separate internal evidence, web research, and open questions.

Suggested plugins: Google Drive, Notion, Browser, SharePoint, BoxSuggested skills: Browser, Google Docs

Example:

I’m deciding whether Acme should sponsor SaaStr Annual 2026. Use “2025 SaaStr Recap,” “Event ROI Model - Q4,” “FY26 Target Account List,” “Events Budget Guardrails,” and related event planning notes. Search the web for current SaaStr dates, audience, sponsorship options, and competitor presence. Write a one-page decision memo with a recommendation, evidence, tradeoffs, cost, risks, missing information, and source links. Make clear what came from our files and what came from web research.

Messy exports from different sources are tedious to clean and easy to mishandle. Codex can apply cleanup rules consistently, combine files into a usable workbook, and preserve a review path for anything that should not be guessed.

Suggested plugins: Google Drive, SharePoint, Box, EgnyteSuggested skills: Excel, Google Sheets, Google Sheets Formula Builder

Example:

I attached “Q2 Webinar Attendee Export.csv,” “Manual Registration Edits.xlsx,” “Partner Invite List.xlsx,” “Field Mapping Notes.docx,” and any related attached file. Clean the attendee data into one workbook. Standardize name, company, title, country, segment, source, and attendance status. Remove duplicates by email. Create an upload-ready CSV using the column order in “Field Mapping Notes.docx.” Put missing or conflicting rows in a “Needs Review” tab. Do not guess missing emails. Add a short change log.

A set of spreadsheet exports may look close enough to join, but the cleanup, mismatch review, and reporting work adds up fast. Codex can consolidate the files, surface what did not join cleanly, and turn the result into a workbook you can actually use and refresh.

Suggested plugins: Google Drive, SharePoint, Coupler.io, Omni Analytics, MotherDuckSuggested skills: Excel, Google Sheets, Google Sheets Formula Builder, Google Sheets Chart Builder

Example:

I attached “Q1 Pipeline by Region.csv,” “Q2 Pipeline by Region.csv,” “Account Segments.xlsx,” “FY26 Sales Targets.xlsx,” and any related attached file. Consolidate them into an updatable workbook. Join on account ID, clean duplicate accounts, calculate pipeline by region and segment, compare Q2 pipeline to target, and create a dashboard with charts and plain-English insights. Add assumptions, refresh instructions, and mismatched account IDs to review.

The signals that tell you which accounts matter right now are often spread across CRM exports, calls, email threads, dashboards, and plans. Codex can pull those signals together, rank the accounts that need attention, and show you where to focus first.

Suggested plugins: Common Room, Demandbase, HubSpot, Pipedrive, Streak, Attio, Gong, Gmail, SlackSuggested skills: Gmail Inbox Triage, Slack Reply Drafting, Google Docs

Example:

I’m an account manager planning my week for my top renewal accounts. Use Salesforce export “April Renewal Account Export,” Gong transcripts from the last 30 days, open buyer email threads, “Renewal Usage Dashboard,” “Q2 Renewal Plans,” and anything else that explains renewal risk or upside. Create a book-of-business priority brief ranking the 10 accounts I should focus on. For each account, include why now, risk or upside, next action, source links, and stale or missing context. Draft customer follow-up notes only where the next step is clear. Mark anything needing AE review.

Month-end review means pulling numbers and context from workbooks, dashboards, prior decks, and close-period discussion without missing anything important. Codex can work across those mate