Using Claude as a pair-programmer on a real MuleSoft project

We spent three months treating a model as a junior on a real MuleSoft project. This is what worked, what stayed firmly with humans, and where the savings actually landed.

Good at the tedious, supervised on the subtle

DataWeave transforms, boilerplate flows and test scaffolding came back fast and mostly correct. Anything touching error handling, transactions or security needed a human in the loop, and we kept it that way on purpose.

The savings were real but unglamorous: less time on the repetitive 60 percent, so the team spent more of its attention on the 40 percent that needed judgement.