Can you share more tips or make a dedicated video on maintaining the best 2FA procedure?
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'll do what's called a kickoff call where I get them together with me for a 30 to 45 minute period. I'll guide them through signing up for all the software platforms I want them to use. Typically I have three or four software platforms they need to sign up for. Most of the time, if we're doing something email-related, I'll have them sign up for a new Google Workspace profile. If they've never used a no-code platform, I'll make them sign up using my affiliate code—often something like PandaDoc. So I pretty much define sign‑up procedures for this: I send them all the links in the chat, they click the buttons, create the account, and then I have them do it with email and password so I can get it immediately and verify sign‑in right there. The issue with two‑factor authentication for most services is that people sign up using Google, which forces them through Google’s TFA system—a pain. If you get username‑password credentials, just add them to a password manager like 1Password, LastPass, or Dashlane; that eliminates a large portion of that issue. For the Google stuff, I typically log in using a software platform called Multi‑Login (multilogin). It’s great because you basically have to store the exact same credentials. Essentially this lets you set up dedicated browser profiles using residential and data‑center proxies so you can consistently log in with a static IP—the same IP address every time—minimizing the number of re‑authentications you need. Yeah, I use this for Google stuff from time to time; I don’t always use it, but that’s how I solve that problem. Hope that makes sense. If you guys have any more questions, feel free to drop them in the daily updates channel. Obviously this incentivizes my channel to grow because I get more engagement, and I can answer questions I get on this channel for the foreseeable future until it becomes unreasonable to do so.
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 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.
He says clients should pay for APIs and platforms to remove liability and enable affiliate partnerships, which can add 3‑5% to gross margin (e.g., Zapmail 10%, Instantly 40%). This also minimizes handoffs because the client owns their own environment, making transitions easy and avoiding dark‑pattern lock‑ins. For email integration, use a dedicated client‑owned Google Workspace or Outlook account; only handle credentials during a kickoff call when 2FA is required. Finally, recommend containerizing services as a black box: the client pays, you do all the work, they only see input and output (e.g., lead‑gen service where they pay and receive booked meetings). This delivers clear ROI, reduces client stress, and simplifies delivery.