The time someone spends going through emails before a meeting. The research on who you're about to sit across from. The summary of where a deal or project stands. The briefing document that lets a busy executive walk into a room already knowing what matters.

Most senior people have someone doing this for them. A chief of staff. An executive assistant. Someone whose job includes knowing what you need to know before you need to know it.

I was sitting with a client who runs a membership club in Austin. Packed schedule. Lots of meetings. We started adding up how much time his team was spending each week just getting him ready.

The number was around 20 hours.

What That 20 Hours Looks Like

It's not one person sitting down for a 20-hour shift. It's accumulated time.

Someone pulls the email history between their boss and the person they're meeting tomorrow. Someone checks the CRM for context. Someone summarizes the last three touchpoints. Someone puts together a one-pager so the boss can read it on the way to the meeting.

Multiply that across a full week of meetings — six, eight, twelve a week for a busy operator — and you're looking at something like half a full-time employee, just for prep.

Most people don't think about it this way because the cost is distributed and invisible. But it's real.

What the Digital Chief of Staff Does Instead

I built something I call a Digital Chief of Staff. It's a bundle of AI agents that collectively do the same job — briefings, context gathering, meeting prep — automatically.

Every morning, the system generates a briefing document. Every meeting on the calendar gets a section: who you're meeting, what you've discussed before, what context from email and CRM and prior conversations is relevant to this conversation.

My client reads it in 15 minutes. He walks into every meeting with the same level of preparation that used to take his team 20 hours to produce.

A friend of mine, Evan, has a version of this too. His runs twice a week. In addition to the text briefing, it produces a visual — an image that maps out the week at a glance, who he's meeting and when, built with Nano Banana image models. He told me it changed how he shows up to meetings. Not just the prep time. The quality of attention.

The Part Nobody Talks About

There's a lot of AI content about writing. Coding. Research. Summarization.

There's very little about what I think is the highest-ROI use case for most people: just knowing what's happening in your own schedule.

It sounds basic. But most people walk into meetings carrying only the context they happened to remember. They do a quick Google search on the way over, or skim the email thread for two minutes in the parking lot. If there was a relevant conversation three months ago, they probably don't remember it.

The briefing doc fixes this. It gives you a complete picture before you need it. And the people on the other side of the meeting notice — not because you tell them about the AI, but because you show up prepared in a way that feels unusual.

One of my AI consulting clients told me the automated follow-up emails it generates — sent three minutes after a call ends — create more trust than anything else he's done. People message him asking how it's possible. Most people take days. He responds in minutes.

The briefing is the same category of thing. It creates a level of attentiveness that used to require a large support staff. Now it requires a few agents and some setup time.

Who This Is For

This isn't just for executives with packed schedules. It's for anyone who regularly meets with people and needs context to make those meetings count.

Sales reps who need to know what happened on the last three calls before they pick up the phone. Consultants who juggle multiple clients and can't remember every conversation. Business owners who are networking constantly and want to walk into every coffee chat knowing something useful about the person across from them.

The barrier to setting this up is lower than most people think. The hardest part is usually the CRM — getting your contact and conversation data into a place where the AI can access it. Once that's done, the briefing generation is relatively straightforward.

What 20 Hours Back Actually Means

When I told Cam and Dan — the clients I was demoing this for — that the briefing prep used to take 20 hours and now happens automatically, Dan said something I keep coming back to.

“It's not really about the 20 hours. It's about what you stop worrying about.”

He was right. The value isn't just the time. It's the mental weight of knowing you're always prepared. Of not having to wonder whether you missed something important in the email history before a call.

That's what an actual chief of staff gives you. And now it's what the digital version gives you too.

Want to build a Digital Chief of Staff for yourself or your business? We cover this and similar AI systems in the 4-Day AI Sprint.

It started as an experiment. I wanted to build a few things — a meeting notes app, an AI executive assistant — and I figured the best way to learn was to just start. So I started.

The problem is that when something breaks (and it always breaks), I don't always know what to do. I'm not a developer. I can't read through code and find the bug. I'm at the mercy of whatever Claude Code suggests.

So a few weeks into this, I sat down with a couple of my software engineer friends and asked the obvious question: what's the best way to actually learn to code?

Their answer was not what I expected.

What They Told Me

“Honestly? You probably shouldn't be focusing on learning to code.”

“The way things are going right now, what you should be learning is how to write really good specs.”

A spec — sometimes called a PRD (Product Requirements Document) — is a document that describes exactly what you want to build. The features. The expected behavior. The edge cases. How the inputs and outputs should work. What happens when something goes wrong.

They put it this way: “It's kind of like being a really good product manager with technical skills.”

I went home and thought about that for a day.

The Test

At the time, I was building an AI executive assistant. Connects to Slack, Telegram, Gmail, and Google Calendar. When I send it a message on Telegram, it figures out what I want add to calendar, look someone up in my CRM, draft an email — and handles it.

The first attempt took me about 7 days. It got complex, tangled, hard to maintain, and eventually broke down in ways I couldn't untangle. I was building as I went, figuring out what I wanted as the code got longer.

I scrapped it and started over.

This time, before I wrote a single line of code, I spent 3-4 hours writing a detailed spec. What the agent needed to do. How it should interpret different kinds of messages. Which tools it needed access to. What it should do when it wasn't sure about something.

I also did something my engineer friends suggested: I asked Claude to look at my spec and show me an ASCII art diagram of the architecture — a rough visual of how the pieces connected. When it looked right, I handed that to Lindy's workflow builder.

The second build took 4 days.

Same project. Same complexity. Four fewer days — just because I started with a clear description of what I was actually trying to build.

Why This Works

Here's what most people get wrong about building with AI: they think the hard part is the code.

It's not. The AI can write most of the code. What it can't do is figure out what you want if you haven't figured it out yourself.

I've said in my AI workshops: you don't need to know how the engine works to drive the car. That's still true. But you do need to know where you're going. A spec is the directions.

When I build without a spec, I'm essentially asking Claude Code to improvise. It does its best. But every time I change my mind or discover something I forgot to include, we have to backtrack. The context gets messy. The code accumulates workarounds. Things break.

When I have a good spec, Claude Code has a clear reference. It knows what “done” looks like. It can catch when something doesn't match the spec. And I can think through the hard questions — what should happen in edge cases? — before I'm in the middle of a build trying to make real-time decisions.

What “Learning to Build” Actually Means Now

My engineer friends were right that I don't need to memorize Python syntax or understand how a database works at the implementation level. But that doesn't mean there's nothing to learn.

What I'm actually learning:

How to describe a system clearly. What questions to ask before building. How to spot when a feature I want is going to be complicated vs. simple to implement. How to break a big idea into smaller, testable pieces.

This is closer to product thinking than programming thinking. And it turns out that's exactly the skill that makes you effective when you're directing an AI to build something.

The people I see struggling most with AI coding tools aren't struggling because they don't understand code. They're struggling because they can't describe what they want with enough precision to give the AI useful direction.

A Shift Worth Making

If you've been putting off building something because you thought you needed to learn to code first — this is worth sitting with.

The access question has mostly been solved. Claude Code, Cursor, and similar tools put building power into non-technical hands in a way that genuinely works. The remaining constraint is clarity: knowing what you're trying to build before you try to build it.

Spend time on the spec. It's not glamorous. It doesn't feel like progress the same way running code does. But 4 hours of good spec writing can save you 3 days of confused building.

I know because I tested it.

Building AI workflows and agents is one of the things we cover in the 4-Day AI Sprint — starting from scratch, no technical background required.

The clinic has one rule: call 30 minutes before you arrive. They need time to prepare the injection. If you don't call, you wait. Maybe 20 minutes, maybe more.

My real assistant used to handle this. She was good. But every once in a while, she'd forget. I'd show up, and they wouldn't be ready. No big deal — 20 minutes in the waiting room. Except I'd also be mentally kicking myself for not having a better system.

So I built one.

What the Agent Actually Does

My Lindy calendar agent checks my schedule every morning. When it finds an event with “allergy shot” in the title, it does the math: if the appointment is today, it sets a trigger for 30 minutes before.

At T-30, an AI phone agent dials the clinic.

But this is where it gets interesting: the clinic has an automated phone tree. Press 1 for the Westlake location. Press 2 for something else. The automated voice reads it out, then waits. A machine calling another machine.

I had to figure out the timing manually. After the call connects, wait exactly 23 seconds — that's how long the recorded greeting takes. Then send a “press 1” DTMF tone. Wait 15 more seconds for the menu to cycle. Then when a human picks up, deliver the message:

“Hey, this is Lindy calling on behalf of Thanh Pham. Thanh is on his way for a scheduled Xolair shot and will arrive in about 30 minutes. Just wanted to give you a heads up. Thank you. Have a great day.”

When the call finishes successfully, Lindy sends me a Telegram message confirming it went through.

I don't think about allergy shots anymore.

Why This Is the Best Automation I've Made

I've built things that automated 20+ hours of executive briefing prep. I've put together AI agents that research 26 people before a dinner event and generate a full dossier. I've set up workflows that handle hundreds of emails a week.

The allergy clinic thing is smaller than all of those.

But it might be the one I'm most satisfied with. And I think I know why.

The big automations are impressive. They save enormous amounts of time and change how entire workflows function. But they're also obvious targets. Anyone who's thought about AI for five minutes would say: “Of course you'd automate executive briefings.”

The allergy clinic automation is not obvious at all. It's a routine task that happens every two months. The kind of thing that falls through the cracks because it's infrequent enough that you never build a real system for it. And when you forget, it's not a catastrophe — just a minor inconvenience.

That's exactly why it's worth automating. Because those minor inconveniences compound. And because the mental overhead of remembering to do something is often worse than the task itself.

My real assistant forgetting the call wasn't the problem. The problem was that I was carrying around this background awareness: has anyone called? Should I double-check? That's the kind of low-grade mental weight that adds up across dozens of similar tasks.

When the agent handles it and sends me a confirmation, that mental weight goes away. I don't think about it. I show up and the shot is ready.

“Life Gets Better One Agent at a Time”

I say this in my AI workshops: life gets better one agent at a time.

Not one giant system. One agent. One task. One workflow.

The people who build the most effective AI setups aren't the ones who start with the biggest vision. They're the ones who start with something small, prove it works, and keep going. After six months of that, they have five or ten little automations running in the background — and collectively, those things make their life noticeably different.

The allergy clinic call was my entry point for AI phone agents. Now I use the same pattern for other calls. I understand how IVR navigation works. I know how to time the pauses. That knowledge came from building something small and slightly silly.

The Right Question to Ask

When people ask where to start with AI automation, they usually want an impressive example. Executive briefings. Department-wide email handling. Something that sounds worth mentioning at a networking event.

Those are fine. But the better question is: what's the recurring thing in your life that you occasionally drop the ball on?

Not the big stuff you track carefully. The medium-small stuff you do every month or two. The phone call you sometimes forget. The follow-up you mean to send but don't. The check-in with a client that happens sporadically enough that there's no system around it.

Those tasks are usually fast to automate. And the return — not just time, but mental quiet — is higher than you'd expect.

Start there.

Want to build agents like this? The 4-Day AI Sprint walks through building your first AI workflows from scratch — no technical background needed.

I used them to build a prototype AI agent specifically for that meeting.

This isn't a story about some polished product I'd been working on for months. This is a story about what you can actually put together in the time between finishing lunch and getting on a call.

The Setup

Seth Gilford and Steve Leathers are commercial real estate brokers at Transwestern. They specialize in medical office properties — physician-owned buildings, healthcare real estate across Florida and Texas markets.

Their prospecting workflow, as Seth described it to me a couple of weeks before, was entirely manual. A virtual assistant in the Philippines compiles leads into a spreadsheet — property address, owner name, company, contact information. Then Seth and Steve each open CoStar on one screen, Google Maps on another, spend 30-45 seconds looking at the aerial view of the property, then pick up the phone.

For every call they make, they've done manual research. For every email they send, they've written something personal — or tried to.

The volume problem: they could only realistically contact a small fraction of the people in their database. There weren't enough hours.

The Prototype

I had a spreadsheet of their Naples prospect list from a previous conversation. With 20 minutes before the call, I opened Lindy, their prospect sheet, and started building.

The agent I put together did three things:

1. Read each row from the spreadsheet
2. Used Perplexity to research the person and their company — looking up their background, their company's profile, any transactions or relevant news
3. Generated a personalized LinkedIn message that referenced what it found

That's the basic structure. Nothing architectural. More like a working sketch.

When the call started, I shared my screen and ran it live.

What Happened in the Meeting

The agent started processing. For the first prospect, it came back with a message that was noticeably more specific than anything you'd get from a generic template. It mentioned the person by name, referenced their company's work, and framed the outreach in a way that connected to their specific situation.

Seth's reaction was positive. But then we got to the third or fourth prospect — a physician who owned a medical office building.

The agent had found something specific. It mentioned a real estate transaction involving a German investment group. It cited an exact dollar figure. It identified that the structure was a sale-leaseback.

Nobody told it the person was a physician-owner. The spreadsheet just had a name, a company, and an address. Nobody programmed it to look for sale-leasebacks or to connect physician ownership to that kind of transaction.

Seth stopped the demo.

“We didn't even specify that the list had physician owners and real estate owners. We just gave you a list.”

Then: “That's pretty incredible.”

Steve: “It kind of found proprietary stuff.”

I was surprised too. Not because I thought it couldn't do it, but because I'd built this in 20 minutes and it was already connecting dots I hadn't drawn for it.

What This Actually Means

I tell this story not to suggest that 20-minute prototypes are always this good — they're usually rougher than this. But to push back on a belief I hear constantly: that custom AI tools take a long time to build, require a developer, or need weeks of planning before they can do anything useful.

The reality is that the tools available now — Lindy, ChatGPT with custom GPTs, Claude, Perplexity — are powerful enough that a working prototype is genuinely a matter of hours or even minutes if you know what you're building.

The harder part is understanding the workflow. That took two weeks and a prior conversation with Seth to understand. The actual build — once I knew what I was building — was 20 minutes.

This is true in most of the consulting work I do. The AI part is usually fast once you know what to automate. The slow part is the conversation that gets you to clarity about what actually needs to happen.

The Question to Ask

If you're sitting across the table from someone who could use an AI workflow — a client, a colleague, your own team — the question isn't “how long will this take to build?”

It's “what exactly needs to happen at each step?”

Once you can answer that clearly, the build tends to be much faster than people expect.

And sometimes it surprises you too.

Want to learn how to build agents like this? The 4-Day AI Sprint covers the fundamentals of workflow design and agent building — starting from scratch, no technical background needed.

I get it. Those markets feel exciting. The language is familiar. The networking events are full of people building the same things.

But the easiest competitive opportunity right now? It's not there.

It's in the industries that haven't changed in 30 years.

The RV Park Observation

A friend of mine is building a business in the RV park real estate space. I asked him what the competitive landscape looked like.

He described something I wasn't expecting.

These are businesses doing $300K or more in annual profit. Some significantly more. They have land, loyal customers, and recurring seasonal revenue. By most traditional measures, they're thriving.

And yet: the websites look like they were built in 2003. The booking systems, if they exist, barely work. Marketing is mostly word of mouth and a listing on a directory nobody under 50 uses. There's no social presence to speak of.

My friend isn't competing against VC-backed platforms with engineering teams. He's competing against owners who still use a whiteboard to track availability.

The opportunity is enormous precisely because the floor is so low.

The Same Pattern, Everywhere

I've watched this play out across industries over the past few years through my AI consulting and workshop work.

I spoke at a hair salon industry conference — three sessions on using AI for marketing, client retention, and content creation. All three were standing room only. People sitting on the floor. Sessions ran over time because nobody wanted to leave.

These weren't people who were slow or resistant to change. They were hungry for it. The problem was that the technology conversation had been happening in places they weren't. Nobody had shown up at their conferences with practical, accessible information about what was actually possible for their businesses specifically.

When I got on stage, I said something that got a real reaction:

“Online scheduling used to be optional. Now if you don't have it, people don't book with you. The same thing is going to happen with AI.”

Five or six years ago, the salons that adopted online booking early looked like they were doing something unnecessary. Now those salons have hundreds of reviews, automated reminders reducing no-shows, and booking systems that run while the owner sleeps. Their competitors who waited are scrambling to catch up.

The same window is open right now with AI tools. And it's open in thousands of industries where the conversation hasn't even started yet.

Why Low-Tech Industries Are the Best Opportunity

When you walk into a competitive tech market, you're fighting for attention against well-funded companies with large teams, established distribution, and existing customers. The barrier to standing out is high.

When you walk into a low-tech industry with high revenue, the situation is almost the reverse.

The businesses already have customers and cash flow — they're not startups looking for product-market fit. What they're missing is the operational and marketing infrastructure that would let them serve those customers better, reach more of them, and retain them longer.

Basic technology creates outsized results here. An automated follow-up system. A working booking page. A way to respond to reviews at scale. Social media content that doesn't require the owner to sit in front of a camera every day.

The bar for “impressive” is just lower. What feels basic to someone with a tech background is genuinely transformative to someone who's been doing everything manually for 20 years.

And because few people are targeting these industries, the first-mover advantage is still wide open.

How to Find the Gap

If you're looking for a business opportunity, a consulting niche, or just a place where your skills have leverage — look for the industries with these three characteristics:

Proven revenue. The business model is validated. People in the industry are making real money. This isn't a market you're trying to create — it exists and it has customers.

Low technology floor. Basic digital tools are missing or broken. The average business in the category has no functioning website, no automated systems, no meaningful digital marketing. Being slightly above average is a significant competitive position.

No dominant tech solution yet. The space hasn't been solved. There's no Shopify equivalent everyone's already on. No industry-specific CRM that owns the category. The void is real.

These industries are everywhere. Specialty contractors. Trades businesses. Niche hospitality. Local services that have been running on relationships for decades. Agriculture. Healthcare subspecialties. They're not glamorous, but they're profitable — and they're waiting for someone to show up with something better than a whiteboard.

The biggest opportunity right now might not be in the tech industry at all.

If you work with businesses in traditional industries and want to bring AI tools to them, the 4-Day AI Sprint covers practical workflows you can implement or teach — no deep technical background required.

And then I said something that surprised him.

“Be careful not to plan every hour.”

He'd just watched me build out a detailed weekly structure with him. Why was I now warning him against planning too much?

Because there's a version of calendar planning that looks productive and actually isn't. And it's more common than people realize.

The Over-Planning Trap

Here's what happens when you schedule every hour of your week.

On Sunday night, it feels great. The week is mapped. Every block has a purpose. You have a plan for everything.

By Wednesday, reality has arrived.

An interesting call comes in from someone you genuinely want to talk to. There's nowhere to put it. A project you're working on takes longer than expected. The cascading effect ripples through the rest of the day. You had plans for Tuesday afternoon and didn't use the time well, but you're still committed to Tuesday evening's block even though you're behind.

When the week is fully planned, there's no slack. And when there's no slack, every unexpected thing — good or bad — becomes a problem.

The worst part isn't the bad surprises. It's the good ones you miss.

The spontaneous conversation that opens a door. The afternoon where your thinking actually gets somewhere. The call you take because something felt right. When the calendar is packed, those moments can't happen.

What the Ideal Week Actually Is

At Asian Efficiency, we've been teaching the Ideal Week framework for years. The goal is a weekly template that reflects your priorities and makes your most important work happen consistently.

But here's what the Ideal Week is not: it's not a schedule for every waking hour.

The framework works by protecting anchors. You identify the things that cannot move — your non-negotiables — and you schedule those first. Exercise. Deep work. The calls that drive your business. The commitments that matter most.

Then you leave the rest open.

Not empty in a lazy way. Open in a deliberate way. White space that allows you to respond to what actually happens rather than fighting against a calendar that was designed before you knew what the week would bring.

I've been using this myself for years. The weeks that feel best aren't the ones where I execute perfectly against a packed schedule. They're the ones where the important things get done and there was room for the stuff I didn't see coming.

The Outcome-Over-Scheduling Mindset

There's a reframe that helps here.

Instead of measuring a good day by how many calendar blocks you completed, measure it by outcomes. If I set out to write a newsletter, record a podcast, and have a meaningful client call — and those three things happen — it was a productive day. It doesn't matter how many other blocks I had scheduled or didn't execute.

This is what hyper-scheduling gets wrong. It mistakes the plan for the goal. The schedule is a tool. The outcomes are the point.

When you design your week around non-negotiable outcomes rather than exhaustive time allocation, you get the structure you need without the rigidity that breaks it.

How to Build In the Right Kind of Margin

If you want to try this, here's a practical approach.

Start by identifying your top three outcomes for the week. Not tasks — outcomes. What would make this a great week if these three things happened?

Then schedule blocks specifically for those three things. Protect them.

Leave everything else as open as you can. That doesn't mean uncommitted — you'll have meetings and obligations. But avoid filling every gap just because it's there.

Do a quick daily check in the morning. What's most important today? What can flex? This keeps you anchored to outcomes without being enslaved to the original plan.

Over time, you'll find that your best weeks have a consistent pattern: the anchors held, and there was space for what you didn't expect.

That's not a loose plan. That's a good one.

Want to build your own Ideal Week? Our weekly review process walks you through exactly how to design a week that works — including how to structure your time so the important things actually happen.

