How are you deploying Claude Code automations for clients?

I am trying to understand how people are actually deploying Claude Code-built automations for clients.

My background is mostly Make.com, so I am used to automations being visual, easy to explain, and fairly easy for a client to understand at a high level.

With Claude Code, Modal, and Trigger.dev, I can see the appeal. You can build something more flexible, probably faster in some cases, and less constrained by the limits of visual workflow tools.

The bit I am still working through is the client side of it.

I am especially interested in how this lands with small businesses and non-technical founders. My guess is that most clients mostly care about whether the automation works, is reliable, is documented, and has someone supporting it.

But I can also see cases where Make.com or n8n might still be the better choice, even if the build is slower or less elegant. A client may want something visual. They may want internal ownership. T

For people doing this in the real world, where are you drawing the line?

When would you use Claude Code, Modal, and Trigger.dev?
And when would you still choose Make.com or n8n because of the client, not because of the technology?

15 comments

How are you deploying Claude Code automations for clients?