What it can do, how we organise ourselves around it, and what this team becomes. No coding required.
Barely anyone here writes software for a living. That is exactly the point — Codex is for the other work.
None of this is a coding problem. It is a "figure it out and do it" problem — and that is what an agent is for.
You say what you want in plain language. Codex looks at the real files, does the work step by step, checks its own result, and shows you everything before anything is saved.
It reads spreadsheets, PDFs, logs, exports and folders — not just code. You never write a line of anything.
Excel, CSV, PDF, Word, logs, config — hundreds at once.
"Which of these 200 devices is out of warranty?" — it goes and looks instead of guessing.
Hands back a finished spreadsheet or document, saved to your folder.
Renames, sorts, converts, merges, exports — in order, without you.
Runs the result, spots its own mistake, fixes it, and tells you what it changed.
Our rules written down once — followed every time after.
Reads vendor docs and the web, then tells you what applies to us.
Hand off a long job, come back to a finished result.
Same conversation. Completely different amount of work left for you.
Real requests, exactly as you would say them to a colleague:
Excel and CSV exports, PDFs, Word docs, emails saved to a folder, screenshots, log files, config files.
Runs on your own machine in a normal window, or in the browser. Points at any folder you choose.
Long jobs run without you sitting there. Come back to a finished result and a summary of what changed.
Can be connected to approved tools and data sources — one at a time, with IT deciding what is in scope.
Repositories are optional. For most of this team, the "project" is a folder on a shared drive.
A technician asks for the monthly ticket summary they normally spend half a day on. No coding, no template, no formula.
≈ 5 minutes, then your review. Illustrative — we confirm real timings on our own data.
The thing people worry about — "will it break something?" — is a setting, not a gamble.
Everyone starts on look, don't touch. We open it up only where it earns trust.
It can look at files and answer. It cannot change or delete anything until you say so.
You see exactly what it wants to write, before it writes it. You approve or reject.
Work happens in a sandboxed folder. Anything outside it needs your explicit permission.
A simple instructions file holds our standards and limits — no secrets, no production, ever.
A capable tool with nothing
written down is just
a faster guess.
Everything so far was what Codex can do. The rest is the part that is on us: what we write down, where we put it, and who keeps it true.
Right now most of how this team works lives in three places Codex cannot reach.
Alignment is the real project. The tool is the easy half.
Rule of thumb: write it where it applies. Team rule → shelf 1. Report rule → that report's folder.
This is the habit that separates a team that gets value from one that gives up in week three.
When it gets something wrong, you don't just fix the output — you say "add that to the rules" and it writes the correction down itself.
Documentation stops being a project nobody has time for, and becomes a by-product of doing the work.
Not a project plan — a standing commitment. Small, but it never reaches zero.
Everyone finding their own way works for a month. Then it quietly becomes a different version of the job per person.
Same tool, same people. The difference is entirely in how we organise it.
Rule that keeps it honest: no owner and no date means not shared.
Not a help desk for AI questions. A small group whose job is that everyone else needs them less — by design.
If Codex can do all that —
what does this team become?
Nobody gets a straight answer by avoiding the question, so here is ours — in three parts.
Nobody's job disappears. The bottom rung gets handed over, and the top rung — the one we never have time for — finally gets done.
Sort, format, copy, check, repeat — by hand.
Is it right, sane and safe to send? Needs business knowledge.
Decide how the job should be done, write it down once, make it repeatable by anyone.
Which problems matter, what to stop, what to fix at the root.
Codex takes level 1 and assists with 2. Levels 3 and 4 are the job — the part that grows careers.
| Role | Handed to Codex the level-1 work |
Stays yours, always judgement & accountability |
What you gain room for level 3 & 4 |
|---|---|---|---|
| Technician | Retyping notes, repeat fixes, manual checklists | The person, the priority, the final call | Fixing root causes so the ticket never returns |
| Infrastructure | Diffing configs, scanning logs, chasing what changed | Approving every change, owning uptime and rollback | Designing the standard, then proving we meet it |
| Business Analyst | Gathering, cleaning and formatting data; waiting on pulls | Knowing what the business actually needs, and why | Asking harder questions, of far more data |
| Managed App | Reading vendor docs, reconciling lists by hand | The vendor relationship, the risk call, the commitment | Judging vendor claims against our own reality |
| DevOps & AI | Repetitive build and glue work | Guardrails, access, what touches live systems | Building the shared foundation the whole team runs on |
Same people, same names. The higher-value half of the same job.
The team spends its time deciding how the work should be done — with the knowledge written down, not carried in a few people's heads.
That is a change in what a good day looks like. It is not a change in who is needed.
Treat it like a fast, tireless junior colleague who never minds being asked again — and always shows their work.
No committees, no waiting list — the whole team gets it, starting in read-only.
Pick the task you dread most this month.
Describe it in one sentence.
Let Codex work it out.
Then write down how it did it — that part is ours.