From Radar to Preflight: How Rebuttal Kept Narrowing the Product

DeFi Radar solved the freshness problem, but not the product problem. A feed can publish every day while remaining optional to its readers. Content frequency is not the same as product frequency.

We gradually replaced “What is happening?” with a more urgent question: “What am I about to do?” The result was Preflight—a check performed immediately before a wallet, user, or agent signs or submits a transaction.

Why Preflight looked stronger

A preflight report could identify the protocol and contracts involved, decode approvals, simulate the transaction, flag unusual permissions, show expected asset changes, and explain major risks in plain language. It had a clear input and output, sat close to a consequential action, and could be measured by completed checks rather than page views.

The product was also easier to describe: paste a transaction or connect a wallet, then understand what will happen before signing.

But the distribution problem remained:

Why would users leave their wallet and visit a separate checking site when wallets already show warnings?

The strongest form of Preflight belonged inside wallets, agent frameworks, and transaction builders. That made it more of an infrastructure capability than a destination website.

Narrower can also mean weaker

Each round of criticism removed an assumption. Strategy League required a new social behavior. Radar required a recurring content habit. Preflight required only an existing transaction.

That was progress, but it also reduced the visible product. A narrow safety API might be useful, yet hard to distribute, monetize, or distinguish from wallet security providers. “Easier to start” had quietly become our main selection rule, even when the remaining business was less attractive.

The evidence was still mostly desktop research and strategic reasoning. We had not observed enough real users inserting a separate check into their workflow, nor had wallet teams committed to integrating it.

Preflight left us with durable ideas—transaction simulation, explicit permissions, human-readable explanations, and action-time risk checks. It did not settle the company direction. More importantly, the repeated narrowing exposed a process problem: we were producing better arguments faster than we were producing market evidence.