How do we handle credentials for multiple customers using the same automation? Do we need a separate automation per customer or can we make it multi-user/multi-tenant?
Typically you provision automations per customer. You take the automation you built, turn it into a template (like a JSON file or a skill), and then apply that template to each customer's credentials. You're not building a persistent app for multiple customers; you build systems and apply them individually into each business, so it doesn't feel cookie‑cutter.
Clients provide their login credentials. I run a kickoff call SOP where I ask them for all their logins, which I then use to set up the automations. I only use an API key if they’re comfortable sharing it, otherwise I work with their direct login.
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.
I track clients in a ClickUp table that syncs from leads via automation. To hand over an AI voice automation, the simplest way is to have the client sign up under their own credentials and give you the username and password so you build directly in their workspace. If the platform lacks a built‑in transfer, you can swap the credit card on your account, have them pay, then change the email to theirs to transfer the account, and later set up your own separate account.
ai voiceappointment settingclient trackingproject handoff
I never give my own credentials to others. When you ask if clients use their API keys on their account, yes—they do. Do they always accept giving me their credentials? No, not everyone does, but the vast majority do. I think this happens because I frame it matter‑of‑factly; I don’t make it a big deal. It’s simply how the service works: you give me your email and password (make sure it’s unique), I log in, set everything up, and then manage everything end‑to‑end. That’s the expectation. I don’t even mention it because it’s obvious to me, and I’ve rarely had issues. Occasionally a technical client prefers to give me their API keys instead, which works just as well since API keys grant the same authorization—I can do everything through the API without logging into their account. Logically, if they give me API keys, I can accomplish the same tasks. I’ve always assumed that if someone hires me for a technical purpose, they’ll accept sharing credentials because otherwise there’s no point. Of course there are exceptions: some platforms let you delegate sub‑accounts, and many are built exactly for that. In short, the simplest approach is to have the client provide a user password and then grant full access in one go.