In 25 years I've watched founders quietly kill good ideas and pour a year into bad ones — for the exact same reason. They never separated the idea from the way it was framed. When a project stalls, the instinct is to read it as an effort problem. Work harder. Add a hire. Run one more push. But most stalled projects aren't stuck at the effort level. They're stuck at the root-problem level — and no amount of effort fixes a problem you've diagnosed wrong. You just get to the wall faster. There are really only two reasons a project won't move, and they look identical from the inside: The idea is wrong. There's no real problem underneath it, or no one who'll pay to solve it. Effort here is expensive theater. The framing is wrong. The problem is real and worth solving — but you've aimed it at the wrong buyer, entered through the wrong door, or described it in words that don't match how anyone actually experiences it. Effort here isn't wasted; it's just pointed at the wrong target. The trap is that both feel the same. Both produce silence, flat numbers, and a team that's working hard with nothing to show. So before you spend more, the question isn't "how do we push harder?" It's "which of these two am I actually looking at?" Here's the diagnostic I run: Does the problem exist when you're not in the room? A real problem shows up in what people already do — the workarounds, the spreadsheets, the money they're spending to cope. If the problem only appears when you pitch it, you likely have an idea problem, not a framing one. Effort won't save it. Change the words, not the product — does the response change? Describe the same thing to the same person using their language, their trigger, their stakes. If a sharper frame suddenly gets nods where you got blank stares, the idea was never the issue. The framing was. Follow the "no." When people pass, are they saying "I don't have that problem" or "I have it, but not like that / not from you"? The first is an idea signal. The second is a framing signal — and it's fixable without starting over. Would a different buyer make this obvious? Sometimes the idea is right and the audience is wrong. Moving the same solution to a segment that feels the pain acutely turns a hard sell into an easy one. That's framing, not effort. The reason this matters: the cost of confusing the two is enormous. Treat a framing problem as an effort problem and you burn a year grinding on something that only needed a repositioning. Treat an idea problem as a framing problem and you keep polishing the message on a thing the market was never going to buy. Clarity here is cheaper than persistence. Diagnose the root before you spend the next quarter on the symptom. So a question worth sitting with this week: The project that's stalled right now — are you actually sure it's a bad idea, or have you just never tested whether it's a framing problem wearing a bad-idea disguise?

Most people I work with are trying to become indispensable. I spend my time trying to become unnecessary. That sounds backwards, so let me explain the difference — because it's also the difference between me and the operators and agencies a founder might hire instead. An agency is designed to keep you as a client. An operator is often measured by how much runs through them. Both, by design, make you a little more dependent every month. That's not a criticism of their intent — it's the incentive built into the arrangement. The longer you need them, the better it works for them. My job is the opposite. I get handed a hard, ambiguous problem, I build the thing, I set a real foundation under it — and then the win is when a capable operator can take it over and scale it without me in the room. I'm not building a dependency. I'm building something that no longer needs me. Here's why that matters even if you never hire anyone: dependency on a single person is a hidden fragility. It feels like control. It reads like importance. But it's the crack that doesn't show until the load shifts. In M&A, buyers actually price this — a business that leans too heavily on its founder gets discounted, sometimes steeply, versus one that runs on people, process, and structure. The market is telling you something founders don't want to hear: your irreplaceability is a liability on the balance sheet. The fix isn't heroics. It's two disciplines most builders skip. First: document the decisions, not just the outcomes. Anyone can inherit a result. Almost no one can inherit the reasoning — why you chose this customer over that one, why you killed the feature everyone loved, what you'd do if the number moved the wrong way. Outcomes tell your successor what happened. Decisions tell them how to think when you're gone. That's the part that actually transfers. Second: treat the handoff as the test, not the goodbye. A clean handoff is the only honest proof the foundation is solid. If the thing wobbles the moment you step back, you didn't build a company — you built a role, and you're standing in it. The transfer is where you find out whether the structure was ever real. I've come to believe the strongest thing you can build is something that outlives your involvement in it. Not because you're leaving tomorrow. Because durability and dependency are opposites, and you have to choose which one you're actually building. So here's the question worth sitting with: Is your company built to outgrow you — or to need you?

"How do I keep from being the bottleneck?" Most founders think they're the bottleneck because of how much they do. They're actually the bottleneck because of what only they're allowed to decide. It's a subtle difference, and it's the one that keeps stalled companies stalled. You can hire more people, delegate more tasks, clear your calendar — and still be the single point of failure. Because the work moved, but the authority didn't. Every real decision still routes back to your desk for a yes. The team isn't waiting on capacity. They're waiting on permission. I've watched this for 25 years across four startups. A founder offloads the doing and keeps the deciding, then wonders why nothing moves when they're heads-down or out of the room. It looks like a delegation problem. It's a decision-rights problem. You gave away the tasks but kept the steering wheel, and a car with one driver can only go one place at a time. The builders I most respect design the opposite way — on purpose, early, before it's comfortable. They treat decision-rights as something you architect, not something that accumulates by default around whoever started the company. Two questions do most of the work: For any recurring decision, who owns it — not who advises, who decides? If the honest answer is "me, eventually," you've found a place the company can only move at your speed. And what does this person need to decide well without me — the context, the constraints, the definition of a good outcome? Authority without judgment is just a faster way to make bad calls. The transfer isn't handing over a decision. It's handing over the thinking behind it, so the call gets made the way you'd make it, whether you're there or not. Here's the reframe I've come to believe: a venture that can't make decisions without its founder isn't a company yet. It's a talented person with help. The moment it can decide well without you is the moment it becomes durable — something built to outlive your involvement instead of depending on it. That's not abandonment. It's the point. You're not designing yourself out because you're leaving. You're doing it because a company that needs you for every decision is fragile in exactly the place that looks like strength. So a question worth sitting with this week: What's one recurring decision that still routes through you by default — and what would the person closest to it need in order to own it outright?

Congratulations to Western Growers and Reservoir Farms on this $1.5 million commitment. This partnership is worth paying attention to—not because of the funding amount, but because of the structure. Western Growers is giving its members exclusive access to robotics field trials across Salinas, Wine Country, and the Central Valley. They're not waiting for perfect technology. They're building a bridge between prototype and commercial adoption. That's a go-to-market strategy. Most early-stage founders I work with struggle with the same problem: they have a working product, maybe even some pilot customers, but no clear path from validation to revenue at scale. The gap isn't always the product. It's access to the right testing ground and the right early adopters who can give real feedback under real conditions. Western Growers is solving that for agtech companies. They're creating a repeatable environment where technology can be tested, refined, and proven before it hits the broader market. That cuts years off the adoption timeline. If you're building a B2B product, the principle is the same. You need a structured way to get your solution in front of the people who will actually use it. Not in a demo. Not in a pitch deck. In their workflow, solving their real problem. That means identifying your early access group—the customers who have the problem acutely, who are willing to test, and who have enough influence to move others when it works. Then you build the program around them. You give them something exclusive. You make the feedback loop tight. You document what works and what breaks. And you use that as proof for everyone else. This is how you move from prototype to repeatable sales: not by perfecting the product in isolation, but by proving it works in the field. If you're stuck between pilot customers and real traction, book a free 15-minute marketing audit and we'll map out who your early access group should be and how to structure the program around them. https://www.radi8.com/free-audit?utm_source=linkedin&utm_campaign=free_audit&utm_content=post_id https://www.santacruzworks.org/news/reservoir-the-field-is-the-lab

Entrepreneurship