How do you approach handing over the system and process to business owners who aren't technically confident? Does it become a one-time sell with a 'call me if it stops working' arrangement, or if they ask you to host it, do you just say yes?
I don't host it myself — I sell it as their intellectual property. Right after payment, we jump on a kickoff call where I have them sign up for the necessary platforms themselves rather than building on my own accounts and renting access to them — I want them to actually own the infrastructure, since it's their ideas, systems, and pipelines, and that way anyone can run/manage/improve it down the line even if things don't work out with me. Clients tend to respond well to that pitch. We sign up for the platforms together on the call (usually 10-15 minutes), I grab the credentials/API keys/2FA right then, and typically keep access for a few days to finish setup — that avoids me effectively holding their business hostage, which I don't want to be in a position to do. On maintainability: I offer a maintenance period, usually 1-2 weeks depending on system size, and lifetime maintenance if they're on a retainer — framed around 'peace of mind': a 99% uptime SLA, 24-hour fixes if something breaks, plus extras like builds, meetings, daily Slack availability, and monthly team training. That tends to be a strong sell.
I start with a kickoff call where I deliver quick wins to minimize buyer's remorse, and I always take payment upfront before any work begins - never considering a client 'onboard' until the money is in my account. After receiving payment, I create a detailed proposal that serves as both a sales document and a roadmap. Roughly 60% of the proposal outlines the client's problems, demonstrating my understanding from any prior small project; about 20% covers the proposed solution; the remaining 20% discusses logistics, principally compensation. I typically pitch a large monthly fee - recently moving from $6,900 to around $12,000-$12,300 - and often add a revenue-share component to align incentives, inspired by the idea that sharing upside makes both parties more comfortable and can lead to more money. I discuss performance-based versus flat pricing, noting that beginners should lean performance-based, intermediates may go flat, and experts often return to performance-based because they have confidence in delivering results. Once the client agrees and pays, I invite them to a kickoff call to set communication expectations: I'm highly reachable via Slack (within 15 minutes) and hold daily office hours from 12 p.m. to 2 p.m. PT, plus a weekly strategy session. I ask clients to commit to the same recurring time each week for at least 50 out of 52 weeks, emphasizing consistency so they take the calls seriously and see ongoing value. During each meeting I review wins from the past week, outline what I'll do next, and address any questions or fires, ensuring I always show up with something tangible to justify the retainer. I then follow the roadmap, checking off the 45-plus tasks in order, and optionally sync with the client's project-management system (though I've moved away from using my own ClickUp board as the single source of truth). I also note that other agencies like DesignJoy use shared boards, but I prefer bringing a quick note of wins and next steps to each meeting.
You should hand over the system completely so that it becomes 100% the client's intellectual property and hosted on their own infrastructure. Holding hosting over a client's head as leverage—where they only stay because they fear losing the system—is a lazy sales tactic used by weak business owners.
The right way to retain clients long-term is by consistently delivering ROI and finding new ways to add value so that they choose to stay, even though they could walk away. Pitching clients upfront that they will own all the IP, SOPs, and code makes closing deals much easier. In the long run, taking the high road of maximum value delivery will far outperform trying to hold client systems hostage.
Oh, here we go again. Should I deliver the entire workflow to the client or retain control and run the automation on their behalf? Well, somebody spent 1.5 years getting really good at workflow automation but probably hasn't made any money with it. How much cooler would it be if you learned enough to talk the language in a couple of weeks, then just started talking to customers? You probably wouldn't have been in this situation. In 1.5 years you could have a big book of business with 20 clients. Time will pass anyway. A lot of lead generation mechanisms like cold email and Upwork just require time to pass while active. You might as well have planted a tree 20 years ago; the second best time is today. That's a good analogy. To answer your question about delivering the entire workflow: yeah, deliver it to the client. Then why would they need you? They don't need you for a one-off, but they'll want you if you make them choose needs and such. I get it; it's kind of a Machiavellian way to run the business—strategic and logical—but you don't build as much goodwill with clients and it becomes annoying working with them, especially with handoffs. So, what are you going to do? Hold the business hostage when they want to let you go? Or would you rather be in a situation where the client wants to keep you on because you constantly produce massive value? I like that situation; having a rising floor where clients want more value forces you to creatively find ways to deliver it. That's one reason I agree so quickly.
That's a philosophical thing. You're terrified of something, and so you're running away from it. Does that really seem like a sustainable way to live your life? You're probably going to run into issues and things that you are terrified of in the future. And if you make a decision now to set the precedent of running away from them, how is that going to benefit you moving forward? If you are terrified of doing something, almost by definition, you should try doing it. Is this the straightest line path to making money? No. I don't do the cold calls these days, as I've mentioned a number of times, but the obstacle is the way. If you have an issue, you should tackle that issue head‑on. You should at least try to do that at least once, maybe at least 10 times. That's my recommendation. So, it is not better to create an automated product and sell it using ads and content. I would make sure you know how to do this first before you try doing anything else.