How would you deliver a Claude-based automation for a client and manage prompt changes?
The simplest and easiest way to build Claude-based automations for clients is to connect to their Claude account using the built-in connector for one-click OAuth into all the services they need. Then, when you build your cloud automation, do it under their routines offering and add the connectors as their off. You only need to do this once, giving you fully automated Agentic workflows that run without you and without constantly having to check in with the client for things like 2FA. They've solved this completely, which is awesome. You could also do it via cloud co-work or cloud code with the cloud routines feature, but I recommend connecting to their Claude account as described.
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
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.
Sure. When a new client signs a contract and the invoice is paid, the first step is a kickoff call. In that call you thank them, clarify the problem you’ll solve, reiterate the value you’re delivering, and cover timelines, communication channels, account sign‑ups, and any two‑factor‑authentication requirements. You walk them through signing up for every platform you’ll use, making sure all 2FA is set up, and you aim to have every account, email, and password ready by the end of the call—ideally stored in a password manager like 1Password, LastPass or Dashlane. Then you invite the client to your communication hub (Slack, email, WhatsApp, etc.) and establish a cadence for updates, such as a brief status every couple of days. From there you proceed with the automation build. The client pays for everything: the automation platform (Make.com), any niche tools you use (Naden, PandaDo, Instantly, Mailfinder, ClickUp, Slack, Apollo/Amplify, etc.). Because you have affiliate partnerships with most of these services, you include your referral links, which typically give you a 3‑5 % margin, providing a small side‑income that continues even after the project is handed off.
I track clients in a ClickUp table that syncs from leads via automation. To hand over an AI voice automation, the simplest way is to have the client sign up under their own credentials and give you the username and password so you build directly in their workspace. If the platform lacks a built‑in transfer, you can swap the credit card on your account, have them pay, then change the email to theirs to transfer the account, and later set up your own separate account.
ai voiceappointment settingclient trackingproject handoff