#64 · $100K MRR From One Skool Community (Step-by-Step)
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.
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.
I don’t really do any deliveries. I build everything inside the client’s account. When it’s time to deliver, I just send them an email saying I’m done, plus a video recording of some documentation (maybe a Google doc) if we discussed it, and walk them through how to use the system. That’s delivery in a nutshell. Most people think they need to handle API keys, authorization, etc., but you don’t have to deal with most of that if you build inside the client’s environment. My preferred approach is to run through a kickoff call SOP: collect all needed credentials, access, emails, passwords, then build the automation directly in their Make.com (or similar) account. That’s it.
You can ask for API access, but it’s essentially the same as having their credentials—full API access lets you do everything the password would. It’s a bit of intellectual dishonesty to claim otherwise. If you go the API route, you can query sent emails, but you’re still controlling their account. I don’t recommend it; it’s better to get the password during the kickoff call.
Don’t automate any client‑facing activities—calls, proposal videos, onboarding, strategy or upsell sessions—because white‑glove service brings in far more money. Automate everything else: lead capture, data handling, invoicing, reporting, and any backend tasks.