AI-Ready Or Not?

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 Episode

Heather 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 Robinette

Heather 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 Takeaways

• Start 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 Markers

00: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-up

Resources & Links Mentioned

Tools & platforms

Claude, Claude Cowork, Claude Code, ChatGPT, Gong, Salesforce, Clari, Asana, AskElephant, Google Docs, NotebookLM, DigitalOcean, Perplexity, Manus, HubSpot, and HubSpot Breeze.

Books & podcasts

None.

Other resources

Overclock's AI for RevOps course.

Connect with Heather Robinette

• LinkedIn: https://www.linkedin.com/in/heatherrobinette/

Connect with Travis

• Rainier RevOps: https://rainierdigital.com
• LinkedIn: https://www.linkedin.com/in/travisscott24
• Instagram: https://www.instagram.com/travis.revops
• YouTube: https://www.youtube.com/@RainierRevOps

If This Episode Resonated

If you're ready to build with AI but aren't sure your CRM data and processes can support it, start with the AI Readiness Scorecard: https://ai-readiness-os.manus.space/

Recorded August 14, 2026. Platform references and examples reflect that conversation.

AI-Ready or Not is a production of Rainier RevOps.

Recorded in Zoom. Edited in Descript. Hosted on Transistor.

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.

About This Episode

Scott 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 Dinan

Scott 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 Takeaways

• Organize 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 business.
• Confidence is the real return - When something is missed, a report surfaces it. That built-in accountability is what makes growth feel possible instead of risky.

Chapter Markers

00:00 - Cold open
00:22 - Leaving staffing to build a vacation rental business
02:53 - The first hire and buying back time
03:53 - Automating guest communication with AI
06:00 - Why AI forced better operational organization
07:46 - Building a custom AI-enabled work order system
09:36 - The Slack triage agent and where AI still fails
12:57 - Airbnb dependence, direct booking, and customer data
17:35 - How AI changes confidence and the ability to scale
19:44 - AI as an employee's direct report

Resources & Links Mentioned

Tools & platforms

• Conduit (AI guest communication for vacation rentals): https://www.conduit.ai/
• Claude Code (used to build the work order system): https://claude.com/product/claude-code
• Yada (the guest communication software Scott started with): https://www.yada.ai/
• SuiteOp (guest verification portal): https://suiteop.com/
• GoHighLevel: https://www.gohighlevel.com/
• Slack: https://slack.com/
• Perplexity: https://www.perplexity.ai/
• Airbnb, VRBO, and Booking.com

Books / podcasts referenced

• Buy Back Your Time by Dan Martell: https://www.buybackyourtime.com/

Other resources

• Dan Martell's Elite coaching program

Connect with Scott

• TrustFirst Management: https://trustfirstmanagement.com
• Instagram: https://www.instagram.com/scott.dinan/
• LinkedIn: https://www.linkedin.com/in/scott-dinan-545b1991/
• Facebook:

Most founders would notice a kitchen fire. A slow leak in the basement is different. Everything looks fine for months, and by the time the water shows up the damage is already done. That is how Alisha Esmail describes client retention, and it is the reason she went from running a coffee company to building Latch AI, a tool that flags which clients are slipping before they leave.

About This Episode

Alisha's path into AI did not start with software. It started with a coffee company that worked directly with farmers around the world, building supply chains for female farmers and a microloan program to help them out of poverty. Running a physical product business across continents taught her where the manual work piles up, and that is where she started adding software, then agents, then AI, to buy her team's time back.

The turning point was an email. At the dinner table with her family, she learned that her biggest client, half of her monthly recurring revenue, had decided to go in a different direction. She had to excuse herself from the table. That moment pushed her to become, in her words, a retention expert if she was going to build a successful company. She won that client back, and they are still a client today, but the lesson stuck: keeping a client is far cheaper and far easier than reselling them after they leave.

Latch AI is the system that grew out of that lesson. It connects to the tools a business already uses, its CRM, calendar, payment system, and support tickets, and sorts every client into one of four categories: at risk, slipping, ready, or stable. Two of those are time-sensitive windows. The point is to catch someone while they are slipping, before they hit red, and to ask for the renewal or the referral at the moment the client is actually ready rather than when the business happens to need cash. Alisha also explains why she did not start with AI at all. The retention engine ran as a manual process first, then her team ran it, then automation, and only then AI. Throwing the kitchen sink at a model without a real problem and a real process is, in her view, the most common mistake people are making right now.

