Andrea started her business 10 months ago as a side hustle. She thought she'd be further along. More revenue. More profit. Less time. She's considering quitting.

The wall is real. Around 9-10 months, the initial excitement burns off. The wins don't come fast enough. The inner voice says: call it a day.

Scott almost tapped out at nine months. If he had, he'd be in a corporate job today.

It's physics, not failure. Starting a business takes rocket launch energy. A side hustle splits that energy three ways: day job, family, business. If you're launching on a third of the fuel, the timeline is longer. Give yourself grace.

There are no bad goals. There are unrealistic time horizons. If you thought you'd be out of your job in a year, make it three. The goal isn't wrong. The timeline was.

The 30X training rule: If a task takes an hour a week, be prepared to spend 30 hours training someone to do it.

The control trap kills side hustlers. You only have a few hours. If you spend them running everything, you'll never get leverage.

When you're feeling defeated, stop. Look at your tasks. Is it $10/hour work or $1,000/hour work? If it's $10/hour, it's not meant for you.

The J-curve: Profitability dips when you hire. Then it rises. That's the trade.

The ones who break through aren't working harder. They're letting go of work they were never intended to do.

Congratulations. You are right on schedule.

Got a business question? Ask Scott here: scotttodd.net/ask

Josh writes: "I keep writing ads but I'm not getting leads. I've hired people. Tried different headlines, different platforms. My team says the ads are good. But no leads."

The diagnosis: You're writing to everybody. Which means you're writing to nobody.

The market is always talking to you. View counts show people are seeing your ads. If they're not converting, the audience is telling you something. The question is whether you're listening.

The Visibility Trap: When you don't understand your customer, you manage with your gut. And your gut is often wrong. You lack data on who your customer actually is and what problem they're trying to solve.

8 billion narratives: Everyone walks around with a story in their head. Your job is to match your message to one of those stories.

The fishing metaphor: Pick one problem. Write to that problem. If nobody responds, that's not the bait they want. Try another problem. Keep fishing until something bites.

Scott's ATV story: Didn't know why people wanted land in one area. Discovered buyers wanted to ride ATVs. Started writing to that. More ATV people came. Applied the same approach in Nevada—asked a truck driver why he was looking for land. Used that intelligence. It compounds.

The fix—four questions before you write:

1. Who is this for?
2. What do they believe?
3. What are they afraid of?
4. What words do they use?

When you put those four elements into your copy, more people like that begin to respond.

Got a business question? Ask Scott here: scotttodd.net/ask

Business owners are wasting massive amounts of time building AI agents when they should be figuring out what their business actually needs.

Scott isn't anti-agent—he has them in his business. But there's an untold tax: onboarding, maintenance, troubleshooting. In small businesses, guess who does it? You.

The Easter Weekend story: Anthropic changed their terms. 3pm Saturday, Scott's OpenClaw stopped working. He spent Easter weekend switching to ChatGPT. His wife was not happy.

The hidden burden: Every new OpenClaw release broke what he'd already fixed. Nights and weekends troubleshooting. Time spent with AI agents is time not spent with the team.

Digital dust: The AI is producing outputs Scott doesn't have time to review. It's not being used. It's digital dust.

The new default: When work needs to come off Scott's plate, the desire is to give it to AI. But his default now is to give it to a human. A VA can be onboarded in 48 hours. An AI agent might take 100+ hours of teaching, testing, and overseeing.

Humans first: Humans allow you to pressure test processes. They know if something's working. They can find a better way. If a process doesn't work with humans, it won't work with AI agents. You're just automating chaos—and chaos amplifies.

The broken speaker: Turn up the volume on a broken speaker and the distortion gets louder. Apply AI to broken processes and the chaos happens faster.

The close: If you've been putting off the AI agent thing because something feels off—trust that instinct.

Got a business question? Ask Scott here: scotttodd.net/ask

Two scenarios: Your team won't stop asking questions. Or you're solo and think this doesn't apply. It does.

The nine-year employee story: A longtime team member messages: "I gave a refund, they got rebuilt. What happened?" Scott's response: "I don't know. Check with the back office team." The reply: "But you've always been the one that knew."

True. But if Scott jumps in, he deprives the team of the ability to learn. It took every amount of restraint not to swoop in. But that restraint is what allows growth.

The capability ceiling: Your business will only rise to the capability of your weakest team member. Every time you answer a question you shouldn't, you pull yourself down and limit the team's growth.

The ego trap: "It's gonna feed my ego—'man, they still need me.' But my team didn't grow. They're still reliant on me. And that means the business is reliant on me forever."

The tactic: Act like you don't know, even if you know. Redirect. "I don't know. What do you think?"

Virtual assistants: We hire them for one task and never explore their full capability. One of Scott's VAs was massively underutilized—until he got to know them.

The football analogy: Your quarterback should be the kicker. Your wide receiver should be the quarterback. You have talented people in the wrong positions. Strong team, no wins.

The solo-preneur trap: "I tried hiring. The people weren't any good. Nobody wants to work." Maybe true. But Disney has 60,000 employees. They didn't magically find 60,000 perfect people. They invested in a process that brings people to standard.

Choose Your Own Adventure: Every decision turns a page. Each choice moves you closer to your goal, keeps you sideways, or pulls you back. The question: Which adventure are you writing?

Got a business question? Ask Scott here: scotttodd.net/ask

The paradox of business ownership: infinite choices, finite time. Every decision changes the trajectory of your business. Most business owners don't have a filter.

Scott's filter: Would me in five years from now appreciate that I spent time on this today?

The time allocation problem: You're the cheapest person you can hire, so you end up doing $10/hour work. But you can't make $1,000/hour if you're spending time on $10/hour tasks.

The Realtor study (National Association of Realtors):

• 31% running errands
• 29% social media
• 19% admin
• 18% email
• 3% client-facing activities

Time allocation doesn't match desired results.

Leverage or labor? That's the question.

Opportunity selection: Shiny object syndrome is real. Every week Scott gets 2-3 pitches. "Maybe I should start an AI company." It's easy to chase. You have to say no—even when you don't want to.

"Pick my brain?" I give it away for free every day. You have it.

Future me wants fewer and better bets. Not scattered everywhere. Consolidated efforts aligned with skill sets.

Daily decisions:

• Could that meeting have been an email?
• Is that urgent project actually a distraction in disguise?
• Focus on what your business needs next.

Strategy isn't a master document. It's the decisions you're making and the trade-offs you're prepared to make.

The inversion: The filter also reveals what you SHOULD be doing. What would future me run back into the past and give me a hug for?

Before starting any task: Pause. Would future me appreciate this? If the answer is no or "I don't know"—that's your signal.

Edward: Scott's daily Substack character—a composite of every business owner facing these same challenges. Free at scotttodd.net/blog.

Got a business question? Ask Scott here: scotttodd.net/ask

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.

Got a business question? Ask Scott here: scotttodd.net/ask

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

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