Activity
Mon
Wed
Fri
Sun
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
What is this?
Less
More

Memberships

GoHighLevel + Vibe Coding

1.8k members • Free

Setterlun University™

4.2k members • $17/m

ADHD Focus Founders

888 members • Free

Agent-N

6.3k members • Free

AI Automation First Client

767 members • Free

AI Agency Starter Kit

2.5k members • Free

Community F.I.R.E. Mojo

1.5k members • Free

HYROS Ads Hall Of Justice

4.5k members • Free

AI AUTOMATION INSIDERS

2.4k members • Free

9 contributions to AI Automation First Client
12 Hours Building What Nobody Bought vs. What Sold in 1 Week (Painful Lesson) 🔥
Spent 12 hours building perfect document classification workflow. Multiple AI models. Advanced logic. Posted about it. Demoed it. Zero clients interested. Not one. WHY IT FAILED: I built what I thought was cool. Not what clients actually needed. Document classification = technical problem I enjoyed solving. Invoice processing = boring problem clients desperately want fixed. THE MISTAKE: Got excited about technical complexity instead of business pain. Built for Reddit upvotes. Not for client checkbooks. Client doesn't care about: AI algorithms, multi-model architecture, technical sophistication. Client cares about: "Will this save me 10 hours weekly? How much? When can we start?" THE REALITY CHECK: Week building classification system: 0 interested clients Week building invoice processor: 2 signed clients ($3,300 total) Market speaks clearly. WHAT CLIENTS ACTUALLY PAY FOR: TIME SAVINGS - invoice processing, form extraction, receipt tracking COST REDUCTION - avoiding new hires, reducing errors GROWTH ENABLERS - scaling without proportional headcount FRUSTRATION RELIEF - eliminating tasks they hate Not "impressive technology." THE BORING TRUTH: Invoice processing = boring, simple, sells immediately Document classification = interesting, complex, nobody buys Your ego wants complex. Your bank account needs simple. THE REDIRECT: Took that classification system. Reframed it completely. Before: "AI-powered document classification system with multi-model architecture" After: "Multi-vendor invoice router - automatically sorts invoices by vendor and posts to correct categories. Saves 3 hours weekly." Same technology. Different positioning. Sold to 2 clients within a week. $1,500 each. THE PATTERN: Features nobody asked for = features nobody pays for. Problems people complain about daily = problems people pay to fix. YOUR ACTION PLAN: Stop building cool technology demos. Start solving boring, repetitive problems people openly complain about. Invoice entry. Form processing. Receipt categorization. Document filing.
2 likes • 3d
Building cool workflows and fancy automations that are completely unvalidated is a guilty pleasure of mine. Makes me feel warm and fuzzy on the inside just by reviewing my past portfolio of them. But reading these types of posts continually helps remind me that growing my business gotta be placed before growing my own ego. Build what they want, not what you want them to want! Great share! @Duy Bui
embarrassing confession: my first invoice workflow was garbage 😃
client sent 20 test invoices. my extraction got 6 right. SIX. tried 3 different approaches: - built-in pdf node: worked on 4 invoices - regex patterns: broke on every layout change - ocr + manual parsing: took 2 hours per invoice format was about to refund the client then someone here mentioned pdf vector. tested it expecting nothing. 18 out of 20 extracted correctly first try. the llm mode just figured out different layouts automatically. same invoices. same workflow. different extraction tool. completely different results. client has no idea how close i came to quitting lol what tool swap saved your project?
1 like • 10d
- "A hero is one who knows how to hang on for one minute longer.”
The Objection I Hear Most (And How I Overcome It) 🔥
Almost lost an $1,800 deal to this one question. Client was ready to sign. Then asked: "But can't I just hire someone on Upwork for $15/hour to do this manually?" My stomach dropped. He was right. He could. THE OBJECTION: Cheap labor exists. Virtual assistants. Upwork. Fiverr. Why pay $1,800 for automation when $15/hour person costs $600/month? Valid question. Deserves real answer. MY FIRST RESPONSE (WRONG): "Well, automation is better because..." Defensive. Made me sound desperate. Not convincing. THE REFRAME THAT SAVES DEALS: "You absolutely could. Let's talk through both options." HIRING APPROACH: - $15/hour × 10 hours monthly = $150 - Sounds cheap - But: Training time, management overhead, sick days, turnover - Real cost: $200-250/month - Plus: You're still managing someone AUTOMATION APPROACH: - $1,800 setup (one-time) - $200/month maintenance - Works 24/7, no management - Never sick, never quits - Scales without hiring THE CALCULATION: Month 1-8: Hiring cheaper ($200 vs $1,800 + $200) Month 9+: Automation cheaper (paid off setup) Year 2: Automation saves $2,400 annually But here's the real difference... THE RELIABILITY ARGUMENT: "Automation processes your 80 invoices monthly with 99% accuracy. Every time. At 2 AM if needed. No vacation days. No training new people when they quit. How much is that reliability worth?" CLIENT RESPONSES: "I didn't think about turnover..." "Managing people is exhausting..." "Actually had 3 VAs quit this year..." THE CLOSE: "If this was just about saving money, hire the $15/hour person. But if it's about reliability, scalability, and your sanity - automation wins." He signed that afternoon. MY CURRENT OBJECTION FRAMEWORK: 1. Acknowledge their point (they're not wrong) 2. Add hidden costs they missed 3. Emphasize reliability and scale 4. Let them choose based on full picture Works on: "Can't I use free tools?" "Can't I do it myself?" "Can't internal team handle it?" WHEN TO WALK AWAY: If they're purely price shopping, you're not the fit. Let them try cheap option. They'll be back in 3 months when it fails.
2 likes • 21d
It's great sharing these insights on sales processes like objection handling to keep these skills improving along the way. Jeremy Miner, big sales guy, says you should always agree with a prospect who raises these valid objections. You do this to disarm them, then redirect to the outcome based thinking. Do they want reliability? Should be a yes answer, and if not, they probably wouldn't buy anyway or aren't the client you want to sell to. Really good post, as usual @Duy Bui . 👍
3 likes • 21d
@Duy Bui The part about hiring the cheapest option ans then letting them "come back later when it fails" is so true. Seen it quite a few times myself
Maintenance Retainers - The Revenue That Compounds 🔥
Setup fees paid my rent. Maintenance retainers built my business. Month 12: 8 active maintenance clients = $1,920 MRR. Every month. While I sleep. WHY MAINTENANCE MATTERS One-time projects = revenue rollercoaster Maintenance retainers = predictable income It compounds: Month 1: 1 client × $200 = $200 MRR Month 4: 3 clients × $220 avg = $660 MRR Month 8: 6 clients × $240 avg = $1,440 MRR Month 12: 8 clients × $240 avg = $1,920 MRR That's $23,040 annually from ongoing value delivery. WHAT MAINTENANCE INCLUDES WEEKLY MONITORING: - Check workflow health - Review error logs - Verify processing volumes - Confirm all integrations working FIXES WHEN NEEDED: - Workflow breaks - Integration issues - Format changes - API updates QUARTERLY OPTIMIZATION: - Review efficiency - Identify improvements - Add requested features - Update field mappings PROACTIVE ALERTS: - PDF Vector credit usage monitoring - Processing volume changes - Error rate increases - Integration health checks HOW TO PRICE MAINTENANCE Rule of thumb: 15-20% of setup fee, monthly $1,200 setup → $200/month $1,800 setup → $300/month $2,400 setup → $400/month Include tool costs (PDF Vector API credits, Make.com operations) in maintenance fee. THE VALUE PITCH "Setup gets automation running. Maintenance keeps it optimized. As your business grows and changes, we'll update the automation to match." Not "in case it breaks" (sounds reactive) But "ongoing optimization" (sounds proactive) CONTRACT STRUCTURE Start with month-to-month (builds trust) Offer 10% discount for annual prepay (after 3 months) Client can cancel with 30 days notice Reality: When automation is saving them hours monthly, they don't cancel. MY RETENTION NUMBERS Average client lifetime: 11 months Longest client: 18 months (still active) Churn rate: About 15% annually Reason for leaving: Business closed or sold HOW TO ACTUALLY DELIVER MAINTENANCE Set calendar reminders for weekly checks (takes 10 minutes per client) Use monitoring dashboards (one view for all clients)
4 likes • 23d
@Duy Bui Pretty cool. Do you have something setup that monitors uptime for all nodes/servers/services? I had email sending suddenly stop for my client and didn't notice it for days. None of their booking reminders wrre sent out during this time 😖 Turns out google cloud just stopped the virtual machine n8n was running on ( why you doing this to me google??! ). I didn't have anything to monitor this. I have a backup n8n instance now where I copy over duplicate workflows to and so makes it possible to instantly turn back on any workflow. Wondering if you set up outer monitoring of system health that can instant notify you if anything goes down or offline.
1 like • 22d
@Duy Bui This type of quick gold info is why this skool group rocks! Will be using uptimerobot from now on. Thanks Duy!
Merging messages into one in ManyChat
Hi guys, How can I combine messages that users send in small separate parts on Instagram into a single message and process them in ManyChat? Only good people who want to help for free should comment.
1 like • 27d
Hey Ez, I don't use ManyChat cause it's very pricey and more for non technical people ( which hopefully we are not in the category of, lol ) The cheat code is to use chatwoot. Cost can be free if you self host and can do everything that manychat does and more.
1-9 of 9
Alex Feher
3
37points to level up
@alex-feher-2882
Navigating the frontier of AI development

Online now
Joined Oct 15, 2025