The Hidden Flaw in Splitting Work Between People and AI

This week, that real estate tech guy himself, Jordan Samuel Fleming, goes solo to tackle one of the biggest questions AI raises for business owners: not what can a person or an AI agent do, but who should do it. Using a hypothetical AI sales agent named Daniel, he breaks down why the old dividing lines between "human work" and "AI work" are starting to fall apart. Jordan introduces the idea of shared execution, where a single responsibility gets carried by a mix of people and AI agents at different moments, based on what actually produces the best outcome rather than who has always done the work. It's a practical reframe for any business owner trying to figure out where AI actually belongs in their operation. # Episode Timeline & Highlights: \[0:00] – Opens with the real question replacing "who can do the work": who should do it \[0:36] – Explains why, for most of history, work requiring judgment always landed on a person by default \[1:15] – AI agents can now communicate, make decisions, exercise judgment, and manage relationships on their own \[1:53] – Warns against drawing a simple dividing line between "human work" and "AI work" \[3:05] – Argues the future workforce gets designed responsibility by responsibility, not by two separate lists \[3:35] – Introduces a hypothetical AI sales agent, Daniel, fully trained on product, pricing, and qualification criteria \[4:38] – A new lead arrives and Daniel handles the entire qualifying conversation with no need for a human \[5:10] – Daniel flags something unusual: this deal could be worth half a million dollars \[5:46] – The real question becomes not "can Daniel continue" but who creates the most value in this specific moment \[7:26] – Flips the example: what happens if a company insists every one of 2,000 leads gets a personal follow up from a salesperson \[8:02] – Points out Daniel may actually maintain relationships better than a person, with no forgotten follow ups \[10:30] – Value belongs to whoever is actually contributing to the outcome, not to a category of worker \[11:05] – Introduces "shared execution," where multiple types of labor intentionally share one outcome \[13:15] – Distinguishes capability from suitability: being able to do something doesn't mean you're the one who should \[14:56] – The labor split isn't fixed. An AI agent might start by owning 20% of a responsibility and grow from there \[18:22] – Closes with the challenge: stop asking "could I do this" and start asking "who should do this, and why" # 5 Key Takeaways 1. Ask "Who Should," Not "Who Can": As AI agents get more capable, the old question of who is capable of doing the work stops being useful. The real design question is who creates the best outcome in this specific moment. 2. The Human vs. AI Line Is Dissolving: Clean categories like "AI does repetitive work, people handle relationships" feel comforting, but they don't hold up as agents get better at judgment, empathy, and context. 3. Shared Execution Beats the Relay Race: The best model usually isn't an AI agent handing off to a person once things get hard. It's an AI agent and a person both staying involved in the same responsibility, moving in and out as the situation changes. 4. Capability and Suitability Are Different Questions: Just because an AI agent, or a person, is capable of doing something doesn't mean they're the one best suited to do it. That decision comes from outcome, cost, risk, and context, not default habit. 5. The Split Isn't Permanent: An AI agent might start by owning 20% of a responsibility and grow into 60% or more as it's trained and trusted. The goal isn't to maximize AI or protect people. It's to get the best outcome. # Links & Resources - smrtPhone: https://www.smrtphone.io - That Real Estate Tech Guy: https://thatrealestatetechguy.com If there's one responsibility in your business you've been assuming needs a person just because that's who's always done it, this is the week to go take a second look. More high-signal conversations coming next.