Thanh breaks down why relationships, purpose, and health are the real foundation of happiness, and why optimizing for happiness, not just output, is what actually makes us more productive. He also shares the simple gratitude practice he uses every morning to keep this front of mind. It's a quick, honest reminder that no task on your list is worth sacrificing the people and moments that matter most.

Visit www.asianefficiency.com for more productivity tips and tactics.

For 50% less your first year, go to HomeServe.com/TPS. Void in Florida.

Listen to this episode (MP3)

Links

• HomeServe
• 25X Productivity Coaching
• 30 Lessons for Living: Tried and True Advice from the Wisest Americans
• Productivity Academy

If you enjoyed this episode, follow the podcast on Apple Podcasts, Spotify, Stitcher, Overcast, Pocket Casts or your favorite podcast player. It’s easy, you’ll get new episodes automatically, and it also helps the show. You can also leave a review!

“This task takes me two hours a week. If I automate it, I get two hours back.”

That framing is accurate but incomplete. Because the more interesting thing that happens when you automate something well isn't about time saved on what you were already doing — it's about what you start doing that you couldn't before.

What Actually Happened When I Automated YouTube Summaries

I have an investment research workflow I've been refining for a couple of years. The core of it: I follow a set of YouTube creators who produce content relevant to things I care about — business, investing, AI, productivity. When they post new videos, I want to extract the key insights without spending an hour watching every one.

The manual version of this was tedious. Download or find the transcript. Paste it into ChatGPT with a custom prompt. Format the output. Save it somewhere useful. Repeat for every video.

So I automated it with Lindy. Now when a creator I follow posts a new video, an agent picks it up automatically, grabs the transcript, runs it through a structured summarization prompt, and drops a formatted summary into my Slack. Key ideas. Main insight. A short “story” version of the big concept for easier recall. All formatted the way I like it, waiting for me in the channel I already check.

Here's what I expected to happen: I'd follow the same 5 creators I was already tracking, but more efficiently.

Here's what actually happened: I now follow 20 creators.

Not because I planned to. There was no moment where I decided “now that this is automated, I'll add 15 more channels.” It just happened organically. When each video costs almost nothing to process, the limiting factor isn't time or effort anymore. So I added channels whenever I came across someone interesting. Why wouldn't I?

The per-unit cost hit near zero. So the scope expanded.

The Real Effect of Automation

This pattern shows up everywhere once you know to look for it.

When meeting prep takes 30 minutes, most people only prep for their most important meetings. When it takes 2 minutes with an AI briefing agent, you prep for every meeting. Not because you have more time — because the friction is gone.

When crafting a follow-up email takes 20 minutes of thought and typing, you send fewer of them. When a draft takes 3 minutes to generate and edit, you follow up on every conversation that deserves it.

When generating a competitive research brief takes half a day, you do it quarterly. When it takes 15 minutes, you do it before every important client call.

Automation doesn't just make you faster at what you were already doing. It changes the threshold for what's worth doing in the first place.

The expected outcome: time savings on existing activities.
The actual outcome: scope expansion into activities that were previously impractical.

Why This Changes How You Should Think About AI

Most people evaluate AI workflows by asking: “How much time will this save?”

That's not the wrong question. But it's not the most important one.

The better question is: “What becomes possible if this costs almost nothing?”

Because the answer is usually more interesting. When your YouTube summarization costs you 10 seconds instead of 45 minutes, you don't just save 45 minutes. You open up a window to follow 4x more content sources. When your meeting prep costs 2 minutes instead of 30, you don't just get 28 minutes back — you show up prepared to every conversation, which changes the quality of those conversations.

That's the real ROI: not the time recovered, but the scope of what you can now do that you couldn't before.

How to Apply This

When you're thinking about automating a workflow, try reframing the question.

Instead of: “How long does this take me manually?”
Ask: “If this cost almost nothing, what would I do more of?”

If the answer to the second question is interesting — if there's meaningful value in doing that thing at 4x or 10x the current volume — then the automation is worth pursuing even if the pure time savings aren't dramatic.

The ceiling removal is the real prize.

A client of mine spent weeks tracking 5-6 investment YouTube channels manually. The workflow was good but heavy. After we automated it with a single Lindy agent, he told me: “I realized I could follow 20+ channels with the same effort. Before it felt impossible. Now it feels like a no-brainer.”

That's what happens when the cost per unit approaches zero. The question stops being “can I afford to do this?” and starts being “why wouldn't I?”

Want to build workflows like this? The 4-Day AI Sprint covers how to design agents that expand what's possible — not just automate what you're already doing.

It works. But it's slow.

Then someone showed me a different format, and I haven't gone back.

The Dinner Format

The idea is simple. Instead of 30 individual investor meetings, you host one dinner.

Invite 30 investors to a buffet-style gathering — casual, no pressure. You give a single pitch to the group. And then something interesting happens that you don't get in individual meetings: social dynamics.

When one investor starts asking sharp questions, others lean in. When someone signals interest or even just says something positive, others notice. Nobody wants to be the person who passed on the deal everyone else was excited about.

The group format creates a kind of productive tension. FOMO, basically. And FOMO makes people move faster than they would alone in a one-on-one meeting where they have all the time in the world to stall.

After dinner, individual follow-ups still happen. But they're much shorter. Much less friction. Because everyone's already mentally engaged with the deal. The group conversation did the heavy lifting.

The Part Nobody Talks About

Here's what took me a while to realize: this format isn't actually about fundraising.

It's about getting high-caliber decision-makers into one room and letting the group dynamics accelerate their individual decisions.

And those dynamics don't care whether the people in the room are investors or enterprise buyers or CMOs or CTOs.

I was talking recently with a company that runs these investor dinners professionally. They've facilitated dozens of them for startups across Austin. Good track record. The format works.

But they noticed something: a lot of their startup clients weren't just raising money — they were also trying to get enterprise customers. And the process for landing enterprise customers often looked suspiciously like the process for landing investors. Warm introductions. Lots of one-on-one meetings. Long sales cycles. Lots of follow-up.

So they started a new format: biz dev dinners. Same curated group structure. Same dinner setting. But instead of investors, you're inviting 20-30 of your ideal prospects — CMOs, CTOs, operations executives, whoever the right buyer is for your business.

One dinner. Potential access to 20 relationships. And the same social proof dynamic that makes fundraising dinners work.

Why This Works for Sales

Most sales processes are designed around isolation. You meet a prospect one-on-one. You give your pitch. They think about it alone. They have every reason to stall.

A curated group format changes those dynamics in a few ways.

The access problem is solved at scale. Getting a one-on-one meeting with a CMO at a large company is hard. But a curated dinner with a few of their peers? That's often an easier ask, especially when the event is positioned as a peer knowledge-sharing experience rather than a sales pitch.

Social proof runs in real time. In a group setting, the reaction of the room is visible. If five people are asking engaged questions, the other fifteen see it. If someone says “this is interesting,” everyone hears it. You can't manufacture that dynamic in a Zoom call.

Follow-up conversations start warmer. After a dinner, the individual conversation isn't starting from zero. You've already built rapport in a group context. They've already seen others respond positively. The ask — a follow-up call, a pilot, a proposal — feels like a natural next step rather than a cold pitch.

The format signals quality. Anyone can schedule a Zoom meeting. Not everyone hosts a curated dinner with interesting people. The format itself communicates that you're selective about who you work with.

How to Think About This

The core insight isn't “host a dinner.” It's that most high-stakes sales and biz dev is still done through one-on-one individual meetings when a group format would be faster and more effective.

If you're trying to land enterprise clients and your process is 20 individual discovery calls followed by 20 individual follow-ups… you might want to ask whether a single curated dinner with those same 20 people would accomplish the same thing in a fraction of the time.

The investor dinner format wasn't invented for investors. It was invented for any situation where you need warm, curated access to decision-makers who respect their peers' opinions.

Sales qualifies.

If you want to read more about networking strategy and curated events, check out The Productivity Show — we've covered several episodes on turning in-person relationships into business outcomes.

YouTube video drops from one of his favorite creators. He watches it. Opens NotebookLM, imports the transcript, exports a summary. Pastes that into ChatGPT with a custom prompt. Gets back a structured breakdown tailored to his investment framework.

Five steps. Probably 10-15 minutes total. A genuinely good system.

For the first few weeks, it worked great. He was processing two or three videos a day.

Then things started slipping.

“In the beginning, I was really excited about this process,” he told me. “But then it kind of started becoming monotonous. And especially if I was watching a video in the evening, after 8 PM where I usually don't like getting on my computer anymore, I was less willing to hop on the computer and go through this manual process.”

He was skipping more than he was doing it. The workflow was intact. The habit was dead.

The Real Problem Isn't Discipline

When a habit falls apart like this, most people's instinct is to blame themselves. I need to be more consistent. I need to be more disciplined. I just need to do it.

But that's the wrong diagnosis.

What Ilias had was a task-energy mismatch. The task was fine. The energy level it required wasn't matching the energy available when he actually wanted to do it.

Here's the pattern I see constantly: people design habits for their best-case self. The version of them that's fresh, motivated, and sitting at their desk at 9am. But habits have to work for their worst-case self, too. The version that's drained at 8:45pm and just wants to decompress.

Every step in a workflow is a decision point. And at low energy, every decision point is an exit ramp.

Five steps sounds manageable. But after a long day, five steps can feel like fifty.

The Friction Audit

Before you overhaul a habit or give up on it entirely, do what I call a friction audit. Just count the steps.

Open your laptop. Open app A. Export file. Switch to app B. Paste content. Run the process. Get the output.

Write them all down. Now ask: which of these steps could disappear?

Not “which steps could I do faster.” Which ones could just not exist.

This is the core idea behind what we call the Automation Spectrum at Asian Efficiency. You have life automation (routines, recurring decisions), digital automation (templates, shortcuts, filters), and AI automation (review, synthesis, drafting). The goal is to automate as much of the backstage work as possible so the front stage… the actual thinking, the insight, the decision… can happen without friction.

Ilias's workflow had a lot of backstage steps that didn't need to be manual.

How We Fixed It

We rebuilt his YouTube research system so it runs automatically.

When a new video drops from one of his tracked creators, Lindy picks it up, transcribes it, runs it through a custom summarization prompt tailored to his investment criteria, and posts the result directly to a Slack channel he already checks.

Nothing for Ilias to open. No copy-paste. No switching apps.

The summary just appears in Slack. Where he already is. Whether it's 9am or 9pm.

He went from skipping the workflow most evenings to checking the Slack channel daily. Same information. Different experience.

The habit didn't change. The friction did.

The Thing Most People Miss

Here's what I find interesting about this pattern. Ilias had great intentions. He'd put real thought into building a good system. The prompts were solid. The output was useful.

But the workflow was designed like it was going to run in a laboratory… controlled conditions, fresh energy, no competing demands on attention.

Real life doesn't work that way.

Sustainable habits don't ask much of you. They're designed to work even when you're tired, distracted, or just don't feel like it. The lower the energy required to do the habit, the more consistent the habit becomes.

This isn't a new idea. But most people applying it are thinking about physical habits… putting your gym shoes by the door, keeping the healthy food at eye level in the fridge. The same principle applies to digital workflows.

If your habit requires navigating multiple tools, copying and pasting, or any sequence of manual steps… it's fragile. It will work when you're motivated. It will break when you're not.

Start Here

Pick one habit or workflow you care about that you're inconsistently doing. Write down every step it currently requires.

Now circle the ones that could be automated or eliminated.

You probably don't need to rebuild the whole thing. Usually there's one step causing most of the friction. Fix that one first.

The goal isn't a perfect system. It's a system you'll actually use on a Tuesday night when you're running on empty.

That's the version worth building.

Want to learn how to build workflows like this? Check out the 25X Productivity System — it covers how to design systems that run even when your motivation doesn't.

I wasn't there as a patient. I was there as a workflow observer — the kind of thing I do before proposing any AI or automation changes. Walk in, watch how people actually spend their time, and look for where the friction is. It takes longer than a questionnaire, but you learn things no survey would surface.

One of the things I learned was that Dr. Vo — the clinic's primary physician — was already using AI. Every day. For one very specific thing.

Most people I talk to assume that professional fields like medicine are still a few years away from meaningful AI adoption. The technology isn't trusted. The stakes are too high. The regulators haven't caught up.

Dr. Vo wasn't waiting.

What She Was Using It For

After every patient visit, Dr. Vo had to write a counseling narrative. Lifestyle recommendations, weight guidance, dietary changes, whatever the patient needed to take home and act on. It had to be clear, personalized, and clinically accurate.

It was good work. Genuinely important work. But it was also repetitive — the same structure, customized for each patient. And it took about 20 minutes per visit.

Now she uses Gemini, ChatGPT, or OpenEvidence to generate that summary. She provides the key clinical points, and the AI produces five clear, patient-friendly sentences in moments.

Same information. Same quality of communication. Twenty minutes back.

Per patient.

She wasn't using AI for diagnosis. Not for interpreting labs. Not for anything that required clinical expertise or judgment — those things she kept entirely to herself. She was using it to eliminate the translation layer. The part of the job that was never the point.

The Pattern I Keep Seeing

This is the same thing I see across industries, over and over.

Doctors write. Lawyers write. Consultants write. Engineers write reports. Accountants write memos. The expertise these people have is in their judgment — the thinking, the pattern recognition, the ability to make decisions others can't. The writing is just how they communicate that expertise to someone else.

And AI is very good at writing.

Not at replacing the expert. At handling the container around the expert's thinking.

This is what I mean when I talk about AI eliminating overhead rather than replacing people. Dr. Vo's clinical work is unchanged. Her ability to diagnose, to understand a patient's history, to make the call nobody else in the room is qualified to make — none of that touched. What changed is the 20 minutes of narrative writing that used to follow each visit.

Multiply that across a day of patients, and you're talking about a meaningful chunk of time returned to the actual work.

Why It Spreads This Way

Dr. Vo didn't get a mandate from hospital administration. There was no AI strategy from the top, no consultant brought in to transform the practice. She just noticed a tool existed, tried it on a task she found tedious, and kept using it because it saved her time.

This is how AI adoption actually happens in the real world, at least among the people who are doing it well. Not a top-down rollout. Not a comprehensive transformation project. One specific, boring task that someone decides to try on a Tuesday afternoon.

The principle I call Start Small, Iterate applies here exactly. The smallest reliable version — AI handles the counseling summary draft, doctor reviews and adjusts as needed — is also the safest version. There's no risk of AI making clinical decisions. There's no integration with the EHR required. Just a tool that takes key points and turns them into readable prose.

And because it works, it sticks. And because it sticks, you start looking for the next thing.

Finding Your 20-Minute Task

The question Dr. Vo's story raises is: what's your version of the counseling narrative?

Most professional jobs have them. Tasks that require some expertise to set up but are fundamentally repetitive in execution. Writing summaries of complex information. Translating technical findings into accessible language. Drafting the same type of email for the hundredth time with different specifics.

These are the right places to start — not because AI can't do more, but because starting here is fast, safe, and produces results you can see immediately. It builds trust in the tool before you ask it to do harder things.

The hardest part, usually, is noticing that the task exists. Most people are so used to the 20-minute writing task that they've stopped questioning it. It's just part of the job.

Dr. Vo started questioning it. That's all it took.

If you're trying to find where AI fits in your own workflow, the 4-Day AI Sprint walks through exactly this process — identifying the right starting points and building real automations without a technical background.

Decision fatigue isn't a dramatic mental collapse. It's a subtle quality decay that creeps in as your day accumulates choices—each one nibbling away at your capacity to judge, prioritize, and choose well. By the time you hit the afternoon, you're not lazy. You're depleted.

