Do you request passwords for Stripe, Google apps, etc., during onboarding, and how do you handle client reluctance and 2FA when obtaining credentials for AI/automation services?
The best approach is to sign up for the needed services together with the client on a kickoff call, rather than asking for codes asynchronously. This gives you temporary access to their platforms for a few days, letting you grab API keys before the next 2FA round. While issues like password changes or data breaches can still happen, handling most of this up front minimizes 2FA headaches.
He mentions he already made a dedicated video on maintaining the best 2FA procedure; look up Nick SAR how to manage an automation project. He explains that 2FA is annoying because you work with many platforms and need to glue them together. His strategy: start with a kickoff call, get the client to sign up using email and password (avoid Google/Facebook/GitHub to reduce 2FA), store credentials in a password manager (he uses OnePass), verify login during the call, frontload 2FA to get it out of the way, then for remaining 2FA (Google/Microsoft) ask the client to send the code directly, use an anti‑detect/multi‑login browser to store fingerprints and cut 2FA frequency to once a month or every two weeks, set a defined Slack availability window (e.g., 12‑2 PM PT) so you can respond quickly to code requests, and offer free maintenance on retainer builds.
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.
I recommend doing a kickoff call right after receiving payment or closing the deal. On that call, your sole goal is to gain access to every account you’ll need for the service. It’s straightforward: just say, ‘Hey Pete, let’s get everything running for you.’ In my experience, the main hurdle with automation integration is two‑factor authentication and access requests. If you’ve worked with someone like this before, you know people constantly ask you to unlock accounts or set them up—which I dislike. Instead, I handle everything ahead of time on a brief 30‑minute call: we walk through signing up on each platform together, I get the necessary access, and after that we don’t need to talk again except for my daily updates you receive each morning. By the end of the call I’ll have all required platforms—say, platform one, two, and three. If occasional two‑factor authentication is needed later, it’s easy because I already have most access. From there, you’ll have full access to their accounts and never need to build anything on your device and transfer it over; I’ve already done everything directly in their accounts, so there’sno handoff. That’s my recommendation.
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.