That Real Estate Tech Guy cover art

That Real Estate Tech Guy

That Real Estate Tech Guy

By: Jordan Samuel Fleming
Listen for free

This Season's Biggest Deal | $0.99/mo for 3 months + $20 Audible bonus

Auto-renews at $8.99/mo. after 3 months - terms apply.
Summary

Welcome to the only weekly podcast dedicated to the Real Estate Investing Tech Stack, hosted by Jordan Samuel Fleming. Jordan has been heavily involved in building technology tools for Real Estate Investors for over a decade, and is the Co-Founder and CEO of smrtPhone, and all-in-one cloud phone system and power dialer. If you're serious about scaling up your Real Estate Investing business then this weekly podcast is for you! You'll learn from the best as each week Jordan speaks with individual investors who have leveraged technology to scale their businesses, as well as technology companies who build the tools you use on a daily basis. That Real Estate Tech Guy brings together expert insights, advice and the latest technology tips for any investor looking to build their Real Estate Investing business.

© 2026 smrtStudio Global, Inc
Economics Leadership Management Management & Leadership
Episodes
  • How AI Labor Breaks the Link Between Growth & Headcount
    Nov 12 2026

    This week I’m going solo to talk about why growth and headcount have always moved together, and why I think AI labor can finally break that link. Technology made people more productive and changed the slope of the line, but more customers still meant more work and eventually more hires.

    Using a company that processes 1,000 applications a month with ten people, I walk through what happens when you redesign the work around people, AI agents, and systems instead of just giving everyone ChatGPT. I also cover the catch: AI agents don’t break the link on their own, and a badly designed business will simply move the line somewhere else. If you’re an investor or operator planning growth and headcount, this one is for you.


    Episode Timeline & Highlights

    [0:00] – The old link between growth and headcount: more customers, more work, more people
    [1:05] – Technology changed the slope of the line but never really broke it
    [1:41] – Why AI labor can break the linear relationship between growth and headcount
    [2:44] – An example: 1,000 applications a month, ten people, and the old pattern of hiring as volume grows
    [4:45] – Redesign the process underneath, not just give everyone ChatGPT and hope the slope improves
    [5:56] – Designing responsibilities: AI agents gather and verify information, chase missing items, and hand off exceptions
    [7:04] – From 1,000 to 10,000 applications: why you add a person, and why volume should not decide it
    [8:39] – Volume climbs while the team stays near ten, and growth and headcount start to disconnect
    [9:53] – What this does not mean: you can still hire, just not only because existing work grew
    [11:00] – Capacity planning, and how AI agents can hold thousands of active contexts around the clock
    [12:00] – The catch: AI agents don’t break the link on their own, and the line can reappear somewhere else
    [13:42] – Why architecture matters: design the work so more volume doesn’t create new manual work downstream
    [15:24] – How growth planning and workforce planning got tied together, and the cost of hiring too slowly or too fast
    [17:30] – Instead of asking how many people you need, ask what actually needs to change if you grow by 50%
    [18:52] – Why “do more with less” misses the point of what AI labor changes
    [20:28] – Economic architecture: hire because a person makes the business better, not because a spreadsheet says so


    Key Takeaways

    1. Growth Used to Mean Headcount: For a long time more customers meant more work and more people, and technology only changed the slope of that line.
    2. Redesign the Work, Don’t Just Add AI: Giving everyone ChatGPT may improve the slope, but breaking the line means redesigning the responsibilities underneath the process.
    3. Hire for Value, Not Volume: Headcount can still grow, but it should grow because a person makes the business better, not because volume crossed a threshold.
    4. The Line Can Reappear: If the architecture is badly designed, the link between growth and headcount simply moves downstream to handoffs, exceptions, and lost context.
    5. More With Less Misses the Point: The real change is that the amount of work your business can execute is no longer tied to the number of people the way it always was.


    Links & Resources

    • smrtPhone: https://www.smrtphone.io
    • That Real Estate Tech Guy: https://thatrealestatetechguy.com


    Before your next planning meeting, pick one growth number and ask what actually needs to change if you hit it, instead of asking how many people you need. You may find the answer is smaller, or very different, than the spreadsheet says. More high-signal conversations coming next.

    Show More Show Less
    22 mins
  • Why Starting With AI Economics Is a Costly Mistake
    Nov 5 2026

    This week I’m going solo to talk about what I think is one of the biggest mistakes companies will make with AI: starting with the economics. When you look at what AI agents can do and start asking whether 20 people could become 10 or 5, you end up calculating the savings before you’ve redesigned the business to actually capture them.

    Using a customer success team of ten, I walk through what goes wrong when you cut to three, from lost context and stuck handoffs to one overwhelmed person holding everything together. Then I show a better path: start with the work, responsibility, execution, and infrastructure, and let the economics emerge from the design. I close with an exercise you can run on any AI calculation you’ve already done. If you’re an investor or operator weighing AI labor in your business, this one is for you.


    Episode Timeline & Highlights

    [0:00] – The biggest mistake companies will make with AI: starting with the economics

    [0:23] – Could 20 people become 10 or 5, or handle three times the volume, and why that math is tempting

    [1:28] – A ten person customer success team and what AI agents can actually do around the clock

    [2:24] – Before you cut to three, did you understand the work, the judgment, and the exceptions those people carry

    [4:02] – The spreadsheet looks great, then handoffs break, context disappears, and exceptions pile up

    [4:31] – The one remaining person who becomes the overwhelmed hub holding everything together

    [5:28] – The hidden assumption: that your organization is just a collection of work done by people

    [6:40] – Economics first on the growth side: can the business absorb ten times more opportunities

    [7:38] – Why economic architecture sits in the AI labor architecture framework as an outcome, not a pillar

    [8:50] – Start with the work, then responsibility, execution, and the infrastructure that connects them

    [10:57] – Redesigning the ten person team with the economics taken off the table

    [12:30] – Maybe three people can do it, or maybe ten people with AI agents can serve five times the customers

    [14:17] – Beyond payroll: speed, consistency, capacity, availability, and where people create the most value

    [15:21] – Breaking the stubborn link between growth and headcount, and what happens if the architecture is wrong

    [19:06] – The exercise: set your AI math aside and go underneath it to the work, the people, and the infrastructure

    [20:32] – Why economic architecture comes at the end of the framework and has to be earned


    Key Takeaways

    1. Don’t Start With the Spreadsheet: Calculating AI savings before you redesign the business means your math rests on assumptions you haven’t tested.
    2. People Carry Invisible Work: The people on your team hold context, make decisions, and move work between systems, so cutting them without understanding that work breaks the infrastructure.
    3. Economics Is an Outcome: Economic architecture sits at the end of the AI labor architecture framework because better margins and capacity come from redesigning the work, not from declaring a number.
    4. Redesign Before You Resize: When you understand the work first, you may find three people can do what ten did, or that ten people with AI agents can support five times the customers.
    5. Break the Link Between Growth and Headcount: With the right architecture, growth no longer has to mean more people, more handoffs, and another layer of managers.


    Links & Resources

    • smrtPhone: https://www.smrtphone.io
    • That Real Estate Tech Guy: https://thatrealestatetechguy.com


    Pick one place in your business where you’ve already done the AI math, set the number aside, and go underneath it to the work, the people, and the infrastructure. You may find the real opportunity is bigger than the savings you first imagined. More high-signal conversations coming next.

    Show More Show Less
    22 mins
  • Using Automation vs. When to Use an AI Agent
    Oct 29 2026

    This week I’m going solo to make a case that some of the most important infrastructure in your business isn’t software, it’s your people. Your systems can move data, but they can’t understand the work, so people like a customer success rep named Mark have become the intelligent integration layer between your CRM, billing platform, Slack, and email.

    I walk through Mark’s customer request step by step, show where traditional APIs and automations stop, and explain how AI agents can move work with the right context when the movement isn’t deterministic. The goal isn’t to remove people from the business but to get them out of the infrastructure layer, and I close with an exercise to find where that’s happening in your own company. If you’re an investor or operator designing a workforce of people and AI agents, this one is for you.


    Episode Timeline & Highlights

    [0:00] – Why some of the most important infrastructure in your business is your people, not your software

    [1:00] – Moving data is not the same as understanding the work, and the customer request that shows the gap

    [1:31] – Mark opens the CRM, billing platform, Slack, product platform, and email to assemble the full picture

    [2:56] – What Mark really did: connected systems, interpreted information, and acted as the integration layer

    [5:09] – The limits of traditional integration, and a failed payment that an API can move but not understand

    [6:45] – Where deterministic movement is perfect: if X happens, do Y

    [7:50] – Systems could never answer who should receive the work, so people provided the intelligence

    [8:28] – How an AI agent handles the failed payment using customer context, policies, and its authority

    [10:21] – Moving the work with the relevant context, not a task that just says please handle

    [12:20] – Not every movement needs an agent: if X reliably means Y, use the API, automation, or rule

    [13:19] – Scale: a person monitors 50 situations while an agent can stay aware across thousands

    [14:52] – The goal is to get people out of the infrastructure layer, not out of the business

    [16:32] – A person who is the right worker for the job versus a person required to connect the work

    [17:36] – Receive, execute, hand off, and who provides the intelligence between those stages

    [19:59] – The exercise: find the people who seem to know how everything connects and watch what they do

    [21:29] – If the movement needs intelligence, could an AI agent provide it instead of a person?


    Key Takeaways

    1. People Became the Infrastructure: Your systems could move data but couldn’t understand the work, so people filled that gap.
    2. Moving Data Is Not Understanding Work: An API can tell your CRM a payment failed, but it can’t tell you what that failure means.
    3. Keep Deterministic Work Deterministic: If X reliably means Y every time, use an API, automation, or business rule instead of an agent.
    4. Agents Provide Intelligent Continuity: An agent can decide where work should go and send it along with the context the next worker needs.
    5. Get People Out of the Layer, Not the Business: People should be involved because they’re the right worker for the responsibility, not because the infrastructure can’t understand the work.


    Links & Resources

    • smrtPhone: https://www.smrtphone.io
    • That Real Estate Tech Guy: https://thatrealestatetechguy.com


    If this made you think of the Mark in your own business, spend a week watching what he actually does between your systems. You may find work that was never his job to begin with. More high-signal conversations coming next.

    Show More Show Less
    23 mins
No reviews yet
In the spirit of reconciliation, Audible acknowledges the Traditional Custodians of country throughout Australia and their connections to land, sea and community. We pay our respect to their elders past and present and extend that respect to all Aboriginal and Torres Strait Islander peoples today.