In this episode, we break down what decision fatigue actually feels like (hint: it's not what the pop-psych headlines say), where it comes from, and the three rules that stop it cold: decide once, decide earlier, decide smaller.

Visit www.asianefficiency.com for more productivity tips and tactics.

Masterclass.com/TPS for at least 15% off any annual membership.

For 50% less your first year, go to HomeServe.com/TPS. Void in Florida.

Get 60% off personal and family plans at Keepersecurity.com/TPS.

Use promo code tps at evenrealities.com to get 10% off Even Ring 1 and/or Even Clip when you add them to your Even G2 order.

Listen to this episode (MP3)

Cheat Sheet

• Top 3 Productivity Resources [2:39]
• The decision-fatigue study you've heard a hundred times — and why it might be wrong [6:23]
• Why AI doesn't reduce your decisions — it concentrates them [10:38]
• Brooks's podcast confession about what he wears every day [18:19]
• The simple rule that stops your team from asking ‘can I do this?' [25:32]
• The one hour a week Thanh blocks off just to think [27:43]
• The 70-document folder that makes Thanh's AI know him better [38:02]
• The 3-step way to make any AI actually know you [42:15]
• The ‘lower the altitude' trick for decisions that feel too big to make [47:37]
• This week's challenge: find the one decision you keep making over and over [53:01]

Links

• Masterclass
• HomeServe
• Keeper
• Even Realities
• 25X Productivity Coaching
• Logitech Spotlight Presentation Remote
• AirPods Max
• Eight Sleep
• Oura Ring
• TEA Framework
• Clear Thinking by Shane Parrish
• The Perfect Bar
• Claude
• Wispr Flow
• Getting Things Done (GTD)

If you enjoyed this episode, follow the podcast on Apple Podcasts, Spotify, Stitcher, Overcast, Pocket Casts or your favorite podcast player. It’s easy, you’ll get new episodes automatically, and it also helps the show. You can also leave a review!

He was being brought in as a fundraiser and sponsor outreach person for a new business. His proposed structure: 1% for the advisory role, another 1% per year if sponsorship goals hit, and 1% per $100k raised. Performance-based. On the surface, reasonable.

But I kept coming back to one question: do these incentives actually align with what the company needs?

Because equity without alignment is just a participation trophy. You can have a great structure on paper and still be pointed in the wrong direction.

That question — whether incentives align — is something I think about a lot. Because I've been doing a version of this myself for the last couple of years, and I've seen how quickly the model breaks down if you get it wrong.

The Model

I close deals as a capital connector. Specifically: I host investor dinners for startups trying to raise.

The format is simple. About 20-30 investors in a room. The founder gives a pitch. There's food, conversation, and a group dynamic that you just can't replicate in one-on-one investor meetings.

What happens in a room that doesn't happen one-on-one: people see each other engaging. Someone asks a sharp question, and it signals to everyone else in the room that this deal is worth taking seriously. Investors who might have said “pass” in a private meeting lean in when they see a peer do the same. It's a social proof mechanism, and it's remarkably effective.

One well-run dinner can do more than ten individual meetings.

I did nine of these deals in 2025. I didn't charge a cash fee for any of them.

Instead, I took a small position on the cap table. Advisory shares. Sometimes a fraction of a percent.

Why Not Just Take Cash

The honest answer is that I don't need it.

Asian Efficiency has been running for over twelve years. It generates consistent cash flow. I don't depend on consulting fees to cover my expenses, which means I can afford to make decisions based on long-term return rather than short-term income.

Cash fees are clean and immediate. You do the work, you get paid, the relationship is settled. There's nothing wrong with that. For a lot of people doing capital connector work, it's the only practical option.

But equity is patient. And patience compounds in a way that cash fees never do.

When you take equity, you're betting on a different time horizon. The return might come in five years. It might not come at all. But when it works, it looks nothing like what you'd make on a fee.

The mental model I use: if I don't believe in this company enough to own a piece of it, I probably shouldn't be spending my network on it. Charging a fee creates a transaction. Taking equity creates alignment.

The Prerequisite

Here's the part that usually gets left out of conversations about this kind of deal structure.

It only works if you have something else paying the bills.

That's not a minor detail. It's the whole thing.

Most people who do capital connector work or advisory roles take cash compensation. Not because they're wrong about the long-term math. But because they have to. If you need the income now, you take the income now. That's not a failure of discipline or imagination — it's rational.

The equity-over-cash model is a luxury available to people with a stable underlying business. Without that foundation, you're always too dependent on the current deal to play the long game. You'll talk yourself into taking the fee every time.

This is why the sequence matters:

Build the cash flow business first.

Then you can afford to get on cap tables instead of invoicing.

The cash flow business isn't just about money. It's about optionality. It gives you the freedom to say no to the short money, to wait, to own pieces of things that might matter in ways you can't predict right now.

I spent years building Asian Efficiency before I was in a position to do this kind of work. The 2025 deal flow wasn't the strategy — it was the result of having a foundation that let me operate differently than most people in my position.

Alignment Is Still the First Question

Back to Ted's deal.

The equity structure was reasonable. But I kept pushing on one specific piece: whether sponsorship performance should be tied to equity or considered part of the core advisory role.

My read was that sponsorship is a natural extension of what a good advisor does. Treating it as a separate equity bucket can create the wrong dynamic — the advisor optimizes for the things that generate their equity rather than the things the company actually needs most.

This is the thing about equity-based deals: the incentives have to be designed carefully. It's not enough to just agree on a number and move on. What behaviors does this equity structure actually reward? Are those the behaviors the company needs?

When it works well, equity aligns everyone's interests over a multi-year horizon. When it's designed carelessly, it creates misalignment you won't notice until it's already a problem.

Getting on the cap table is the long play. But only if you're playing the right game.

If you're thinking about your own deal structures or business strategy, the weekly review is where I do most of this kind of reflective thinking — stepping back from the immediate decisions to look at the longer game.

He can only work about two hours at a time — when he has energy. That's the constraint he lives with.

He runs two multimillion-dollar businesses.

When I asked him what he'd learned from his situation, he said something I've never forgotten. He told me the injury was actually a blessing in disguise. Because he could only work for two hours a day, he couldn't afford to spend any of it on things that didn't matter. Every minute had to count. He became hyper-focused, ruthlessly prioritized, and eliminated anything that wasn't essential.

The constraint didn't limit his success. It amplified it.

I think about John's story often when coaching clients on their daily structure. Because there's a version of his constraint that any of us can create deliberately — and it produces the same clarifying effect.

It's called a firm end-of-day cutoff.

The Client Who Worked Too Late

I was working with a client named Patrick who kept pushing his workday past 7pm, sometimes later. He'd get deep into something in the afternoon and just… keep going. Dinner was late. By the time he wound down, it was nearly midnight. Waking up early wasn't happening.

His instinct was to fix his mornings — build a better morning routine, set multiple alarms, force himself out of bed earlier.

I told him the mornings weren't the problem. The evenings were.

The fix wasn't a better start time. It was a firm stop time: 5:30pm.

What a Hard Cutoff Actually Does

Here's why a firm stop time improves your productivity — before you ever hit the cutoff.

When you know work ends at 5:30 — really ends, not “I'll just finish this one thing” ends — your brain starts treating the afternoon differently. The tasks that actually need to get done today get done. The lower-priority items that you'd normally push through “just because you're already working” get deprioritized to tomorrow.

Parkinson's Law states that work expands to fill the time available for its completion. An open-ended workday gives work room to sprawl. A hard cutoff shrinks the container — and the work adjusts.

I've seen this work for home-based workers especially. Without a natural end time, it's easy to feel “always on.” An office gives you a built-in transition: you leave, and you're done. At home, that switch doesn't exist unless you create it. Setting a clear end time doesn't just feel better — it actually changes how you use the hours before it.

The Downstream Effect

But the real payoff isn't just better afternoons. It's what happens after 5:30.

Stop at 5:30 → dinner at 6 → start winding down by 8:30 → asleep by 9:30 → better sleep → better morning.

Your morning quality is a direct function of your evening. Most people try to fix their mornings without touching their evenings, and then wonder why it doesn't stick. You can't optimize a morning that starts from a place of sleep debt and late-night screen exposure.

This is why one of the frameworks we use at Asian Efficiency is the Shutdown Ritual — a deliberate end-of-day sequence that closes open work loops, reduces stimulation, and prepares your body and mind for recovery. The shutdown isn't just a nice habit. It's part of tomorrow's performance.

How to Actually Make This Work

The challenge with a hard stop time is that it requires a real commitment to not keeping going. A few things that help:

Make the cutoff non-negotiable, not aspirational. “I'll try to stop at 5:30” doesn't work. “Work ends at 5:30” does. The difference isn't a scheduling detail — it's the psychological commitment that changes how you treat the time before it.

Build a transition into the routine. A five-minute end-of-day scan — what got done, what carries to tomorrow, one note about tomorrow's top priority — creates a clear boundary between work mode and off mode. Your brain needs the signal.

Let things carry to tomorrow. The anxiety that keeps people working late is usually about unfinished tasks. The reframe: an item not done by 5:30 isn't an emergency. It carries. Most “urgent” things are not as urgent as they feel at 6pm.

Stack the evening. Having something to look forward to after 5:30 reinforces the cutoff. Dinner plans, a workout, time with people you care about. The cutoff becomes easier to hold when there's something on the other side of it.

The Counterintuitive Part

John Morrow's story is extreme. Most of us don't have a physical constraint forcing us to work two hours a day.

But we can choose to impose a constraint.

And the counterintuitive truth about constraints is that they don't take productivity away — they clarify what productivity actually means. When you have unlimited time, it's easy to fill it with work that feels productive but isn't. When the time is finite, you have to ask a harder question: what actually needs to get done today?

That question makes you better.

Your mornings will improve. But you have to start with your evenings.

If you want a structured approach to the end-of-day transition, the weekly review is the weekly version of the same principle — a deliberate close that protects the next cycle.

“You don't have to design the perfect system from day one. The most important thing is the centralization of data and the cleanup of data. Once you figure that out, everything else is relatively easy.”

Most people who want to implement AI in their business assume the hard work is on the AI side — picking the right model, writing the right prompts, choosing the right platform. And those things matter. But they're not where projects fail.

Projects fail because the data underneath is a mess.

The Real Bottleneck

Picture a team that wants to automate their meeting debriefs. They want AI to listen to a call, update the CRM, draft the follow-up email, and add tasks to their project management tool.

Technically, all of that is buildable in a day. The platforms exist. The integrations are available.

But here's what actually happens when they try to build it: the CRM has fields that don't match. Some contacts have been entered three times under different names. The “meeting notes” field has been used for completely different things by different team members. Some records have never been updated.

Now you automate on top of that. The AI updates the wrong record. Drafts a follow-up to someone who left the company six months ago. Creates duplicate tasks in a project that doesn't exist.

The AI didn't fail. The data failed. The AI just moved faster on bad inputs.

AI Doesn't Fix Messy Data — It Amplifies It

I learned this the hard way in my own work. I was building a multi-step agent workflow, and no matter how well I tuned the prompts, the outputs kept coming out wrong. A mentor finally told me: clean and structure the data before feeding it to AI. Remove redundancies. Strip unnecessary information. Make sure your fields mean what you think they mean.

Once I did that, the same prompts that had been producing garbage started producing exactly what I wanted.

Same AI. Better data. Completely different results.

This is why one of the core principles I use when advising clients is what I call Data Centralization First — the idea that centralized data, consistent field definitions, and a clear data structure create the actual unlock for automation. Not the AI layer. The data layer underneath it.

If the numbers aren't trusted by the people who see them, the automation won't be trusted either.

What “Data First” Actually Looks Like

This doesn't have to be a massive project. Here's the practical version:

Step 1: Find where your data lives. Most teams have it scattered — a CRM, a spreadsheet, notes in someone's inbox, data in a project management tool that nobody updates. List all the sources.

Step 2: Pick one source to clean first. You don't need to fix everything at once. Pick the data source that would unlock the most value if it were reliable. For most businesses, that's the CRM or a customer database.

Step 3: Standardize the fields. Make sure the same thing is always entered in the same place, in the same format. Names, dates, company names — consistency here matters a lot for AI.

Step 4: Remove duplicates and fill gaps. One afternoon of cleanup work here is worth weeks of prompt engineering later.

Step 5: Now build the first automation. Start simple. One voice note that auto-updates the CRM after a meeting is a huge win on its own. That single workflow improves data accuracy across the team. Then you layer the next thing.

The Compounding Effect

Here's what good data hygiene does for your automation over time.

Every workflow you build on top of clean, centralized data works well. Each one compounds. You add a briefing automation — works. You add a follow-up email draft — works. You add a network matching agent that surfaces relationship opportunities — it has the data it needs to find good matches.

The hard part is done once. Everything after that is layering.

Teams that try to design the perfect AI system before sorting out the data almost always get stuck. They spend weeks troubleshooting prompts, when the actual problem is two levels deeper. The teams that start by cleaning and centralizing one data source end up with something that actually works — and scales.

There's an analogy I keep coming back to from a different context. When we were designing the camera systems for Padel Society, the temptation was to focus on the cameras themselves — which models, what specs, how many. But the real decision that determined everything else was where to run the wires. Get the infrastructure right first. Then the surface-level decisions are easy.

Data is the infrastructure. Get it right first.

If you want to see what's possible once the foundation is in place, the 4-Day AI Sprint covers the practical workflows — what to build, in what order, and how to layer them.

Here's the idea: when you set a target — close 10 deals, hit $500K in revenue — you're technically in a state of failure until the moment you hit the number. Even if you're doing everything right, every day before the milestone is a miss by definition. It's an all-or-nothing frame that creates a lot of anxiety and very little useful feedback.

His alternative: track the activity that causes the outcome, not the outcome itself. Build short feedback loops. Find daily wins in the process. That way you're succeeding every time you show up, not just when the deal closes.

I've been doing a version of this for about two and a half years now in my capital connector work, and I think it's the most important thing I've figured out about building deal flow.

The Number I Actually Track

When I started focusing on making deals happen in Austin — connecting startups with investors, facilitating real estate rounds, making introductions across my network — I could have tracked a hundred things.

Deals closed. Revenue from advisory shares. Number of active opportunities. Follow-ups sent.

Instead, I started tracking one thing: how many lunches and dinners did I have this week?

That's it.

My reasoning was pretty simple. I'm hyper-focused on Austin — deliberately so, because relationships deepen in person and geography matters for this kind of work. Deals come through relationships. Relationships deepen at meals. So the meal is the leading indicator, and everything else is downstream of it.

The goal every week wasn't “close two deals.” It was “have enough meals with the right people.”

Why Leading Metrics Are Better

Most people in sales or business development track lagging indicators. Revenue. Deals closed. Clients signed. These are fine metrics to understand — they tell you how you're doing. But they can't tell you what to do next, because they're measuring outcomes of actions you took weeks or months ago.

A leading indicator is something you can influence today that will show up in your results later. It's predictive rather than reflective. And critically, it gives you something actionable: when results feel random, you can ask “did I have enough dinners this week?” instead of “why aren't deals coming?”

The problem with lagging metrics is you don't know they're bad until it's already too late to fix it. By the time revenue dips, the relationship window you needed to open six weeks ago has already closed.

What Happened When I Applied This

Two and a half years of tracking dinners. Nine deals closed in 2025.

I won't pretend it was all linear or that the metric alone caused the outcomes. But I can say that consistency in the activity created consistency in the results. When I had a good stretch of meals, deal flow followed, usually with a lag of a few weeks to a few months. When I went quiet — didn't prioritize the meals — the pipeline thinned.

The other thing I noticed: the group format is meaningfully different from the one-on-one meal, especially for anything involving capital.

I'll invite 20 or 30 investors to a dinner where a founder pitches. The buffet-style, informal format does something that individual meetings never replicate — people see each other engaging. One investor starts asking sharp questions. Another leans in. Someone commits. And suddenly the social proof is doing the work that months of cold outreach couldn't.

The one-on-one conversations that happen after that dinner move fast. People have already decided they're interested. You're just working out the details.

But whether it's 2 people or 30, the underlying question is the same: am I having enough meals?

How to Find Your Version of This

The specific metric — dinners — works for me because of how my business model functions. Your version might be different.

If you're building a consulting practice, your leading metric might be discovery calls. If you're trying to grow a newsletter, it might be the number of original observations you record each week. If you're trying to hire well, it might be the number of deep reference conversations you have per candidate.

The key question: what activity, done consistently, almost always produces the outcome I'm after? Not what outcome do I want — what input causes it?

That's the number to track.

The Practical Test

Here's a fast way to find your leading metric:

Look back at the last 5-10 times you got the outcome you wanted. What activity happened in the weeks before it? Is there a pattern?

If deals always seem to follow a stretch of active relationship-building, you've found your leading indicator. If new clients always come from referrals, the leading indicator is probably the quality of service you deliver to existing clients.

Most people spend a lot of energy optimizing lagging metrics. The faster path is to identify the leading one and do that, consistently, regardless of whether the lagging number feels satisfying yet.

The deal follows the dinner. Track the dinner.

For a structured approach to tracking what matters and designing the week around it, the weekly review is where I do this weekly — asking whether I moved on the things that actually cause results.

Camera systems running across the walls. Infrastructure everywhere. The technology was obviously there, and it took something away from the space.

So when we designed the courts for Padel Society, we made a different decision. Run the wires underground. Keep the surfaces clean. Same cameras, same tech — just hidden.

The experience you want to have on a padel court shouldn't include noticing the infrastructure.

I've been thinking about this a lot while building AI systems. Because the same principle applies.

What Great AI Implementation Actually Looks Like

I'm currently building an AI system for Arena Hall, a new members club opening in Austin. One of the features we're designing is how to make sure the right members meet each other.

The problem sounds simple. In practice, it's complicated.

You have hundreds of members with different interests, goals, professional backgrounds, and social circles. Every event, the right introductions need to happen — but you can't rely on a staff member knowing everything about every member at every moment.

Here's how the system works.

Every member interaction gets captured — meetings, event check-ins, conversations. Profiles are built and updated continuously. Before any event, an AI agent cross-references who's attending against the member database, identifies the introductions worth making, and surfaces them in a briefing for the hospitality team.

Staff reviews the brief. Shows up prepared. At the right moment during the event, they find you and introduce you to exactly the person you should know.

From your perspective as a member? The staff just seems incredibly attentive. Perceptive. Like they really understand the room.

You have no idea that AI compiled that briefing thirty minutes before you arrived.

That's the outcome worth building toward.

The Problem With Visible AI

A lot of AI deployments get this backwards. They make the technology prominent — the chatbot widget, the “AI-generated” label, the automated response that feels obviously automated.

Sometimes that's fine. Sometimes people want to know they're talking to an AI.

But in a premium service environment, visible AI can actually subtract from the experience. The moment a guest thinks “oh, this is automated,” the warmth of the interaction disappears. It stops feeling like a curated experience and starts feeling like a product.

The goal in most service businesses is the opposite: the person should feel seen, recognized, taken care of. If AI can create that feeling — great. But they shouldn't see the machinery.

The Principle Applies Everywhere

Think about the best restaurants you've been to. You don't think about the kitchen logistics, the reservation system, how the staff coordinates on who's going where. You just notice that your water gets refilled before you ask, your order comes out right, the experience is smooth.

The infrastructure is doing a lot of work. You're just not seeing it.

This is the standard to aim for with AI in service businesses.

Another example: a client I worked with who runs a membership club in Austin was spending enormous amounts of time on meeting preparation. Hours of digging through emails, calendar notes, and documents to be ready for each conversation. We built a digital chief of staff that now handles all of that automatically — meeting context, attendee backgrounds, key discussion points. What used to take twenty hours a week now takes fifteen minutes.

Does his counterparty know he has an AI briefing them? No. He just shows up better prepared. That's the experience they get.

What This Means for Building AI Systems

If you're deploying AI in your business — for customer service, for operations, for relationship management — the question worth asking is: will people notice the technology, or will they just experience the result?

Both can be valid. But in premium contexts, the invisible option is almost always better.

A few things that help:

Start with the outcome, not the feature. What should someone feel when they walk away from this experience? Then work backwards to what the AI needs to do.

Centralize the data first. Most AI systems underperform not because the AI is bad but because the underlying data is messy or scattered. Before building workflows, get your data into one clean place. Once the data is right, the automation is the easy part.

Audit what's visible. Every AI touchpoint is either adding to or subtracting from the experience. The ones that feel clunky or robotic are worth redesigning, not just improving.

The padel court doesn't show its wires. The members club doesn't explain its AI. The meeting prep system doesn't announce itself.

They just create the experience you wanted them to create.

If you're thinking about where to start with AI in your business, the 4-Day AI Sprint walks through the practical implementation — from first workflows to more sophisticated systems.

Not because balance is a bad goal. But because the framing assumes work and life are in opposition — like you're managing a zero-sum trade. Work hard enough, and life suffers. Protect life too aggressively, and work slides.

But after years of coaching and being coached, I've come to think that's the wrong model entirely. The question isn't how to balance work against life. It's whether what you're doing every day reflects what you actually care about.

When it does, something interesting happens. You don't need to manage your energy as carefully. The motivation is just there.

The Coaching Session That Made This Click

I was working with a client named Patrick Davidson on his weekly schedule. Patrick is an entrepreneur going through a significant life transition — new constraints, new priorities, trying to figure out what a great week actually looks like for him right now.

We could have just blocked out work time and called it done. But the first thing we did was map his values. Not his goals. His values.

He named things like serenity, connection, contribution, physical wellness, adventure, growth.

Then we asked a different question: where do those things actually show up in your week?

The answer was: they don't. Not intentionally. They happened accidentally when there was time left over — which, in a busy week, meant they often didn't happen at all.

So we built them in.

Serenity time became 8-9pm on Monday, Tuesday, Thursday, and Sunday — protected for meditation, journaling, or just quiet. Adventure Wednesdays became a deliberate physical or social activity scheduled after his morning deep work. Saturday stayed reserved for whatever social experiences he actually looked forward to.

When we were done, I said something I've believed for a long time: the more your daily schedule reflects your actual values, the happier you become. And happy people are productive people.

Why This Is Backwards From Most Productivity Advice

Most productivity frameworks ask: how do I get more done?

They optimize for output — faster task completion, fewer distractions, tighter time-blocking, better prioritization systems.

And all of that can help at the margins. But it addresses the symptom, not the cause.

The question underneath is: why aren't I energized to begin with?

When you're doing work that conflicts with your values, or when your schedule has no room for what matters to you, the resistance that shows up every morning isn't laziness. It's misalignment. Your brain is quietly telling you that the day ahead doesn't feel worth showing up for.

The productivity problem is actually an alignment problem.

And alignment problems have a different solution than time-management tricks.

The Ideal Week as a Values Test

One tool I've used for years is what we call the Ideal Week — a weekly architecture that isn't about fitting more in, but about making sure the right things are protected.

The exercise starts with a simple question: if you designed a week that reflected your actual priorities, what would it look like?

Not what you think a “productive week” should look like. What would feel genuinely good?

Most people, when they do this honestly, discover a significant gap between their actual week and the answer. Exercise that keeps getting bumped. Creative time that never gets protected. Time with people they care about that keeps getting pushed.

The Ideal Week isn't a rigid schedule you follow perfectly. It's a design intention — a reference point for evaluating whether your current calendar actually reflects your priorities. When you look at next week and it looks nothing like your Ideal Week, that's the signal that something needs to shift.

The Real Mechanism

Here's why values alignment drives productivity rather than the other way around:

Energy. When you're spending time on things that matter to you, the energy is there. You don't have to manufacture motivation. You might even find that you have more left at the end of the day.

Decision-making. When your values are clear and your schedule reflects them, a lot of decisions get easier. You're not weighing every opportunity on the fly. You have a filter.

Sustainability. Efficiency-first approaches often work for a while and then collapse. Values-aligned systems tend to last because they're built around what you actually want — not around hitting some abstract output target.

Start With the Right Question

If your productivity isn't where you want it, before you try another app or system or time-blocking method, ask this:

Does my calendar reflect what I actually care about?

Not what you think you should care about. Not what your schedule says your priorities are. What do you actually value — and where does it show up?

If the answer is “not much,” you've found the problem.

The fix isn't a better task manager. It's a redesign.

If you want a structured way to build this, the weekly review is a good starting point — it's the practice that keeps your schedule from drifting away from your intentions week after week.

Someone shows a creator's AI clone — a digital avatar that looks and sounds like the real person, publishing content, answering questions, building an audience. And the first response is always some version of that question.

I understand the instinct. It does feel strange, the first time you see it.

But I've been thinking about where I've felt that exact strangeness before. And the answer is: getting in a stranger's car.

The Uber Parallel

When Uber first launched, the idea was genuinely odd. You were supposed to get in the car of a stranger you'd never met, who wasn't a licensed taxi driver, using an app on your phone.

People said it was dangerous. Unsafe. Weird. Not normal.

Now it's the most unremarkable thing you can do on a Thursday afternoon. You don't think twice. The concern that seemed so real in 2010 looks almost quaint today.

This isn't unique to Uber. It's how almost every new social technology works. The strangeness fades when the format proves itself. Quality becomes the standard, not novelty.

What Disney Figured Out First

Here's an angle that doesn't come up enough.

Children — and adults — have been learning real things from fictional characters for nearly a century. Lessons about courage, loss, friendship, growing up. Millions of people have been genuinely moved by animated characters who don't exist.

Nobody watches Up and says “that didn't count because the characters weren't real.” The emotional output was real. The learning was real. The format — animated, fictional — became irrelevant once the quality was there.

I had a conversation recently with Jeff Brewer, who works closely with high-performing content creators. He described this point using almost the exact same analogy: Disney taught us to accept non-real characters as teachers. Uber taught us to accept strangers as drivers. The same shift is coming for AI clones.

What's Actually Happening Right Now

Jeff was describing a creator named Onyx Singal. Onyx went from spending $75,000 a month on his content team to under $10,000. His AI clone — built on a stack of tools including ChatGPT, Nano Banana for visuals, ElevenLabs for trained audio, and HeyGen for video — now gets tens of millions of views per month.

And here's the part worth sitting with: sometimes the clone outperforms his personal content.

The cultural reaction is predictable. “It feels fake.” “I want the real person.” Some audiences actively push back.

But Onyx's metrics don't lie. The output is working. People are watching, following, engaging — at scale.

The Real Threshold Is Quality

Here's what I think people miss when they focus on authenticity.

The question of “is it really him?” assumes that realness is what audiences are responding to. But if that were true, Onyx's numbers wouldn't look like they do. People aren't watching because they believe it's the real Onyx. They're watching because the content is worth watching.

The threshold for acceptance is quality, not authenticity.

This matters for how you think about AI clones as a business tool. The resistance you're seeing right now isn't permanent — it's the early phase of a cultural shift. The same phase Uber went through. The same phase streaming went through when people said they'd never give up physical media.

What we're in is the “getting in a stranger's car” moment for digital avatars. The strangeness is real. And it will fade.

What This Means If You're Building Content

If you're a creator, consultant, or expert who publishes content as part of your business, this shift matters.

The early movers on AI clones — people who got in when the format was still strange — are building scale that would have required a full content team two years ago. Onyx cut his content spend by 87% while growing his reach. That's not a marginal improvement. That's a business model change.

The caveat: quality is the threshold. A low-quality clone doesn't benefit from the cultural shift — it just confirms people's skepticism. The creators who are making this work have invested in output quality to a degree that makes the “is it real?” question irrelevant.

The Adoption Curve Is Predictable

One framework I keep coming back to is AI Fluency Levels — the idea that most people are still at level one with AI, doing basic text prompting, and haven't yet seen what level three (agents and automation) looks like in action.

The same curve applies to AI clones. Most audiences have barely encountered a well-made one. The skepticism is genuine, but it's also based on early, lower-quality examples. As the quality floor rises — which it's doing fast — the “I want the real person” argument gets harder to maintain.

The Uber moment is when the format becomes the expectation. When not having a digital presence feels like the unusual choice.

We're not there yet. But we're closer than the skepticism suggests.

If you want to explore what AI can actually do for your content and business, the 4-Day AI Sprint is a good place to start — four days of practical implementation, no theory.

I could have built an online course. I had the audience for it. The economics would have been better on paper — no venue, no travel, unlimited seats. But I knew the people I wanted to reach — founders, operators, investors — weren't going to commit to a weekly online module. They're too busy, and honestly, they've already bought too many courses they didn't finish.

So I chose a full day in a room.

That first workshop filled up. People referred others. I've been running them every six weeks since, and they've done something unexpected: they've made me better. Staying current enough to teach a live room forces a level of preparation that producing asynch content doesn't.

But there's a bigger idea here — one I've been thinking about more as AI gets genuinely capable at creating content.

The Scarcity Shift

Here's the question worth sitting with: as AI gets better at creating content, recording courses, and handling everything asynch, what becomes scarcer?

The human being in the room.

For years, the calculus was that live presence was expensive and hard to scale. A recorded course could reach thousands; a live workshop could only reach fifty. AI flips part of that equation — it handles the scalable, asynch content layer. What's left is the live experience.

And what's scarce tends to become more valuable.

I had a conversation recently with someone who works with high-performing content creators. One of them — Onyx Singal — has an AI clone that runs all of his social content, creates his ads, and is responsible for getting people to his live events. The clone does the marketing. The human shows up for the in-person event.

His summary of the situation: the clone got everyone in the room. The human delivered the experience.

This is the model. AI handles the funnel; people pay premium for access to the real person.

What Live Does That Digital Can't

I want to be specific about what I mean, because “in person is different” can feel vague.

When you're in the same physical space as someone, several things happen that don't happen on a Zoom call or in a course:

Questions change quality. People ask things in a live room that they won't type into a chat box. Partly because they can see the room's reaction. Partly because something about the physical presence makes the question feel more real.

Ideas spark differently. When two people are literally looking at the same screen, working through the same problem, the conversation takes unexpected turns. I've seen this in workshops — someone makes an offhand observation, someone else builds on it, and suddenly the whole room is on to something none of them had thought of before. That doesn't happen in asynch.

Trust builds faster. This one is hard to quantify but easy to feel. A few hours in a room with someone does more for a relationship than months of email exchanges. The energy, the body language, the shared experience — these compound in ways that don't have a digital equivalent.

The Practical Implication

If you're building a business that involves your expertise — consulting, coaching, education, any kind of knowledge work — the live experience is the layer AI can't replicate.

That's not an argument against using AI. It's an argument for being strategic about what you protect.

Use AI to handle the content that markets you. Let it create the posts, run the sequences, produce the recordings. Let it fill the room.

But save the room for yourself.

The businesses that will do well over the next decade aren't the ones that resist AI, and they're not the ones that just automate everything either. They're the ones that use AI to scale the output layer and then show up live for the experiences that actually matter.

The premium used to be the content. The premium is becoming the presence.

If you want to see this in action, the 4-Day AI Sprint covers how to build the AI workflows that free up your time — so you can show up fully for the live experiences that create real value.

Brian Tracy turned it into productivity advice. The frog is your biggest, most important, most avoided task. Eat it first. Get it done before anything else gets in the way.

It's good advice. For most situations.

But there's one specific scenario where eating the frog will derail your entire day — and it's more common than people realize.

When You're Behind

Here's the situation I'm talking about.

You have a backlog. Things that are overdue. Tasks that have been sitting on your list longer than they should. The pile has grown and now you need a session to work through it.

Some of those tasks are genuinely easy. A quick reply. A bill that just needs a credit card number. A form to fill out. Tasks that, with normal focus, you'd finish in five minutes each.

Others are harder. They require phone calls. Being put on hold. Navigating a bureaucratic process. Coordinating with someone whose schedule you don't control.

Eat the frog says: start with the hard one.

But here's what actually happens when you do.

You dial the bank. You wait 20 minutes on hold. You get transferred. You wait again. By the time the call is over, 45 minutes have passed and you've accomplished one thing. You're tired. And now you look at the rest of your list.

The easy tasks that should take 10 minutes feel heavier than they did before. The momentum you needed to work through the backlog is gone. A lot of people just stop there and walk away.

The Momentum Principle

When you're operating from a full tank — fresh energy, no backlog, a clear day ahead — eat the frog works well. You attack the hardest thing while you're at your sharpest. Everything easier comes after.

But when you're behind and need to rebuild, the dynamic is different. You're not operating from a full tank. You need to build momentum first, and momentum comes from finishing things.

I had a coaching client working through exactly this situation — a pile of overdue bills, some that were one-click payments and others that required phone calls. I told him: start with the click-to-pay ones. Clear four or five of those. Get moving.

After a few quick completions, the state changes. You're not staring at a pile anymore — you've already made a dent. The hard task at the end, the phone call you've been dreading, feels different when you're already rolling.

Matching Task to Actual Energy

At Asian Efficiency, we talk about High, Medium, Low task matching — the idea that different tasks require different amounts of cognitive energy, and you should match task type to your actual available energy, not some idealized version of it.

High-energy tasks: complex thinking, writing, strategic decisions. These need full focus.
Low-energy tasks: routine admin, simple payments, confirmations. These can run on fumes.

When you're behind and feeling overwhelmed, your available energy is often lower than usual. The overwhelm itself costs something. In that state, leading with a low-energy task and building up is more practical than leading with a high-energy task that might not get finished cleanly.

The goal isn't to avoid hard things. It's to sequence them correctly for the conditions you're actually in.

How to Apply This

Next time you have a backlog session, sort your tasks before you start.

Look at everything you need to get through and ask: what's the easiest thing here? What can I finish in under 10 minutes without much friction? Start there.

Do two or three of those first. Get some completions behind you.

Then work your way up. By the time you get to the hard thing, you'll have momentum — and that momentum is a real input into how well the hard thing goes.

Eat the frog when you have a full tank. Build momentum first when you don't.

For a full system to manage your tasks based on energy and priority, the Productivity Academy covers the complete High/Medium/Low matching framework along with weekly planning and daily execution workflows.

I had a Plaud recording pin on my chest the whole time. Small device, about the size of a USB stick. Everyone in the room could see it. Everyone knew it was recording.

And because I knew the transcript was running, I never once worried about notes.

I just asked questions. What's your workflow? Walk me through a typical day. What slows you down?

I was fully present in every single conversation.

The Thing Most People Miss

When most people hear “AI transcription tools,” they think: backup. Something to search later if you missed a detail. A safety net for forgetful people.

That's the wrong mental model.

The real payoff isn't what happens after the meeting. It's what happens in the meeting when you trust the recording to remember.

Here's what I've noticed: when you're taking notes, you're doing two things at once. You're listening and you're capturing. Your brain splits its attention. You hear what someone says and immediately start deciding: is that worth writing down? And in that moment of deciding, you half-miss the next sentence.

This happens in almost every meeting for almost everyone. It's just background noise — you barely notice it.

But take away the note-taking, and something shifts. Your whole attention goes into the room. You catch the hesitation after an answer. The thing someone almost said but didn't. The follow-up question that opens everything up.

The transcript isn't a substitute for presence. It's what makes presence possible.

What a Full-Capture Day Looks Like

I've been using the Transcript First approach for a while — the idea that conversations are raw material, and transcripts are the artifact that makes them reusable. But the health clinic day took it further.

Eight hours. Continuous recording. No note-taking, no laptop, no pen. Just conversations.

I asked one doctor how she handled patient counseling documentation. She mentioned offhand that she'd started using Gemini to generate the summaries instead of writing them herself — 20 minutes of writing compressed into a few seconds of prompting. That detail would have been easy to miss if I'd been looking down at a notepad.

Another staff member described a Friday afternoon meeting where they reviewed every patient scheduled for the following week. An obvious candidate for an AI pre-brief workflow. He mentioned it almost as an aside. I caught it because I wasn't distracted.

By end of day I had eight hours of raw material. I fed it all into Claude that evening. By end of the week I had a full AI implementation proposal ready to send.

The document was the output. But the quality of the document depended entirely on what I captured — and what I captured depended on being fully in those conversations.

The Counterintuitive Principle

There's a concept at the core of this: capture everything. Not because you'll use all of it — you won't — but because you can't predict in advance what will matter. The offhand comment, the half-explained frustration, the thing someone says when they think the real conversation is over.

None of that makes it into your notes. All of it makes it into a transcript.

And the other half of the principle: because the recording is capturing, you don't have to. Your attention is free.

This is why I use wearable recorders like the Plaud pin for on-site work, and Granola or similar tools for regular video calls. I'm not optimizing for better notes. I'm optimizing for better conversations — and letting the AI handle the memory layer afterward.

How to Start

You don't need a full on-site consulting day to try this.

Next time you have a 1-on-1 or a client call, turn on a recorder — your phone, a Granola bot, whatever you have — and commit to not taking notes. Just listen. Follow the thread of the conversation wherever it goes.

Afterward, look at the transcript. You'll almost certainly find things you would have missed if you'd been writing.

That's the real reason to record meetings. Not backup. Not search. Presence.

If you want to build out a full AI-powered meeting intelligence system, the 4-Day AI Sprint covers how to set up transcription, processing, and follow-up workflows so every conversation turns into something reusable.

Every day felt urgent. His to-do list was always red. He was reactive from the moment he woke up — putting out fires, playing catch-up on emails, bouncing between crises. After a couple of months working together, we managed to shift things. He started planning his weeks in advance. He had visibility into what was actually coming. That margin let him do something he hadn't been able to do before: prevent problems instead of just responding to them.

But getting there required one thing first that most productivity advice skips entirely.

He had to stop trying to build and just get to neutral.

The Debt Analogy

There's an idea most people understand intuitively when it comes to money: you pay off debt before you invest.

You don't start putting money in index funds while carrying high-interest credit card debt. The math doesn't work — the returns on your investments can't outpace the drag of the debt. The right move is to clear the liability first, then build on solid ground.

The same logic applies to how you manage your time and attention.

When your life is in genuine chaos — overdue things, a backlog you can't see the bottom of, open loops running in the background every hour — adding new systems on top of that doesn't help. The systems have to fight against the chaos to work. They rarely win.

I've seen this pattern repeat in coaching: someone wants to redesign their week, build a new morning routine, start a weekly review. And all of those are good ideas. But they're building on a cracked foundation. The habits don't stick not because they're bad habits, but because the environment is hostile to them.

Reactive → Neutral → Proactive

At Asian Efficiency we talk about the spectrum from reactive to proactive.

Reactive work is everything you're doing because something external demanded it. The email that just came in. The fire that just started. The meeting you forgot to prepare for. Reactive work keeps the lights on but it doesn't compound — you finish it and immediately there's more.

Proactive work is what moves things forward. It's the planning, the strategic thinking, the things you do because you decided they mattered, not because they landed in your inbox.

Most people want to get to proactive. They read about deep work blocks and Ideal Week designs and weekly reviews and think: I want that. They try to install those habits. And then the chaos absorbs them.

The missing step is neutral.

Neutral is where the chaos is resolved but you haven't yet built anything new. Bills are current. Inbox is processed. Brain dump is done. You know what you actually owe the world and when. Nothing is pulling at you from the past.

From neutral, you can actually build. The things you add will stick because there's nothing fighting them.

What Getting to Neutral Actually Looks Like

It doesn't have to be dramatic. A few hours, usually.

The most common elements:

Brain dump. Get everything out of your head. Every open loop, every thing you've been meaning to do, every vague commitment you made to someone. Write it all down somewhere — doesn't matter where, just get it external. When things live only in your memory, your brain keeps running them in the background. Getting them out frees up processing power.

Clear the most pressing backlog. Not everything. Just the things that are actively causing stress. Overdue bills. The email thread you've been avoiding. The task you said you'd do two weeks ago. Pick the three things that, if you handled them today, would make you feel genuinely lighter.

Do a brief review of what's actually ahead. Look at your calendar. Know what's coming in the next week. A lot of reactive behavior comes from surprises — things you didn't know were coming until they arrived. A ten-minute scan prevents a lot of that.

That's it. You're not building anything. You're clearing the ground so building is possible.

Why This Works

The insight that changed how I coach this was simple: you can't build on a messy foundation.

Every new habit, system, or routine is a bet that the environment will support it. When life is chaotic, the environment doesn't support much. When you've gotten to neutral — cleared the most pressing backlog, resolved the things that were pulling on you — the environment is actually ready.

This is also why “just start somewhere” advice often fails. You start somewhere. And then life absorbs it. The problem wasn't motivation or the habit itself. The problem was starting before the ground was clear.

If you want a structured way to move from reactive to proactive, the weekly review is the practice that makes this shift sustainable over time. It's the system that turns getting-to-neutral from a one-time emergency into a weekly reset.

I came back exhausted. And it made me realize: my mornings were only good because my evenings were boring.

The Math Most People Skip

Let me walk through this with the way I explain it to coaching clients.

Say you want to wake up at 5:30. And let's say you know, from experience, that you feel best on about 8 hours of sleep. That means you need to be asleep by 9:30pm.

Now, most people don't fall asleep the moment they decide to. There's a wind-down period. You need to turn off screens, let your mind settle, maybe read for a bit. For a lot of people that's 30-60 minutes. Let's say it's an hour for you.

That means you need to start winding down by 8:30.

Which means your workday has to end by… 8:30. Or earlier, if you want to eat a real dinner in there.

I call this the reverse alarm clock. Instead of asking “how do I wake up earlier?” ask “what time do I need to stop working?”

Wake time → sleep time → wind-down start → work cutoff.

That last number is your actual target. And most people have never calculated it.

Why This Diagnosis Usually Surprises People

When I've done this exercise with clients, the math almost always reveals the same thing: they're ending their workday 2-3 hours later than they should be if they actually want the morning they're picturing.

Not because they're lazy. Because nobody reverse engineered it.

One client I worked with recently was trying to wake at 5:15. He needed 8 hours. He also needed about an hour to wind down and eat dinner. The math said he needed to stop working by around 8pm. He was wrapping up at 7, sometimes 7:30.

Forty-five minutes off. That's it. But those 45 minutes pushed everything back — dinner later, screens later, sleep later, wake-up later.

He'd been trying to solve a morning problem that was caused by an evening problem.

The Constraint That Creates Urgency

Here's something that surprised us both when he started actually honoring the cutoff.

Once he committed to stopping at 5:30 (which was his target, more aggressive than the minimum), his afternoons got sharper. Not because he was more motivated. Because he had a real deadline.

When the end of the day is open-ended, work expands. When you have a hard stop, you start making real decisions about what's worth doing before then.

This is one of the core ideas behind what we call the Ideal Week at Asian Efficiency — you schedule your important work into real blocks and protect them. But the protection has to go in both directions. Not just protecting the morning from meetings, but protecting the evening from work so the morning is even possible.

The Shutdown Ritual

What actually fills the wind-down period matters too. We call this the Shutdown Ritual.

The goal is simple: close open loops before you stop working, then step away from screens and let your nervous system settle. This isn't about candles and journaling if that's not your thing. It's about not going from “email refresh” directly to “trying to fall asleep” because that transition takes longer than most people budget for.

A basic shutdown ritual might be:

1. Spend 5 minutes processing any open tabs or notes into tomorrow's task list
2. Close the laptop
3. Do something with your hands or body — walk, stretch, cook dinner
4. No screens for the hour before bed

That's it. But it has to happen on time for the math to work.

Try This Tonight

Before you go to sleep, work backward.

What time do you want to wake up tomorrow? Subtract your ideal hours of sleep. That's your sleep time. Subtract your wind-down period. That's when work has to stop.

Write that number down. Set an alarm for it if you need to.

Most people who say they're bad at mornings have never actually run this calculation. The morning they want is possible — it just requires protecting the evening that makes it happen.

If you want help designing a week where your time actually matches your priorities, the Productivity Academy is where we work through this kind of design in depth, including Ideal Week templates and the full Shutdown Ritual framework.

Visit www.asianefficiency.com for more productivity tips and tactics.

Get 20% off your first order: dripdrop.com and use promo code tps.

Listen to this episode (MP3)

Links

• DripDrop
• 25X Productivity Coaching

If you enjoyed this episode, follow the podcast on Apple Podcasts, Spotify, Stitcher, Overcast, Pocket Casts or your favorite podcast player. It’s easy, you’ll get new episodes automatically, and it also helps the show. You can also leave a review!

The problem he described is universal. He had project documents. He had meeting notes. He had email threads. And none of them reflected what was actually happening. The real status of any given initiative existed somewhere between three Slack conversations, a Granola transcript, and two emails he hadn't replied to yet.

His team could only know the true state of things by asking him. And asking him meant interrupting him.

The system we designed to fix this is something I call the Master Memo.

What a Master Memo Is

A Master Memo is a living project document maintained automatically by an AI agent.

The agent reads incoming emails, meeting transcripts, and voice notes related to a specific project. After each new input, it updates the document — surfacing key developments, things team members have committed to doing, items that are currently stuck, and follow-ups that were promised but never closed.

The raw quote I wrote when we were designing it: “The purpose of the memo: information sharing, prompting action, tasks stuck, things we said we're going to do but haven't done. Following up on the previous week — you said you were going to do this, is this done?”

Nobody has to manually maintain it. The agent does it. The document just stays current.

Why Most Project Docs Don't Work

The pattern I see across teams of every size: a project document gets created with good intentions. It has the initial scope, the stakeholders, the timeline. And then it becomes a fossil.

The meetings keep happening. The decisions keep getting made. But none of it makes it back into the document because updating the document is extra work — it's overhead that competes with everything else on the agenda. So everyone stops trusting it. And the real source of truth becomes “ask someone who was in the room.”

The problem with that isn't just inefficiency. It's that the institutional memory lives in people instead of systems. When someone is out sick, or leaves, or just can't be reached, a critical piece of project context goes with them.

How the System Works

The implementation isn't complicated, but it does require setting it up correctly.

Step 1: Define the memo structure. What does the document need to track? For most project memos, this is: current status, key decisions made, outstanding commitments (with owner), things stuck, and open questions. This structure becomes the template the agent writes to.

Step 2: Connect the agent to your inputs. The agent needs to read emails related to the project (filtered by project name, participants, or a keyword), meeting transcripts, and any voice notes or async updates. In practice, this usually means connecting to Gmail (filtered), a Granola or Otter integration, and possibly a Slack channel.

Step 3: Set the update cadence. The agent runs on a schedule — daily or weekly depending on project velocity. It reads new inputs since the last run, decides what's worth adding or updating, and writes directly to the shared document.

The version I showed one of my AI consulting clients earlier this year gave him a broader context file system — folders covering identity, operating style, and current projects, all built by feeding Claude a year of meeting transcripts and having it extract patterns. The setup took about an hour. Now it powers dozens of agents that reference the same information.

His takeaway: the leverage doesn't come from having the files. It comes from agents using them.

What This Changes

The most obvious change is time. A team that was spending 30-60 minutes per week on manual status updates gets that time back. But that's not really the point.

The deeper change is trust. When people know there's a document that actually reflects reality — not what someone typed in three weeks ago — they reference it. They rely on it. The coordination overhead that comes from “does anyone know the latest on X?” drops significantly.

And the document itself becomes a useful object for retrospectives, onboarding new team members, or quickly briefing stakeholders who weren't in the room.

Most meetings generate more follow-up work than they eliminate. A memo that writes itself changes that ratio.

To explore how to build AI systems like this for your own work, the 4-Day AI Sprint walks through how to design and deploy AI workflows that handle your most time-consuming recurring tasks.

I told him there's a better way.

Not because individual meetings don't work. They do, eventually. But they're what I call hand-to-hand combat. Every meeting takes roughly the same amount of time. There's no leverage. No momentum that carries from one conversation to the next. And — critically — there's no social proof.

When you pitch one person at a time, that person is evaluating your deal in a vacuum. There's no signal from other people they respect. No visible interest from peers who've already heard the story. Just you, them, and a cold decision.

The investor dinner model fixes this.

How It Works

The model has three stages:

Stage 1: Pre-qualify with the deck. Before you schedule anything, circulate your deck to your relevant network. The goal here isn't to close — it's to filter. You're looking for who's actually interested. The people who respond positively, who ask follow-up questions, who say they want to hear more — those are your dinner guests.

Stage 2: Host a curated dinner. Invite the interested parties to a dinner. The format is simple: the founder does a 10-15 minute pitch, opens for Q&A, then everyone mingles. Buffet-style works well. The room should feel like a gathering of people who all have genuine interest in the same opportunity — because that's exactly what it is.

Stage 3: Follow up individually. After the dinner, individual conversations happen. But they move fast. Everyone's already warm. They've heard the pitch, heard the questions, seen what other people in the room were thinking.

Why This Works: FOMO

The thing that makes this model different from a series of individual meetings isn't the efficiency — it's the social dynamic.

When a prospective investor sees other people they respect leaning in, asking sharp questions, expressing real interest in an opportunity… it changes the calculus. There's a signal that their peers see something worth paying attention to. That signal doesn't exist in a one-on-one meeting.

I've seen this work firsthand. I hosted a fundraising dinner with around 30 investors — buffet-style, easy to work the room. What made it effective wasn't the pitch itself. It was watching the engagement. When people see others getting genuinely excited about an opportunity, they don't want to miss something their network already knew about.

The group format creates energy that you simply cannot replicate across individual conversations. And that energy does a lot of the closing work before you ever have the final one-on-one.

Who This Is For

The investor dinner model works best for:

• Founders raising a round who have at least a warm network to circulate to
• Anyone raising capital from angel investors or early-stage VCs (the format is less suited to large institutional raises where process is more formal)
• Situations where you need to build momentum quickly — the dinner creates a sense that something is happening, which accelerates decision-making

One important note: the quality of who you invite matters more than the quantity. A dinner of 15 highly relevant, genuinely interested investors is far more valuable than 50 people who showed up out of vague curiosity. The pre-qualification step — circulating the deck first — is what ensures the room is curated.

The Format Itself Is Leverage

Most fundraising advice focuses on the pitch — how to tell the story, how to answer hard questions, how to handle objections. That's all necessary.

But format is leverage too. A well-designed room creates conditions that help you close. It does some of the work for you.

If you're grinding through individual meetings and wondering why it's taking so long, consider whether the format is the problem. The hard way isn't always the only way.

For more on how to approach capital raising and building strategic relationships, Thanh works with founders and executives on high-leverage networking and business development through Asian Efficiency's consulting programs.

He came to me because he'd been struggling to maintain consistency with the things he knew mattered — exercise, connection, time to think. The weeks kept slipping by and those things kept getting skipped.

When I asked him to describe a typical week, the pattern was immediately clear. He was treating his priorities like items he'd get to after the real stuff was handled. The real stuff always expanded to fill the available time. His priorities always ended up at the bottom of a list that never got finished.

This is extremely common. And the fix is one of the oldest ideas in time management — so old that most people have heard it and dismissed it as too simple to actually work.

The Jar Analogy You've Probably Heard

If you've ever been to a productivity seminar or read a book on time management, you've probably encountered the rocks, pebbles, and sand analogy.

A jar represents your week. Big rocks are your highest priorities — the things that matter most. Pebbles are mid-level commitments. Sand is everything else: emails, requests, small tasks, reactive work.

If you pour the sand in first, then the pebbles, there's no room for the rocks. But if you put the rocks in first, the pebbles settle around them, and the sand fills in whatever remains.

The point isn't subtle. But most people don't actually do it. They know the analogy and still treat their most important commitments like things they'll get to when everything else is handled. Then everything else is never handled. And the rocks get skipped again.

Applying It In Practice

With my client, we did one thing first: identified three non-negotiables. The things that, if he did them consistently every week, would make the biggest difference to how he felt and performed.

For him, it came down to exercise, his morning team call with his company, and some form of outdoor adventure to start each day — a walk, coffee outside, anything that got him out of the van and moving before the day started.

Those three went into the calendar before anything else. Locked. Protected.

Then we designed around them. We blocked serenity time in the evenings — Monday, Tuesday, Thursday, Sunday — not as a luxury but as a structural anchor. Wednesday mornings became his adventure block: a physical activity or social engagement after his deep work session. Saturday was reserved for social time.

When we finished the design, he said something that stuck with me: “It doesn't feel like adding constraints. It feels like the week finally has a shape.”

That's exactly right. A week without intentional anchors doesn't feel free — it feels shapeless. And shapeless weeks fill up with other people's priorities.

The White Space Problem

One thing I always add to this conversation: don't fill every hour.

Once you have your three rocks locked in, the temptation is to keep scheduling — fill the remaining space with secondary priorities, recurring commitments, everything on the list. Resist this.

When a calendar is over-scheduled, it becomes rigid. And rigidity has a real cost: you miss the opportunities you couldn't have predicted. A call worth taking. An idea that needs an hour to breathe. A conversation that runs long in the best way.

The goal isn't to plan every hour. It's to anchor the non-negotiables and then protect real margin. Buffer blocks, empty mornings, unscheduled afternoons. That white space isn't wasted time — it's capacity.

The Ideal Week Framework

At Asian Efficiency, the Ideal Week is one of the core frameworks we teach. The first move is always the same: schedule the important work first, before anything else gets access to your calendar.

That means your deep work blocks, exercise, family time, and recovery aren't negotiable. They go in first. Then meetings, then everything else. The calendar shapes around your priorities instead of your priorities squeezing into whatever the calendar leaves.

Most people treat their calendar as a record of what's happening to them. The Ideal Week treats it as a design problem — one where you get to decide what a good week actually looks like before anyone else does.

The three rocks for my client were specific to him. Yours might be different: a daily writing block, three workouts, a weekly date night, uninterrupted deep work before 10am. Whatever they are, they belong in first.

Find your three. Lock them in. Let everything else organize itself around them.

To build your own Ideal Week with a structured process and templates, the 25X Productivity System includes the complete Ideal Week design method, including how to identify your non-negotiables and protect them across different seasons of work.

His question was basically: which one do I build first? And also — when do I use ChatGPT versus Lindy?

I get that question a lot. And the honest answer isn't “it depends” — there's a clean split that most people miss, and once you see it, everything gets easier.

The Two Jobs AI Tools Do

Every AI tool in your stack is doing one of two things.

Thinking. You go here when the problem isn't fully formed yet. You need to brainstorm, explore options, work through trade-offs, or just clarify what you actually want. The AI pushes back, asks questions, helps you think out loud. Reasoning quality matters here. ChatGPT and Claude in chat mode are strong here.

Executing. You go here when you know what you want and you need it to happen. Send this email. Create this document. Pull the relevant items from this spreadsheet. Update the project tracker. The AI is wired into your real tools — email, calendar, Google Drive, Airtable — and it can chain multiple actions together in one pass. Lindy, n8n, and purpose-built agents live here.

The problem is that most people use one tool for both jobs, or they collect multiple AI tools with no clear logic for which to use when. Either way, they're not getting what they want from either.

What This Looks Like In Practice

I was planning content strategy for Q1 earlier this year. I had a bunch of loose ideas — directions I'd been noodling on, things clients kept asking me about, content I'd been meaning to write for months.

First I took everything into ChatGPT. Let it ask me questions. Explored what resonated. Argued a little. An hour later, I had a clearer picture of what I actually wanted to do — a structured quarter of content by theme.

Then I took that output to Claude Code and said: structure this into a content calendar by week, create individual docs for each piece, save them to my Drive folder, and update the project tracker.

Same problem. Two different tools. Two different phases.

Neither could have done the other's job as well. ChatGPT doesn't have access to my Drive or my tracker. And prompting a super agent through vague, half-formed ideas is a mess — you get confused outputs because the prompt was confused.

I've also seen this with a film producer I was coaching. He'd built a habit of running every new idea through three different models — ChatGPT first for initial ideation, then Claude for technical architecture, then Gemini for creative angles. Each one gave him something the others missed. He wasn't being indecisive. He was being strategic.

The Two-Step Workflow Pattern

Once you understand the thinking/execution split, a simple two-step workflow starts to emerge naturally:

1. Work out the idea, the direction, and the output spec in chat (ChatGPT or Claude)
2. Pass the final output to your agent/workflow tool and say: do this, create this, update this, send this

A common version of this: you have a meeting, you dump the transcript into ChatGPT, you get a structured summary and the decisions made. Then you drop that into your super agent and say: create a Google Doc from this, email it to the team, update the project memo, create Todoist tasks for the action items.

Twelve seconds instead of thirty minutes. And the quality is better because each tool did its own job.

What This Means for Your Tool Stack

At Asian Efficiency, we teach AI fluency as a progression — from using AI as an assistant, to building workflows, to deploying agents that take actions autonomously. Understanding the thinking/execution split is part of moving from the first level to the second.

The question to ask about every AI tool in your stack: is this where I think, or is this where I execute?

ChatGPT: thinking. Super agent: execution. Notebook LM: synthesis. Claude Code: building.

Each one has a job. The skill isn't picking the best AI. It's knowing which AI to pick for which phase of work.

That's actually what fluency looks like.

Want to build a workflow system that puts the right AI in the right place? The 25X Productivity System walks through how to design your AI stack so thinking, execution, and review each have their own tool and their own time.

He'd just gotten back from 30 days at a mental health retreat. He went in carrying a lot: a divorce, a company he was trying to hold together, his daughter going through her own difficult stretch, all while living out of a vehicle. It was one of the more complicated situations I'd seen anyone navigate.

He went because he had to. Not as a luxury, not as a wellness experiment. He'd hit a wall — the kind that doesn't move when you push harder.

He came out different in a specific way.

What He Said When He Got Back

He described it like this: “I can feel those emotions now. But they don't devastate me. I move through them and come out the other side. It's like an emotional superpower.”

I've thought about that phrase a lot since that call.

What he's describing is a distinction most people never make. When hard things happen, most of us fall into one of two patterns. We either suppress the feeling and keep moving — numb to it, pushing through — or we get completely swallowed. The emotion lands, and it takes us out.

Very few people learn the third thing: feel it fully, sit with the weight of it, and still come out the other side intact.

That's what he came back with.

Why This Matters More Than You'd Think

My sports psychologist once told me I have a high baseline for wellness. He meant it as a compliment, but it also made me think about what I actually do when things go sideways.

On hard days, my instinct is to do something physical. A cold plunge. A walk by the water in downtown Austin. Going to bed an hour earlier instead of staying up scrolling. It's not a formal system — it's just replacing bad coping habits with better ones. And it works reasonably well.

But what my client described is a level beyond active coping. He's not managing the emotion by doing something else. He's sitting with it, feeling it completely, and then moving through it without being derailed.

That's the thing most coping strategies don't teach you. They help you avoid the full impact of hard feelings — which is useful, but it's not the same as being able to absorb the full impact and stay functional.

This Is a Skill, Not a Trait

What I've noticed coaching a range of people is that emotional resilience often gets treated as a fixed personality trait. Either you're someone who bounces back from hard things, or you're not.

But my client didn't always have this capacity. He went somewhere, specifically, to build it. He did 30 days of structured inner work, under real conditions. And he came out changed in a concrete way.

That's not magic. It's practice under pressure, the same way any skill gets built.

At Asian Efficiency, one of our foundational beliefs is that happiness and wellbeing are prerequisites, not rewards. You don't earn emotional stability after you've handled everything. You need it to handle everything in the first place. Without it, you'll keep hitting walls — and pushing through them harder instead of understanding what's actually happening.

The Practical Version

Not everyone can take 30 days off. But the underlying principle is accessible without a retreat.

The ability to feel a hard emotion without being destroyed by it comes from practicing small-scale versions of the same thing. It's noticing what you feel, naming it accurately, sitting with it for a beat instead of immediately problem-solving or numbing out, and then choosing what comes next.

Over time, that practice builds tolerance. And tolerance builds what my client described — the ability to feel it fully and still move through it.

I don't think there's a shortcut to the version he built. He did it the real way, and it cost him something.

But the direction is available to anyone.

If you want a framework for building the kind of week that supports your wellbeing — not just your productivity — the 25X Productivity System includes tools for designing around your values and energy, not just your task list.

He's managing a company launch, a potential real estate deal, and some significant personal circumstances — all while living out of a vehicle and bouncing between cities. He's also one of the more disciplined, self-aware people I've coached.

And he was struggling to get to the gym consistently.

Not because he lacked motivation. Not because he didn't value health — it was actually at the top of his priority list. The problem was structural: on gym mornings, he had a 9 am call with his company team, and the drive to the gym and back left no margin. One thing ran into the next, and the gym got skipped.

He told me his solution in the middle of our session, almost as an aside: the night before a gym day, he drives to the gym parking lot and sleeps there.

He wakes up. He's already there. No commute, no time pressure, no negotiation with himself.

My response: “That's the key insight right there.”

The Problem With Willpower as a Strategy

Most productivity advice implicitly relies on you making a good decision when you're tired, stressed, or already behind.

Push through the resistance. Just do it anyway. Get up earlier. Try harder.

That advice works sometimes, for some people, in some conditions. But it has a fundamental flaw: it treats motivation and willpower as the variable to optimize, when the real variable is friction.

Friction is structural. It's the gap between where you are and where the behavior needs to happen. The drive to the gym. The extra steps before you can start a task. The password you have to look up before you can open the tool. These are small things, but they're surprisingly powerful because they give you something to negotiate with at 6am when your reasoning faculties aren't fully online.

“I'll do it tomorrow.” “It's already tight on time.” “I'll make up for it this weekend.”

The friction is the raw material for the excuse. Remove the friction, and you remove the excuse.

What Removing Friction Actually Looks Like

The van-in-the-parking-lot solution sounds extreme, but it's just an unusually literal version of the same principle that works in every context.

The classic examples: laying out your gym clothes the night before. Putting running shoes next to the door. Prepping coffee the night before so your morning routine starts one step earlier. Setting the alarm in the other room so you have to physically get up to turn it off.

These all work because they eliminate a decision — or eliminate the opportunity to talk yourself out of something — before you arrive at the moment when you'd make that choice. You're not trusting future-you to make the right call. You're engineering the situation so future-you doesn't have a choice to make.

A former coaching client of mine called this “setting an elaborate trap for yourself.” Which is exactly right. The goal isn't to become more motivated. It's to make the behavior so easy and frictionless that motivation barely enters into it.

The Less Obvious Places to Apply This

Everyone understands it for exercise. Fewer people apply it to cognitive work.

If there's a project you've been procrastinating on, the question to ask isn't “how do I get more motivated to work on this?” The question is: “what's the friction that's actually stopping me?”

Sometimes it's a missing piece of information you need to gather before you can start. Handle that first, then close the loop.

Sometimes it's that the task lives on a platform you find annoying to open. Find a way to make it easier to access, or move the work somewhere more natural.

Sometimes it's that the task is vague — “work on the project” — which creates cognitive friction because your brain doesn't know what to do first. Breaking it down to a first physical step removes that friction.

The principle generalizes everywhere: find the friction, eliminate it before the moment of truth, and the behavior becomes easier almost automatically.

The Bigger Idea Here

My client's van solution struck me because it was so specific. He didn't say “I'm going to try harder to get to the gym.” He looked at the actual structural obstacle — the commute was too much margin on a tight morning — and solved that specific problem in the most direct way available to him.

That's the mindset shift. When a behavior isn't happening, your first question shouldn't be “how do I increase willpower?” It should be “what's in the way?”

Most of the time, something is literally in the way. A decision you'd rather not make. An extra step that's just annoying enough to skip. A mismatch between where the behavior needs to happen and where you already are.

Fix that first. Everything else gets easier.

For more on how to design your week around your actual priorities, the 25X Productivity System includes the tools for identifying where the real friction is in your work and life — and what to do about it.

Over nearly a decade of this, I've built what most people would call a big network.

But here's the thing I've noticed: the size of the network isn't what makes it useful. I know plenty of people with enormous contact lists who still struggle to make effective introductions or close deals. They have the contacts, but they don't know what to do with them.

The gap is almost always the same. They built a network. They didn't build a map.

What a Map Actually Means

A map of your network isn't complicated. It's just knowing what each person in it is actually looking for.

What industries does this investor focus on? What stage? What check size? Is she actively deploying right now or sitting on the sidelines?

What kind of introductions does this person actually want? Is he looking for clients? Operators? Co-investors?

What problem is she trying to solve this year that she might not have mentioned publicly?

Most people can't answer these questions about more than a handful of people in their network. They know the person exists. They have the LinkedIn connection or the email. But they don't know the thesis — what the person is actually trying to do and what would genuinely matter to them.

The Moment When It Shows

I was talking with Josh, a legal tech founder doing a pre-seed raise, about how I work with investors. He asked how I'm able to move quickly when a deal comes in.

The answer: the prep work is already done.

When a new opportunity lands in my inbox, I can usually think of five to ten specific people to text within a few minutes. Not a broadcast email to everyone I know. Targeted texts to people I've been paying attention to for months or years. “Hey, I've got something here that matches exactly what you told me you were looking for.”

That's a fundamentally different ask than cold pitching. The person on the other end doesn't feel like they're being solicited. They feel like someone remembered what they said and found them something relevant.

That difference — between being the person who sends mass emails and being the person who sends targeted texts — comes entirely from whether you've done the pre-work.

How the Pre-Work Actually Gets Done

It doesn't happen in a single session. It accumulates.

Pay attention when people tell you what they want. When an investor at a dinner says she's focused on B2B SaaS with a particular kind of ARR profile, write that down somewhere. When someone mentions they're looking for a specific type of operator for a portfolio company, make a note.

Most of this information gets shared in normal conversation. People tell you what they care about all the time. The difference is whether you're capturing it.

I keep a rough mental model of each person in my active network — what they're working on, what they told me they wanted to see more of, where they are in a deal cycle. For the people I work with most closely, there's a note somewhere that tracks this more formally. For others, it's just a habit of paying attention and remembering.

The tool matters less than the habit. The habit is: treat what people tell you as signal, not small talk.

Why Most People Skip This

The honest reason is that it doesn't feel like networking. Collecting contacts feels productive. Going to events feels productive. Following up and adding people on LinkedIn feels productive.

Taking notes on what someone told you about their investment thesis six months ago feels like homework.

But that homework is exactly what creates the asymmetry. When a deal lands, the people who've done it can move in minutes. The people who haven't are starting from scratch — trying to figure out who in their network might be relevant, crafting a mass outreach email, hoping for the best.

The speed difference is significant enough to matter. In fast-moving situations, being the person who responds immediately with the right names closes more deals than being the person who follows up a week later after doing research.

When I Hosted Gary Vaynerchuk

A few years ago, a friend of mine named Robbie moved to Austin. He'd noticed how I built my Austin network — through dinners, hosting, creating environments for people to connect. One day Robbie invited Gary Vaynerchuk to town and brought me in to host Gary, show him around, introduce him to the right people.

What made that possible wasn't that I happened to know who Gary was. It was that I'd spent years understanding who in Austin would genuinely matter to someone with Gary's interests and what he was working on at the time. I could curate the room because I'd done the homework on both sides — I knew Gary's thesis and I knew my Austin network's interests.

Hospitality at that level isn't really about being nice. It's about having done the prep work so well that when the opportunity appears, you can add value immediately.

That's true whether you're hosting a dinner, making an introduction, or responding to a deal that just landed in your inbox.

The Practical Starting Point

You don't need to audit your entire network this week. But here's a version of the question worth sitting with:

Pick five people in your network who you'd consider in your “inner circle.” For each one, write down:

• What are they currently working on?
• What would a genuinely useful introduction look like to them right now?
• What did they tell you they wanted — a deal, a hire, a partnership, a customer — the last time you had a real conversation?

If you can answer those questions for all five, you're ahead of most people. If you can't answer them for any, that's your gap.

The network you can actually use is the one you know well enough to deploy without researching it first.

On building leverage in your work and relationships: Most of the systems I use to stay organized and effective are covered in the 25X Productivity System — including how I track information that matters for relationships and deals.

Someone asks: “Did you finish the thing from last week?”

And the room goes quiet. Not uncomfortable silence — just a beat of confusion, followed by someone saying they thought someone else was handling it, followed by the realization that no one wrote anything down.

This is the action item problem. It's not dramatic. It doesn't feel like a crisis. But it costs teams real time and real results, week after week, because the way most meetings work is fundamentally broken.

What Actually Happens in Most Meetings

When someone says “can you follow up on that?” in a meeting, nothing about that statement creates accountability.

The person who said it assumes it's been noted. The person it was directed to may or may not have caught it. The three other people in the room heard it but weren't sure if it was meant for them. By Thursday, when the work was supposed to happen, it's entirely possible no one remembers the conversation at all.

I was talking with Dr. Vo — she runs a medical clinic in Austin — about this exact issue. Her team has a weekly Friday meeting to review patient cases and coordinate care. During these sessions, tasks get verbally assigned across the team. Follow this up with this patient. Reach out to this specialist. Check on this referral.

And every week, some of those things slip. Not because her team isn't capable, but because a verbal assignment in a crowded meeting doesn't naturally translate into a tracked, followed-up task. No one has a system. The assumption is that people will remember. Often they don't.

The Simple Fix That Changes Everything

Here's what I told her: record the meeting.

That sounds obvious, but most people stop there. They record the meeting, occasionally go back to listen to parts of it, and still end up doing most of the follow-up work manually.

The change is in what happens after the recording ends.

Once the meeting is transcribed — which happens automatically if you're using a tool like Granola, Otter.ai, or similar — an AI can process that transcript and do the extraction work. It identifies every action item. It notes who it was assigned to. It formats each task clearly and emails the relevant person directly.

And then, a few days later, it sends a follow-up. “Hey, just checking in — did you get to this?” Simple. Automatic. No manager has to track it manually or remember to ask.

What was a chaotic verbal exchange becomes a tracked, accountable system. Without adding any manual work after the meeting.

Why This Is the Right Place to Start with AI Automation

I think about AI automation through a simple filter: automate the things that happen daily or weekly first.

Not the flashy one-off tasks. Not the complex multi-step workflows you'd love to have someday. The repetitive ones. The pain that shows up every Monday or every Friday. Because frequency is what makes automation actually pay off.

Weekly meetings are almost universal. Most teams have at least one. They almost universally suffer from the same follow-through problem. And the fix requires no custom software, no engineering, and no major workflow redesign. You record something you're already doing, and you let the AI do the extraction and routing that no one wants to do manually.

This is what the 80-20 approach to AI looks like in practice. Find the high-frequency pain. Build the simplest possible fix. Get compounding returns every week.

What a Basic Setup Looks Like

You don't need an elaborate system to start. A minimal version:

1. Use a meeting recorder that auto-transcribes (Granola, Otter.ai, Fireflies — pick one)
2. After the meeting, paste the transcript into a well-crafted AI prompt that extracts action items by name
3. Send each person their specific tasks by email

That's it for version one. No automation required. Just a consistent habit.

A more sophisticated version uses an AI agent to monitor incoming transcripts and handle the extraction, assignment, and follow-up automatically — but that's a build-out step, not a starting point. Start simple. The goal for the first week is just: no action item disappears.

The Part That Surprises People

What I've found when I show people this setup is that the useful part isn't actually the AI extraction.

It's the follow-up.

Most teams will write down action items if you remind them. What nobody does is send a reminder three days later to check on them. That's the part that falls apart. Someone writes the summary, sends it right after the meeting, and assumes that's enough. Then Thursday arrives and nothing happened.

Automating the follow-up is the lever. “Hey — the meeting on Friday assigned you this task. Just checking in.” That one email, sent automatically, changes the accountability dynamic completely.

Dr. Vo is setting this up now for her Friday reviews. The expectation is that every verbally assigned task in the meeting gets emailed out automatically and followed up on before the next session. No manager remembers to send the summary. No one manually tracks who owes what. The recording handles it.

That's a small change with a big compounding effect. Every week, the meeting produces real outcomes instead of verbal intentions.

If you want to go deeper on AI automation for your team's workflows, the Two Hour Workday program walks through exactly these kinds of builds — starting with your highest-frequency pain points and building from there.

Get 20% off your first order: dripdrop.com and use promo code tps.

For problems worth solving go to Claude.ai/tps. 

Get 60% off personal and family plans at Keepersecurity.com/TPS.

Use promo code tps at evenrealities.com to get 10% off Even Ring 1 and/or Even Clip when you add them to your Even G2 order.

Visit www.asianefficiency.com for more productivity tips and tactics.

Listen to this episode (MP3)

Cheat Sheet

• Top 3 Productivity Resources [3:01]
• The meeting where AI bots outnumbered the actual humans [5:32]
• Why some meeting organizers are now blocking AI notetakers outright [8:16]
• The strange email problem you get when your AI drafts everything for you [12:03]
• The one popular meeting assistant that never actually joins your call [22:39]
• How your action items could update your task list without you lifting a finger [25:16]
• How one offhand story in a meeting becomes content gold automatically [32:10]
• The one type of meeting where an AI assistant is a bad idea [40:45]
• The parking-lot trick people use to hide that their smart glasses are recording [47:45]
• The 15-minute fix that could save you months of repeated meetings [50:03]

Links

• DripDrop
• Claude
• Keeper
• Even Realities
• 25X Productivity Coaching
• How We Decide by Jonah Lehrer
• TextSniper
• Tech Brew Ride Home
• Lindy
• Otter
• Fireflies
• Fathom
• Granola
• MacWhisper
• Zapier
• Make

If you enjoyed this episode, follow the podcast on Apple Podcasts, Spotify, Stitcher, Overcast, Pocket Casts or your favorite podcast player. It’s easy, you’ll get new episodes automatically, and it also helps the show. You can also leave a review!

She also told me she can't take vacations.

Not that she doesn't like vacations. Not that she's a workaholic who prefers staying busy. Can't, as in: the clinic closes when she leaves.

The covering doctor who fills in for her isn't licensed to see her patients. So the last time she took time off, they had to shut down the clinic. The business stopped completely because one person wasn't there.

This is what software developers call the bus factor. And it's not just a tech problem.

What the Bus Factor Actually Means

The bus factor is a simple question: if a key person on your team got hit by a bus tomorrow, how many people would have to scramble?

The original framing is a bit dark, but the question is genuinely useful. It's asking: how concentrated is the critical knowledge, access, or capability in your business?

A bus factor of 1 means one person leaving would break everything. A bus factor of 5 means five people would need to disappear before things fell apart. Higher is better.

For Dr. Vo, the bus factor was 1. She was it. The clinic's ability to function was entirely dependent on her being physically present.

It's More Common Than You'd Think

I work with a lot of small business owners and team leads, and the bus factor shows up constantly. Just not usually as dramatically as a clinic shutting down.

Sometimes it's the founder who's the only person who knows how to do client onboarding, so every new customer goes through them personally, no matter how busy things get.

Sometimes it's the office manager who's the only one with the QuickBooks password, so every hire, every vendor, every billing question flows through one person.

I was working with a professional services firm recently and noticed they had a similar problem — one person controlled all the software access for the whole team. New clients coming in, staff transitions, permissions for different tools — it all ran through that single person. They were a bottleneck, not by choice, but by design. The work itself wasn't complicated. The concentration was the problem.

The pattern is the same every time. Things got concentrated in one person not because anyone planned it that way, but because that person was available, capable, and said yes enough times that the system organized itself around them.

The Part That Catches People Off Guard

Most people don't think about their bus factor until they need to leave.

A sick week. A vacation that's been planned for months. A family emergency. That's usually when it surfaces — not in a planning meeting, but in the moment when you realize you can't actually step away.

Dr. Vo knew the problem existed. She'd felt it for years. But the pressure of daily operations kept pushing the fix to the back of the list. It wasn't until she tried to take time off that the real cost showed up.

This is the thing about single points of failure: they're invisible until they fail.

The Fix Isn't Always Dramatic

Here's what I told Dr. Vo after she walked me through this: the solution doesn't have to be complex.

It might be documenting one process in enough detail that someone else could run it. It might be sharing access credentials with one other trusted person. It might be training one staff member to handle one type of patient call.

You don't have to solve the entire dependency problem at once. You just have to bring the number down.

Bus factor of 1 → bus factor of 2. That's a meaningful improvement. Someone else can cover, at least partially, if you're gone.

The real first step is knowing your number. Most people haven't actually thought about it explicitly. They've felt the pressure of being needed everywhere, but haven't mapped out exactly where the concentration lives.

So try this: write down every part of your business that would stop or significantly slow down if you were unavailable for two weeks. Anything that only you know how to do, only you have access to, or only you are trusted to handle.

That's your bus factor list. It tells you where to start.

Why It Matters More at Small Scale

Big companies have redundancy built in, even if imperfectly. Multiple people know the same systems. There's documentation. There are backups.

Small businesses usually don't have that by default. The founder wears seven hats. The team is lean. Things get done because someone figures it out, and that someone tends to be the same person every time.

Which means the bus factor problem is actually a bigger risk the smaller the operation.

Dr. Vo is working on this now — building out documentation for the parts of the clinic that rely entirely on her, and thinking about what it would actually take to train someone else to cover certain functions.

It won't happen overnight. But the goal is clear: a business that can function, at least partially, without her. One that doesn't shut down every time she needs to leave.

That's what a real business looks like.

One way to build more leverage into how you work: The 25X Productivity System is where I teach the frameworks for identifying where your time and energy are most concentrated — and how to start distributing them.

I'd been helping people in my network get started with AI — informal conversations, a few demos, the occasional coaching session. But I kept running into the same thing: most people I knew were smart, motivated, and genuinely interested, but they weren't taking online courses. They were too busy. They'd start something, life would interrupt, they'd fall behind and stop.

So I put together a one-day in-person workshop. Sent a few texts. Posted on Instagram once. Whatever happened, happened.

It sold out in four days.

I wrote it off as a novelty. These were people who knew me, who already trusted me, who happened to be curious at the same time. I ran a second one a month later. Same thing — sold out in days.

That was interesting, but not the part that surprised me.

The Detail That Changed How I Think About This

A lot of people who attended the first workshop came back to the second one.

I didn't expect that. My assumption was that once someone got the fundamentals — how these tools work, what they're actually capable of, how to start using them — they'd be off. They didn't need a second round of the same basics.

But they weren't coming back for the basics.

I started asking. The answer I heard most often was some version of this: “I wanted to see what's changed.”

Why AI Moves Differently Than Other Skills

The thing about AI right now is that the pace of change is high enough to disqualify even reasonably recent knowledge.

The tools that were genuinely impressive six months ago have been replaced or significantly upgraded. The workflows that felt cutting-edge last quarter are already being superseded by approaches that are cheaper, faster, or more reliable. The mental models people built up in 2023 about what AI can and can't do are often meaningfully wrong in 2025.

For most skills, once you have the fundamentals, the fundamentals stay. What you learned about writing or negotiation or financial modeling doesn't expire. You might refine and deepen your knowledge, but the foundation holds.

AI doesn't work that way right now. The fundamentals keep shifting under you.

That means someone who took a workshop six months ago and has been using AI actively isn't necessarily set. They might be using approaches that have been surpassed. They might be missing tools that would change how they work. They came back because they needed a curated update, not a refresher.

What the Workshop Actually Became

Once I understood this, I realized what I was actually providing.

It wasn't a fundamentals course. It was a recurring curation service.

“Here's what's worth paying attention to right now.” That was the real value proposition — not the foundational education, but the ongoing signal filtering. In a space where there are ten new tools and frameworks announced every week, the job of figuring out what's actually worth learning versus what's noise is significant work. The workshop was doing that work for them.

That's a different thing than a one-time course. It's more like a subscription to clarity, delivered in person a few times a year.

What This Says About the Demand

I was initially thinking about AI workshops as a product for beginners — people who don't use AI yet and need a starting point.

The repeat attendance told me there's a different market: people who are already using AI and want to stay current without doing the research themselves. These aren't beginners. They're practitioners who are busy enough that ongoing curation is more valuable to them than more hours of self-directed learning.

Both markets exist. But the second one is the one I hadn't fully recognized.

When customers come back to something a second time, it's not because they forgot what they learned. It's because the underlying problem keeps recurring. For AI professionals right now, the recurring problem is: things keep changing faster than any individual can track alone.

That's the demand signal I missed when I was thinking about who these workshops were for.

The first-time attendees tell you there's curiosity about AI. The second-time attendees tell you there's a need for ongoing navigation of it. Those are different problems. And the second one, it turns out, is actually the bigger one.

On learning AI without getting overwhelmed: I cover what's actually working right now — tools, workflows, and frameworks worth building on — in the Two Hour Workday program. If you want the curated version rather than the fire hose, that's the place.

I walked her through what the role would look like: managing a content pipeline, coordinating publishing, overseeing quality. Then I got to the AI part.

“The AI handles a lot of this,” I said. “You don't have to build the agents unless you want to learn how. A lot of it is just running them and overseeing them.”

She looked relieved.

I've been thinking about that reaction ever since.

The Fear That Gets in the Way

I teach AI workshops regularly. In-person sessions in Austin, mostly for executives, business owners, and professionals who've heard enough about AI to know they should be paying attention but haven't quite figured out where to start.

At every single workshop, within the first ten minutes, someone says some version of this: “I'm not technical enough for this.”

It's the single most common objection to AI adoption I encounter. And it's based on a misunderstanding about what the valuable skill actually is.

Three hours later, those same people are building their first agents.

Not because it suddenly got easy. Because “not technical” turned out not to be the barrier they thought it was.

Builder vs. Operator

There are two roles in an AI-powered organization. Builders and operators.

Builders design and construct the systems. They understand APIs, write prompts, configure tools, debug when workflows break. This is a real skill set. It takes time to develop and it's genuinely useful.

But operators are different. Operators run the systems. They feed the right inputs, review the outputs, catch the errors, make the judgment calls that AI can't, and know when to intervene versus when to let the workflow run.

Operators don't need to know how to code. They need to know the work.

That's a completely different skill requirement. And it's the one that scales.

For every person who builds an AI workflow, you need multiple people who can run it. A content pipeline needs someone who understands what good content looks like. A client communication system needs someone who understands the client relationship. An AI research assistant needs someone who can evaluate whether the output is accurate and relevant.

None of those people need to have written the code. They need domain knowledge and judgment. Which, if you've been working in your field for any length of time, you already have.

What Operating Actually Looks Like

I built an AI content pipeline at Asian Efficiency that produces first drafts for multiple platforms. The pipeline is complex — it pulls from transcripts, searches a story database, runs multiple writing steps, and formats output for different channels.

Building it required a certain kind of technical knowledge.

Running it requires something different: understanding what a good piece of content looks like for each platform, knowing when the AI has captured the right angle versus when it's missed it, catching factual errors, recognizing when the voice is off, and making editorial decisions the system can't make on its own.

The OBM I hired didn't build that pipeline. She runs it. And the running is where the judgment lives.

You can think of it the same way you'd think about managing a capable new hire. You don't need to understand every technical aspect of their background to give them effective direction. You need to understand the work well enough to evaluate their output, give useful feedback, and redirect when something's off.

AI agents respond to the same kind of management.

The Skill Worth Developing

If you're waiting to get “technical enough” before engaging with AI at work, you're waiting for the wrong thing.

The operators who create the most leverage aren't necessarily the best prompt engineers. They're the people who understand their domain deeply — their clients, their industry, the quality bar for their work — and can apply that knowledge to evaluating and directing AI output.

I taught a workshop at a salon owner conference a while back. Three sessions, standing room only. Most of these people considered themselves nowhere near technical. By the end, they had AI systems handling social media content for their businesses.

The barrier wasn't technical ability. It was the assumption that technical ability was required.

The builders will always be valuable. But operators are going to outnumber them significantly, and they're going to do a lot of the work that actually reaches clients and customers.

If you understand your work well enough to explain it to someone new — you can operate an AI system that does it.

That's the starting point.

If you want to develop the operator skill set: The Two Hour Workday program walks through how to run AI workflows in practice — not just build them — with real examples from client implementations. That's where most of the practical work happens.

I described the approach I wanted to move toward: if the podcast goes out on Monday about a particular topic, I want the newsletter that week to cover the same topic. Different angle, different format, but the same core idea.

Her first reaction: “Won't that feel repetitive?”

It's the right instinct. And it's wrong.

Why Content Creators Avoid This

There's an unwritten rule in content production: don't cover the same topic twice in the same week. It feels like running out of ideas. Like padding the calendar. Like you're asking your audience to sit through the same lecture twice.

So most people plan their content calendar the other way. Podcast on one topic, newsletter on a different topic, LinkedIn on something else. Maximum variety. Every piece covers new ground.

I understand the thinking. It's wrong in practice.

What Actually Happens When You Stack

Consider how your audience actually consumes content.

Most people who listen to your podcast don't read your newsletter. Most people on your email list don't follow you on LinkedIn. Most people on LinkedIn didn't catch the YouTube video. Even the small overlap — the people who consume multiple channels — doesn't always happen in the same week.

Your audience is fragmented across platforms and their attention is fragmented within each platform. The podcast listener who opened your newsletter this week is not guaranteed to have listened to Monday's episode. They might have heard it, filed away the idea, and then forgotten it by the time Wednesday's email landed.

When both pieces hit in the same week on the same topic, something different happens. The idea gets a second opportunity to land. And for the rare person who consumed both, hearing the same concept twice — once as audio narrative, once as written argument — reinforces it in a way that a single exposure never does.

That's not redundancy. That's how learning actually sticks.

The Wide-and-Thin Problem

Most content plans are wide and thin.

Podcast on topic A. Newsletter on topic B. LinkedIn on topic C. Three channels, three distinct topics, each piece of content standing alone.

The problem is that each idea gets exactly one shot. If the metaphor didn't land, if the reader was skimming, if the listener was distracted — the idea doesn't make it. There's no second door.

Same-week stacking flips the approach to narrow and deep.

One topic. Multiple formats. Multiple touchpoints. One week.

The podcast version explores the idea through conversation and story. The newsletter version grounds it with a specific example or action. The LinkedIn post hooks on the most counterintuitive angle. Each format reaches a different subset of your audience, and for the people who encounter more than one — the idea is reinforced rather than repeated.

How to Actually Do This

The practical change is smaller than it sounds.

Instead of planning your content calendar by assigning different topics to different channels each week, you plan one topic per week and let the channels serve it.

The question shifts from “what's the newsletter topic this week?” to “what's the topic this week?” Everything else flows from that.

That doesn't mean the content is identical across channels. The podcast might spend 40 minutes exploring nuance and context. The newsletter might spend 400 words on the most actionable takeaway. The LinkedIn post might just surface the counterintuitive hook. Same idea, different depth, different format — all reinforcing each other.

When I rebuilt the AE Q1 calendar this way, the planning actually got easier. We stopped having to generate ten separate ideas each month. We started generating four or five strong ideas and figuring out how to express each one well across channels.

The Reframe

Most content creators are optimizing for coverage — how many different topics they can touch in a given month.

Same-week stacking optimizes for penetration — how deeply one idea can land across your audience.

Neither approach is always right. But if you have a strong idea, giving it one exposure across one channel is underselling it. That idea might change how someone thinks about their work. But only if it actually lands.

The chance of it landing goes up every time it shows up in a different format from a different angle in the same week.

You're not repeating yourself. You're giving one good idea its best shot.

On building a content calendar that actually works: The Productivity Academy covers content planning, systems for consistent publishing, and how to build a sustainable output rhythm. Worth checking out if you're trying to make your content work harder.

Then she pulled up the newsletter queue in Ontraport.

Over 100 newsletters. Fully written. Never sent.

Not drafts. Not rough outlines waiting for someone to polish them. Finished newsletters, sitting in the system with zero recipients. A content repurposing project from earlier in the year had generated all of them, and then… they just stayed there.

My first reaction was embarrassment. My second was clarity.

We didn't have a content creation problem. We had a content deployment problem. And those are completely different things.

What Content Debt Is

I've started using the term content debt to describe this pattern.

In software, technical debt is what happens when you take shortcuts in your code — you get a working system quickly, but you accumulate hidden costs that compound over time. Content debt is similar: you create assets that never activate. The creative work gets done, but the distribution never happens.

Most businesses have more content debt than they realize.

Blog posts that got written and never promoted beyond an initial social share. Podcast episodes that exist but never got repurposed into newsletters or clips. Email sequences that were drafted but never turned on. Case studies that got produced and sat on a shared drive. Recordings from workshops that were never edited or distributed.

You can often feel content debt even when you can't name it. It shows up as a vague sense that you should be doing more with what you have. Or a friction around content, where creation feels heavy because you're not sure it'll ever get used.

Why It Accumulates

Creation is more interesting than deployment. That's the root of the problem.

When you're writing a newsletter or recording a podcast episode, you're making something. There's a start, a middle, and an end. There's visible progress. The work feels complete when you finish it.

Deployment is operations. Scheduling, formatting, sequencing, distributing. It's the part that takes something from done to out-in-the-world. And it's easy to defer. There's always something more interesting to do instead.

So content piles up in the gap between “finished” and “shipped.”

This isn't a discipline problem. It's a systems problem. If you don't have a clear owner and a clear process for moving content from created to deployed, deployment just keeps getting pushed back.

The Audit

Before you commission any new content, spend 20 minutes doing a content debt audit.

Go through your email platform — how many drafts are sitting there that have never gone out? Check your content docs or Notion or whatever you use — what's been written but not distributed? Look at your podcast or video archive — what's never been repurposed? If you've run workshops or produced case studies, where did those go?

You're looking for content that crossed the finish line of creation but never crossed the finish line of deployment.

For most businesses, the list is longer than expected.

What to Do With It

Once you have the list, you have options.

Some content will still be relevant and can be sent or published as-is. Schedule it. This is the easiest win.

Some content will need minor updating before it goes out. That's still faster than creating from scratch.

Some content will be too dated or off-brand to use. Archive it. The point isn't to force everything out — it's to consciously decide what happens to it instead of letting it drift.

The goal is to get to a state where you know what you have, what's in the pipeline, and what's been retired. No more invisible backlog.

The Bigger Shift

The content debt audit isn't a one-time fix. It's a shift in how you think about content work.

Production isn't the finish line. Distribution is. A piece of content that gets made but never reaches anyone is functionally equivalent to content that was never made. The work happened, but the value didn't get delivered.

That framing changes what you pay attention to. Before adding to the production queue, you ask: do we have a deployment gap? Is there already content that should be going out that isn't?

In our case, we had 100 newsletters ready to go. The content calendar problem I thought we needed to solve was already solved. We just hadn't looked.

Most businesses have a version of this. The asset library exists. It just hasn't been activated.

On building systems that actually ship: The Productivity Academy covers content systems, deployment workflows, and how to build the kind of operational clarity that prevents content debt from accumulating in the first place. Worth a look if this resonates.

One of the interviews I did that day was with the clinic's head physician. She runs a boutique concierge medicine practice, sees premium patients, and manages a small clinical team. I asked her about clinical decision support tools — whether she used any, whether she wanted any.

What she told me stuck with me.

She's already using it

She uses Gemini and ChatGPT to write patient counseling summaries. Instead of spending 20 minutes per patient developing her own written narrative — lifestyle advice, dietary notes, whatever the patient needs to hear — she asks AI to draft it in five sentences. Then she reviews, adjusts if needed, and shares with the patient.

She also uses the AI scribe built into her EMR. It transcribes consultations in the background while she talks with patients. Before she had this, she was charting during appointments — trying to type notes while simultaneously listening and responding. Not ideal for anyone in the room. Now she can be fully present.

And she uses AI to summarize lab trends across a patient's history. Her EMR has a clinical assistant that can pull up changes in liver enzymes or blood panels over time. Instead of manually scanning through hundreds of reports to find the relevant patterns.

None of this involves diagnosis. All of it is paperwork.

The line that changed how I think about this

“My time should be used for diagnosing,” she told me. “Not charting.”

That one line names something I've been watching play out across dozens of client engagements. AI creates the most value in professional work not by replacing expert judgment — the part that requires training, experience, and accountability — but by eliminating the overhead that surrounds it.

Every knowledge worker has this split. There's the expertise work, the stuff that actually requires you. And then there's the overhead: writing things up, organizing information, following up, summarizing, explaining, preparing. That second category is where a lot of the hours go.

For a doctor, the expertise work is diagnosis. The clinical judgment that requires years of medical school and a license. Everything else — the charting, the write-ups, the record review — is overhead.

The same pattern shows up in every profession. A lawyer's expertise is legal judgment. The research, the drafting, the summarization is overhead. An executive's expertise is strategic decisions and key relationships. Calendar management, email triage, meeting prep is overhead.

AI is best at the overhead.

I've seen this across a lot of different clients

Last year I was working with an executive team on AI automation. One of their assistants was spending 20-25 hours a week on administrative tasks — email, scheduling, meeting follow-ups, basic research. We built a set of AI agents to handle the routine work. Within a few weeks, that same work took 4-5 hours instead.

She didn't lose her job. She got her time back for the work that actually required her.

That's the version of this story that plays out when people use AI well. Not handing off the judgment calls. Handing off everything that was never really a judgment call in the first place.

The question most people ask about AI — “will it replace me?” — usually points to the expertise work. Will AI diagnose patients? Will it argue cases? Will it make strategic decisions?

In most fields, for now, no. But that's not where the time is going anyway.

The time goes to the overhead.

A useful test for your own work

Before your next task, ask: does this require my expertise, or just my time?

Writing up meeting notes after a call — that's time, not expertise. AI can do it.

Deciding what the next move should be based on those notes — that's expertise.

Drafting a patient counseling summary — time, not expertise. The doctor already knows what the patient needs. She just needs it written down.

Knowing what the patient actually needs — expertise.

That split is different for every person and every profession. The doctor figured out where her line was. A doctor with a different specialty might draw it differently.

The professionals getting the most out of AI right now aren't asking whether AI can replace them. They're asking which 20-minute tasks they've been doing that never required their expertise in the first place.

That's the question worth sitting with.

Want to map out where the overhead is in your own work? The Two Hour Workday program walks through exactly this — identifying which parts of your day require you versus which parts AI can handle. More info here.

That argument was always true. It still is. But there is a newer reason to care about file organization that most people have not thought through yet.

Your AI tools need it just as much as you do.

What Changed

I have been building AI agents for the past year — tools that retrieve documents, search through transcripts, pull context from meeting notes, surface relevant information automatically.

The agents that work well have one thing in common: the underlying files are organized. Good names, consistent structure, searchable keywords.

The agents that keep failing? Often it comes down to the same thing. Poorly named files. Folders with nothing but dates. Documents called “final v3 REVISED USE THIS.” Notes that have content but no searchable label.

AI does not browse folders the way you do. It searches. And if your files are named in a way that only made sense to past-you in that specific moment, the agent either cannot find what it needs or grabs the wrong thing and confidently runs with it.

The result is a lot of avoidable errors that feel like AI failures but are actually organization failures.

The Plaud Experiment

A few months ago I spent a full day on-site at a health clinic, doing workflow interviews. Eight hours of conversations. I had a Plaud recording pin on the whole time — the point was to stay fully present while still capturing everything.

After the day, I came home with a lot of audio files and had to figure out what to do with them. The ones I labeled clearly — with the date, the department, what workflow we were discussing — were easy to process. An AI agent could search for the right session, pull the transcript, and work with it cleanly.

The ones I labeled generically were harder to work with. Even knowing what was in them, finding the right clip took longer than it should have.

Scale that up to months of files and dozens of documents, and the difference becomes significant.

The Three-Keyword Rule

Here is the naming system I use, and it takes about ten extra seconds per file.

Think of three keywords that future-you would search to find this file. That is the name.

Date first — YYYY-MM-DD format so files sort chronologically. Then the keywords. I add “ae” to anything related to Asian Efficiency. Podcast episodes get “tps.” Client names, tool names, topic keywords — whatever future-me would actually type.

So instead of “Meeting notes Dec 17,” the file becomes “2025-12-17 tps file organization ai automation.”

Future-me can find it by searching any of those words. Any AI agent I point at my files can find it too. The name is self-describing enough that even without opening the file, you know what is in it.

The “underscores vs. spaces” debate comes up sometimes. Underscores are a legacy convention from DOS-era computers where spaces would break file paths. They are mostly unnecessary now. Spaces are fine. Just pick one and be consistent.

Why This Matters More Than It Used To

There is a concept I think about a lot: your files and transcripts are the raw material that makes AI work for you. Not the AI tools — those are cheap and getting cheaper. The real asset is the organized, searchable library of your own work.

Well-named meeting transcripts become the input for a weekly synthesis agent that surfaces patterns across months of conversations. Well-named project files let an AI assistant pull relevant context before a client call without you having to remember which document has what. Well-organized notes become the foundation for a knowledge base an agent can actually use.

None of that works if the underlying files are a mess.

Every organized file you create is a small investment in the infrastructure that makes your AI stack actually functional. That framing makes the ten extra seconds feel worth it.

The Practical Test

Before you save any file, ask two questions:

1. Would future-me find this by searching for these words in six months?
2. If an AI agent searched my files for information about this topic, would it find this file and know what it contains?

If the answer to both is yes, the name is good. If not, spend five more seconds on it.

You are not just organizing for yourself anymore. You are building the infrastructure that lets the tools work for you.

If you want to go deeper on this: The weekly review process I teach in the Productivity Academy covers building these kinds of systems — file organization, AI-ready structure, and the habits that make them stick. Worth checking out if you want the full framework.

Near the end of my interview with the head physician, I asked her a question.

“If everything worked perfectly — imagine you're walking in tomorrow morning. What would that feel like?”

She paused and described the reality. Checking three different calendars that didn't sync properly. Trying to figure out which patients were coming in and whether their intake information had been collected. Scanning messages for follow-ups she'd meant to track but hadn't. Starting her day in catch-up mode before a single patient had arrived.

That's not a designed day. That's a survived day.

What a Designed Day Looks Like

I told her what I thought the perfect version could look like.

The night before, a document is waiting. It has every patient coming in the next day, with the most important context pre-loaded — especially for first-time visitors, their intake information is already there. There's a brief summary of open follow-ups from previous visits. There are two or three things worth flagging at the Friday team meeting. There's a task list, but it's organized, not a raw dump.

She reviews it in five minutes over coffee.

She walks in already knowing what to expect.

Nothing in that scenario requires extraordinary effort. It doesn't require her to work longer or be more disciplined. It requires a system — a workflow that assembles tomorrow's context today, before the day begins.

I've started calling this the Perfect Day framework.

The Core Idea

Most people plan their day by building a task list. And that's worth doing. But a task list tells you what to do. It doesn't tell you what you're walking into.

Perfect day design adds a layer: preparing the context, not just the schedule.

There's a distinction between planning and preparation. Planning answers “what am I doing today?” Preparation answers “what do I need to know before I start?”

A physician needs to know which patients are coming and what their baseline is. An executive needs to know who they're meeting and what the history is. A consultant needs to know which projects have outstanding items and what's been waiting on their response.

That context exists somewhere. But left to gather on its own, it shows up scattered — across calendars, email threads, notes apps, and memory. The morning scramble is the cost of not organizing it in advance.

The Reactive Default

There's a reason most people default to reactive rather than designed.

Reactive requires no setup. You show up, look around, figure out what needs attention, and respond. It works well enough in low-volume environments, and it has an advantage: you're always handling what's actually urgent.

The problem is that reactive thinking consumes the same cognitive energy you need for your best work. Before you've done anything, you've spent an hour just orienting. That's not a small tax — it's often the difference between a day that feels scattered and a day that builds.

Proactive design doesn't eliminate surprises. But it means you start from a position of orientation instead of confusion.

Building the Preparation Layer

The practical question is: what does the person who will start your day tomorrow actually need?

For the physician, it was patient context and open follow-ups.

For an executive I worked with, it was a brief morning briefing — who they're meeting that day, relevant background on each person, and any time-sensitive emails that came in overnight. Before we built a system for it, they were spending 20-30 minutes doing that manually every morning. After, it arrived automatically.

For someone doing deep work in the morning, the preparation might be different: knowing exactly which task to start on, with all the relevant files open, so they can begin without the decision overhead.

The specific form varies. The structure is the same: you build the context before the day demands it.

The Night-Before Design

The most practical version of this starts with one question at the end of each workday: what does tomorrow's me need to know?

Not what do I need to do. Not what's on my calendar. What context would make tomorrow run better if it was assembled tonight?

For some people that's a brief review of the next day's meetings and what each one requires. For others it's a flagged short list — a few things worth knowing before I start. For people using AI tools, it might be an automated briefing that gathers this across email, calendar, and project files.

The medium matters less than the habit. Preparation either happens deliberately or not at all.

The Ideal Week Connection

The Ideal Week framework from Asian Efficiency is about designing your weekly schedule in advance — protecting time for deep work, meetings, and margin before the week fills in around you. Perfect day design operates at a finer resolution: it's the same idea applied to each day.

You don't just schedule the hours. You prepare the person who will show up to fill them.

That preparation is what turns a plan from an aspiration into a day that actually runs the way you intended.

The physician I interviewed was competent, experienced, and motivated. She wasn't falling short because of any deficiency. She was starting every day without the context she needed. The fix wasn't more effort. It was better preparation.

That's usually how it goes.

On designing your day with systems: The Productivity Academy includes the weekly review, the Ideal Week, and the core planning frameworks for building a day that starts from orientation instead of chaos. Check it out if you want the full architecture.

It takes a podcast transcript and turns it into a full set of social media images — the kind that would normally take a designer a few hours to put together. This one runs in minutes.

I built it for Asian Efficiency. We record a podcast almost every week, and I had been wanting a way to turn those episodes into visual content without adding hours of work to someone's plate. So I sat down, built an AI agent in Lindy, tested it on a recent episode, and it worked.

Here is what I did not fully anticipate: that thing is now one of my best consulting demos.

The Problem With Traditional Case Studies

Most consultants and service providers build case studies the slow way. A client hires you, you do the work, you document the results, you clean it up, you put it in a deck. Then you bring that deck to the next meeting.

There is nothing wrong with that. But there is a delay built in. You have to do client work before you can demonstrate client results. And by the time the case study is ready, the example might already feel dated.

There is a faster loop.

Build It for Yourself First

When you solve a problem in your own business, you get two things at once: the tool and the proof.

I know the carousel generator works because I run it on my own content. I can show someone the actual output from last week's episode. When a potential client who creates a lot of content asks “can this work for my situation,” the answer is not theoretical — I can pull up something real and run it live.

That demo lands differently than a case study. A case study says “I helped someone else do this.” A live tool says “I use this myself and here is what it does right now.”

This is something I have noticed across a lot of the consultants doing well in AI implementation: their own operations are their R&D lab. They do not separate “building the business” from “solving the problem.” They solve the problem in their own workflow first, and the client work follows naturally from what they have already proven works.

The Feedback Loop Is Real

It runs in both directions, which is the part worth paying attention to.

The tools I build for Asian Efficiency become demos for consulting clients. And the problems clients bring to me teach me what to build next for AE.

Working with a real estate firm on meeting automation gave me ideas for how to handle my own post-meeting workflows. A session with a CPA helped me think about email filtering in a way I had not before. I came back from those engagements and built things for my own system that I now use every day.

Your client work is also R&D. You are just not logging it that way.

One consultant I talked to recently described building a talent pool from his workshop attendees — people who came to learn would then take on overflow client work. His teaching lab became his workforce. Same principle: what you build for one purpose feeds the other.

What This Means Practically

If you do any kind of consulting, coaching, or service work, there is a simple question worth asking at the start of any new project: would this same solution be useful in my own business?

Not always. Sometimes a client's situation is specific enough that the solution does not generalize. But more often than not, if the problem is worth solving for them, it is worth solving for yourself too.

Build it for yourself first. Document it as you go. When it works, you have already done the proof-of-concept work. Then you bring it to clients as something you use, not just something you have theorized about.

Your business stops being overhead. It becomes the product.

If you want to see what this looks like in practice: I do a small number of one-day AI workshops in Austin and occasionally other cities — working through real workflows live, so you leave with something you have built yourself. If that interests you, the best starting point is the Productivity Academy — I post workshop dates there first.

You sit down to do the work. The task is clear, the time is blocked, the intention is real. And nothing happens. You check your email. You reread the same paragraph. You open a new tab and close it immediately. Twenty minutes pass and you've produced exactly nothing.

The standard response is to reach for a technique. Pomodoro timer. Time blocking. Binaural beats. Turn off your phone. Put on headphones. Use an app that blocks distracting sites.

All of those can work. But there's something faster and more reliable that most people skip: change your environment.

Why Environment Beats Technique

Every focus technique follows the same basic logic: your internal state is scattered, apply the technique, and your internal state becomes more focused. You're working from the inside out.

Changing your environment works from the outside in. The shift in your surroundings creates a shift in your state directly. You don't have to engineer the focus — the new environment signals it.

The research on this is consistent. People are remarkably susceptible to context cues. The same person, doing the same task, in a different physical setting, will often produce a different quality of work because their brain maps the environment to a mode. A cluttered desk signals “chaos is normal here.” A clean desk signals “this is where focused work happens.”

This is also why people who work from home often struggle to stop working at the end of the day — when your home and your office are the same space, the context cues that normally separate work from rest do not exist.

The Desk Declutter

The fastest environmental intervention is clearing your desk.

Not a deep reorganization — that is a different project. Just remove what does not belong there right now. Put away the coffee cups. Clear the papers you do not need for this work session. Reset the surface.

This takes five minutes. Maybe ten if things have really accumulated.

Sit back down after. Notice the difference.

What you have done is sent a signal: this is a clean state. The visual noise that was competing for your attention is gone. The environment is now arranged to support focus rather than diffuse it.

There is a concept called “clear to neutral” that captures this well — returning your workspace to a neutral state so that the next session can start fresh rather than starting in the aftermath of the previous one. People who do this consistently report that starting work feels easier because there is no inertia to overcome from what came before.

The Location Change

The second environmental lever is more dramatic but equally reliable: leave where you are and go somewhere else.

When the desk declutter is not enough — when the slump is deeper, or when you have been stuck in the same space for days — a location change can reset the state in a way that no amount of technique work can.

Coffee shop. Hotel lobby. Library. A different room. A park bench with a laptop. The specific destination does not matter much. The change of context is what does the work.

Brooks Duncan, who co-hosts The Productivity Show with me, has a dedicated garden office that is genuinely ideal for focused work. And he still goes to coffee shops regularly to write. Not because the office is inadequate — because the context switch is the point. Moving to a new space signals “we are in a different mode now” in a way that staying put simply cannot.

This is especially useful when you have a category of work that requires a different mental state than your default. Writing might need a different environment than strategic planning. Client calls might need a different setup than deep focused work. Using different physical contexts for different types of work trains your brain to associate those locations with those modes — and over time, arriving at the location starts to trigger the state automatically.

When to Use Each

Use the desk declutter when you are in a moderate slump and have not moved locations recently. It is the lowest-friction intervention and often sufficient for resetting focus within a work session.

Use a location change when the slump has persisted for more than a session, when you have been in the same space too long and the context has gone stale, or when you need a different quality of thinking than your usual environment supports.

Both work because they operate on the same principle: your environment shapes your internal state. Change the environment, change the state.

The Real Advantage Over Techniques

Most focus techniques require setup time and sustained willpower to execute. You have to remember to start the timer, resist the urge to check your phone when it buzzes, maintain the system across sessions. They work, but they have friction — and friction is what tends to make techniques not get used when you actually need them.

Environmental changes have low setup friction and work on their own. A clean desk does not require you to do anything after you have cleaned it. A new location changes your state whether you think about it or not.

That is why decluttering your desk is often a better focus hack than any technique: it is faster, it is free, and it works by changing the conditions rather than requiring you to override them through effort.

When you are stuck, change the environment first. The techniques will work better from there anyway.

One thing to try today: The next time you sit down to do focused work and cannot get going, spend five minutes clearing your desk before you try any technique. Remove everything that does not belong there for this session. Reset the surface. Then sit back down and notice whether the work starts more easily.

New campaigns to run. Content to update. Course improvements. Maybe a new offer.

But before I committed to any of it, I asked a different question first: what's already broken?

It's not a glamorous question. It doesn't generate excitement. But the answer, when I actually went looking, changed what I decided to prioritize.

What We Found

Here's what a real audit of a business that's been running for over a decade looks like:

Email sequences pointing to a domain we don't use anymore. Years ago we used ae-links.com for campaign links. We stopped using it. But we never went back through every email sequence to update the links. Every person who clicked those links hit a dead end — and we had no idea how many that was until we looked.

Landing pages that have been live for years with no traffic, no conversion, and no purpose. They're not hurting anyone directly. But they're being crawled and indexed as thin content, which doesn't help our SEO footprint.

Blog posts from 2015-2017 that used to rank. Some of them are now outdated on their facts. Some reference tools or strategies that no longer exist. Some are probably suppressing the newer, better content we've published on the same topics — Google sees both, and if the older one has more historical links, it might outrank the more accurate current version.

Automations that reference products we no longer sell. Sequences that were built for an old offer and never turned off. They're not sending (the triggers don't fire anymore), but they're still there creating confusion during onboarding.

