← All questions

#141 · Simple way to add 3-5% to your margins (AI agencies only)

youtube ↗Agency Operations

Can you provide a detailed guide on onboarding, payment splitting for chat API services, and account access management?

For onboarding, use the kickoff call SOP available in Maker School (search 'kickoff call SOP' in the forum). Regarding payments, have the client pay for all tools (chat API, services like Panda, Make.com, etc.) so you can use affiliate links to boost margins by 3‑5%, simplify handoffs (everything stays on the client’s account), and remove liability for tools and payments. If the client refuses to pay these fees, it usually indicates you haven’t delivered enough perceived value; focus on increasing ROI so the software cost feels marginal.

onboardingpaymentsaccount accesschat api

Related answers

youtube ↗Agency Operations

How should I deploy automation agents or chatbots for clients—who pays for APIs/platforms, whose email to integrate, and should the client run the automation or do we manage it?

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.

automation deploymentclient onboardingaffiliate revenuehandoff
youtube ↗Pricing

I’m pitching a customer‑support chatbot for an e‑commerce store that handles WhatsApp and Instagram DMs. How should I price the setup fee and monthly retainer?

First, figure out how much revenue the client currently makes and estimate the incremental lift your chatbot will provide. If you calculate that the bot will generate an extra $3,000 per month, a reasonable pricing model is to charge about 30 % of that added value. In this example you could charge roughly $1,000 per month for ongoing maintenance and a one‑time setup fee around $1,485 (plus a monthly maintenance component of about $943). In practice most chat‑bot services sell for around $1,000 per month; larger, more hands‑on implementations can command higher fees, but a good rule of thumb is to price based on the value you deliver, not just the hours you work.

chatbotpricingsetup feemonthly retainer
youtube ↗Pricing

Who should pay for software subscriptions (like Apollo, Appify, OpenAI, Make.com) when delivering automation services to clients — the agency or the client? If the agency pays, do they need separate subscriptions per client? If the client pays, how does payment and trust work?

If you're building a system that generates $5,000 a month in value for a client, having them pay a small percentage fee is not a big deal; they care about the upside, not the tiny downside. As the service provider, you might worry about subscription costs, but the AI and automation field attracts technical people who overthink this. Get the client to pay for everything. On a kickoff call, walk them through exactly which platforms they need to sign up for. This builds perceived value because they see the technical setup and appreciate you handling it. You can also use your affiliate links—being a Make.com partner, for example—to earn 3–5% kickback or give clients discounts. If a client stays for a year, you earn recurring affiliate fees; e.g., 40% on a $100/month plan yields $40/month, or $480–$500 per year per client even if they stop working with you. This approach also minimizes your liability since you’re not making monthly payments on their behalf. It’s the best way to handle software costs. If you’d like a kickoff call SOP, I have a document that outlines how to run the call and get clients signed up on the platforms.

subscriptionsoftware costclient paymentautomation
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