If the client is the one paying, how do the specifics work? For example, how would they trust me to handle their payment details?

#114 · $350K/M AI Automation Expert Answers Questions For 80Mins

youtube ↗Agency Operations

If the client is the one paying, how do the specifics work? For example, how would they trust me to handle their payment details?

You don’t actually take their payment details or sign up to the platform yourself. The client enters their payment information directly into the platform, so you never have access to their credit card. In practice there’s very little risk: the client can always get a refund if you upgrade their plan without notifying them, and you can check the logs to see who accessed the account. As a beginner you don’t need to charge clients large monthly fees; the subscription cost is usually only about 1% of the total problem you’re solving for them, so it’s not a big deal.

paymentclienttrust

Related answers

youtube ↗Pricing

When setting up an automation flow, who pays for the specific subscriptions?

Most of the time the client pays for services like Apollo, Appify, OpenAI, and NAN. You can use your affiliate links so you get a cut, but the client is the one covering the subscription cost. They enter their payment details directly into the platform, so you never handle their credit card info. The risk is low, and as a beginner you generally don’t charge the client for those recurring costs directly.

subscriptionsclient paysservice delivery

youtube ↗Pricing

Should I include the pricing of client-managed accounts (like NAND) in my fees, or treat it as an additional expense for the client?

I recommend treating those costs as an additional expense for the client. Add a line item on your pricing table labeled 'pass-through fees' or 'platform fees' to make it clear you don't retain any of that money. This is the simplest way to start and also protects you from liability—if you ever offer a guarantee tied to results, the client pays you only if you deliver, otherwise they get a refund. Conceptually separating the fees this way keeps things clean. I agree with Mr. Gfar that the client should manage their own accounts. Regarding which platform to use—Make or NAD—pick the one you're most comfortable with; there's no need to have clients set up both, as each platform can do what the other does.

pricingpass-throughclient-accounts

youtube ↗Pricing

Nick, truly appreciate the value from your videos. I want to know how you'd set up the API keys, password, and payment methods when onboarding clients for a new project. Would you set the tools up yourself from your account, but for them, and then you charge them a monthly return? Do you set it up from their account, use their passwords, etc.? So, the billing and the data goes directly to them. I have the billing and the data and everything go directly through them, and then they just share me their username, password, email, everything that I need in order to access the account. So the account is doiciled on them if that makes sense.

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.

api keyspayment methodsonboardingaffiliate

youtube ↗Pricing

For a cold email system that relies on paid platforms like Instantly, should I cover those platform costs by charging the client a small monthly maintenance fee, or should I have the client pay for the platforms directly?

There's only a minor difference between the two — either works. If having the client pay directly is a limiting belief for you, just get them to pay you instead. But the benefit of having the client sign up for the platform themselves is affiliate revenue: you can get a cut of their Instantly signup (e.g. 30-40%), so if they spend $100/month you've effectively made yourself an extra $40/month, plus there's perceived value in being a platform partner. I personally prefer having the client own the whole tech stack and sign up directly, mainly to avoid liability — when a client inevitably stops working with you (it happens a lot), you don't want to be stuck handing off usernames/passwords for tools you're sharing. Yes, it takes a bit longer to onboard since you have to walk them through signup on a kickoff call, but it eliminates that handoff problem entirely.

cold emailinstantlyclient billingaffiliate revenue