None of this required any investment to accumulate. It's just what happens when you build for years and never circle back.

What Technical Debt Actually Costs

In software engineering, technical debt is the hidden cost of shortcuts taken in the past. A quick fix that worked at the time but now makes future work harder. Code that runs but nobody fully understands anymore. Systems built for an older version of the product that now slow everything down.

Businesses accumulate the same thing, but they don't usually have a name for it.

Every broken link in an email sequence is a conversion that didn't happen. Every outdated landing page is a credibility signal that's slightly off. Every automation built for an old product is a place where something can go wrong silently, without any error message or alert.

The cost is diffuse — no single instance of broken technical debt is catastrophic. But the aggregate is significant. And unlike a competitor outspending you or a market shift, it's entirely within your control to fix.

Why “Add More” Is the Wrong Default

The instinct when a business isn't growing the way you want is almost always to add something.

More traffic. More content. More ads. A new product. A better campaign.

Sometimes that's right. But often it's a response to symptoms rather than causes.

If your email sequences have broken links, running more traffic to your list just sends more people through a funnel that's leaking. If your old content is suppressing your new content in search, publishing more new content doesn't solve the structural problem. If your onboarding automation is broken, acquiring more customers just means more people hitting the broken onboarding.

Adding more builds on a cracked foundation. Fixing the foundation first means everything you add afterward actually works.