Travis brings the revenue operations side of the same problem. Most CRMs are a mess: duplicate contacts, pipeline stages nobody defined the same way, stale deals, and historical data dragged over from two previous systems. Layer AI on top of that and it amplifies the mess. Alisha agrees without hesitation: the cleanup comes first. The conversation closes on a counterintuitive point from Travis. Companies often document why they lost a deal, but almost nobody documents why they won one, and the expectations set at the moment a client says yes are where a lot of churn is born.

About Alisha Esmail

Alisha Esmail is the founder of Latch AI. Her background is in international development, which led her to start a coffee company that worked directly with farmers, created streamlined supply chains for female farmers, and ran a microloan program. She went through a tech incubator and won funding to build a platform around those microloans before the pandemic put it on pause. Inside the coffee business she built an AI brain and agents to streamline the workflow, and a manual retention and client-intelligence system that eventually became Latch. Today she helps business owners keep their clients longer and grow through expansion revenue, working with an invite-only early adopter program of agencies, coaches, clinics, and other repeat-relationship businesses.

Key Takeaways

• Retention is a leak, not a fire - Nobody ignores a fire. Slow client loss feels like nothing is wrong, which is exactly why founders notice it too late. Treat it as urgent before it is visible.
• Build the manual system before the AI - Alisha ran her retention process by hand, then handed it to her team, then automated it, and only then added AI. The model speeds up a process that already works; it does not invent one.
• Ask at the right time - Renewals, upsells, and referrals fail when they are asked for at the wrong moment, usually when the business needs revenue. Latch's "ready" category exists to find the moment the client is actually a cheerleader.
• A few points of retention move profit, not just revenue - Once hard costs are covered, retained revenue can have an outsized effect on profit. In one example Alisha shares, a company that believed it retained about 80 percent of its clients discovered the real number was closer to 60 percent.
• Clean the CRM first - Duplicate contacts, undefined pipeline stages, and stale deals are exactly the variables AI has to grab onto. Feeding it a mess only makes the mess faster.
• Document why you won - Closed-lost reasons are common. Closed-won reasons almost never are, and the gap between what a client expected at yes and what got delivered is where churn starts.

Chapter Markers

00:00 - Cold open
 00:22 - From Coffee to Code
 05:33 - Don't Throw the Kitchen Sink at AI
 08:06 - Inside Latch: Four Client Categories and Early Wins
 14:49 - Messy CRMs: Cleanup Comes First
 18:29 - Growing Flat: The Retention Self-Sabotage Trap
 21:59 - The Real Cost of Churn
 24:28 - The Dreaded Email
 26:47 - Retention Is the Business's Job, Not the Client's
 32:32 - The Latch Dashboard and Where to Find Alisha

Resources & Links Mentioned

Tools & platforms

