Field notes from the third way.
What we learn shipping software with AI agents, automating operations, and governing AI in real companies — written by the people doing it.
We build software with AI agents for a living, so this is where we publish what that actually means: the cost models we run with clients, the autonomy rules our engineers work under, and the security findings from real assessments. No hype, no doom — just field notes from the middle ground between "AI changes everything" and "AI changes nothing".
Looking for something practical first? Start with our services or see the model in action in our case studies.
We publish when we have something worth saying — usually two or three times a quarter — rather than on a content calendar. Every post is written by the person who did the work it describes, and every number in it comes from a real engagement. If a topic here raises a question about your own situation, the fastest answer is a conversation.
Human-only vs. AI-only vs. the third way: a cost model
Everyone has an opinion on AI and software teams. Fewer people have run the numbers. Here is the cost model we use with clients, derived from real engagements.
Read the post →What we actually let AI agents do (and what we never will)
"AI-assisted development" is uselessly vague. Here is our actual autonomy policy: the exact lines we draw, and why they sit where they do.
Read the post →Shadow AI: the security risk already inside your company
In every assessment we run, we find AI tools the security team did not know existed. Shadow AI is not a future risk — it is a present, unaudited data exfiltration channel.
Read the post →