AI-Ready Or Not? cover art

AI-Ready Or Not?

AI-Ready Or Not?

By: Travis Scott
Listen for free

This Season's Biggest Deal | $0.99/mo for 3 months + $20 Audible bonus

Auto-renews at $8.99/mo. after 3 months - terms apply.
Summary
Most companies are buying AI tools. Almost none of them have the data, processes, or systems in place for those tools to deliver. The CRM is a mess. The processes aren't written down. The tribal knowledge is locked in three people's heads. Then the AI gets layered on top, and nobody understands why it doesn't work. AI-Ready or Not is the show about fixing the foundation first. Host Travis Scott talks with founders, operators, authors, and practitioners about how they're actually using AI. What's working. What's not. What they had to do to make it work. New episodes every two weeks.©️RainierDigital LLC 2026 Economics
Episodes
  • A Trial Lawyer on Cutting the Noise Before Adding More AI
    Nov 19 2026
    Adam Phillips was alone at a hotel desk at 3:00 in the morning, cutting videos for a trial. He was away from his family, with no staff to help. That was the moment he decided something had to change. About a year later, his firm runs on an AI brain that knows every client, every meeting, and every email. It reconciles all of it overnight. The surprising part is what he built it for: to make his staff less burnt out and his firm feel more human to clients."You're talking to my assistant, to me, to my attorneys, and it feels like you're talking to your hometown lawyer."About This EpisodeAdam is a trial lawyer in San Diego who started working with AI only about a year ago. That was after joining Dan Martell's Elite group, which he and Travis are both part of. He describes the system he built as two brains. The legal brain is closed. It holds his memos, case law, and statutes, and it pulls and categorizes a new case when one comes up. Only one agent is allowed to connect it to the rest of the system. He set it up that way after watching general chat tools hallucinate, and he says the design means it can't cite a case that isn't real. The operational brain is the one most business owners would recognize. It holds context across the whole firm, from meetings and emails to client records.Every night, the system runs what his team calls the night shift. It reads through the day's inputs. It works out what's important, where a document belongs, who needs to make a decision, and what's missing from the calendar. When a client calls to ask about a scheduled medical procedure, his staff can answer without making the client repeat themselves. Adam built it mostly on Claude Code. It runs on a Mac Mini, with Dropbox and an external drive backing everything up every night, plus Outlook and the firm's phone system feeding it context. He is also clear that he doesn't want to depend on one vendor. After a tool he relied on shut down on him, with a lot of his work built inside it, he now thinks about which models he could move to if he had to.Travis shares where he is with his own second brain, including a team of about 20 agents he built in a week. Then he put them to a real test. He handed them a list of client build tasks so he could take his son to a pumpkin farm for the afternoon. It wasn't perfect, and it still gave him the time back. That leads to one of the most practical parts of the conversation. Adam built a full client portal, found that clients weren't really using it, and scaled it back. His rule now is that if something adds noise, it makes things worse.Adam also walks through his read on California SB 574, a new law on how attorneys can use AI. In his telling, much of it turns existing good practice into a rule, with new requirements around disclosing generative AI use in court filings and firm-wide responsibility for bad citations. Both of them land in the same place on accountability: AI can do a large share of the work. A professional still has to check it, the same way you would check anyone else's work before it goes out.Adam's comments on California SB 574 are his own analysis shared in conversation, not legal advice.The conversation ends on where Adam wants to take this next. His answer is less AI, at least from the client's side. He wants the technology running in the background, lowering costs, while clients feel like they are dealing with a hometown lawyer who knows them.About Adam PhillipsAdam C. Phillips is a trial attorney and the founder of the Law Offices of Adam C. Phillips in San Diego, California. He tries cases himself and says he hasn't lost a trial in 15 years. After a stretch of trial work that left him burnt out, he spent the past year building an AI brain for his firm with a closed legal knowledge base. An operational layer gives his staff real-time context on every client. He now helps other attorneys set up similar systems for their own firms.Key TakeawaysSeparate what must be right from what must be current - Adam keeps legal research in a closed brain with a single agent linking it to operations. He says that structure is why it can't cite a case that doesn't exist.Run a night shift - His system reconciles each day's meetings, emails, and documents overnight, so decisions, filings, and calendar gaps surface without anyone hunting for them.Build so you can switch - A tool Adam depended on shut down on him. Owning your workflows and context lets you switch models when prices or products change.If it adds noise, cut it - His client portal sounded great and went mostly unused, so he scaled it back. Everything the system surfaces should be something someone needs to act on.Check AI the way you'd check a person - Adam's test: you wouldn't send out a brief from someone you just hired without reading it, so there's no reason to treat AI output differently.Aim for invisible - The goal he describes isn't more automation in front of clients. It's a firm that feels more personal because the...
    Show More Show Less
    42 mins
  • Why Bad Data Breaks AI with Heather Robinette
    Nov 3 2026
    You can build a dashboard that pulls together your forecast, call transcripts, and CRM. You can build an agent that handles one task surprisingly well. But if you don't trust the information underneath it, a confident answer doesn't get you very far.“So it's just a good reminder, too, that just 'cause it sounds confident doesn't mean it's right.”About This EpisodeHeather Robinette joined me to talk about what changed after she completed Overclock's 10-week AI for RevOps course. Before it, she mostly used AI through chat. By the end, she was connecting APIs, building applications, and working with agents. The useful part of that story is what she started doing with those skills. She describes pulling call information, Salesforce data, and weekly forecast discussions together to give leadership more context around a forecast. Her example of a risk-adjusted number is illustrative, not a reported business result.She also walks through a marketing dashboard that started with sourced versus influenced pipeline. Then came campaign performance, conversion rates, goals, and the questions her team actually wanted to answer. She estimates putting about 20 hours into it through repeated iteration. Now the team has somewhere to start when it wants to understand a campaign, instead of asking her to pull every number. That is a practical change in how the work gets done, even if building it took more than a clever prompt.I share some of the smaller agents I've been building for my own work: triaging email, drafting replies, and finding duplicate tasks in Asana. We also get into the context problem. Someone helping with a project needs more than a task name. They need to understand the conversations and decisions behind it. I explain how I'm connecting meeting summaries, Google Docs, and NotebookLM so the people working with me can find that context themselves.The conversation comes back to boundaries. Which systems should an agent be able to read? Which should it be able to change? Heather talks about learning to work inside a virtual machine and being deliberate about connectors. We discuss giving agents specific jobs, including checking other agents' work. She describes an instructor's team of agents as one example; she is clear that she has not built that whole setup herself. We also compare models by the actual task and cost, instead of assuming the newest option is automatically the best fit.Then we get to the data. In one client example, I describe finding that 10,000 of 14,000 company records were missing revenue, even though revenue mattered to the targeting criteria. An AI-generated account list still has to work with that gap. Heather's point is straightforward: get the data to a place where you can trust a basic report before expecting AI to produce dependable insight from it. The work can get faster. The responsibility for checking it stays with us.About Heather RobinetteHeather Robinette works in revenue operations and is now Senior Revenue Operations Manager at Zafran Security. When we recorded this conversation, she was at AppOmni. Her examples come from the operational work of helping teams understand forecasts, pipeline, campaigns, and the data behind their decisions. After completing Overclock's AI for RevOps course, she began applying what she learned to dashboards, applications, and agents. In this conversation, she shares what she built, what she had to learn, and why security and data quality became a bigger part of how she thinks about AI.Key TakeawaysStart with a question your team needs answered. Heather's marketing dashboard grew from a specific pipeline question into a place the team could explore campaigns and progress against goals.Give agents a clear job. Narrow responsibilities made it easier for me to see what was breaking and fix one workflow without disturbing another.Treat access as a design choice. Heather distinguishes what an agent can connect to from what it should be allowed to read or change.Test models against the work. We discuss comparing the same task across models and weighing the result against cost.Check the data and the answer. Missing fields can undermine a useful-looking output. Confidence in the wording is not evidence that the underlying answer is right.Chapter Markers00:00 - Cold open 00:18 - AI for RevOps course 03:30 - CRO and marketing dashboards 05:59 - Travis's agents and shared context 13:01 - Security guardrails and sandboxing 15:15 - Single-task agents that check each other 18:41 - Choosing models and managing cost 22:58 - What companies want from AI 25:43 - Bad data means bad AI 31:01 - Wrap-upResources & Links MentionedTools & platformsClaude, Claude Cowork, Claude Code, ChatGPT, Gong, Salesforce, Clari, Asana, AskElephant, Google Docs, NotebookLM, DigitalOcean, Perplexity, Manus, HubSpot, and HubSpot Breeze.Books & podcastsNone.Other resourcesOverclock's AI for RevOps course.Connect with Heather RobinetteLinkedIn: https://www.linkedin.com/...
    Show More Show Less
    32 mins
  • How AI Gave a Vacation Rental Business Confidence to Scale
    Oct 6 2026
    Scott Dinan thinks the thing that holds most business owners back from scaling is not money or demand. It is confidence, and the fear that everything will break once the business gets bigger. Running a vacation rental management company on Florida's Gulf Coast, he has plenty that can break: guest messages around the clock, maintenance calls that cannot wait, owner accounting. AI did not make that work disappear. It gave him systems that catch what gets missed, and that changed how he feels about growing."We all know business is a psychological game. You know, the only thing that holds people back, in my opinion, from scaling is confidence."About This EpisodeScott came to vacation rentals from healthcare staffing, where the COVID years taught him that $200,000 a year was not as much money as he thought. He bought his first property in 2022, started managing for other owners as a side gig in 2023, and went full time at the end of that year. Before he had a team, every guest escalation landed on him, including calls he took in a hospital hallway while his son was being born. His first hire was an executive assistant, the first step on the replacement ladder from Dan Martell's Buy Back Your Time, which he and Travis both work from in Dan's coaching program.AI came into the business in 2024, aimed at the most tedious part of the job: guest communication, especially overnight. The first tool he tried, Yada, got the team's feet wet and exposed a bigger issue. For AI to answer guests well, the business had to be organized. His team inspected every property to document details like where the electrical panel is and what size the AC filters are. Today a system called Conduit answers guests from a knowledge base for each property and handles about 65% of guest communication, which frees his guest communication team for work that moves the business forward.From there Scott built his own tools. A custom work order system, built with Claude Code, notifies vendors in real time, lets them update jobs as they go, uses checklists specific to each property, and requires photos of the finished work. In hospitality the stakes are concrete: a slow fix on an HVAC issue can cost a $5,000 to $10,000 reservation. He also built what he calls a Slack triage agent, which follows each guest's stay, posts escalations, and creates tasks so his team has the full context before they pick up the phone. He is candid that it is not finished. He puts these systems at about 60% of the way there, and he shares two recent misses: the agent mixing up properties with similar names, and a late-night cancellation that never got flagged.The conversation also covers the business side of the AI shift. Airbnb accounts for about 65% of Scott's reservations, and he says its channel fee rose from 3% to 15.5% over the past year. His answer is direct booking: capturing every guest's contact information through SuiteOp's verification portal, running campaigns through GoHighLevel and Meta ads, and hiring someone to lead it. Travis adds why the search side is shifting too, as more research starts in AI tools rather than a list of links.The episode closes on people. Travis explains why he uses AI to triage his inbox so his executive assistant can focus on work a human does better, and Scott describes a new hire who brought him a broken task management process, heard "fix it," and came back having built the work order system. Scott's summary of where this leaves a team: the AI is like everyone's direct report.About Scott DinanScott Dinan is the founder of TrustFirst Management, a vacation rental management company on Florida's Gulf Coast. Before starting it he worked in healthcare staffing, placing travel nurses in hospitals across the country. The company owns one of its properties and manages the rest. Scott has built much of the operation around AI, from automated guest communication to a custom work order system and a Slack-based triage agent, and he is now building out direct booking to reduce the business's dependence on Airbnb.Key TakeawaysOrganize before you automate - Scott's first AI messaging tool only worked once his team documented details like breaker panel locations and AC filter sizes. An AI agent is only as good as the knowledge it can draw on.Know what share of the work AI actually handles - With a knowledge base for each property, Conduit handles about 65% of his guest communication, which tells him what his team can take on next.Build around your most expensive failure - A delayed HVAC repair can cost a $5,000 to $10,000 reservation, so his work order system pushes jobs to vendors in real time with checklists and photos.Be honest about where AI still breaks - He rates his own systems at about 60% of the way there, so his focus is improving what he has rather than adding new projects.Own the guest relationship - With Airbnb at about 65% of bookings, he captures guest contact details from every channel to build repeat, direct ...
    Show More Show Less
    24 mins
No reviews yet
In the spirit of reconciliation, Audible acknowledges the Traditional Custodians of country throughout Australia and their connections to land, sea and community. We pay our respect to their elders past and present and extend that respect to all Aboriginal and Torres Strait Islander peoples today.