What Business Technical Debt Looks Like

Different types of businesses accumulate different kinds of technical debt, but the common categories are:

Dead or outdated content. Blog posts, landing pages, and resource pages that no longer reflect what you do, what you sell, or what's accurate. Especially costly for SEO, where outdated content can actively depress more current work.

Broken sequences and automations. Email sequences with dead links, automations that reference products you no longer sell, welcome sequences that mention old offers. These run silently in the background creating friction you're not aware of.

Orphaned infrastructure. Old domains, deprecated integrations, abandoned product pages, tools you're still paying for and not using. These aren't usually doing active damage, but they add overhead and confusion.

Stale positioning. Marketing copy, website messaging, and email templates written when you were at a different stage of business, for a different version of the offer, to a different version of your customer.

How to Do the Audit

The process is simple, though not quick:

Start with the most critical customer paths. What does a new lead experience from the moment they first interact with you? Sign up for the email list and go through every sequence as a new subscriber. Click every link. Find every dead end.

Audit your top pages. Which pages get the most traffic? Which have the highest exit rates? Pull up the top ten and look at them with fresh eyes — do they still reflect what you do and what you sell?

Check your automations. What's actively running? What was set up more than a year ago and hasn't been reviewed? What references products or offers that no longer exist?

Look at your oldest content. For any content that's more than two years old and still indexed, ask: is this accurate? Is it working for or against the content strategy you have now? Should it be updated, redirected, or archived?

