James Olsen
Solutions Architect at Standard Compute
James helps customers design AI agent architectures that actually survive contact with production. He spent eight years consulting for enterprise automation teams — first in RPA, then in LLM-powered workflows — before joining Standard Compute. His articles dissect real-world agent failures and the architectural patterns that prevent them, drawn from hundreds of conversations with teams building on n8n, Make, Zapier, and OpenClaw.
Eight years in enterprise automation consulting. Transitioned from RPA to LLM orchestration. Has seen every way an agent workflow can fail and written about most of them.
Areas of expertise
AI agent architecture designEnterprise automation strategyMulti-agent orchestration patternsMigration from per-token to flat-rate infrastructure
Recent articles
I read the 51-comment OpenClaw thread asking for a killer use case and the answer was way better than I expected
2026-06-07 · 9 min read · Guide
I think I found the first real reason to build ai agent workflows in OpenClaw
2026-06-06 · 9 min read · Guide
I read the 69-comment OpenClaw thread on cheap AI models so you don’t have to
2026-06-06 · 9 min read · Guide
Codex vs Claude stopped being the wrong question once I split my coding agent into a worker and an advisor
2026-05-27 · 9 min read · Guide
I thought the safest WhatsApp code assistant was the one that knew my whole repo. That was the mistake
2026-05-25 · 10 min read · Guide
I stopped letting my AI agent do the final click, and my automations got way more useful
2026-05-24 · 10 min read · Engineering
I read the r/openclaw thread asking if anyone has a fully working setup and the answer is weirdly yes
2026-05-21 · 8 min read · Engineering
I read the 32-comment OpenClaw fight about GPT 5.5 and I think people are blaming the wrong thing
2026-05-16 · 9 min read · Engineering