Edward asks: "I spent months documenting our processes in Notion. The problem? My team ignores them and asks me the same questions over and over. How do you actually get people to use the systems you build?"

In this episode, Scott calls out Edward's hidden control trap (you're still getting an ego boost from being the answer), explains why people flow to the path of least resistance, and shares the "I don't know" technique that stopped his team from treating him like a human AI. You'll learn why going from knowing everything to knowing nothing is the key, and when ignored SOPs actually reveal a staffing gap.

The bottom line: Stop being the easiest answer. Say "I don't know." Your team will start using the systems when you stop being the path of least resistance.

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

Emily asks: "We're doing a quarterly audit of our subscriptions and our software bills are absurd. There are features we never use but some we do at the premium level. How do we cut our software bloat without breaking the operation?"

In this episode, Scott exposes the "software moat" (how SaaS companies trap you in premium plans), shares his access rules and 45-day login audit policy, and tells the Hertz cell phone story about finding zero-minute phones still on the bill. You'll learn the "cut, cut, cut—add back" mantra, how to handle vendor fear tactics (sunk cost fallacy), and why mapping your workflows is essential before you cut anything.

The bottom line: Cut, cut, cut—add back if needed. Audit logins. Map workflows. Don't let fear keep you paying for tools you don't use.

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

Ryan asks: "What should I automate first in my business? And what is the biggest automation mistake?"

In this episode, Scott kills the "silver bullet" myth, shares the pain point rule and his VP whiteboard story, and reveals the A-to-C framework for micro-steps instead of trying to automate everything at once. You'll learn why elimination comes before automation, the three biggest automation mistakes (not mapping process first, choosing tools before process, automating chaos), and why you're not actually getting left behind in the AI race.

The bottom line: Find the pain point. Eliminate if possible. Map the process. Micro-step (A to C). Then find the tool. You cannot automate chaos.

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

Eric asks: "I work full-time and I'm trying to grow my side hustle. It's so hard to find time to observe my team's work and make more calls. What's your secret when working full time?"

In this episode, Scott reveals why "I don't have time" is really a discipline issue, shares his own 8-11 PM time blocking experience while raising kids, and breaks down the micro-chunking technique most people miss. You'll learn why Ben Franklin was a time blocking advocate, how to defend your time ruthlessly, and why escape velocity requires protecting your calendar at all costs.

The bottom line: Block your time. Micro-chunk it. Defend it with honor. That's the only way out.

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

Jake asks: "I finally got the growth I wanted, and now everything is harder. More leads but I'm dropping half. More revenue but cash flow is a mess. More deals and every new one creates new issues. What should I have put in place before I scaled?"

In this episode, Scott delivers a counterintuitive truth (growth is not always the goal), explains why you cannot scale chaos, and shares two stories—his own company nearly shutting down, and a multifamily investor whose back office collapsed at scale. You'll learn the doubling test (can you handle 2X before 10X?), why scaling is like building an airplane in flight, and why slowing down is sometimes the fastest way forward.

The bottom line: Before you hit the gas, slow down. Make sure your systems can handle double. Then scale. You cannot scale chaos.

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

Joe asks: "I've been running my business solo for three years. I'm working long hours and burning out. Every time I run the numbers, I can't justify someone—the margins aren't there. But I can't keep doing this alone. I'm starting to resent the thing I built. Help."

In this episode, Scott diagnoses Joe's real problem (the "control trap"—either pricing too low or hoarding profits), explains why you can't grow beyond one person's capacity, and shares the Uber model for hiring strategically. You'll learn the difference between an asset and a job, why the short-term profitability dip is worth it, and how to shift from $10/hour work to $1,000/hour work.

The bottom line: Fix your pricing, hire per-job, get out of your own way. The dip is temporary—the growth is permanent.

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

Jenna asks: "Last year I closed more deals than ever. My revenue is up 40%, but I'm looking at my bank account and I honestly have less money than when I was doing half the volume. Where's all the cash going? Am I doing something wrong?"

In this episode, Scott diagnoses Jenna's real problem (she's in the "sales trap"), explains why revenue is a vanity number, and breaks down the only two solutions to margin decline: raise prices or cut expenses. You'll hear Scott's Cloudflare story about using AI to audit expenses and finding $150/month in unnecessary spend, learn why your company might need a financial diet, and understand how to diagnose whether you have a sales problem or a profit problem.

The bottom line: You don't have a sales problem—you have a margin problem. Put your company on a diet.

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

Mike asks: "We've used our own cash reserves for deals, but we're contemplating using other people's money—not because we need it, but to deploy our capital elsewhere. We've been debt-averse but see value in this if done correctly. How would you view this?"

In this episode, Scott breaks down the decision using the Investor Priority Pyramid, explains why capital is foundational (use it first), when debt makes sense (only when levered and proven), and shares a cautionary tale about six-figure credit card bills that worked—until revenue shifted. You'll learn why debt is fine until it's not, and why you should never take on debt without a proven model.

The bottom line: Use your capital first. Take debt only when you KNOW it returns more than it costs.

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