← All questions

#139 · How to Run "Smart" LinkedIn Ads for an AI Automation Agency

youtube ↗Agency Operations

What client access is needed when onboarding a client for an agency, including NADN/Make account and other accesses?

Requiring clients to create their own Make (or NADN) account and granting you access is non‑negotiable. It simplifies handoffs, speeds up onboarding, and reduces liability because you avoid persistent recurring costs on your side. You can also add affiliate links to boost margins by 3‑5%. I’ve tried pass‑through billing, but managing everything on the client’s account is more transparent and avoids the dark‑pattern risk of owning their business infrastructure.

client onboardingnadnaccess

Related answers

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 ↗Pricing

Should I include the pricing of client-managed accounts (like NAND) in my fees, or treat it as an additional expense for the client?

I recommend treating those costs as an additional expense for the client. Add a line item on your pricing table labeled 'pass-through fees' or 'platform fees' to make it clear you don't retain any of that money. This is the simplest way to start and also protects you from liability—if you ever offer a guarantee tied to results, the client pays you only if you deliver, otherwise they get a refund. Conceptually separating the fees this way keeps things clean. I agree with Mr. Gfar that the client should manage their own accounts. Regarding which platform to use—Make or NAD—pick the one you're most comfortable with; there's no need to have clients set up both, as each platform can do what the other does.

pricingpass-throughclient-accounts
youtube ↗Agency Operations

When a project requires third‑party platforms or services that need account creation (e.g., APIs, cloud providers, communication tools), should the agency create those accounts or should the client create them and give the agency access?

I recommend having the client create the accounts. The simplest way is to schedule a kickoff call after they’ve paid you. During the call walk them through the three or four platforms they need to sign up for, have them share their screen, and guide them step‑by‑step—press this button, sign up for this plan, etc. This avoids two‑factor authentication issues, which are a major pain point. Most of the time you can bypass 2FA by using just email and password. If you can’t moderate the sign‑up, they’ll usually use Google OAuth or similar (GitHub, etc.), which often require authorization codes. As a bonus, if you provide an affiliate link for the platform, you can earn 20‑40 % of what they spend.

account setupclient onboardingthird‑partyaffiliate
youtube ↗AI & Automation

If I custom build an AI agent using code, how can I give it to the client?

Well, ideally you would build the AI agent using code directly in the client’s environment, so you’d create the NADN AI agent there or use the NADN code block inside their environment. That way you never have to hand over anything because it already lives in their system. This is one reason I recommend getting the client to pay for the services and handling everything during a kickoff video call where you guide them through the process. You avoid a handoff, which can be annoying. It adds a bit more friction up front, but it saves a lot of hassle later and lets you use things like affiliate codes. I would completely eliminate the handoff.

ai agentclient deliverycode