What We've Learned
Lessons from 300+ automations shipped to production. No theory. Just what actually works when you need AI automation to ship.
Featured Posts

AGENTS.md vs CLAUDE.md: which file your agent actually reads
Both files in one repo, measured: load order, token cost, and which one wins when they disagree. Every guide explains the difference; this one runs the test.

AI readiness checklist: five checks before you automate a workflow
Readiness gets assessed at two levels. Organization readiness plans the program; workflow readiness picks the next build. This is the second one: five checks, scored out of 25, in about five minutes, with your weakest check named so you know what to strengthen first.

Compound engineering for Claude Code: the AGENTS.md setup
What compound engineering actually is, how the Claude Code plugin's 33 skills implement it, and the AGENTS.md file that makes each unit of work leave the next one easier.

Conductor joins Meta: what Claude Code users do before November 20
Conductor is joining Meta. Conductor Cloud goes read-only on November 13 and shuts down on November 20, while the local Mac app keeps working until early 2027. What to move, what keeps working, and what replaces it in Claude Code.

Claude Team vs Pro vs Max: which seat each person needs (2026)
Claude Team vs Pro vs Max, decided one person at a time: which seat a light chat user, a daily Cowork user and an all-day Claude Code user need, when usage credits beat a Premium seat, and what Max's and Team's API credits actually cover.

PHP2Shell and the AI exploit: what changed for anyone shipping code
AI helped turn PHP2Shell, a PHP bug class judged unexploitable in 2024, into working remote code execution, and attackers were probing within hours of the fix. What happened in October 2026, where AI showed up on both sides, and how a pipeline that agents run should patch now.

Best Claude plugins for teams: what to standardize on (2026)
The Claude plugins a team should standardize on in October 2026, grouped by job: knowledge work, sales and CRM, Claude Code, finance and legal. Each with its source and install count, plus how a Team owner rolls them out and vets community plugins.

Claude scheduled tasks: how to set one up for your team (2026)
How Claude scheduled tasks work in Cowork in October 2026: how to set one up, which plans include them, where they run on a Team plan, a read-only weekly digest to start with, and how approval modes interact with connectors set to Needs approval.

Claude Projects for teams: how to share and set them up (2026)
How to use Claude Projects as a shared knowledge base on a Team plan: what a Project holds, Projects vs chats, public vs private sharing, Can view vs Can edit, the Data and privacy settings, and the limits to plan around.

Claude Cowork vs Claude Code vs chat: which to use for each job
Which Claude surface each teammate should use on a Team plan: chat for thinking, Cowork for finished files and tasks, Claude Code for software. How Cowork runs after the September and October 2026 changes, and what one seat shares across all three.

Claude plugins vs skills vs connectors vs Projects: which to use (2026)
Skills, plugins, connectors and Projects compared in one table: what each is, what it contains, where it runs in chat, Cowork and Claude Code, when to use which, and how a Claude Team owner provisions each one org-wide.

Claude SSO and admin settings: how to set up a Claude Team org (2026)
How to set up Claude SSO on a Team plan: domain verification, Require SSO and the lockout traps, roles and JIT provisioning, every organization settings page and its Team default, and what needs Enterprise (SCIM, audit logs).
Ready to put AI to work?
Book a free discovery call and we'll tell you what we'd automate first – and what we wouldn't touch yet.
30 minutes. No pitch. You keep the plan.
Prefer to build it yourself? Try Flow free