The goal isn't to do this all at once — that's its own project. The goal is to make one pass, identify the biggest leaks, and fix those first.

The Compound Return on Cleanup

Here's what made the Q1 cleanup priority click for me: if we fix all the broken things and do nothing else, the business still grows.

Fewer dead ends in email sequences means better conversion from the existing list. Better content hygiene means our newer posts rank instead of being cannibalized by older ones. Cleaned-up automations mean fewer people falling through gaps silently.

That's growth that doesn't require a new campaign, a new product, or a new audience.

Most Q1 plans are full of new initiatives. This one started with the question: what do we already have that we should actually finish?

Fix before you build. The returns on cleanup compound quietly — and they're almost always higher than the returns on the next new thing.

One thing to try this week: Pick one critical customer path in your business and walk through it as a new customer. Sign up for your email list. Go through the welcome sequence. Click every link. Note every place where something is broken, outdated, or confusing. That's your cleanup list.

Visit www.asianefficiency.com for more productivity tips and tactics.

For problems worth solving go to Claude.ai/tps.

Listen to this episode (MP3)

Links

• Claude.ai/tps
• 25X Productivity Coaching
• Pomodoro Technique
• TEA Framework
• SXSW
• Clearing to Neutral

If you enjoyed this episode, follow the podcast on Apple Podcasts, Spotify, Stitcher, Overcast, Pocket Casts or your favorite podcast player. It’s easy, you’ll get new episodes automatically, and it also helps the show. You can also leave a review!

