Compound Conversations

Most leaders running growing companies have bought the AI tools, hired the consultants, run the pilots, and still have nothing to show for it. The Compound podcast is for operators who are tired of that story. Every episode covers what actually changes when a growing company redesigns how its people and AI work together: the constraints worth solving, the organizational structures that make AI stick, and the education that turns a skeptical team into one that thinks AI before headcount. This isn't a show about what AI can do. It's a show about how to build a business where it does. Hosted by Jesse Flores and Julie Mann at Compound, the organizational design firm for AI.

Compound Conversations is a business podcast hosted by Jesse Flores and Julie Mann, with 10 episodes on record and a Required Pod Score of 80. PitchCentric scores this show on Booking Probability, Listen Score, and live audience signals refreshed every 24 hours.

Jesse Flores and Julie Mann hosts Compound Conversations, a business show with 10 episodes published.

Our AI reads these to draft pitches. Use them as grounding for a pitch that cites a real guest and a specific topic.

• 

  Episode #11

  Compounding vs. scaling

  Aug 13, 202634 minS1

  Most organizations are chasing scale. Scale is a rate, not a structure. Chase it before the structure exists and it breaks under its own weight. In this episode, Jesse Flores and Julie Mann break down the difference between scaling and compounding, and why treating the two as the same thing is the most expensive mistake in the current AI conversation. You will walk away understanding why scale is a byproduct of structure rather than a goal to pursue directly, what actually compounds from one sprint to the next, and how to spot vendor language that sells scale while calling it compounding. They also walk through all six stages of the Sequence: Signal, Source, Design, Build, Deliver, Compound. The infrastructure a sprint leaves behind, not the agent or workflow it produces, is what makes the next sprint cheaper to run. Takeaways Scaling is a rate. Compounding is a structure. Treating them as the same thing is why so many AI investments plateau instead of building on themselves. The real output of a sprint is not the agent or the workflow. It is the infrastructure that sprint leaves behind, which is what makes the next sprint cheaper to run. Compounding growth is geometric, not linear. That is the entire reason a fourth sprint costs a fraction of what the first one did. Chapters 0:00 Scale is a rate, compounding is a structure 2:23 The untrained marathon 7:13 Why compounding is geometric, not linear 14:27 The paradox of slowing down to speed up 24:04 What sprint one actually leaves behind Connect with Compound https://linktr.ee/compoundorg

  ListenShow Notes
• 

  Episode #10

  Deployed is not the same as adopted

  Aug 6, 202640 minS1

  Most organizations celebrate going live. Nobody plans for what comes after. That is where the investment quietly dies. In this episode, Jesse Flores and Julie Mann break down the difference between deployment and delivery — and why confusing the two is the most expensive mistake in AI implementation. You will walk away understanding why going live is a technical state and adoption is an organizational one, what changed handoffs, retraining, and real cost measurement actually look like in practice, and how to tell the difference between a project that launched and a workflow that landed. They also walk through the five dimensions of delivery — changed handoffs, retraining people, cost measurement, trust and adoption, and the shadow process — and why each one has to be tracked, not assumed. Takeaways Deployment is an event. Delivery is the phase nobody plans for. The three to four weeks after go-live is where most AI investments quietly stop compounding and start collecting dust. Changed tooling and changed behavior are not the same thing. Installing the tool is the easy part. Getting people to actually work differently is where the real adoption work begins — and it takes repetition, structure, and a culture that makes it safe to try and fail. If people are still doing something in secret that the new workflow was supposed to replace, that shadow process is not a problem to punish. It is the most valuable signal you have about where your delivery phase broke down. Chapters 0:00 Deployment as an event versus delivery as a phase 4:39 Where the investment quietly dies 11:56 Deployment is a technical state. Adoption is an organizational state. 21:58 The five dimensions of delivery 32:37 Trust, culture, and the shadow process Connect with Compound https://linktr.ee/compoundorg

  ListenShow Notes
