How do you hand over a Make.com workflow to a client after building the automation?
Normally you create the automation inside the Scenario Builder, then schedule a kickoff call with the client. During the call you walk them through signing up for a Make.com account, often sharing your screen and guiding them step‑by‑step. Once they have their own Make.com environment, you can build the automation directly in that workspace. When the automation is ready, you deliver it within their environment, completing the hand‑off and turning the lead into an official client.
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.
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.
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
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.