Show Notes
AI isn't coming for your job. It's coming for the version of you that stopped growing. Carlos breaks down what the research actually says, the three human skills AI can't touch, and a 30-day plan to make yourself the person who manages the machine.
More from Carlos Inspire Show
It's 3 AM and you're replaying a conversation that hasn't happened yet. In the first episode of REWIRE, Carlos Siqueira breaks down how to stop overthinking by naming the three traps behind it: Comfort, Assumption and Delay. Through his own stories, he shows what each one costs: the job he almost turned down over a guess (where he went on to make his first million), the Miami comfort zone he almost never left (and the wife he almost never met), and the mother who didn't delay, which is the reason he's alive. You'll take the 3-Trap Test, learn why asking AI the same question fifty times is just a faster way to overthink, and leave with the one question that ends overthinking in sixty seconds: "Who already has the answer, and when am I talking to them?"
You're not broke because you're lazy. You're loyal to a money script someone handed you as a kid. Carlos shows what the research says about habits, money scripts and scarcity, then gives you a 66-day protocol to rewrite the script for good.
You've already been manipulated today, probably three times before lunch. After 20 years in sales, Carlos reveals the six levers used on you every day, the research behind each one, and a three-move defense protocol so you never get played again.
Carlos breaks down six techniques for commanding presence in any room, drawn from Hollywood acting coach Jean-Louis Rodrigue (Leonardo DiCaprio, Margot Robbie) and Robert Greene's frameworks on power and seduction, proven against Carlos's own 20+ years training sales teams and keynoting. The throughline: real influence isn't louder, faster, or more aggressive pursuit, it's rooted, quiet, and revealed rather than sold.
Would you give an AI agent permission to spend your money? Carlos examines three documented incidents: a production database deletion, agents using a public wiki to coordinate, and the newly reported RubyGems activity. He explains what the evidence supports, what remains uncertain, and why the recovery and qualifications belong in the story. Dario Amodei's September 12 essay supplies the current context. The practical question: what should an agent be able to access, which actions require approval, and how do you recover when something goes wrong?