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.
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.
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.
Sure. When a new client signs a contract and the invoice is paid, the first step is a kickoff call. In that call you thank them, clarify the problem you’ll solve, reiterate the value you’re delivering, and cover timelines, communication channels, account sign‑ups, and any two‑factor‑authentication requirements. You walk them through signing up for every platform you’ll use, making sure all 2FA is set up, and you aim to have every account, email, and password ready by the end of the call—ideally stored in a password manager like 1Password, LastPass or Dashlane. Then you invite the client to your communication hub (Slack, email, WhatsApp, etc.) and establish a cadence for updates, such as a brief status every couple of days. From there you proceed with the automation build. The client pays for everything: the automation platform (Make.com), any niche tools you use (Naden, PandaDo, Instantly, Mailfinder, ClickUp, Slack, Apollo/Amplify, etc.). Because you have affiliate partnerships with most of these services, you include your referral links, which typically give you a 3‑5 % margin, providing a small side‑income that continues even after the project is handed off.
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.