Back to the podcast
EP03349:05 · Sep 17, 2026

Building Your Own UI, Named Agents, and a Bank's AI Playbook

Jeff built seven screens of a customer success platform from one throwaway prompt, then sat in disbelief for three minutes. Jay argues he didn't build a platform at all — he built a UI, and that distinction may reshape who owns the CRM layer.

Plus: the most pragmatic AI adoption playbook either host has seen, from a 700-person bank.

KEY TAKEAWAYS

  • You're building a UI, not a platform: The data layer, permissions, and system of record still have to live somewhere. Generated interfaces sit on top — they don't replace it.
  • Make models check each other: Jeff runs Claude and Codex against the same codebase and PRs. Trusting one model unchecked is how quiet mistakes ship.
  • Bake permissions in on day one: Field-level controls are cheap to design now, expensive to retrofit after someone overwrites a CRM field.
  • Agents are employees, automations are triggers: Jay's team gives agents names, email addresses, and Slack accounts, then scopes specific tasks to them.
  • Meet people where they work: A great internal tool nobody opens loses to a mediocre one that lives in Slack.
  • Native beats bolted-on: Lightfield builds call recording into an agentic CRM — raising whether platforms simply absorb point solutions like Gong and Fathom.
  • The 20-year default is up for grabs: AI-native companies are re-evaluating Salesforce and HubSpot, and $10–30M niche software businesses look far more buildable.
  • Adoption is change management: Licenses aren't a strategy. Training, champions, and executive time are.

CHAPTERS

  • 00:00 - Six-and-a-half-minute podcast intros, and why we don't do them
  • 01:26 - Building a CS platform at Junction, and what early users saw in it
  • 02:50 - Running Claude and Codex against each other for checks and balances
  • 05:21 - One prompt, seven screens: the project management mockup
  • 10:23 - Dreamforce, and Jay's case that you're building a UI
  • 13:50 - Permissions, field-level controls, and moving slower on purpose
  • 16:39 - Working where your team works: the Slack problem
  • 17:36 - Agents as employees: names, email addresses, Slack accounts
  • 19:27 - Muse, personal agents, and Lightfield's agentic CRM
  • 22:16 - Do platforms eat point solutions like Gong and Fathom?
  • 24:02 - Would a new company pick Salesforce or HubSpot today?
  • 27:46 - Compound startups and the case for $10–30M software businesses
  • 30:50 - Bending Spoons, Airtable, and the no-titles debate
  • 38:41 - Superhuman acquires Fathom, and a very confusing product strategy
  • 41:33 - A bank CTO's pragmatic AI adoption playbook
  • 47:11 - Change management, prerequisites, and what most companies skip

About the Show: Chief Customer Officer Podcast is a show about real strategies for customer-led growth in the AI era—from leaders actually executing, not just talking about it.

Your Hosts:

Want to be a guest, or just talk to one?

Most guests are Uncommon members first. It's the fastest way to end up on the show — or just DM one of them directly.

Join Uncommon