Founder story // EP11

Ep11: She Was Fired. Then Built a Tech Company

The Dispute Buddy Story

Some of the best AI companies don't start with technology at all. In this episode Kim Fernandez talks with Jenny Rudd, founder and CEO of Dispute Buddy, who was fired from a magazine job, bought the business, became an award-winning editor, sold it, then built a legal-tech startup with no technical background. Her story is a masterclass in building around a real problem.

Based on AI Your Business Podcast2026-03-25Guest: Jenny Rudd

The short version

Jenny Rudd built Dispute Buddy, a platform that turns messy, emotional communication into structured, lawyer-ready evidence, without coming from a technical background. What makes the story useful isn't the tech, it's the discipline: she stayed in the problem long before building, and let lived experience shape a product people could trust. For established businesses, that's the transferable lesson.

Non-technical founders can build real tech when they understand the problem deeply and bring the right people around them.
The unglamorous early work, customer discovery, MVPs and staying in the problem space, is what separates useful products from clever demos.
In sensitive, high-trust domains like legal, guardrails and a trauma-informed approach aren't extras, they're the product.

Why this matters

The temptation with AI is to start from the tool and hunt for somewhere to use it. Jenny's story is the opposite, and that's exactly why it works. For an established business the same trap applies internally: build too broadly or too fast, and you dilute the very problem you set out to solve.

  • Sensitive use cases need stronger guardrails than a slick interface suggests
  • A clever product can hide unclear accountability for what it outputs
  • Users over-trust results when the limits aren't spelled out
  • Building too broadly dilutes the specific problem worth solving

What to do with this insight

Borrow Jenny's sequence. Pick one real problem your team or customers keep hitting, get properly close to it, then build the smallest useful version before you scale anything.

  • Start with one specific, painful user problem
  • Define the outcome and the boundaries before building
  • Build a small version around the real process, not the tech
  • Review quality and risk honestly before you scale

How AI Collab thinks about it

This is exactly how we scope custom builds: problem first, then the smallest thing that genuinely helps, then careful expansion. Jenny's story is the founder version of what we do for established teams, find the friction that matters and remove it with AI, without losing trust or accountability along the way.

Frequently asked questions

What can businesses learn from AI founders?
Start with a real problem, understand the user deeply and build around the outcome rather than the novelty of AI.
Does every AI idea need to become a product?
No. Many of the best AI opportunities inside established businesses are internal tools.
How should a business test an AI idea?
Start with one workflow, define success and review outputs before expanding.

Want to turn this into a practical AI plan?

AI Collab helps established Australian businesses move from interest to implementation: strategy, team capability, governance and custom builds that fit the way the business actually works.

Talk to AI CollabListen to the episode