Case studies

Systems we actually run, documented honestly

Most agency case studies are testimonials with a metric bolted on. These are engineering write-ups of production agent systems we operate ourselves — including what broke and what they do not prove.

Get my free blueprint

We are a new studio, so we are not going to show you a wall of client logos we do not have. What we can show you is the agent infrastructure we built for ourselves and run in production every day — because the systems we run for clients are built the same way, from the same patterns, with the same guardrails.

Every number on these pages was read directly off our own production host on. Nothing is estimated and nothing is rounded up. Where we cannot prove something, we say so instead of implying it.

What you will not find here

No cost claims. Our host carries no per-task cost ledger, so any dollar figure would be a guess dressed as data. When we have measured cost data, we will publish the methodology with it.

No client outcomes. Client engagements are covered by NDA. We do not publish client names, client metrics, or client architecture without written permission, and we are not going to anonymise a client into a "leading B2B SaaS company" to imply proof we cannot show you.

No ROI percentages. These are capability studies — how a system is built, governed, and kept running. They demonstrate engineering judgement, not return on investment. Those are different claims and we are not going to blur them.

Questions

Why are all your case studies about your own systems?

Because they are the only production systems whose numbers we can publish without a permission problem. Client engagements are under NDA, and we will not anonymise a client into a vague descriptor to imply proof we cannot actually show. The systems we run for clients use the same architecture and guardrails documented here.

Why is there no ROI or cost data in these case studies?

Our production host does not carry a per-task cost ledger, and we have no client-side outcome measurement to draw on. Publishing a dollar figure or a percentage saved would mean estimating and presenting it as data. These are capability studies: how the systems are architected, governed, and kept running.

How were these numbers verified?

They were read directly off our own production host on 27 July 2026 — systemd service state and restart counts, scheduled job definitions with their last-run status, session counts on disk, and line counts in the research and lead ledgers. The full survey is documented internally and every figure on these pages traces back to it.

Can you build something like this for us?

Yes — that is the business. The engagement starts with a free agent blueprint that scopes which workflow to automate first, which framework fits, and what the guardrails need to be. You see the plan before any invoice.

Want a system like this?

Tell us the workflow that eats your week. We'll scope the first agent and the guardrails it needs — free, before any invoice.

Goes straight to hello@iamagentman.com — we read every message ourselves. Prefer to answer three questions instead?Build your blueprint.

Get my agent blueprint — free

No retainer to start · reply within 24 hours