TL;DR Most decision frameworks answer one of two questions: should I commit to this, or how should I think about it under uncertainty? Confusing the two is the most common failure I see. 37signals answers the first. Annie Duke answers the second. Pick the question first. The right framework follows.

A founder messages me: "I need a decision framework." I ask what the decision is. They cannot tell me. They want the framework first.

The framework is comfort. The decision is the work.

TL;DR Gokul Rajaram's 8 Moats framework, articulated in full on 20VC in March 2026, is the cleanest update to Hamilton Helmer's 7 Powers for the AI era. It is also dangerous if applied to a pre-seed or seed company without staging. By Rajaram's own admission, only three of the eight (Data, Workflow, Regulatory) are meaningfully assessable before Series A. The other five are post-scale phenomena that founders systematically claim and investors systematically credit. The Critical Path Layers framework supplies the missing discipline: it tells you at which CPL layer each moat earns its evidence, and what counts as evidence rather than intent. Without that overlay, the 8 Moats become moat theatre.

"Coachable" is doing real work in real investment decisions.

No one has agreed what it means.

Fifteen years of research, term sheet language, accelerator screening forms, and coaching sales decks. Press any two practitioners for a definition and you will get two different answers.

Tatiana Somià published the most rigorous recent attempt last year in Cogent Economics & Finance. Fifteen competencies, five areas, stitched from four different literatures. When her investor panel and her coach panel disagreed about what counted as coachability, she resolved it by weighting the investors most. The final scale includes items the coaches in her own study said were coaching outputs, not coachability markers.

That is not a rigour problem. It is a construct problem. When you build a definition by negotiating across raters with different interests, what you produce is a map of what investors want to see in founders. Useful. Not the same thing as coachability.

Here is the definition I am willing to defend.
Three capacities, one precondition.

• Seek feedback: the capacity to incorporate signals that do not originate in your own perception.

• Reflect: the capacity to think past the mental models that constructed your current view.

• Act: the capacity to break habits that worked at an earlier stage and no longer fit.

The precondition is courage. Before any of these can operate, the founder has to be willing to deliberately expose a blind spot. Not discover one by accident. Not admit one after the consequences are undeniable. Go looking for the view they have been avoiding.

Key takeaway: The pilot that converts into a contract is not designed to prove the technology works. It is designed to arm the internal champion with the evidence the organisation's governance process requires to say yes. Three criteria separate pilots that convert from pilots that demonstrate: representativeness, boundedness, and learnability.

TL;DR: Recent research identifies four distinct ways corporates absorb AI through startup partnerships. The technology matters far less than the collaboration design. When both sides are operating in different modes without knowing it, the partnership stalls. One honest conversation can fix this.

Most startup sales failures are not sales failures. They are positioning, ICP, or validation problems that surface at the point of sale. Every major sales methodology, from Challenger to MEDDIC to Sandler, assumes upstream work that most founders have not done. Fixing your sales process when the real problem is two layers upstream is the most expensive way to learn nothing.

TLDR;-) Most innovation frameworks organise by domain. The problem is that domain-based thinking hides the only question that actually matters in early-stage work: what needs to be true before this can work? Critical Path Layers reorders the familiar themes of startup growth and corporate innovation into a dependency sequence. Each layer gates the next. It doesn't tell you what to do. It tells you what to solve first.

Every coaching and advisory framework I've encountered makes the same structural error. Strategy in one column, operations in another, fundraising somewhere else. Neat. Logical. And almost entirely unhelpful for sequencing decisions.

Domain-based organisation tells you what to think about. It says nothing about when. And in early-stage work, when is everything.

Critical Path Layers takes the same familiar themes and reorders them into a dependency sequence. Each layer gates the next. You can work on anything you like at any time, of course. But effort spent on downstream themes before upstream prerequisites are resolved is the single most common pattern of wasted founder and corporate innovator effort. I see it constantly. Strategy before problem clarity. Pricing architecture before product-market fit. Hiring plans before unit economics.

The framework doesn't prescribe. It sequences.

Most B2B proof-of-concept projects fail not because the technology doesn't work, but because no one validated whether the client was willing to bear the internal cost of solving the problem they just discovered.

Your POC worked perfectly. The technology performed. The data confirmed your hypothesis. The client nodded along in the final presentation.

And then nothing happened.

If this sounds familiar, you're not alone. After working with dozens of B2B startups navigating enterprise sales cycles, I've observed a pattern so consistent it deserves a name: the Successful Failure.

The POC technically succeeds. The commercial outcome fails. And founders are left wondering what went wrong.

Here's what went wrong: you validated the wrong thing.