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.
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.
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.
He recommends a two‑step process: first, when you get the money, book a kickoff call; on that call, have the customer sign up directly to all the platforms you’ll use, capture their username and password, then proceed with the standard SOP (which is the same regardless of automation platform). He likes this because it’s simple and lets you also get the customer to sign up using your affiliate code. This eliminates the handoff problem—clients front‑load the work, you earn affiliate revenue, they retain full intellectual property, and you avoid any handoff. When delivering, you simply record a video walking the client through the system, explaining how to access it and providing any necessary links.
If you're building a system that generates $5,000 a month in value for a client, having them pay a small percentage fee is not a big deal; they care about the upside, not the tiny downside. As the service provider, you might worry about subscription costs, but the AI and automation field attracts technical people who overthink this. Get the client to pay for everything. On a kickoff call, walk them through exactly which platforms they need to sign up for. This builds perceived value because they see the technical setup and appreciate you handling it. You can also use your affiliate links—being a Make.com partner, for example—to earn 3–5% kickback or give clients discounts. If a client stays for a year, you earn recurring affiliate fees; e.g., 40% on a $100/month plan yields $40/month, or $480–$500 per year per client even if they stop working with you. This approach also minimizes your liability since you’re not making monthly payments on their behalf. It’s the best way to handle software costs. If you’d like a kickoff call SOP, I have a document that outlines how to run the call and get clients signed up on the platforms.