The B2B Podcast Index
Index
All categories
MarketingSalesSaaSFinanceHROpsLeadershipCustomer SuccessAI & DataProductStartups & FoundersRevOpsEngineering & DevTools
MethodologySubmit
Best of:MarketingSalesSaaSFinanceHROpsLeadershipCustomer SuccessAI & DataProductStartups & FoundersRevOpsEngineering & DevTools
An independent project byFame
SearchBest episodesGuestsInsightsMethodologySubmit a podcast
Index/Customer Success/Straight To Voicemail
Straight To Voicemail artwork

The Crawl, Walk, Run Approach to AI Automation | Paul Kortman, Connex Digital

Straight To Voicemail · 2026-06-25 · 5 min

0:00--:--

Key moments - from our scoring

Substance score

18 / 100

Five dimensions, 20 points each

Insight Density4 / 20
Originality3 / 20
Guest Caliber6 / 20
Specificity & Evidence3 / 20
Conversational Craft2 / 20

Paul Kortman of Connex Digital breaks down why most revenue organizations struggle with AI implementation and offers a practical alternative to paralysis-inducing transformation initiatives. Rather than attempting enterprise-wide agentic workflow overhauls, he advocates a 'crawl, walk, run' framework borrowed from MVP methodology - start with the smallest, most painful manual task and automate it first. His examples are concrete: automating lead imports from Apollo into CRM, filing call recordings automatically, or using hybrid deterministic-plus-AI workflows that let humans stay in control while AI handles classification tasks. Kortman distinguishes between fully deterministic automation (rules-based, repeatable processes) and truly agentic systems (where AI makes decisions), arguing most teams should begin in the deterministic space before graduating to agents. This approach works because it delivers immediate value, builds organizational confidence in automation, and keeps projects simple enough to launch without extensive upfront mapping. Revenue leaders, sales ops managers, and GTM teams struggling to justify AI investments will find his framework immediately actionable.

Key takeaways

  • →Begin AI automation by identifying and solving one specific pain point rather than attempting comprehensive transformation, such as automating lead copying from Apollo to CRM tools.
  • →Use deterministic automation for well-defined, repeatable processes before graduating to agentic AI that makes decisions independently, allowing teams to validate value before scaling.
  • →Start with simple agents that perform a single function well, then iterate and add capabilities rather than building complex multi-step automation upfront.
  • →The crawl-walk-run methodology mirrors MVP principles from startups, removing the need to map out entire processes before implementation.
  • →Focus on immediate tangible benefits from automation first to build confidence and momentum before tackling more ambitious agentic workflows.

In this episode

  1. 1The Overwhelm Problem: Why Leaders Struggle with AI Implementation
  2. 2Introducing the Crawl, Walk, Run Framework
  3. 3Starting with Low-Hanging Fruit: The Crawl Phase
  4. 4Deterministic vs. Agentic Automation Approaches
  5. 5Building Simple Single-Purpose Agents First
  6. 6Scaling Automation Incrementally Without Over-Engineering

Mentioned

Connex DigitalPaul KortmanApolloMake

Guests

Paul Kortman

Topics in this episode

AI agentsMakeApolloMinimum Viable Product (MVP)Agentic workflowsRevenue operationsCrawl Walk Run FrameworkDeterministic AutomationCall Recording Automation

Questions this episode answers

What is the crawl, walk, run approach to AI automation that Paul Kortman recommends?

It's a framework that borrows from MVP methodology: start with the smallest, most painful manual task (crawl), automate it fully, then build incrementally to more complex workflows (walk) and eventually agentic systems (run). Rather than attempting enterprise AI transformation all at once, you pick one low-hanging-fruit process - like importing leads from Apollo to CRM - and automate that first to deliver immediate value.

Should companies start with deterministic automation or agentic AI according to this episode?

Companies should begin with deterministic automation - well-defined, repeatable processes that happen the same way every time - before graduating to agentic systems where AI makes decisions. A middle ground involves mostly deterministic steps with an AI prompt layer that classifies responses (positive/negative) and triggers actions based on that classification.

What real example does Paul Kortman give of a simple agent automation?

He built an agent that automatically files his call recordings into folders without manual intervention, replacing the previous manual workflow. This single-purpose agent does one thing well and can later be iterated on - like adding sales coaching analysis - rather than trying to build the complete system upfront.

Why does Paul Kortman say most leaders should avoid mapping out entire AI transformations upfront?

