One of our engineers wrote an internal post a while back about why talented teams route around their own problems. Four words in there really struck me: Courage as a Service.
AI has made the knowledge part of consulting cheaper. Understanding a codebase, mapping dependencies, planning refactors. Things that took senior engineers days now start with a few prompts. The knowledge barrier is shrinking, but the problems aren't. Teams still avoid the legacy system. Architecture decisions from three years ago go unchallenged. Everyone knows where the skeletons are. They just don't seem to open that closet.
Hear me out. It's a football game, minute 73, and the team is trailing. The coach brings in a substitute, not the flashiest player, but someone who'll do things with more bravery and a nothing-to-lose attitude. He scores the winning goal a few moments later. That substitute doesn't have more skill than the players already on the pitch. There was a reason he sat on the bench. The difference is simpler, but harder to teach. They walk on and immediately do something everyone else had been avoiding: demand the ball, take ownership, give it their all.
That's what we do. We walk into a codebase where talented engineers have been quietly routing around a foundational problem for months. We see a module nobody wants to touch and deployment pipelines held together by duct tape. And instead of mapping the problem and writing a report, we start fixing it.
The internal team usually knows exactly what's wrong. They might even have a plan. What they don't have is the mandate. The developer who says "this architecture needs to be torn down" is risking relationships, standing, their daily working environment. The external consultant who says the same thing flies home afterwards.
The flattering version is that we're braver. The honest version is that we're temporary. Our courage comes at a structural discount. We get to be fearlessly honest because we don't live with the long-term social cost of that honesty.
That stung, but it sharpens the point rather than undermining it. Organisations generate knowledge about their own problems and then build invisible walls around acting on that knowledge. Not because people are cowards. Because the incentive structure punishes the messenger. The courage is a structural gap, not a personality trait. We fill it, that's the job.
I've spent years trying to articulate what madewithlove brings to the table. We've said technical expertise, engineering leadership, senior talent for hard problems. All true. But that post nailed something none of those capture. We offer the willingness to say the thing out loud and then do something about it.
The best version of what we do is fixing it so visibly that the team starts fixing things too. When someone commits to the risky pass, the players around them start making runs they weren't making before. The courage is contagious.
In a world where AI makes knowledge cheaper by the minute, the part that stays expensive is the willingness to act on what you know.
Courage as a Service. Four words. I wish I'd written them first.
