TL;DR: When an organization handles information that must not leak, audit coverage decides the agent platform — not model quality. This series walks through a real selection process I supported, why a desktop app excluded from Compliance API lost the lead role, and what would change the conclusion.
One-line summary: Audit coverage > model benchmarks for regulated environments; pick the platform whose entire surface set is auditable.
Most articles about choosing an AI platform are written by and for engineering organizations. This one is not. The organization I recently helped has no dedicated engineering staff, handles pre-release information whose exposure carries material consequences, and runs ordinary managed Windows laptops. If that sounds unusual: per 2026 surveys, only ~12% of companies have deployed AI agents at all (under half among large enterprises). The constraint set in this series is not exotic — it is the default starting point for most first-time adopters.
I've anonymized everything the NDA covers. What remains is the decision process, which is the part worth recording.
Why this series exists
The existing guide on this site, Choosing Your Agent, answers "which agent should I run." This series answers a harder question: "which platform can my organization live with for the length of a contract?"
That reframing matters because three things are expensive to change after signing:
- Audit coverage — what the vendor records about user activity, and whether you can pull it into your own systems.
- Management plane shape — how many consoles, toggles, and config files it takes to keep the deployment consistent.
- Cost structure — where the bill is flat (seats) and where it is variable (usage).
Model quality, feature velocity, benchmark deltas — all of that churns monthly. The three items above are structural. You inherit them for the contract term.
The parts
Each part stands alone: direct answer in the first paragraph, tables over prose, facts dated "as of August 2026," and a one-line takeaway you can lift into your own decision memo.
| Part | Title | Core question |
|---|---|---|
| 1 | The Audit Gap Decides the Platform | Which surfaces actually land in audit logs? |
| 2 | One Admin Console Beats Three | How much management complexity can a staff-less org absorb? |
| 3 | What Seat Pricing Actually Covers | Where does the flat rate end and usage billing begin? |
| 4 | Why Command Allowlists Fail Alone | What actually constrains an agent on a managed laptop? |
| 5 | Research Tasks on a Locked-Down Network | Can agents do web research under default-deny egress? |
| 6 | The Decision, and What Would Change It | What was chosen, and which facts would reverse it? |
(Links go live as each part publishes.)
Who this is for
- Compliance / IT owners at companies adopting AI agents without a dedicated engineering team
- Vendors' docs readers who want to know which admin controls matter first
- Anyone who has been asked "can we just buy licenses?" by their board
FAQ
Q: Is this a recommendation to avoid Anthropic?
No. It's a record of one selection process where audit coverage outweighed model preference. The reversal conditions are documented in Part 6.
Q: Are the prices in this series official?
All pricing is quoted as of August 2026 from public plan pages; Enterprise tiers are custom quotes, so treat numbers as directional.
Q: Why write about a client engagement?
Because the failure mode — picking a platform nobody can audit or operate later — is common enough that the process deserves documentation.
Next: Part 1 — The Audit Gap Decides the Platform
Originally published at agentjournal.dev.
Top comments (0)