The catastrophe you're trying to avoid

I have been out of the day-to-day building game for fifteen years.

I am still going to tell you what I think you should do before you write a single line of code, because the structure of the question hasn't changed in those fifteen years. The catastrophes don't update. They have been the same five since the dotcom bust, and they will be the same five in 2040. Distance is not the disqualifier some people will tell you it is. Sometimes it is the opposite — the further out you stand, the more clearly the patterns hold their shape.

Here is the pattern that holds most clearly from this distance.

Most founders are optimisers. They want to find the best idea, the strongest market, the cleanest revenue model. They line their options up and try to pick the highest-scoring one.

This is the wrong frame.

The real value of asking the go/no-go question — honestly, before you build — is not that you might find a 9/10 idea. It is that you might avoid a 3/10 catastrophe. Twelve months of your life, twenty thousand dollars, the better part of your relationship with your own ambition — all of it spent on something the public record was telling you not to build, if you'd been willing to look.

---

The optimiser's trap.

The trap goes like this. You have an idea. You ask yourself: how good is this? You score it on potential. You think about market size, revenue model, viral mechanics. You compare it to other ideas you've had. You look for the highest-scoring one and you commit.

The trap is not that this is wrong. It is that it is incomplete.

An idea can score 7/10 on potential and still be the wrong idea for you, in this exact moment, with the resources you actually have. An idea can be theoretically excellent and operationally suicidal. The optimiser's frame asks "is this the best idea?" The catastrophe-avoidance frame asks a harder question: is this an idea that, if I commit, will not destroy the next 12 months of my life?

Most founders never ask the second question. They feel the pull of the first. They build. And the catastrophe — when it arrives — arrives quietly, by inches, over the course of a year.

---

What Rory Sutherland calls "always invert".

In Alchemy, the British advertising executive and behavioural-economics writer Rory Sutherland describes a thinking habit borrowed from the mathematician Carl Jacobi: invertere semper. Always invert.

Jacobi's point — and Sutherland's, applied to business — is that some questions are easier to answer in their negative form than in their positive one. You ask "what makes a marriage succeed?" — the answer is hazy. You ask "what kills marriages?" — the answer is sharper. You ask "what makes a startup succeed?" — the founders who succeeded disagree on the answer. You ask "what kills startups?" — the founders who failed agree, almost word for word.

The go/no-go decision benefits enormously from this inversion. Asking "is this idea great?" is a near-impossible question to answer honestly — your enthusiasm is in the room. Asking "what catastrophes is this idea most likely to walk me into?" is much easier to answer. And the answer is often visible from the start, if you are willing to write it down.

---

The five quiet catastrophes.

The patterns are documented in the public record any returning founder reads to catch up: post-mortem indexes, failed-startup wikis, the published anatomies of well-funded ventures that nevertheless came apart. Five catastrophes appear and reappear. They are quiet because none of them announces itself at the start. Each is a structural feature of the idea itself, hiding in plain sight, waiting for a year of build to reveal it.

• The market is real but unreachable. The customer exists, but you have no plausible path to them at this scale, with these resources, in this timeframe. WeWork's commercial real-estate ambitions ran into a version of this — the thesis was real, the operational path to scale was not.
• The revenue model is wishful. You can describe how the business makes money, but each of the assumptions underneath has the word "if" in front of it. Quibi's premium-short-form-video model — $1.75B raised, eighteen months to closure — was a textbook revenue catastrophe: subscribers and advertisers, premium-priced, on a format people watched for free elsewhere.
• The viral mechanic is a hope, not a structure. You believe people will tell other people. There is no specific reason embedded in the product that makes them. Path, the social network of the early 2010s, was designed for closeness — the structural reason to invite anyone never existed in the product itself.
• The competitive position erodes the moment you launch. You are first to market, briefly, in a category where being first is not a defence. Clubhouse's audio-social moment closed the day Twitter Spaces shipped — first-mover advantage in a feature-shaped category is not a moat.
• The build is solo-feasible only if everything goes right. The plan works on paper. The plan does not work on a Tuesday in November when you are tired.

None of these is fatal individually. Two of them, present together, is usually a no-go. The decision exists to surface them — before the build starts.

---

The gate that protects your time.

What a go/no-go gate does, structurally, is force the question to be asked in writing — once, on purpose, before the build starts. Not in the founder's head, where the answer is filtered through enthusiasm. On paper, where the catastrophes have to be named.

A founder who runs the gate honestly and arrives at NO has not failed. They have just been given back twelve months. A founder who arrives at CONDITIONAL GO and addresses the named catastrophes before building has converted what would have been a failed venture into one with a fighting chance. A founder who arrives at GO has done the work that lets them build with a different quality of conviction — not because the gate removed the catastrophes, but because the gate confirmed they were not the kind that would walk them into one.

Sutherland writes that in business, opposites can both be true. A venture can be a great idea and a personal catastrophe. A venture can be a mediocre idea and a perfect fit. The gate's job is to surface which of these you are actually looking at — not by guessing, but by inverting.

---

What changes when you invert.

When the idea is run through this frame — explicitly, in writing, before the build starts — three things change in the work that follows.

The idea gets sharper. Listing the catastrophes the idea is most likely to walk into surfaces the design choices that would prevent each one. The gate becomes a build brief. The catastrophe-avoidance logic transfers directly into the construction logic.

The pace changes. A founder who has written down the five catastrophes does not stop building — but they build differently. They build with the catastrophes named, in their peripheral vision, every week. The build serves the question; the question does not stop the build. This is the structural difference between disciplined optimism and unexamined enthusiasm.

The quitting becomes easier. Most ventures that fail, fail because the founder couldn't quit them in time. The harder version of quitting is quitting because the venture cannot succeed in the form the founder is building it. That decision is almost impossible without a list of catastrophes written down at the start. With a list, it becomes possible — sometimes within a few months instead of two years.

---

Why I built this gate.

I built Touchstone because I wanted the gate to exist for founders coming up now — the gate I would have wanted before I built the ventures I built earlier in my career. The methodology in the gate is not new. The structure of asking it before the first line of code is what's missing in most founders' processes — and what I have spent the last fifteen years watching the public record document, idea by idea, post-mortem by post-mortem.

This is not a claim of special insight. It is a claim that distance, properly used, is its own form of evidence.

---

Conclusion.

The go/no-go question, asked honestly, is not optimism's enemy. It is optimism's structural support. Without it, optimism builds on assumption. With it, optimism builds on evidence — including the evidence that says, sometimes, not this one.

Most founders ask "is this idea great?" The harder question — the one a mentor sitting across from you should ask, and the one I would ask myself if I were starting again tomorrow — is this: what is the catastrophe you are most likely to walk into, and is that catastrophe worth the upside you are buying?

If the answer is yes — proceed, with the catastrophes named.

If the answer is no — the gate has just returned twelve months of your life to you.

Either way, you'll know.

What's the catastrophe your current idea is most likely to walk you into — and have you written it down?