Skip to content
Shows/Building Modern Business
Building Modern Business·Episode 2·Series

Pros and Cons of Vibe Coding Your CRM

When AI-assisted building helps, and when it bites

Feb 12, 2026·36:20·James Bond, Paul Maxwell

Video coming soon

No YouTube video has been added yet.

Your browser does not support the audio element.

About this episode

AI coding tools make spinning up a custom CRM feel effortless. Paul and James examine where vibe coding delivers real speed and where it quietly accumulates risk you'll pay for later.

Key ideas

  • 01Vibe coding excels at prototypes, glue, and throwaway tools
  • 02AI optimizes for looking done, not surviving production
  • 03A convincing demo is not a system you can trust revenue data to
  • 04Keep a human accountable for the architecture and data model

Show notes

What we covered

You can now describe a CRM feature and watch an AI build it in minutes. That's genuinely powerful and genuinely dangerous. Paul and James separate the legitimate uses of AI-assisted building from the failure modes that show up three months in.

In this episode

  • What vibe coding is great at: prototypes, glue, and throwaway tools
  • Where it breaks down: data integrity, edge cases, and scale
  • The maintenance question nobody asks the AI
  • How to keep a human accountable for the architecture
  • A sane workflow for AI-assisted internal tooling

Links & resources

  • Paul's AI-assisted build guardrails
  • When to prototype vs. productionize
  • Notes on reviewing AI-generated data models

Timestamps

Chapters

  1. —What vibe coding is
  2. 5:40Where it shines
  3. 13:40Where it breaks
  4. 22:00The maintenance question
  5. 29:40Keeping a human accountable

Quotable

“Don't confuse a convincing demo with a system you can bet your revenue data on.”

— Paul Maxwell

Full transcript

Transcript~1 min read

Show transcriptHide transcript

Paul: Vibe coding a CRM feels like magic right up until real data hits it. The demo works, the prototype dazzles, and then someone imports ten thousand messy records and the whole thing buckles.

James: The problem is the AI is optimizing for something that looks done, not something that survives contact with production. It won't tell you about the edge case it didn't consider.

Paul: So use it for what it's genuinely great at. Prototypes, glue code, throwaway internal tools. Just don't confuse a convincing demo with a system you can bet your revenue data on.

James: And keep a human accountable for the architecture. The AI can write the code, but somebody still has to own whether the model is right.

Mentioned

  • Claude
  • Vercel
  • Neon

Related links

  • Guardrails for AI-assisted internal tools

Hosts

  • JB
    James Bond

    Host

    VP of Sales, RevOps HQ

  • PM
    Paul Maxwell

    Host

    CEO, RevOps HQ

Topics

  • Artificial Intelligence
  • CRM Strategy
  • Software Engineering

Subscribe to Building Modern Business

  • YouTube
  • Spotify
  • Apple Podcasts
  • LinkedIn

Related episodes

Building Modern BusinessHow to Pick a CRM—and Who to TrustEvery CRM vendor and consultant has an incentive. Paul and James lay out a buying process that surfaces real fit, exposes hidden costs, and helps you tell honest advisors from salespeople in disguise.
Building Modern BusinessCRM Is a Core Executive CompetencyPaul and James argue that understanding your CRM is now a leadership skill, not an admin's job. Executives who treat the system of record as beneath them lose visibility into their own business.
Building Modern BusinessBuild vs. Buy a CRMPaul and James debate the most consequential systems decision most companies face: build a custom CRM or buy a platform. They cut past the hype to the real total cost, ownership, and risk tradeoffs.
Building Modern BusinessWhen to Buy a CRM Integration from an AgencyIntegrations are where CRM projects quietly succeed or fail. Paul and James break down when to hand an integration to an agency, when to keep it in-house, and when an off-the-shelf connector is enough.