A few years ago that would have sounded like a bad idea — a small business owner abandoning their accounting software for… what exactly? Now it sounds like a calculated move.

Here's what he's doing instead: keeping all his transactions on a local server and using AI prompts for any analysis or reporting he needs.

“What was our ad spend in November and how much revenue did it generate?”

“Which clients are trending down this quarter?”

“What's our margin by product line for the last six months?”

QuickBooks can't answer those questions in a conversational way. You'd need to know which reports to run, which filters to apply, and then interpret the output yourself. With AI and raw transaction data, he just asks.

So he stopped paying for QuickBooks.

Why This Is Happening

The software categories most exposed to AI disruption share a common characteristic: their primary value is providing structured access to your own data, or generating outputs from templates you could replicate with a good prompt.

Jasper was one of the early casualties. It launched as an AI writing tool that charged a significant monthly subscription for generating marketing copy. When OpenAI introduced custom GPTs, a lot of people realized they could build a “Jasper” for their specific brand voice and use case for basically nothing. The subscription evaporated.

The same logic is now spreading to other categories. When AI can replicate what the software does — and often answer questions the software was never designed to handle — the subscription becomes harder to justify.

Which Tools Are Most at Risk

Single-function reporting tools. Any software whose main job is to slice and display your existing data in a particular format is vulnerable. You don't need a dedicated tool to query your data if AI can query it directly.