• 

  Episode #7

  Design before deploy

  Jul 2, 202647 minS1

  If you're running the Entrepreneurial Operating System, you already have an accountability chart. It names who owns what outcome. But the moment an agent or an agent team enters the work, that chart goes silent. No box, no owner, no accountability. In this episode, Jesse and Julie introduce the hybrid accountability chart, a layer that runs on top of the one you already have. It maps a dual workforce, human and agent, so every outcome carries four things: the outcome itself, the agent or agent team doing the work, the human supervisor who owns it, and the level of autonomy that team is allowed to operate at. They walk through it with two real examples from inside Compound: a small agent team that files video footage so nobody burns an afternoon hunting for a clip, and a daily Facebook ads report that lands by text every morning at 7am. Same structure both times. Name the outcome, name the team, name the human who's accountable when something breaks. They also cover where this goes wrong. What it means to match the right human to the right agent team, and why Jesse wouldn't hand his ad reporting team to someone without the context to judge its output. Why agents have a maturity curve just like people do. What happens when an agent hits an input it wasn't built for, told through the story of a prompt injection that nearly booked a hundred fake appointments across a quarter of Jesse's calendar. And why "how can we use AI" is the wrong first question, every time. Design before deploy. Know the outcome, name the owner, then decide what to build or buy. The goal isn't just accountability, it's a structure you can see and one that holds up. Stop transforming. Start compounding. Click Here to Connect with Compound --- Chapters 00:00 — If you run EOS, you already have this chart. It just doesn't account for AI. 02:26 — The four parts of a hybrid accountability chart 04:53 — Example: the video filing agent team 07:21 — Example: the daily ad performance report 09:43 — Individual efficiency vs. operational efficiency 17:00 — Name your agent teams before you lose track of them 19:25 — Buy, try, scale is backwards. Design before deploy. 24:09 — When Claude went down for an hour, and why you need fail safes 28:42 — Naming a human orchestrator (first and last name) 29:30 — Agents have a maturity curve too 31:00 — Fit matters: why the wrong human on the wrong agent team is a mismatch 33:27 — Teaching judgment, not tasks 38:08 — The prompt injection story: 100 calendar invites 42:52 — Governance: data access, approvals, kill switches 45:10 — Recap: visible and durable, not just accountable

  ListenShow Notes
• 

  Episode #6

  What your judgment heavy role is actually doing all day

  Jun 25, 202640 minS1

  <p>Every senior role has a job description. Almost none of them reflect what that role is actually doing all day.</p><p></p><p>In this episode, Jesse and Julie break down the 60-30 pattern, the diagnostic signal that surfaces when you look at how judgment-heavy roles actually spend their time. The finding is consistent: these roles spend sixty percent of their time on coordination, routing, documentation, and policy questions, and only thirty percent on the actual judgment they were hired to exercise. And that ratio is one of the clearest signals that your organization isn't ready to compound.<...

  ListenShow Notes
• 

  Episode #6

  What your judgment heavy role is actually doing all day

  Jun 25, 202640 minS1

  Every senior role has a job description. Almost none of them reflect what that role is actually doing all day. In this episode, Jesse and Julie break down the 60-30 pattern, the diagnostic signal that surfaces when you look at how judgment-heavy roles actually spend their time. The finding is consistent: these roles spend sixty percent of their time on coordination, routing, documentation, and policy questions, and only thirty percent on the actual judgment they were hired to exercise. And that ratio is one of the clearest signals that your organization isn't ready to compound. You'll walk away able to do three things: Categorize your organization's knowledge systems into the three buckets that determine how AI can use them: systems of record, systems of knowledge, and systems of semantics. Apply the 60-30 diagnostic to identify where senior capacity is being absorbed by work that belongs somewhere else. Map your sources, assess API and MCP connectivity, and tier your automation decisions so your design matches the actual work. They also walk through the real cost of disorganized knowledge, not just the human cost of wasted time, but the token cost your AI workforce incurs every time your data isn't clean. Jesse shares a real story about a $2,000 surprise token bill in six days and what it revealed about the gap between how humans tolerate messy systems and how AI prices them. There's a downloadable systems map worksheet so you can run this on a real process before the week is out. Chapters 00:00 The knowledge problem underneath every AI implementation 02:27 Three categories: record, knowledge, and semantics 04:52 Why systems fail when the business process doesn't change 07:16 What the role is actually doing vs. what the job description says 09:37 Systems of knowledge and the document discipline problem 12:03 Structuring the unstructured 14:27 Two workforces, two cost structures 16:48 The token bill that's coming 19:14 The $2,000 surprise 21:34 The key bowl: a simple analogy for knowledge discipline 23:53 Every place AI has to look costs you something 26:18 Design steps: list your sources 28:46 APIs, MCPs, and connectors explained 31:09 Tiering your systems: assisted, notified, or automated 33:19 What's missing and how to find it 35:43 The 60-30 pattern 38:02 Why humans almost never need to do data entry 40:12 Making the design decisions 42:37 Stop transforming. Start compounding. Register for Live Conversations via the link. https://compoundorg.com/webinars

  ListenShow Notes

Recent guests on Compound Conversations. Study who booked and why before you pitch.

Based on semantic analysis of episode topics and host coverage, this show is a strong guest fit for executives in:

Industry fit is computed by PitchCentric using vector embeddings of the show's episode catalog.