Because you don't need to pre-plan everything in today's no-code automation environment; you waste time on theoretical architecture rather than shipping value. Starting small and iterating keeps projects simple, makes them more fun by delivering immediate benefits, and builds momentum and organizational confidence for more complex automations later.

What our scoring noted

Our reviewer’s read on each dimension, with quotes from the episode.

Insight Density

4 / 20

The episode is five minutes of near-pure platitude: start small, build up, don't boil the ocean. The only non-obvious point - a spectrum between deterministic and agentic automation with a brief sentiment-classification example - is underdeveloped and buried in clichés. There is almost no information a B2B operator couldn't have inferred independently.

Stop trying to eat the elephant in one bite. Start with the smallest pain point, automate that, and then build from there.
start with something small. The nice part in today's day and age is you're not building code.

Originality

3 / 20

The crawl/walk/run label is slapped onto the standard MVP concept with no fresh mechanism or counterintuitive angle. Every metaphor used - low-hanging fruit, eating the elephant, minimum viable product - is recycled consulting boilerplate with no first-principles reasoning applied to AI or automation specifically.

if you know anything about minimum viable product MVP in the startup world, it's very similar to that
Let's tackle the low hanging fruit as it were

Guest Caliber

6 / 20

Paul Kortman is a working practitioner running a boutique digital agency and appears to actually implement these systems for clients, which gives him baseline credibility. However, there is no evidence of scale, notable client outcomes, or domain depth that would elevate him above a typical agency founder.

we're doing this with agents for a lot of our clients
I have an agent right now that files my call recordings for me

Specificity & Evidence

3 / 20

The episode offers exactly two concrete examples - copying leads from Apollo into a CRM, and an agent that files call recordings into a folder - both trivial and unaccompanied by any metric, timeline, cost, or outcome. No client names, no numbers, no before/after data anywhere in the transcript.

you've got somebody who's copying leads from Apollo and putting it into your CRM or into your email marketing tool
I have an agent right now that files my call recordings for me. just puts it into a folder

Conversational Craft

2 / 20

There is no actual conversation: Adam delivers a scripted intro and Paul delivers an uninterrupted monologue framed as a voicemail callback. No host questions are asked, no claims are challenged, and no follow-up occurs. The format structurally prevents any craft from being demonstrated.

Hey, Adam, thanks for giving me a call. I'm just returning your call
Feel free to call me back with any questions you have

Conversation analysis

Computed from the transcript - who did the talking, and the words that came up most.

Most-used words

start17agent8call6whole6crawl5automation5today5small5agentic4paul4walk4simple4trying3build3overwhelming3smallest3

Episode notes

AI is everywhere, but most leaders are paralyzed trying to figure out where to start. The pressure to implement "AI transformation" or build agentic workflows can feel overwhelming, and that overwhelm leads to inaction. In this episode of Straight to Voicemail, Adam Sockel hears from Paul Kortman, Founder of Connex Digital , about his crawl, walk, run framework for implementing AI and automation in revenue organizations. Paul's advice cuts through the noise: stop trying to eat the elephant in one bite. Start with the smallest pain point, automate it, and build from there. You'll learn: Why starting with low-hanging fruit beats mapping out a full transformation The difference between deterministic automation and agentic workflows, and when to use each How to get value from AI today without overcomplicating your stack Jump into the conversation: (00:00) Why we wanted to hear from Paul Kortman (00:20) The crawl, walk, run framework explained (01:24) Starting with agents: one task, done well (02:20) Deterministic vs.

Full transcript

5 min

Transcribed and scored by The B2B Podcast Index.

Adam I'm not breaking any news when I say that AI is literally everywhere. It seems like every single process and document we dig into has an AI copilot of some sort attached to it, helping us optimize and create synergy and make us work smarter without working harder. But the reality is most leaders are paralyzed trying to figure out exactly where to start. There's this pressure to implement AI transformation or build agentic workflows and it can feel overwhelming.

And that overwhelming feeling leads to inaction. That's why I was so excited to hear from Paul Cortman. He's the founder of connects digital and he has built out this framework all about crawl, walk, run. It's simply put, it's all about implementing AI and automation for your revenue organizations in a way that's actually sustainable and provides immediate impact without feeling overwhelming.

Paul's advice cuts through the noise. Stop trying to eat the elephant in one bite. Start with the smallest pain point, automate that, and then build from there. Let's see what he has to say.

