• Craig Sturgis: Every Workaround Is a Feature You Missed
    Nov 15 2026
    Every workaround your customers use is a feature you missed. It is already sitting in your support and training calls. Craig Sturgis spent 20 years building software and now runs Vibecto, an agency that helps founder-led companies deploy agents. He mines those calls into a distilled knowledge base the whole company can query: what the product is for, the language customers actually use, and the workarounds that go to the backlog until a fix retires them. We also get into handing people a toolbox instead of a conveyor belt, why a shortcut makes you sound like everyone else, the client whose automated product demos got better after the knowledge base was hooked up, and why verification is the bottleneck. Chapters 00:00 Hook: stepping outside your comfort zone 00:38 Intro 00:55 What Vibecto does 02:36 Agents in founder-led companies 03:17 What an agent actually is 04:09 Agents in marketing: finding the workflows 06:16 Workshops and opportunity solution trees 08:32 Which tasks go to a human 10:12 A toolbox, not a conveyor belt 13:19 Verifying AI content 16:38 Content factories and early SEO 19:16 Where agents fall short on copywriting 21:04 Outside your expertise: hot garbage 22:54 Verification is the bottleneck 26:06 Turning customer workarounds into your roadmap 30:37 Where your company's knowledge should live 34:41 Where to find Craig Host: R. Hunter Harris https://www.linkedin.com/in/rhunterharris/ Guest: Craig Sturgis https://www.linkedin.com/in/craigsturgis https://vibecto.ai/ By Hunter Software Consulting https://huntersoftwareconsulting.com/ Newsletter: Don't SaaS Me https://hunter-software-consulting.beehiiv.com/
    Show More Show Less
    36 mins
  • Todd Katcher: The Business That Pays the Bills
    Nov 8 2026

    Todd Katcher runs product at Digital Dealership System and builds several other companies on the side, including Matching Paws, free software for animal rescues. With more ideas than hours, he has had to get disciplined about where attention and engineering go.


    We talk about how he decides: the business that pays the bills comes first, a customer request has to earn its place with a real business case instead of one loud voice, and his own day runs on systems that keep unfinished work from piling up. We close on what AI actually changes for a small team building several products at once, and what it doesn't.


    Chapters

    00:00 Meet Todd Katcher

    00:51 Matching Paws and the side ventures

    09:57 The business that pays the bills comes first

    11:18 Notepads, browsers and a CRM

    17:13 The mental backpack

    20:33 When customers say "everybody would want this"

    28:13 Where AI still needs humans

    31:12 Where to find Todd


    Host: R. Hunter Harris

    https://www.linkedin.com/in/rhunterharris/


    Guest: Todd Katcher

    https://www.linkedin.com/in/toddkatcher/

    https://toddkatcher.com/

    Digital Dealership System: https://digitaldealershipsystem.com/

    Zoney: https://zoney.com/

    Matching Paws: https://www.matchingpaws.com/

    Price Alerts: https://pricealerts.ai/

    Essential Sports Nutrition: https://essentialsportsnutrition.com/


    By Hunter Software Consulting

    https://huntersoftwareconsulting.com/

    Newsletter: Don't SaaS Me

    https://hunter-software-consulting.beehiiv.com/

    Show More Show Less
    33 mins
  • Malisa Nguyen: What a Burnt-Out Founder Costs the Business
    Nov 1 2026

    Malisa Nguyen is a mental performance coach for founders and sales reps.


    Burnout, she says, "happens as a result of chronic stress," not hours. Founders cling to the grind because "there's this fear that if I were to stop burning out, then I would lose my edge."


    We also get into the business cost of a burnt-out founder, fight, flight, freeze and fawn on customer and management calls, and why a leader's vulnerability builds trust.


    Chapters

    00:00 The fear behind the grind

    00:22 Meet Malisa Nguyen

    00:51 What burnout really is

    03:02 Chronic stress, not long hours

    04:32 Moral injury and values

    06:29 Why self-aware founders don't change

    08:51 What burnout costs the business

    11:31 Why this work is personal

    13:36 Success without the burnout

    15:22 Fight, flight, freeze and fawn

    16:28 Fight mode on customer and management calls

    17:46 Flight and freeze: avoidance and stalled decisions

    19:43 Building a culture that prevents burnout

    21:58 Vulnerability and trust

    22:54 Leaders and layoffs: show up, don't send an email

    25:40 What flow state is

    28:07 Group flow on startup teams

    29:10 Where to find Malisa


    Host: R. Hunter Harris

    https://www.linkedin.com/in/rhunterharris/


    Guest: Malisa Nguyen

    https://www.linkedin.com/in/malisa-nguyen/


    By Hunter Software Consulting

    https://huntersoftwareconsulting.com/

    Newsletter: Don't SaaS Me

    https://hunter-software-consulting.beehiiv.com/

    Show More Show Less
    30 mins
  • Danny Davis: Cheaper to Start, Not Cheaper to Build
    Oct 25 2026

    Danny Davis took a company public, sold another, and is now building StackYak.


    "AI is making things more efficient, but it's still expensive to build a company." Founders say "we only need 500,000." What if you need two million? "You fail before you finish."


    We also get into why the company's lawyer is not your lawyer, why you take the small check that gets you to the next round, and why "debt is still cheaper than equity."


    Chapters

    00:00 People are craving real relationships

    00:21 Meet Danny Davis

    01:08 Why start a third company?

    05:22 AI isn't making things cheaper yet

    07:18 The truth about taking a company public

    08:59 Selling for less and planning for taxes

    11:19 The second exit: Origin Labs

    14:24 The company's lawyer is not your lawyer

    16:01 Why founders skip legal help

    17:20 Don't let ChatGPT write your contracts

    19:44 Where AI helps with legal documents

    20:25 What he'd do differently: due diligence

    21:54 The right investors are your friend

    24:21 Investors who do more than write a check

    25:54 Get into an accelerator early

    27:08 Co-founders versus solo founders

    28:20 Take the small check

    29:10 Cheaper to start, not cheaper to build

    30:30 Debt, grants and specialty investors

    32:49 What StackYak is building

    33:34 Real conversations, real discovery


    Host: R. Hunter Harris

    https://www.linkedin.com/in/rhunterharris/


    Guest: Danny Davis

    https://www.linkedin.com/in/dannydavis12/

    https://stackyak.ai/


    Newsletter: Don't SaaS Me

    https://hunter-software-consulting.beehiiv.com/


    By Hunter Software Consulting

    https://huntersoftwareconsulting.com/

    Show More Show Less
    35 mins
  • Jeff Patton: Build What Customers Will Use
    Oct 18 2026

    A company Jeff Patton worked with this year shipped a glossy new release to 2.65 million customers. AI helped them get it out on time. It didn't break. There were no bugs. Nobody liked it.


    Jeff, author of User Story Mapping, joins me to talk about dual track development. He says the book needs a second edition: it described a discovery team and a delivery team, but after 10 years of coaching he sees two tracks and one team, with engineers and testers pulled up into discovery.


    Jeff asks the whole team, on a scale of 1 to 5, how confident they are that people will see a feature and want to try it. If one says 3 and another says 5, ask what they'd need to learn to be sure. Keep using is the hard one to test: release something usable to a small group, and in Jeff's words, "don't build it at scale."


    We also get into release to learn versus release to earn, and what I've seen in client GitHub repos since they adopted AI: a lot more output, but the share of work going toward customer results is flat or down. Jeff on asking AI what customers think: "the AI is not your customer."


    His homework: do an opportunity canvas for the feature you're working on right now. If you can't say who it's for, what problem it solves and how you'll measure it, stop building it.


    Chapters

    00:00 A release customers did not like

    00:21 Meet Jeff Patton

    04:54 Discovery and delivery together

    07:33 Two tracks within one team

    09:46 Expose the beliefs behind a feature

    12:52 Where does the team's confidence differ?

    13:58 A usable release that teaches you something

    16:03 Learning about technical risk

    17:16 Ship to learn, earn, or burn

    23:24 AI output and customer outcomes

    27:40 AI opinion and actual customer evidence

    33:18 An exercise for the next feature

    34:46 Where to learn more from Jeff


    Host: R. Hunter Harris

    https://www.linkedin.com/in/rhunterharris/


    Guest: Jeff Patton

    https://www.linkedin.com/in/productdesigncoach

    https://jpattonassociates.com/


    Newsletter: Don't SaaS Me

    https://hunter-software-consulting.beehiiv.com/


    By Hunter Software Consulting

    https://huntersoftwareconsulting.com/

    Show More Show Less
    40 mins
  • Making AI Useful with David Rasch
    Oct 11 2026

    How much of the feedback on a release actually needs to block it?


    David Rasch looks for the checks his team can automate so nobody has to keep thinking about them. If an agent repeatedly makes the same mistake, a deterministic check can catch it before a person spends another review pointing it out. That leaves the person reviewing the work to decide what matters.


    We talk about where to spend that judgment: the data model, changes to the interface, and the parts of a system that need careful design. Code may be easier to replace now, but someone still has to understand what the software is supposed to do.


    David gives an example of an AI review getting caught up in a race condition for a task that runs about once a month. In that case, he decided the extra complexity wasn't worth it. I share an experiment where repeatedly responding to review feedback left my project unable to do anything at all.


    The useful question is what needs fixing before this release, and what can become a separate ticket whose priority you decide later. A patient reviewer can always find more work. You still need a person who can decide when the work is worth doing.


    Useful questions from the conversation

    Which repeated review comments could become automatic checks?

    Which parts of this change need someone to understand the design?

    Does this issue need to stop the release, or can you decide its priority separately?


    Chapters

    00:00 When AI agrees with everything

    00:12 Meet David Rasch

    02:12 What you still need to understand

    05:02 Data foundations before more code

    10:00 Building and selling as an engineering education

    14:42 Which parts need careful design?

    19:12 Automating repeatable review checks

    21:20 Code is easier to rework

    22:31 When review becomes a loop

    25:02 Human judgment and work worth doing

    28:55 Where to find David


    Host: R. Hunter Harris

    https://www.linkedin.com/in/rhunterharris/


    Guest: David Rasch

    https://www.linkedin.com/in/rasch


    Newsletter: Don't SaaS Me

    https://hunter-software-consulting.beehiiv.com/


    By Hunter Software Consulting

    https://huntersoftwareconsulting.com/

    Show More Show Less
    30 mins
  • Control Before Thrust: Making AI Work with Josh Colter
    Oct 4 2026

    What would help your customers more: another round of faster AI output, or a better way to see what you're building?


    Josh Colter, the majority owner of Cardboard, has put a lot of thought into that question. He bought the company with a bet on AI and has been combining story maps with detailed instructions so he can see the big picture while the models work through the details.


    His comparison comes from the Wright brothers. He says "they thought about control first." A bigger engine is useful once you can steer. Josh applies that idea to building software: make the work visible, understand the customer behavior you're trying to change, and keep releases small enough to inspect.


    We talk about the difference between having AI drive and learning to operate it yourself, why a long specification can hide something a human needs to see, and how Josh planned and shipped dark mode in three days after finding years of requests from users of a competing product.


    Useful questions from the conversation

    Can you see the work clearly enough to tell where it's going?

    Can the people building it understand the plan as readily as the AI can?

    What customer request are you trying to meet, and how will you check the result?


    Chapters

    00:00 Control before thrust

    00:45 Show intro

    00:53 Meet Josh Colter

    01:26 Buying Cardboard and betting on AI

    02:46 Chauffeurs and airmen

    08:47 Why a bigger engine needs control

    11:05 Make the work visible

    15:20 Story maps, specifications and human understanding

    20:32 Planning and shipping dark mode

    25:26 Checking what you've actually built

    26:35 Where to find Josh and Cardboard


    Host: R. Hunter Harris

    https://www.linkedin.com/in/rhunterharris/


    Guest: Josh Colter

    https://www.linkedin.com/in/joshcolter

    https://cardboardit.com/


    Newsletter: Don't SaaS Me

    https://hunter-software-consulting.beehiiv.com/


    By Hunter Software Consulting

    https://huntersoftwareconsulting.com/

    Show More Show Less
    28 mins
  • Brandon Valentine: Unit Economics - Why Founders Can't Raise Capital Without Them
    Sep 27 2026

    In this episode, Brandon Valentine, a CPA and the founder of Valentine Advisory Group, explains why a founder who can't speak to their unit economics can't raise capital: lenders and investors want to understand how the company makes money and how they get their capital back. He breaks down what goes into the numbers (cost of goods sold, operating expenses and a price the market will pay), why pricing starts with market research and the problem you solve for the customer, and how a three statement financial model turns "I want money because my idea is very good" into a specific ask backed by numbers. Hunter adds why bad unit economics get worse with growth: lose money on one widget and you lose more on a thousand. They also cover finance tools versus finance expertise, how to vet a CPA, and how AI is changing accounting work, including why it still depends on good data going in. Founders preparing to raise will learn which numbers to get right before the pitch.


    Chapters


    00:00 Asking for capital with numbers, not belief


    00:37 Introducing Brandon Valentine and Valentine Advisory Group


    01:11 Where founders should start: unit economics


    03:40 Why you can't raise without your unit economics


    04:53 Labor, operating expenses and early foundations


    06:55 Bad unit economics lose more as you scale


    07:40 Pricing, freemium and market research


    10:16 Pricing to the problem you solve


    12:50 The three statement model and the capital ask


    15:03 Finance tools versus finance expertise


    16:33 How to find and vet a CPA


    18:07 How AI is changing accounting and finance


    23:02 Where AI goes wrong: bad data in, bad data out


    24:23 Where to find Brandon


    Host: R. Hunter Harris

    https://www.linkedin.com/in/rhunterharris/


    Guest: Brandon Valentine

    Brandon is a CPA from Atlanta and the founder of Valentine Advisory Group. He helps people buy and sell businesses in the lower middle market and helps founders and small business owners build their accounting and finance foundations.

    https://www.linkedin.com/in/brandon-valentine-cpa

    https://valentineadvisorygroup.com/


    Newsletter: Don't SaaS Me

    https://hunter-software-consulting.beehiiv.com/


    By Hunter Software Consulting

    https://huntersoftwareconsulting.com/

    Show More Show Less
    25 mins