How do you deploy and host cloud code automations for customers, and do they need cloud code themselves?

#274 · stop cold calling, send loom videos instead

How do you deploy and host cloud code automations for customers, and do they need cloud code themselves?

If the automation is purely procedural (no AI), you don't need to host it on cloud; you can run it on a serverless platform such as Modal or a .dev trigger, or any other server solution. Cloud Code just builds the script, which you then attach to an event like an incoming booked meeting, and it runs the procedure. If you want AI woven into the automation, use Cloud Routines—skills that run in the cloud on the client's Anthropic account. To set this up, you need a kickoff call where you explain that you'll configure a cloud routine as your infrastructure, which is easy to manage and gives you full control over your IP and infrastructure. You can gain access in three ways: have the client share their Cloud Code login, create a Teams account and add you as a user with full access, or provide their API key so you can work programmatically. I prefer full access via login or Teams because it simplifies handling missing permissions.

cloud codeserverlesscloud routinesAPI access

Related answers

youtube ↗Agency Operations

When building Claude Code automations for clients, do you build them on your own cloud/account or the client's? What does the delivery process actually look like?

On the client's. I'd recommend looking into Claude Routines — a workflow offering Anthropic launched a couple months ago; it's essentially a skill that runs in the cloud on a loop (you set the loop interval, or trigger it via API). It costs more in tokens since you're running AI inference, but it's straightforward. Delivery works the same way as delivering an n8n or Make.com automation: build it in their workspace, then record a walkthrough video showing them the whole system end-to-end so they can run it independently with or without you — it's their IP, and making things stable long-term for the client is part of the job as a service provider. After the delivery video (also a great relationship-building moment), always try to upsell: point out something you noticed while building that could make them more money with a few tweaks, and offer a call to talk through it.

claude codeclaude routinesclient deliveryautomation ownership

youtube ↗Agency Operations

How do you deliver your automations to clients?

I don’t really do any deliveries. I build everything inside the client’s account. When it’s time to deliver, I just send them an email saying I’m done, plus a video recording of some documentation (maybe a Google doc) if we discussed it, and walk them through how to use the system. That’s delivery in a nutshell. Most people think they need to handle API keys, authorization, etc., but you don’t have to deal with most of that if you build inside the client’s environment. My preferred approach is to run through a kickoff call SOP: collect all needed credentials, access, emails, passwords, then build the automation directly in their Make.com (or similar) account. That’s it.

deliveryautomationclient onboarding

youtube ↗AI & Automation

How should I deploy AI automation solutions for clients—specifically, who pays for APIs/platforms, whose email should be used, and who runs the automation? Please provide a step‑by‑step guide.

The client should cover the cost of any APIs or platforms used in the automation. You set up the automation using the client’s own email address. In most cases, you manage the automation on their behalf—that’s where your value lies. For a detailed walk‑through, check out my video titled 'Nick Sarif, how to manage an automation project'; it shows my step‑by‑step automation agency delivery process, which hasn’t changed in the last few months, so you can follow it directly.

ai automationdeploymentapiclient management

youtube ↗AI & Automation

How am I going to set up automations for clients? Do I need to prepare a front end and back end for them?

Setting up automations for clients is mostly about the back end. The front end is simply the deliverable you produce—like a Google Doc, a WordPress post, or any content you hand over. In software terms, the front end is what the user sees, while the back end handles the processing, usually via cloud functions in our case. You don’t need to worry about building a front end; the back end is managed automatically with tools like Make.com.

automationfrontendbackendmake.com