• Latch AI (Alisha's company; currently invite-only with a wait list)
• HubSpot
• Stripe
• Intercom
• Claude Code

Books / podcasts referenced

• Obviously Awesome by April Dunford

Other resources

• Alisha's churn scorecard: message her on LinkedIn with the word "churn" and she will send it

Connect with Alisha

• Latch AI: https://yourlatch.com/
• LinkedIn: https://ca.linkedin.com/in/alisha-esmail
• Instagram: https://www.instagram.com/alishaesmail/
• Road Coffee: https://roadcoffeeco.com/

Connect with Travis

• Rainier RevOps: https://rainierdigital.com
• LinkedIn: https://www.linkedin.com/in/travisscott24
• Instagram: https://www.instagram.com/travis.revops
• YouTube: https://www.youtube.com/@RainierRevOps

If This Episode Resonated

Alisha's warning about layering AI on messy data is the same problem we see in almost every CRM we open. If you are not sure whether your data, your process, and your team are ready for tools like Latch, the AI Readiness Scorecard is a quick way to find out where the leaks are:

She Almost Lost the Business. Then She Rebuilt It With AI.

Andrea Palacio and her husband bought a "boring" landscaping company expecting an easy win — and nearly lost everything within a month. This is the story of how she clawed it back with AI and automated it into a business that runs without her.

About This Episode

After a decade as an entrepreneur — including seven years running an e-commerce business from a sailboat in the Caribbean — Andrea Palacio and her husband decided to buy a "boring business" and put an operator in place. The reality hit fast: within a month of acquiring a landscaping company, the manager quit and told the crew to find other jobs, staff dropped from 12 to 2, and revenue was cut nearly in half. With their home attached as SBA-loan collateral and a second baby on the way, they were working 80-hour weeks and ready to sell.

Instead, Andrea went down the "YouTube University" rabbit hole and started solving her own problems with AI. In this conversation you'll hear how she put AI on every inbound phone call (answering and booking every lead automatically), how that stopped a 30–40% revenue leak, and how AI-optimized Google Ads increased their leads 20% while cutting ad spend. You'll also hear exactly how she runs ads with AI today — connecting Claude Code directly to Google Ads with an AI agent, while her non-technical husband uses Claude's Chrome extension to audit the account, catch broken links, and find ads running without landing pages. The business became automated enough that a buyer offered full asking price — so they kept it, hired an operations manager, and stepped away. That turnaround became RunCrewless.com, where Andrea now helps service-business owners build self-operating companies.

About Andrea Palacio

Andrea spent 10 years building and exiting businesses — an e-commerce company she ran while living on a sailboat, then a landscaping company (Mokai) she and her husband acquired and nearly lost before automating it with AI. That turnaround led her to found RunCrewless.com, where she now helps service business owners run self-operating companies using Claude Code and automation. She's also a business coach in Dan Martell's Elite program.

Key Takeaways

Chapter Markers

Resources & Links Mentioned

Connect with Andrea Palacio

Connect with Travis

If This Episode Resonated

If your company is buying AI tools but hasn't done the work underneath — clean CRM data, documented processes, a single source of truth — that gap is the whole reason the tools feel disappointing. The AI Readiness Scorecard diagnoses it in about 10 minutes.

Get Your AI Readiness Scorecard

Recorded in Descript Rooms. Edited in Descript. Hosted on Transistor.

AI-Ready or Not is a production of Rainier RevOps.

Divine Intervention: How One Founder Cracked a Two-Company Monopoly with AI

For as long as anyone can remember, an online pharmacy could only get accredited by one of two companies — and the backlog showed it. Aaron VanStone is building the third, ScriptSafe, and he coded the entire platform himself, with no software background, using Claude Code.

About This Episode

Aaron VanStone has spent more than 20 years in payments. In 2008 he founded Processing Brokerage, a pay-for-performance firm that audits merchants' credit-card processing fees across the U.S., Canada, and the U.K. A project with a compounding-pharmacy trade group pulled him into the pharmacy world — where he ran headfirst into a bottleneck: to accept online payments or run Google ads, a pharmacy needs third-party accreditation, and "since the beginning of time" there have been only two accreditors. The backlog was enormous.

His answer is ScriptSafe, an AI-powered accreditation platform that reviews a pharmacy's licenses and then monitors its website every night to confirm it isn't selling anything illegal. What makes the story remarkable is that Aaron built the technology himself — starting at the end of January with zero coding experience, using Claude Code (with Codex as a second set of eyes). As he puts it, the timing felt like "divine intervention": the tools arrived exactly when he needed them, and what he built "wasn't possible a year ago."

This is a tactical conversation. Aaron and Travis get into the workflow that actually works: writing a detailed planning document before building, running two models against each other so they have to agree, building a brand system for consistent design, and the cheap starter stack — Vercel, GitHub, and Supabase — that lets anyone ship. They also dig into the lesson that cost Aaron a month: there was no observability layer, so the AI was guessing at bugs. Once he added one, nightly pharmacy scans dropped from four hours to under 90 seconds.

It's also a candid take on the risks — vendor lock-in, the coming wave of "AI-slop software," and why vibe-coding your own CRM might be shortsighted if you ever need to hire or train for it. And underneath it all runs an encouraging message: there has never been a better moment to learn this, especially if you've just been laid off and finally have the runway to dig in.

About Aaron VanStone

Aaron VanStone leads three companies at the intersection of payments, fintech, and healthcare compliance, drawing on more than 20 years in the payments ecosystem. He founded Processing Brokerage in 2008, a pay-for-performance consulting firm that audits credit card processing fees for merchants across the U.S., Canada, and the U.K. Most recently, he launched ScriptSafe, an AI-powered pharmacy accreditation platform designed to eliminate regulatory bottlenecks for online pharmacies. He's built ScriptSafe's technology stack using AI coding tools, a workflow he discusses in depth on topics ranging from Claude Code to brand systems in web development.

Key Takeaways

• Prep beats prompts — Aaron spends 90 minutes to two hours building a working planning document (with the model interviewing him) before writing any code. The richer the plan, the better the build.
• Run a second model as a reviewer — He has Codex continuously review Claude/Fable's output; when the two models agree, the code is far more trustworthy.
• Build a brand system first — Define your colors, logo, fonts, and overall look up front, then tell the builder to follow those rules so everything stays consistent.
• You can't fix what you can't see — Adding an observability layer turned guess-and-check debugging into real analysis and took nightly pharmacy scans from 4 hours to under 90 seconds.
• The starter stack is cheap and learnable — Vercel (hosting) + GitHub (code) + Supabase (database), roughly under $30/month, is enough to "do anything."

Chapter Markers

• 0:00 — Cold open
• 0:29 — Meet Aaron & ScriptSafe
• 1:56 — From payments consulting to a new problem
• 3:42 — Divine intervention: finding AI at the right moment
• 6:07 — Fable 5 vs. Opus — you feel the upgrade
• 11:29 — The "building a house" analogy for model progress
• 12:59 — Prep beats prompts: plan before you build
• 15:18 — Running Claude and Codex against each other
• 18:35 — Vendor lock-in and the coming software shakeout
• 20:56 — The "vibe-code your CRM" debate
• 26:47 — The observability fix: 4 hours to 90 seconds
• 29:23 — Starting from zero coding experience
• 31:23 — "If you don't know where to start, ask it" + the hotel scanner
• 34:03 — Why now is the time to learn — even if you've been laid off
• 39:16 — The starter stack: Vercel, GitHub, Supabase
• 40:52 — Design: Manus, Claude Design & brand systems
• 42:04 — Two big tips to finish

Resources & Links Mentioned

Tools & platforms:

• Claude Code — https://claude.ai 
• Claude Design — https://claude.ai 
• Claude (Max plan) — https://claude.ai 
• Codex (OpenAI Codex CLI) — https://openai.com/codex/ 
• Vercel — https://vercel.com 
• GitHub — https://github.com 
• Supabase — https://supabase.com 
• Manus — https://www.manus.space 
• Opus Clip — (mentioned by Travis) 
• ChatGPT — (referenced)

Books / podcasts referenced: None.

Connect with Aaron VanStone

• Website: https://scriptsafe.com
• Social / newsletter: LinkedIn — https://www.linkedin.com/in/aaronvanstone-b86622b8 · ScriptSafe on LinkedIn — https://www.linkedin.com/company/scriptsafe/about/

Connect with Travis

• Rainier RevOps: https://rainierdigital.com
• LinkedIn: https://www.linkedin.com/in/travisscott24
• Instagram: https://www.instagram.com/travis.revops
• YouTube: https://www.youtube.com/@RainierRevOps

If This Episode Resonated

If your company is buying AI tools but hasn't done the work underneath - clean CRM data, documented processes, a single source of truth - that gap is the whole reason the tools feel disappointing. The AI Readiness Scorecard diagnoses it in about 10 minutes.

Get Your AI Readiness Scorecard

Recorded in Descript Rooms. Edited in Descript. Hosted on Transistor.

AI-Ready or Not is a production of Rainier RevOps.

The Foundation Before the Agents: Jenny Blake on What Has to Be True Before AI Actually Works.

After two years of watching the AI hype cycle from the sidelines, author and keynote speaker Jenny Blake (Free Time, Pivot) finally dove in — and now she's hitting inbox zero for the first time in fifteen years of self-employment. But the leap wasn't about the tools. It was about what she had already built underneath them. In this opening episode, Travis and Jenny unpack the infrastructure - context files, documentation, clean processes - that separates people who get leverage from AI from people who get noise.

About This Episode

Jenny Blake has spent the last few years publicly underwhelmed by generative AI. It impressed her (everyone can write a poem in ten seconds) but it didn’t transform her business. 

Then, at the start of 2026, something shifted. Claude Cowork launched for non-developers. Notion released Custom Agents. Her brain, in her words, "caught fire."

This episode is not about which tool to buy. It’s about what has to be done in your business before any of these tools can give you leverage. 

Jenny walks through the practical prerequisites - context files, markdown documentation, the "interview me until you're 95% clear" prompting pattern - and Travis connects those principles back to what founders and revenue leaders are dealing with at larger scale: messy CRM data, tribal knowledge in people's heads, and processes that were never written down.

If you’ve been sitting on the sidelines wondering whether AI is finally worth your time, or you've tried it and found it more annoying than useful, this conversation is the context you've been missing.

About Jenny Blake

Jenny Blake is the author of three award-winning books: Free Time: Lose the Busywork, Love Your Business; Pivot: The Only Move That Matters Is Your Next One; and Life After College. She runs a media and growth strategy company, licensing her IP to clients such as Google, CHANEL, and the Stanford Graduate School of Business.

Before launching her own business in 2011, Jenny co-created Google's global drop-in coaching program, Career Guru, which is still in operation today. She hosts two podcasts with over two million downloads combined: the Webby-nominated Free Time podcast for heart-based business owners, and Pivot with Jenny Blake for navigating change. She lives in New York City with her husband and their German shepherd, Ryder.

Key Takeaways

1. Context files are the foundation, not the AI. Jenny's agents only became useful once she'd fed them markdown files describing her business, her clients, her voice, and her goals. The AI is only as good as what it knows about you. Before every prompt, she tells the model to read her context files first.
2. Reverse prompting: make the AI interview you. Instead of trying to front-load every piece of context in a prompt, tell the model: "AskUserQuestion until you're 95% clear on what I'm trying to do." The questions it asks will surface blind spots you would have missed.
3. The agentic shift was specific and recent. Jenny was a skeptic for years. The turning point was agents (Claude Cowork, Notion Custom Agents, Perplexity Computer) launching for non-developers in early 2026. The difference from older automation: you direct them in natural language, and they improve themselves with every run.
4. AI levels the playing field for neurodiverse operators. Travis, diagnosed with ADHD in 2023, describes the shift from seeing AI as a way to replace assistants to seeing it as a way to work around personal weaknesses, so he can spend more time in his strengths. The frame is not "replace a person," it's "build a better version of yourself."
5. A good idea is no longer enough. Anyone can vibe-code a copy of your product in an hour. The moat is now distribution, marketing, and taste, the things AI can't replicate on command. A "one-person billion-dollar startup" usually means the founder already had marketing leverage, not just a working prototype.
6. If it's not documented, it can't be delegated. This applies to humans AND agents. Travis realized the SOP he was writing to hire someone was also the exact prompt an agent needed. Documentation isn't overhead, it's the interface between you and everything you could offload. Most companies have skipped this step, and it's about to bite them.
7. You have many doorways in and you only need one. Jenny's closing advice: you don't have to be a software engineer anymore. If you're a good people manager, problem-solver, builder, opinionated about taste, or simply curious - that's your doorway in. Pick one and stop waiting.

Chapter Markers

00:00  —  Cold open & welcome

00:30  —  "Impressed but underwhelmed": what changed in early 2026

05:30  —  Reverse prompting: make the AI interview you

07:30  —  Context files and why Claude Desktop is the unlock

10:30  —  The Claude Council prompt and open-source prompt sharing

12:30  —  Travis's origin story: HubSpot, INBOUND, and the ADHD unlock

17:00  —  Starting small: solve a real pain point, not a novelty

19:30  —  Why learning time has to live on your calendar

22:30  —  The vibe-coding trap: when a good idea isn't a moat

27:30  —  Small businesses have the advantage — for now

30:00  —  Notion vs. Claude Desktop: when to use which

33:30  —  The prerequisite nobody talks about: clean data, documented processes

35:30  —  SOP-to-agent: 30 minutes of cleanup becomes 2 minutes

37:30  —  Every question lives three lives: Jenny's documentation principle

39:30  —  Why Jenny doesn't use AI to write

41:00  —  "Words I Hate" and tropes.fyi: controlling AI voice

44:00  —  Closing: the many doorways in — pick one, stop waiting

Resources & Links Mentioned

Jenny's Books

• Free Time: Lose the Busywork, Love Your Business
• Pivot: The Only Move That Matters Is Your Next One 
• Life After College

Jenny's Podcasts, Newsletter, & Community

• Free Time Podcast