Template-based content generators. Tools that charge to generate variations of a specific content format — social captions, email subject lines, ad copy — have been among the first to lose customers to custom GPTs and Claude. The underlying generation is now a commodity.

Simple workflow automation with no native integrations. Tools that charge primarily for their automation logic, without deep integrations or proprietary data, are increasingly replaceable by AI agent builders.

Specialized research or analysis tools. Tools built to process a specific type of document or answer a specific type of business question may be replaceable by a capable AI model with the right prompt and access to your data.

Which Tools Aren't Going Anywhere

Core infrastructure with compliance requirements. Accounting systems used for tax compliance, payroll platforms with legal obligations, systems that need to produce auditable records — these aren't going anywhere. Compliance isn't a prompt problem.

Deep integration hubs. Software that serves as the hub connecting your entire stack — a CRM with deep integrations across your sales, marketing, and service tools — is harder to replace because the value is in the network, not just the features.

Specialized tools with proprietary data or networks. Software where the value is the data inside it (industry databases, market intelligence, professional networks) rather than what it does with your data is in a different category.

Communication and collaboration infrastructure. Email, messaging, and video conferencing are table stakes — they're not being replaced by prompts.

How to Audit Your Own Stack

Go through your active software subscriptions and ask two questions about each one:

1. Does this tool primarily help me get structured access to my own data?

If the answer is yes, and your data could be exported and made accessible to an AI model, there's a case for evaluating whether a custom solution could replace it.

2. Does this tool generate outputs I could replicate with a well-crafted prompt?

If the main deliverable is a type of content, summary, or analysis that AI can produce, the standalone subscription is worth questioning.

For the tools that fail both tests — infrastructure, compliance, network-value software — keep them. For the ones that pass, the question is whether building or prompting is worth the effort compared to the subscription cost.

A commercial real estate firm I worked with uploaded their ledgers and balance sheets directly to Claude Code and started asking it to identify issues and build financial models. What used to take days of manual analysis now happens in minutes. That's not a special case — it's a preview of how a lot of specialized business tools will get displaced.

The Skill That Matters Now

Knowing which tools to question is becoming a real competitive advantage.

The businesses that are paying full price for mid-tier software that AI has made redundant are subsidizing a slow transition. The ones doing the audit and rebuilding the tools worth replacing will have lower overhead and more flexible infrastructure.

This isn't about eliminating software. It's about understanding what the software is actually doing, and whether AI can do that thing better, cheaper, or on terms you control.

Start with your smallest subscriptions. Those are the easiest to experiment with. Find one tool where most of the value is “it organizes my data so I can query it” — and see what happens when you move that logic into a prompt.

One thing to try this week: Open your subscriptions list and find one tool that primarily summarizes, reports on, or generates content from data you already own. Export a sample of that data and ask an AI model the question you'd normally use the tool to answer. See how close it gets.

It's not that the habit doesn't deliver. The weekly review is one of the most consistently high-value practices in productivity — a dedicated window to step back, review the previous week, and set clear intentions for the next one. People who do it regularly report feeling more in control, less reactive, and more aligned with what actually matters.

The problem is how people start it.

The Classic Failure Pattern

You discover the weekly review. Maybe through GTD, maybe through a productivity book or podcast. You find a detailed template — capture review, calendar review, project list review, someday/maybe list, the works. It looks thorough and compelling.

You commit. First week: done, felt great. Second week: you do most of it. Third week: something came up on Sunday, you moved it to Monday, it didn't happen. Fourth week: “I'll restart next month.”

This isn't a willpower problem. It's a design problem. You started with the advanced version of a habit before the habit existed.

Three Rules for Making It Stick

There are three things that reliably determine whether a weekly review habit survives its first month:

1. Same day, same time, every week.

Consistency of schedule matters more than the specific day you choose. I do my weekly review on Sundays at 6 PM. Not because Sunday is inherently better than any other day — because having a fixed anchor removes the weekly negotiation with yourself.

When the time is variable, you spend energy every week deciding when to do it and then defending that decision against competing demands. When it's always Sunday at 6, there's nothing to decide. It just happens.

GTD traditionally recommends Friday afternoon. For most people, that's actually one of the worst times — the week has wound down, energy is low, and the next week feels abstract. Sunday evening before the week begins works better for most. But the right answer is whatever you'll actually do consistently.

2. Have a checklist.

The checklist serves two functions: it removes the cognitive overhead of figuring out what a weekly review involves, and it gives you a clear endpoint. You're done when you've gone through the list.

A good starting checklist is short. Three to five items:

• Clear your inbox (email and physical)
• Review last week's calendar: what happened, what didn't, what do you want to capture?
• Review the week ahead: any conflicts, prep needed, decisions required?
• Review your project list: anything that needs to move?
• Set your top three priorities for the week

That's enough. You can add more later.

3. Start with 15 minutes and build from there.

This is the one most people get wrong.

The version of the weekly review you see described in productivity books is not your starting point. It's what the habit looks like after months of consistent practice, when you've refined it to match your specific work and life context.

Starting with an hour-long weekly review is like deciding to run a marathon because you want to get in better shape. The goal is legitimate but the starting point guarantees failure.

Start with 15 minutes. Set a timer. Run through your short checklist. Stop when the time is up, even if you're not done.

What you'll find: after a few weeks of consistent 15-minute reviews, you'll start adding things naturally. A question you wish you'd answered. A section you want to include. The review gets a bit longer — but by then the habit is embedded, and longer doesn't feel like a burden. It feels like evolution.

The Kaizen Parallel

Paul Akers, who popularized lean thinking for small businesses, teaches what he calls “two-second lean” — the idea that making tiny, consistent improvements, even ones that save you just two seconds, compounds into extraordinary efficiency over time. The key word is consistent. A two-second improvement made every day for a year is worth far more than a ten-minute improvement made once.

The weekly review follows the same logic. A 15-minute review done every week produces dramatically more clarity and control than an elaborate hour-long review done twice a year. Frequency beats depth, especially at the start.

The habit is the leverage point. Get the habit first. The depth comes after.

What the First Few Months Look Like

Weeks 1-4: 15 minutes, same time, short checklist. Focus entirely on consistency. If you miss a week, don't try to “catch up” — just do the review for the current week.

Months 2-3: You'll notice gaps — questions you wish you'd reviewed, areas of your life that keep getting ignored. Add one or two items to your checklist.

Months 4-6: The review feels natural. You may find it extending to 20-30 minutes because there's more you genuinely want to cover. You're building the version that fits your life, not implementing someone else's template.

After six months of consistent practice, most people report that missing a weekly review feels noticeably disorienting. That's the signal that the habit has taken root.

One thing to try: Block 15 minutes on your calendar for this coming Sunday at a time you'll actually use. Open a blank note or doc. Write down three questions: what happened last week, what's coming next week, what needs to clear or move. Answer them. That's your first weekly review. Build from there.

It is a real concern. Understandable. Every headline seems to confirm it.

But I have been working inside real businesses for the past year — a CPA firm, a commercial real estate company, a hair salon, a nonprofit — and what I have watched happen is almost nothing like the story that gets told.

Nobody Got Fired

Not a single client I have worked with has fired someone because of AI.

I want to be clear about that because it is not what you would expect from the discourse. People talk about AI like it is a wave of layoffs waiting to happen. In practice, the businesses I have seen are asking a different question: not “how do we cut headcount” but “what can we now do with the team we already have?”

The honest answer: a lot more.

Typically what happens is that people get reskilled. They learn a tool, they build a workflow, and over a few weeks they become meaningfully more capable at the work they are already doing. Two or three times more productive is not an exaggeration — that is a number I have seen come up repeatedly.

The Real Thing That Changes: The Hiring Plan

Here is the shift nobody talks about.

When a small business adopts AI well, they do not fire the people they have. They stop hiring the people they were going to hire.

I had a client, Amanda, who runs a CPA firm. She had been trying to fill two roles for months. After we built AI into her inbox and some of her team workflows, she stopped interviewing. The people she had could now handle the volume she had been trying to solve for with new hires.

She was not thinking about reducing her team. She was thinking about growth — more clients, more services, same-sized team.

That is the actual story. Not fewer jobs, but different math around growth.

The Change Management Part Is Real

Getting there is not frictionless.

Amanda's lead accountant had been doing everything manually for over 20 years. She was resistant when we first started. That makes sense — when your identity and your expertise are tied up in a way of working, something that replaces that method can feel like a threat.

The thing that changed was not the tool. It was the framing.

Amanda stopped presenting it as “this is replacing how you work” and started presenting it as “this is getting rid of the boring parts so you can focus on the work that actually requires your judgment.” That landed.

Her lead accountant is now one of the biggest advocates on the team.

This is the part most AI adoption plans skip: the people side. You can build a technically perfect workflow and have it sit unused because nobody trusts it or understands it. You can get someone deeply resistant to come around when you take the time to frame the change in a way that does not feel like an attack on their value.

What I Tell Clients Who Are Worried

If you are an employee wondering whether AI is coming for your job: the businesses I have watched closely are not trying to eliminate your role. They are trying to eliminate the parts of your role that nobody actually likes doing.

The manual data entry. The inbox triage. The same email you have written 300 times. The report that takes three hours to produce and 10 minutes to read.

If those things get automated, what is left is the work that actually required you in the first place.

If you are a business owner worried about what AI means for your team: start with the boring stuff. Look for the work that nobody enjoys, that does not require judgment, that just needs to happen consistently. That is where AI earns its keep. That is where you will free up capacity for the things only humans can do.

The three-level framework I teach in workshops applies here — AI Assisted (using chat tools to speed up existing work), AI Workflows (automating repeatable tasks), and Building Agents (deploying AI that runs on its own). Most teams start at level one and find that alone creates enough capacity to defer planned hires indefinitely.

The Short Version

You are probably not going to lose people to AI.

You are going to lose the parts of the job everyone hated. And the business is going to find it can grow without adding as many people as it thought it needed.

That is different from the story you are hearing. But it is what I have watched happen.

If you want to see what this looks like in practice: The Productivity Academy has workshops on building your first AI workflows — starting with the ones that free up your team first. Worth checking out if you are ready to stop theorizing and start building.

New project means new folders. More clients means more apps. Bigger team means more channels and labels and categories.

The instinct makes sense. More stuff going in means you need a bigger system to hold it.

But it backfires. And the more complex your work gets, the more it backfires.

Why Added Structure Compounds

The problem with adding organizational layers as complexity grows is that the complexity compounds.

Every new app is a new place to check. Every new folder category is a new decision point when you're trying to file something. Every new label system requires you to remember the system before you can use it.

At some point, you're not managing your work anymore — you're managing the system you built to manage your work.

The overhead of navigation starts eating into the time you're trying to save. You spend ten minutes looking through five different tools to find a document you know you saved. You pause every time you want to file something because you have three plausible homes for it and can't remember which one you decided on last time.

More structure creates more friction. And friction is what kills productivity.

The Counterintuitive Principle

The rule I came back to, after years of adding and then simplifying: as your world gets more complex, your organization should get simpler.

Not more elaborate. Simpler.

What does that actually look like? One place per type of thing. Not five options that all seem reasonable — one.

For me, it looks like this: 80% of my working files live in Google Drive. Whatever's in Dropbox now is archival stuff from years ago that I haven't touched since. Active work documents, notes, transcripts — all in one place, named consistently, searchable.

Not because Google Drive is perfect. Because one searchable location beats five perfectly organized locations.

When everything has one clear home, the filing decision disappears. You don't deliberate about where to put something — you put it in its place. You don't search across five tools — you search one. The overhead drops. The system becomes transparent.

The Rule That Makes It Click

The organizational principle that simplified everything for me: every type of thing has one home. Not two, not “it depends” — one.

Working documents go in Drive. Tasks go in the task manager. Transcripts go in the transcript folder.

When something has five possible homes, it effectively has none. You waste time deciding where to put it, then you can't find it later because you can't remember which of the five places you chose. The abundance of options creates decision overhead on the way in and search overhead on the way out.

The constraint of one forces clarity. You decide once where this type of thing lives, and then you never think about it again.

The New Reason This Matters

The original argument for simple, consolidated organization was always about you: fewer places to look, less time navigating, less mental overhead.

That argument still holds. But there's a second reason now that most people haven't considered yet.

Your AI tools need to find your files too.

When you build agents — meeting prep tools, weekly synthesizers, content systems — they need to retrieve files from your storage. An agent that can't find the files it needs either fails silently or produces poor output. Scattered files across multiple platforms with inconsistent naming mean your agents are working with incomplete information.

Consolidated, consistently named files in one accessible location mean your agents can actually do their jobs.

Organization used to be something you did for yourself so you could find things. Now it's infrastructure for every tool you put on top of it. The better your foundation, the better everything running on it performs.

What to Simplify First

If your current system has accumulated too much structure, the first move is consolidation, not reorganization.

Pick one place for active working documents. Everything in that category moves there — not renamed, not reorganized, just moved. Search will do most of the work of finding things once they're all in one place.

Do the same for each type of thing you regularly work with: tasks, notes, transcripts, reference material. One location each. If you're torn between two places, pick one and commit.

The goal isn't the perfect organizational system. It's the simplest one that you'll actually maintain — where things reliably have one home and you can find them without thinking about it.

The world keeps getting more complex. The response isn't to match that complexity in your organization. The response is to simplify the container, so the work inside it has room to breathe.

One thing to simplify this week: Pick one category of files or documents you work with regularly (notes, working docs, transcripts, etc.) and identify the single best home for it. Move everything in that category there. The consolidation itself will be faster than you expect, and finding things will get immediately easier.

I'd built a good network over the years in other places, but I was starting over in a new city. I knew maybe three or four people here. And I did what most people do when they want to meet more people: I started going to events.

Meetups. Industry happy hours. “Networking” events with name tags and terrible appetizers. I went to a lot of them. I met people. I handed out cards. I had follow-up coffees.

And after a year of this, I still felt like I didn't really know anybody.

Something wasn't working.

The Moment I Flipped It

Back in 2017, I tried something different. Instead of attending other people's events, I decided to host my own.

Small dinner parties. Jeffersonian-style — eight people around a table, where everyone can actually hear each other and have a real conversation. I was deliberate about the invite list: one or two people I knew well, a few I'd recently met and found interesting, and usually one or two I'd just barely met but had a good feeling about.

No agenda. No pitching. No structured “networking” activity. Just dinner and conversation.

I did this pretty much every other week for two years. That's about 50 dinners.

And what happened over those two years surprised me.

What Actually Happens When You Host

The first thing I noticed: people who came to my dinners started introducing me to others. Not because I asked them to. Just because, when someone asks “how do you know Thanh?” and your answer is “he hosted this incredible dinner,” it creates a story. People share that.

Then the connections between guests started happening. A woman came up to me at one of my events and said, “Thanh, I met my co-founder here at your dinner last year. We're building something that's already helping hundreds of people.”

I had no idea that dinner would lead to that. I just thought I was cooking for some people.

That's the thing about bringing people together… you never know what sparks will fly when two people sit next to each other. Sometimes it's a co-founder match. Sometimes it's an investor for a startup. Sometimes it's just a friendship that becomes something else years later.

But here's what I know for sure: none of those connections would have happened if I'd just been another attendee at someone else's event.

Why Hosting Works Better Than Attending

There's a psychological shift that happens when you host instead of attend.

When you attend, you're there to get something — contacts, opportunities, maybe a job lead. Even if you're not aware of it, that energy comes through. People can feel it. And it makes real connection harder.

When you host, your job is to make sure everyone else has a good time. That completely changes how you show up. You're asking questions because you genuinely want to know who people are so you can connect them with the right people. You're listening more than talking.

And here's the practical piece: as the host, you become the connector by default. You know everyone in the room. Every new person who walks in gets introduced through you. You're the node that everyone passes through.

That's how I got the nickname “the human router.” Not because I was especially brilliant at networking. Because I kept putting myself at the center of a room I created.

You Don't Need to Go Big

I want to be clear about the scale here. These weren't fancy catered events. They were dinners in my apartment. Eight people. Food I cooked or ordered in. A good table and decent wine.

The most important ingredient was curation. I was thoughtful about who I invited and why. I'd think about which two people in the room would really hit it off and make sure they ended up next to each other.

That level of intention — even at small scale — is what made people want to come back. And want to bring their friends.

Over those two years, my network in Austin grew from a handful of people to founders, investors, operators, advisors, and friends I talk to every week. The consulting clients and partnerships that define my business today trace back to connections made at those dinners.

A Different Way to Think About It

There's a broader lesson here that goes beyond networking.

When I travel to Vietnam — where my family is from — I'm always struck by the people who have almost nothing and seem completely at peace. One time I sat in an alleyway with a family friend's family, eating outside, cooking together. They were living on maybe $400-500 a month to support the whole family.

And they were genuinely happy.

Meanwhile there I was, stressing about business, stressing about my network, stressing about all the things that felt urgent.

That contrast stuck with me. The dinners I was hosting in Austin weren't just networking events. They were a way of slowing down, being present, and actually connecting with people. Not “growing my network” in the abstract but just… having real conversations over food.

That's the part that made it work. You can't fake that.

What to Try This Week

If your network feels stale, or you're new to a city, or you just feel like you're meeting people but nothing's sticking… try this.

Host one dinner. Invite six to eight people. Some you know well, some you barely know. Cook something or order in. No agenda.

Just create the space and see what happens.

You don't need a big list of contacts for it to work. You just need to start. The first dinner leads to the second. The second leads to the third. And somewhere around the twentieth or thirtieth, you look up and realize you know everybody.

If you want a system for managing the relationships that come out of this, our weekly review process has a section specifically on relationship maintenance. It's one of the most underrated parts of the whole system.