Paul Kortman Hey, Adam, thanks for giving me a call. I'm just returning your call, wanting to give a little bit more clarity into our crawl, walk, run approach. Basically, if you know anything about minimum viable product MVP in the startup world, it's very similar to that. of let's take something that's going to alleviate pain today.

Say right now you've got somebody who's copying leads from Apollo and putting it into your CRM or into your email marketing tool. OK, well, that's like let's just start there when it comes to automation. Let's tackle the low hanging fruit as it were. And that's what we call kind of our crawl phase of like let's just start there.

Do a little bit. Some people get really overwhelmed, even like with AI and like, how do I implement AI transformation and how do I do agentic work now? And it's like, start with the smallest thing, start small and then expand beyond that. And that's the whole concept of crawl, walk, run.

I could get into all the details of each one, but right now we're doing this with agents for a lot of our clients of like, okay, Why would I use an agent versus like a make scenario or defined automation? And we start with the smallest, most simplest agent. I have an agent right now that files my call recordings for me. just puts it into a folder instead of going through the whole process of like, okay, now decide, do a sales coach on that, decide, did I do the right model, et cetera.

That's going to be the next iteration of that agent. So instead of trying to eat the whole elephant in one bite, start small, start with a simple agent that does one thing and does it well, and then add onto it. Or maybe you divide that and and add a separate agent that does even more. So that's the whole concept with crawl, walk, run of just like start small, start simple.

What's one thing today that you could automate that you could put on autopilot, whether it's through what we call deterministic, which is very, very well defined or through agentic, which is, you you let the agent figure it out. And there's a middle ground in there too, where you have mostly deterministic steps, but you have an AI prompt that says, hey, tell me whether this was a positive response or a negative response, and then take action based on that. So that's just kind of the real simple lay of the land of how to approach agents, AI, automation in 2026.

Basically, Let's start with something. Paul Kortman Don't try to map it all out. You're dealing with a whole lot of different features and functions and capabilities. so instead start with something small.

The nice part in today's day and age is you're not building code. You're not building scripts. You're not having to think everything through because otherwise you wasted time and effort. Start with something today and build on that.

That keeps it simple. It makes it a lot more fun of just like, can I get value and benefit out of an automation or an agent today? Well, there's this one thing that's annoying to me. Yeah, there's this huge thing that's annoying to me, but if I could get this one thing started, then we can work towards the end after that.

there's a whole lot there. Feel free to call me back with any questions you have, but just kind of a basic framework of start small and even work on the deterministic scale of start with something you know, I want this done this way every time. And then you can start working your way into the agentic scale, which is having agents do stuff for you and hiring less employees. That's the kind of the name of the game here.

Related episodes across the Index

Other episodes covering the same guests and topics, from across The B2B Podcast Index.

  • 115: Rethinking AI Governance for Enterprise Adoption with Dr. Markus SchmidbergerUsing AI at Work · on AI agents92 / 100
  • 5 Rules for Building AI Agents That Work in Production | Nan Yu & Jacob ShumwayBehind the Craft · on AI agents91 / 100
  • AI Agents, False Productivity, and the Sales Team Reset with Gabe LarsenMake It Happen Mondays · on AI agents91 / 100
  • Why Ploy.ai is more than another website tool - 60 MINUTES with Bryant Chou20 MINUTES by Noco · on AI agents87 / 100
  • Why a $1.2B exit felt like his biggest failure, and the customer-obsession thesis behind AgencyThe GTMnow Podcast · on AI agents86 / 100
  • AI Agents Are About to Move Off the Cloud. Here’s What ChangesThe Neuron: AI Explained · on AI agents81 / 100

More from Straight To Voicemail

All episodes →
  • Why finding human truths and brand mythology wins customers | Alan Roll, Deel72 / 100
  • What does a successful B2B podcast actually look like? | Carly Baker, HubSpot46 / 100
  • How is AI transforming senior care from reactive to predictive? | Steve Keys, NtelCare70 / 100
  • How do you balance empathy and business results? | Liesel Mertes, Founder & Workplace Empathy Consultant, Handle With Care Consulting51 / 100
  • How is AI changing B2B buying behavior and making partnerships more important for distribution and trust? | Bryn Jones, Co-Founder, PartnerStack47 / 100
Explore the best B2B Customer Success podcasts →
All Straight To Voicemail episodes →