#150 · How to Handle 3 Common Objections When Selling Cold Email

youtube ↗Agency Operations

How do you deliver n8n workflows to clients who aren't familiar with them? Do they self-host their own account or pay a monthly subscription for cloud hosting? How do you get their credentials/API keys — do you get access on the call and set it up on their n8n account yourself, or do you guide them through it?

They pay for cloud hosting on a monthly subscription and sign up themselves — I get them to create the account, guide them through it, and then they hand me the account access, since it's tied to their card. That's the 80/20 approach: guide them to create it, get access, but they own and pay for it.

client deliveryn8nhostingcredentials

Related answers

youtube ↗AI & Automation

Can you help me understand when businesses choose to self-host n8n versus using the cloud version? I believe self-hosting for anything beyond personal use requires being an Enterprise client—is that generally true? And how should I work through this with clients?

Honestly, nobody really knows for sure, and there hasn’t been any backlash yet. Many people using n8n to make money are on the self‑hosted version, but they usually just run the executions through their own endpoint rather than setting it up for the client, which adds nuance. If you want to play it safe, I’d recommend the cloud‑hosted offering: it’s easier, faster, you don’t have to mess with webhooks, and the platform handles reliable updates and server uptime for you. Yes, it costs more—around $50 a month for five workflows and 5‑10k executions—but when you’re delivering $5k‑$15k of value per client, that fee is negligible. So my recommendation is to go with cloud hosting.

self-hostcloudn8nautomation
youtube ↗Agency Operations

How do you fulfill client work? Do you send them a template and guide, or do you do something else?

I recommend getting on a kickoff call with the client. Walk them through signing up for every platform you’ll need, then have them give you their usernames, passwords, and any credentials—doing two‑factor authentication live if required. Log in to confirm access, and then perform the work directly in their account. No templates or handoffs are needed; you complete 100% of the work there.

kickoff callclient credentialsfulfillment
youtube ↗Pricing

Nick, truly appreciate the value from your videos. I want to know how you'd set up the API keys, password, and payment methods when onboarding clients for a new project. Would you set the tools up yourself from your account, but for them, and then you charge them a monthly return? Do you set it up from their account, use their passwords, etc.? So, the billing and the data goes directly to them. I have the billing and the data and everything go directly through them, and then they just share me their username, password, email, everything that I need in order to access the account. So the account is doiciled on them if that makes sense.

The reason I do this is twofold. First, it makes handoffs really easy. If you're no longer working with someone on this thing, you can say, 'Hey, you have everything you need. Here's the documentation on projects I've already delivered. Good to go. Goodbye. I love you. See you never.' Second, when you get people to sign up to these platforms, you can use your own affiliate link, which adds 3 to 5% to your margins almost immediately. That's how I do it—I don't have them deal with API keys or anything; I handle it all myself.

api keyspayment methodsonboardingaffiliate
youtube ↗Agency Operations

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