Fix My Business

Meet Arlo: 5 Ways I'm Using an AI Agent Across My Businesses

Arlo Zephyr is Scott's first AI agent. Built on OpenClaw. Named by Scott's wife. Last name comes from Zephyr Hills, Florida. Tool vs. Team Member: Most people think of AI as a tool—ready to use like a hammer. Scott treats Arlo as a team member. That means onboarding, training, watching limitations, and bringing in humans when needed. "It's going to be terrible in the beginning." The 5 Use Cases: 1. Morning Brief Arlo aggregates revenue from multiple sources, delivers metrics, and stops the obsession of checking email for every sale notification. "Disney isn't getting an email every time someone swipes a card. Revenue is expected." 2. Email Distribution Arlo pulls data, compiles newsletters, formats HTML, and schedules emails. Freed up ~10 hours/week for the team to do other things. 3. Customer Account Analysis (Land Moto) Arlo reviews customer listings, identifies improvement opportunities, and feeds research to humans who reach out. This is a new capability—work that wasn't being done before. 4. Phone Calls (Testing) Early experiments with inbound and outbound calls. Results are mixed. "I called a restaurant, talked to an AI, and asked for a human." It will get better, but it's not there yet. 5. Cold Email Outreach (B2B) Arlo identifies 20-30 leads/day, does research, and explains why each is a fit. Humans review and send. The temptation is to let it run wild—don't. Human in the loop. Key Insight: "Capability" is the word. Adding Arlo is like adding a team member—you gain new capabilities the organization didn't have before. Human in the Loop: Repeated throughout. AI makes things up (hallucinations). Humans must review before sending. Connection to SCALE: "I scoped it. I clarified the flow. I built one use case, watched it, and added more when comfortable." The framework enabled Arlo. Your Action: Think about one task you could use an AI agent for. Map it out with SCALE. Then figure out how to turn it into an automated agent. Bonus — Edward: Scott's new daily micro-parables on Substack. Edward is a composite of every business owner. Follow at scotttodd.net/blog [http://scotttodd.net/blog]. Got a business question? Ask Scott here: scotttodd.net/ask [https://www.scotttodd.net/ask]

Build Session: Applying SCALE to a Real Lead Response Process

Scott walks through a live build session with Chad Coffman, a land investor whose lead system broke when volume spiked. Instead of stopping production or ignoring the problem, Chad triaged it—kept moving, documented the friction, and circled back when he had time. The friction: Leads were coming in faster than they could respond. Responses were delayed by weeks. The process was manual, inconsistent, and overwhelming. Applying SCALE: S — Scope the Solution: Not the entire sales process. Just the initial lead response. One play, not the whole game. C — Clarify the Flow: * Email comes in (trigger) * AI triages the email * AI pulls from knowledge base (county rules, property info, zoning) * AI drafts response * Human reviews and approves * Response sent via customer's preferred method (email, text) * Human uses newfound time to strengthen the knowledge base A — Automate the Trigger: Four types of triggers: event, time, condition, manual. Manual is the worst—requires memory. In this case, the trigger is an event: lead submission. L — Leverage the Data: Plan for failure. How do you know if the email didn't arrive? How do you know if AI failed? Build in regular human checks. Start with humans overseeing, then automate the oversight later—that's a separate play. E — Elevate the Experience: AI should sound like Chad and Cindy, not a robot. Build a voice guide. Create feedback loops so AI improves over time. Make sure error messages are human-readable, not "Signal 19." Key insights: * "We're not trying to boil the ocean. We're running one play." * "The time you gain from automation is shifted—use it to strengthen the knowledge base." * "If you just threw a person into your business with no training, that's what throwing AI at something looks like." * "There will be a competitive advantage to dealing with a human instead of a robot." The 40-minute investment: Planning the framework before building saves you from building the wrong thing. Your action: Pick one friction. Apply SCALE. Scope it to one play. Clarify the flow before you touch any tools. Got a business question? Ask Scott here: scotttodd.net/ask [https://www.scotttodd.net/ask]

Clarify the Flow: How to Audit a Process Before You Automate

