← All questions

#189 · live audit of a 287 sub youtube channel by a $400k/mo creator

youtube ↗Pricing

Do clients who pay a one‑time plus monthly fee for custom automation own the automation outright?

I’ve already covered this, but since it’s the last question I’ll be crystal clear: I give my clients full access to everything because I don’t believe intellectual property is that important nowadays. I prefer they have access to all the systems and own the intellectual property in case we ever stop working together. This avoids extra hand‑off work for me, and I don’t want to gate‑keep my automations or make clients feel they must keep paying me for their business to run. That would be a dark pattern, maladaptive, and it harms my reputation.

automationownershippricing

Related answers

youtube ↗Agency Operations

Who owns a custom automation after the client stops working with me?

My recommendation is to let the client own the automation outright once they’ve paid. Trying to gatekeep the IP is old‑school and unnecessary—an automation is just a collection of N8N or make.com nodes (essentially AWS Lambda‑style functions), which are difficult to patent and offer little defensive value. By handing over the full system, you avoid legal complexity and build trust.

ipownershipautomationcontract
youtube ↗Pricing

How should we charge a monthly retainer for ongoing automation work after we set up the system for a client?

Charge a monthly retainer because you continuously deliver value. The automation you build keeps producing repeat value for the client, and you act as a strategist and consultant who maintains the system. Systems can break, and handling that month‑to‑month is a big pain point for clients, so they prefer to pay you to ensure everything runs smoothly. By positioning yourself as the person who provides ongoing support, maintenance, and incremental value, a recurring fee is justified.

retainerautomationpricing
youtube ↗Pricing

How can I justify charging a high monthly retainer when the automation runs without my ongoing involvement?

The high ticket retainer is justified because the automation system works on its own and keeps delivering results—think of a Slack bot that notifies the client when a meeting is booked. Even though you’re not involved day‑to‑day, the client attributes the value to you. To make this clear, pair the autonomous system with light touchpoints like weekly strategy calls, occasional deliverables, or team training, so the client sees ongoing guidance without you trading hours for dollars.

retainervalueautomationongoing involvement
youtube ↗Pricing

Who should pay for software subscriptions (like Apollo, Appify, OpenAI, Make.com) when delivering automation services to clients — the agency or the client? If the agency pays, do they need separate subscriptions per client? If the client pays, how does payment and trust work?

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.

subscriptionsoftware costclient paymentautomation