How should I handle client security and working solo with five high-quality individuals?
Get those five high‑quality individuals together and focus on the top lane (gank top lane) all the time—just kidding, that's a game reference. Regarding security when working solo, I don't think about it much, so it's hard for me to give advice. If you mean working solo with a team of five people, secure yourself reasonably but don't make security the sole focus, or you'll never get anything done. For client security, I use an 80/20 approach: I collect their credentials (emails, passwords) for the accounts I'll manage and store them in a single password manager (not plain‑text). Because I also have access to their API keys, I'm a bit more secure than most of my clients. I basically centralize all that information.
We actually tried separate Chrome profiles per client — it works until you hit about 10 profiles, since Google doesn't easily allow more than that. You could also use something like a Multilogin instance to store credentials with longer-lasting cookies and residential/Bright Data proxies, giving you a fixed IP so you get logged out less (especially useful for accounts with 2FA). But honestly, I don't do any of that — I just use my own browser profile and manage everything with 1Password, which solves both the multiple-logins problem and general credential coordination. On handoff: since everything is built directly in the client's own accounts, there's no major handoff needed — I just send an email with a 20-minute SOP video plus a written Google Doc walking through the whole system, including how to maintain and upgrade it themselves, so they're covered even if we stop working together down the line.
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'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.
When I first started I was juggling a lot without a defined project‑management system. Eventually I got a system, but I don’t think you need a fancy tool right away. Managing two or more clients depends on what you’re building, deadlines, expectations, and whether the client is recurring. For recurring clients, scope the process and deliverables so you allocate time for each. Set a unified schedule for client management—e.g., be available on Slack from 12 p.m. to 2 p.m. PT—and bundle work. I usually set aside two hours to handle about 20 clients because only one or two will message daily. A 2‑hour Q&A period in a retainer adds perceived value with little effort and works well for progress updates. When building for multiple clients, I create separate make.com environments for each, keep a big password manager, and use templated projects—copy a blueprint and make a few adjustments—so everything stays isolated. If it feels overwhelming, simplify the builds. Juggling two massive $20k custom projects is stressful, but handling five simple templated projects that cost $3‑4k and take two hours each is much easier. I didn’t adopt a formal project‑management system until I was making at least $10k a month; before that I just used email and Slack. Develop personal and mental systems that let you avoid external tools, because those skills transfer across roles. Improve your ability to project‑manage if that’s a major issue.