Most people see a broken process and think "I'll automate it." That's a mistake. You're locking in the problems—baking in the traps, the patches, the operational debt. It's like a blown car speaker. Turn up the volume and you amplify the distortion. Automation amplifies whatever is already there—good or bad. Clarify the Flow isn't just "document the process." It's about seeing the REAL process. There's a difference between how you think people work and how they actually work. Have them record themselves. Watch with your eyes. Walk through each trap: Control Trap: Where does work get stuck waiting on someone? Is the approval necessary? Can you build in thresholds? The Ritz-Carlton $2,000 story: Any employee can spend up to $2,000 to solve a guest problem. A couple lost a wedding ring on the beach. Five employees bought metal detectors, found the ring, delivered it at breakfast. The husband called local news. Free publicity—because they removed control. Variability Trap: Does the output depend on who does it? Is there a defined standard for success? Memory Trap: Does someone have to remember? Can you add an automated trigger instead? Visibility Trap: Do you have the data to know if it's working or failing? The three questions before automation: 1. Should this step exist at all? (Sometimes the best automation is deletion) 2. Can it be redesigned to remove the trap? 3. Only then: Can it be automated? Automation is the last decision, not the first. Even Elon Musk says automate last. The goal isn't to replace humans. It's to amplify their output. Plan for handoffs between human and machine. Anytime there's a handoff, traps hide there. C comes before A in SCALE for a reason. Clarify first, then automate. Skipping C is how you amplify chaos. Your action: Pick one process you're thinking about automating. Map it out. Walk through the four-trap audit. For each step: eliminate, redesign, or automate—in that order. Next episode: The build session. Watch Scott take a real process through the entire framework. Got a business question? Ask Scott here: scotttodd.net/ask [https://www.scotttodd.net/ask]

The Traps Never Leave (And Why Patches Make It Worse)

The four traps—Control, Variability, Memory, Visibility—never go away. You can minimize them. You can manage them. But you can never fully eliminate them. They're baked into every process. When business owners see a trap, their instinct is to patch it. Add a checklist. Add an approval. Add a reminder. Add a review. But patches don't fix traps. They create operational debt. The bathroom checklist example: A checklist that requires someone to remember to use it is a patch on the Memory Trap... that itself has a Memory Trap. The checklist didn't solve the problem. It just moved the problem. Patches are workarounds disguised as systems. * Memory Trap → checklist, reminder, calendar invite * Control Trap → approval step, sign-off * Variability Trap → review, quality check * Visibility Trap → report, dashboard Operational debt is like financial debt but not on your balance sheet. Research shows it can cost up to 25% of your revenue. Every checklist, approval, review, and dashboard adds weight. Operational debt creates three types of drag: 1. Speed (every patch slows things down) 2. Confusion (new employees can't figure out the buried system) 3. Brittleness (patches don't adapt; changes break them) The alternative isn't more patches. It's seeing the traps for what they are. Patching is reactive—you see a problem, you slap something on it. Managing is intentional—you ask: Can I remove this step? Can I redesign so the trap doesn't exist? Can I automate so humans don't have to remember? "Patches add to the process. Managing subtracts from it." "Remove before you automate. Simplify before you systemize." If you automate a trap without fixing it first, the trap gets amplified. Now you have faster, more consistent chaos. The key insight: Seeing the traps is the advantage. Once you see them, you can't unsee them. You're not seeking perfection. You're seeking awareness. Your action: Find one patch in your business. A checklist nobody uses. An approval that's rubber-stamped. A report nobody reads. Ask: Is this solving the problem or just moving it? Next episode: How to audit a process before you automate—Clarify the Flow. Got a business question? Ask Scott here: scotttodd.net/ask [https://www.scotttodd.net/ask]

The Visibility Trap: Why the Data You're Missing Is More Dangerous Than the Data You Have

Why do your customers buy from you? Not what you think—why do they actually choose you? Why do your employees work for you? What do they actually think? If you hesitated on either question, you're in the Visibility Trap. Scott shares the story of David—a business owner with perfect financials who watched revenue drop 30%. He cut costs, adjusted pricing, ran promotions. Nothing worked. Finally, he called his customers. They didn't buy because of his product. They bought because of Maria—one employee who made them feel taken care of. Maria left six months earlier. David barely noticed. His customers noticed. One by one, they left. The Visibility Trap shows up in three blindspots: 1. Financial data (margins, cash flow, CAC, LTV—not just revenue) 2. Customer data (why they buy, stay, leave) 3. Employee data (why they work here, what they think, what would make them leave) The diagnostic question: Do I have the data I need to make this decision? Why it's the most dangerous: The Visibility Trap is the meta-trap. It hides the other three. You can't see the Control Trap until someone burns out. You can't see Variability until a customer complains. You can't see the Memory Trap until revenue disappears. The uncomfortable truth: You might prefer not to see. Visibility means accountability. "Ignorance feels easier. But that's not leadership. That's hiding." The three-part escape: 1. Identify your blindspots (list the questions you can't answer) 2. Build feedback loops (surveys, check-ins, dashboards, conversations) 3. Look at what you don't want to see The key insight: "The data that makes you cringe is usually the data that matters most." Connection to SCALE: L = Leverage the data. Visibility isn't just collecting data—it's using it to make decisions and building alerts for failures. The truth about all four traps: They never go away. They exist in every process. Once you see them, you can't unsee them. And that's half the battle. Next episode: How to find the traps before you automate—because automating the traps amplifies chaos. Got a business question? Ask Scott here: scotttodd.net/ask [https://www.scotttodd.net/ask]