Episode 6
Vibe Coding: The Owner's Unfair Advantage
You don't need to code to build software anymore. You need clarity. May and Jab break down vibe coding: what to build, what it costs, and the risks.
Listen on
Show Notes
You no longer need to know C++ to build software. You need to know what you want.
In this episode of May Contain Jab: The Owner's Edge, May and Jab dig into vibe coding: describing an app in plain English and letting AI build it. Tools like Lovable, Replit, Cursor and Claude Code have turned weeks of developer time into an afternoon. But is it really that easy, or is it just hype?
May shares what she has built herself, from a client portal to a lightweight to-do app and her own CRM. Jab demos two vibe coded lead magnets live on the show: a marketing "time machine" that shows the cost of doing nothing, and a swipe-style app that asks what it would be like to date yourself based on your lifestyle habits.
They also get honest about the risks. Security. Messy code you cannot read. Credits that disappear like coins in a slot machine. And knowing when to stop building and bring in a developer.
In this episode
- What vibe coding actually is, in plain English
- Why clarity is the real skill, not code
- The simplest thing a founder can build first
- What May has built with Lovable and Claude Code
- Is it really a vibe, or just hype?
- Vibe coding vs automation tools like n8n: when to use which
- The hidden costs: credits, tokens and tool subscriptions
- Where the risks lie: security, authentication and going live
- When to bring in a real developer
- Clawbot and OpenClaw: shiny, but not all green pastures
- Is an MBA still relevant in an AI world?
- Are tech layoffs really about AI?
- Rapid fire: Canva vs Opus Clip, Perplexity vs Gemini, DIY vs consultant
- Live demos: the marketing time machine and the "date yourself" app
Timestamps (from the live edit, check against the final cut)
- 00:00 Welcome to May Contain Jab
- 00:35 What is vibe coding?
- 02:52 How vibe coding differs from ChatGPT
- 04:18 The simplest thing a founder can build
- 07:40 What May has built recently
- 09:08 Is it really a vibe?
- 10:28 Where business owners should start
- 11:28 Best marketing use cases
- 13:23 Is software cannibalising itself?
- 16:13 How to think about tool costs
- 17:54 Common mistakes and the downsides
- 21:01 When to bring in a developer
- 22:19 Clawbot and OpenClaw
- 26:10 Where vibe coding gets dangerous
- 28:57 How to cut through the hype
- 31:56 Is the MBA still relevant?
- 35:26 Tech layoffs and AI
- 39:04 Rapid fire
- 40:53 Three things May would vibe code
- 42:43 Live demo: the marketing time machine
- 45:45 Live demo: date yourself
- 51:27 The takeaway
Blog
All posts →
You Don't Need to Code Anymore. You Need Clarity.
A few years ago, building an app meant hiring developers, learning what C++ was, and paying tens of thousands of pounds before you saw anything work. Today you can describe what you want in plain English and watch it get built.
That is vibe coding. And in the latest episode of May Contain Jab: The Owner's Edge, May and Jab ask whether it is the unfair advantage it is cracked up to be.
What vibe coding actually is
Vibe coding means building software by describing it to AI tools like Lovable, Replit, Cursor and Claude Code. You say what you want. The tool plans it, builds it and documents it.
Jab's analogy: imagine sitting on a beach, dictating to a scribe who writes everything down and makes it real. The catch is that the scribe cannot get into your head. If you do not know what you want, you will not get it.
That is the real skill now. Not code. Clarity.
What you can actually build
May has been building. A client portal where clients review deliverables and submit change requests. A lightweight to-do app to replace a heavy Notion setup. Her own CRM.
Jab's view: the obvious first build is a landing page, but the bigger opportunity is lead magnets. Interactive tools that pull your ideal customer in. On the show, he demos two. One shows a brand the cost of doing nothing with its marketing. The other is a playful swipe app that asks what it would be like to date yourself, based on your lifestyle habits.
It is not all green pastures
Both hosts are clear that vibe coding has limits.
When something breaks, it is hard to see where. In a visual automation tool like n8n, the broken step lights up red. In vibe coded software, you are often guessing. If you cannot read code, you cannot judge whether it is clean or quietly bloating in the background.
Security and authentication are still real concerns. A tool you use privately on your own machine is low risk. Anything you put in front of the public needs a developer to check it, and someone trying hard to break it.
Then there is cost. Credits and tokens add up. Jab compares it to a slot machine: you keep feeding it, hoping for the jackpot. His rule of thumb is to vibe code your first version, then bring in a developer once you need databases, proper front end work and scale.
How to cut through the hype
New tools launch every week, and each one is the next big thing until it is not. Jab's advice: get married to the mission, not the model. Pick one tool, give it a month, and learn it properly before jumping to the next. And check your sources, because the loudest voices are sometimes invested in the tools they are promoting.
The takeaway
You do not need to become a developer. You need to know your process, know where it falls short, and be able to describe the fix clearly.
The episode also covers whether an MBA still matters in an AI world, whether tech layoffs are really about AI, a rapid fire round on the tools May and Jab actually use, and May's three dream builds.
Listen to the full episode to hear the live demos, the stories behind the builds, and the one challenge every owner should try this week.