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

Memberships

12 contributions to AI Automation Society
Two paths into AI work (which one is yours?)
Most YouTubers show you a single path into AI work: start an automation agency → take clients → sell automations. It works. I know because I built an AI automation agency and sold it. But it's not the only way in, and for a lot of you it's not even the best one. I made this video to break down the two real paths: The AI Career Opportunity Nobody is Talking About in 2026 Here's the quick version: Path A is the agency play. You go independent, take clients, build your own practice. Path B is the employment play. You become the most AI-fluent person in the room, and that's who companies want to hire or promote for AI work. If you're already employed, you become the obvious pick when an AI role opens. If you're looking to get hired, or move somewhere better, you walk in with real work instead of just claims. It's the less obvious path, but it's actually the more common one. The employment numbers (see the video) are shocking actually. Watch the full breakdown in the video. Then do one thing for me in the comments because I'm super curious: Tell me which path you are on. A, B, or both. And one line or so on why. I'll be reading these. Nate
Poll
1095 members have voted
1 like • 30d
@Mahendra Sharma Depends on your goals.. what path are you on?
Zero to One Babyyyy!!!
After following Nate and the general AI industry for the past year, starting to build and practice and do the coursework, I finally locked in my first client!! I can't claim victory on an amazing sales strategy as that part was a God thing but the preparation and skills offered through a lot of Nate's content made it possible. I'm 38. I have a full-time job and a toddler and it was still possible. You can do it!!!
Zero to One Babyyyy!!!
1 like • Jun 7
@Ty Aleivve Great job! Sounds like you’ve made a real impact on your client’s success! 🙏
How much should your AI OS know about you?
Honest question for the builders here. Over the last weeks I gave my AI OS access to more and more of my life, my accounting, my trading journal, my meeting transcripts. It makes me faster every day and I genuinely love it. And still, some evenings a thought creeps in: I'm feeding a big corporation a pretty complete model of how I think, decide and spend money. We might be the first generation training AI on our own lives, and nobody knows yet what that data is worth or who ends up holding it. So where do you personally draw the line? Is there data you refuse to give your setup, or is the productivity simply worth the trade?
1 like • Jun 7
@Roman Hromenkov Agree fully, that info is likely already out there albeit piecemeal. IMHO what you are adding (potentially) is confidence. In my experience, your data is stored with a confidence rating. By confirming, your data becomes more valuable to the holder. They aren’t selling your data at that point, but confidence in your data. 1. Never put anything anywhere digitally that you wouldn’t want your mother, significant other or boss to see. 2. Always start with reading privacy policies. Make sure you are comfortable before you start - different tools may have different options. Have Claude summarize if it’s too much legalese. 3. Fast, confidential, correct - usually a trade off in there somewhere…
54% of LinkedIn posts are AI... You can tell
Originality AI analyzed 8,795 LinkedIn posts. More than half came back AI-generated. The generic intros. The recycled ideas. The weird formal tone nobody speaks in. The sentence that starts with "This is not X, this is Y" and somehow gets worse from there. But here is the thing nobody talks about... AI is not the problem here... The problem is AI amplifies whatever structure you give it. Give it flat structure, you get flat content. Give it no hook, you get a post that starts with "I wanted to share some thoughts on." Give it a list of facts with no narrative thread, you get exactly what you would expect from a robot to write. I have been building AI content systems that actually sound like the person they are trained on. There are three specific mechanics that close the gap between AI-sounding and you-sounding. The hook must create a specific curiosity gap. Not "here is what I think about automation." More like "I tested 47 webhook configs and only one never broke." The brain needs a question it wants answered. AI cannot invent that question because it does not know what is actually interesting. You have to give it one. The structure has to move. ABT (And, But, Therefore) is the simplest one. Setup AND continuation, BUT complication, THEREFORE resolution. Every line either opens a micro-question or closes the previous one. AI defaults to flat information delivery because that is what most prompts ask for. Give it a narrative arc instead of "write a post about X" and the output changes completely. The voice has to be specific. AI defaults to formal because formal is the statistical average of everything it was trained on. You have to give it voice rules. Contractions. Sentence fragments. Words you never use. The exact rhythm of how you talk. Otherwise it goes right back to "leveraging robust solutions." The wild part? People are already tuning out AI content without even realizing it. Nobody logs onto LinkedIn expecting sincerity anymore. Artificiality is what everyone expects.
2 likes • Jun 6
@Shahbaz Hussain Question: Did AI write/revise this post? Curious if this is your design flow or your actual “voice” in writing. :)
I accidentally built something this week that I didn't think was possible 6 months ago.
Was putting together a multi-agent workflow; one agent researching, another writing, another reviewing and flagging inconsistencies before anything goes out. No human in the loop until the final check. What got me was the review agent. It didn't just rubber stamp the output. It pushed back. Flagged a claim that wasn't backed up, rewrote a weak section, flagged the tone as off-brand. That's not automation anymore. That's closer to a system that thinks. The infrastructure for this stuff has moved so fast. 6 months ago you were duct-taping APIs together and hoping. Now with MCP and proper agent orchestration frameworks, you're building actual pipelines with memory, context, and decision logic baked in. We're past "automate your emails" territory. That's table stakes now 🔥🔥
1 like • Jun 6
@Johnson Muhavi What you actually built was your team! 🎯 Close knit non territorial never taking a sick day to play video games dictionary carrying team with an auditor on standby. Great job! No w-2’s required at end of year 👏
1-10 of 12
Andie Jameson
3
43points to level up
@angie-bush-4990
Automation enthusiast

Active 1h ago
Joined Mar 16, 2026
Powered by