Not every prospect should be a client. Here are the red flags. THE RED FLAGS: FLAG 1: "What's your best price?" Before they even understand the value. They're shopping on price, not solution. FLAG 2: "Can you do it for free first?" Doesn't respect your time or expertise. Will not respect your boundaries later. FLAG 3: "We need this yesterday" Unrealistic expectations from day one. Will blame you when reality doesn't match fantasy. FLAG 4: "My last automation person was terrible" Maybe. Or maybe they're difficult clients. Ask: "What went wrong?" Listen carefully. FLAG 5: Budget conversation goes nowhere "What's your budget?" "I don't know." After 3 attempts, they either can't or won't pay. THE WALKAWAY SCRIPT: "Based on what you've described, I don't think I'm the right fit for this project. I can recommend [alternative] that might work better for your situation." THE MATH: Bad client at $1,500: - 20+ hours of work (scope creep) - 10+ hours of support (high maintenance) - Negative testimonial risk - Effective rate: $50/hour Walking away: - 0 hours of frustration - Time to find a good client - Mental energy preserved THE LESSON: Saying no to wrong clients makes room for right clients. Your first priority is learning and building confidence. Difficult clients destroy confidence. Easy clients build momentum. THE QUALIFICATION QUESTIONS: "What's your timeline for this?" (Filters unrealistic) "Do you have budget allocated?" (Filters non-buyers) "What have you tried before?" (Reveals expectations) 📚 More templates in Github What red flag will you watch for in your next prospect call?

A few days ago I landed a client to help them set up an AI agent for email, Facebook, and Instagram. Working on this project taught me lessons most YouTubers don't share. This is knowledge from the trenches. Here we go. When building an AI agent, combine the system prompt and the user prompt in the same field in n8n. This gives the AI a better response to the customer. 2. Spread the information across multiple agents. Create a billing agent, a tech agent, and so on. This stops you from stuffing one agent with too much information, which leads to misfires. 3.Always use Sonnet 4.6 or higher for customer service work. It is the best model on the market for this type of work right now. 4.When updating your prompts, focus on the start and end. Add all rules and constraints there. Sometimes repeat the same rule at both ends. The AI tends to glaze over the middle section. Use the middle for FAQ information and knowledge. The AI will draw on that to write its own responses. 5.When building your knowledge base, do not write it as Question and Answer format. Do not write it like: "When a customer says hello, answer with hello back." Write it so the AI can use the data to form its own answer from the available knowledge. For example, I write something like this: - **Topic: Ball Slicing (Driver)** - **Terms**: "stop slicing with driver", "driver slice", "curving right" - **User Intent**: Ball curves excessively to the right (for righties). - **Advice**: Strengthen grip slightly, aim a bit left, and shallow the swing path. Shorten the backswing and prioritise tempo over raw speed. When you write it this way, the AI reads the user intent and writes a message based on it. It is not rigid. I hope this helps someone when they start building their own agent!

No contract = Problems waiting to happen. Here is the simple template I use. THE SECTIONS: 1. SCOPE "I will build [specific automation] that [does specific thing]." List exactly what is included. List what is NOT included. 2. TIMELINE "Work begins on [date]. Target completion: [date]." 3. INVESTMENT "Setup fee: $X (50% due before work begins, 50% upon completion)" "Monthly maintenance: $X (begins after completion)" 4. MAINTENANCE INCLUDES - Weekly monitoring - Bug fixes - Minor adjustments - Email support 5. MAINTENANCE DOES NOT INCLUDE - New features (quoted separately) - New document types (quoted separately) - Additional integrations (quoted separately) 6. REVISION POLICY "Includes 2 rounds of revisions within original scope." 7. TERMINATION "Either party can cancel with 30 days notice." THE TOOLS: HelloSign (free tier): Digital signatures Google Docs: Draft the contract PDF export: Professional delivery THE CONVERSATION: "I'll send over a simple agreement that outlines what we discussed. Just covers scope, timeline, and investment. Take a look and let me know if anything needs adjusting." THE REALITY: In 12 months and 11 clients: - Contracts signed: 11 - Disputes about scope: 0 - Confusion about what's included: 0 Clear contracts prevent uncomfortable conversations. THE MINIMUM: Even for small projects, get in writing: - What you're building - What they're paying - When it's due Text message confirmation works better than verbal. 📚 More templates in Github Do you have a simple contract template ready for your first client?

So something that has happened to me so far when working with new people is that after a large majority of projects, the person I’m working with asks me, ‘What else can you do for me?’ or says we need to work more together because they’re really impressed. The craziest part is that I’m not doing anything crazy. When I get the job, I build the solution as fast as possible, ask for feedback, and then keep building until it’s done. This is actually how the people I work with end up upselling themselves on more things from me. What I’m trying to say is that once I get hired, I try to deliver the automation within 2 to 4 days. Most of the time it goes even faster, depending on how complex it is. By doing that, I get repeat business and more orders. So for anyone out there who wants to get clients, when you get that one, overdeliver so they’ll pay you more.

Guess what? It's exactly 80 days ago, when I started with a local n8n setup. Not more than some "maybe" and the desire to do something. 80 days ago. That was Oct, 1st. I accepted the challenge. The last 80 days I spent hours building, supporting, coaching, reading. I texted some friends and family. I registered a server. A domain. Participated in a challenge - successfully. Went through the 30 Day accountability plan here. --> Thanks to @Duy Bui Amazing how far I have come in this short time! 80 out of 360 days (roughly about 22%). I got stuck - and you helped me to get unstuck! --> Thanks to @Chris Jadama, I still remember your Loom spotting my HTTP request issue, spot on. I found friends 😊 --> Thank you, @AI Automate Services 🥰 My lesson? Conclusion? I'm right at the beginning. Next year is around the corner. It will be good, really good. Some fresh new 365 days. Check this out. This, was meant to encourage you. Every single one of you. You might be at the beginning or before the finish line, doesn't matter, everyone can do it, everyone can share. And if you need some inspiration, check out @Sarah Martinez posts. 🎉