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
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.
Start with a kickoff call after the client pays, where you help them set up any needed platforms and possibly share your affiliate or partner codes for discounts or revenue. Then state that you’ll build everything in their environment so they retain full control if they stop working with you. Build using their tools (they give you credentials), and deliver the project with a video SOP that walks them through the system and serves as documentation for future maintenance. Use that video as a retention mechanism, then upsell related projects based on the knowledge gained from the current job. Mention that you can save them $500–$10,000 per month with a simple system, and invite them to a quick call if interested. The loop gets you in and prints money; you can pitch a monthly upsell or another one‑time project.
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.
Thanks for the question. Shipping an automation isn't really needed—you don't need to ship it at all because the shipping happens during the building process. You start by talking with somebody who likes what you have to offer, get them on a call, discuss the problems and solutions, do quick math to see how much the problem is costing them, and pitch your solution at a fraction of that cost—usually around 30%. Once they agree, you send a proposal, they sign it and pay you a little money. I like doing a 50/50 upfront and then upon delivery structure for a small intro offer, then transitioning to a retainer fully paid up front at the beginning of each month. After they sign, you need to get them on a kickoff call to walk through expectations, scope, timelines, and confirm the scope again before starting work—this is your point of highest leverage. If there are project problems, deal with them now while you have some of their money and haven't done work yet, rather than at the end when they're holding money out on you. On the kickoff call, you also have them sign up to the necessary platforms (like Make.com or N8N) so they have everything they need upfront and you never have to bug them again for access; the only messages you'll get are positive happy updates. As a Make.com partner and NN verified creator, I get preferential treatment like a thousand free operations via affiliate promo codes, which adds 3‑5% to your margin because they use your affiliate links and trust you as an authority. You have no liability for recurring payments—they take that on. Before the end of the call, you have all the credentials so you never have to bug them again. That's how you actually go about doing the shipping. To find clients in the really early stages of your automation agency, join Maker School.