Three Questions Before Any Yes

When you run a platform, the temptation is not that you cannot build things. It is that you can build almost anything, and the ideas never stop coming. Every customer conversation is a potential product. Every gap in a market looks like an opening. The constraint is not capability. The constraint is judgment.

So before any new product gets a yes, it has to survive three questions. If it cannot clear all three, it does not start, no matter how good the pitch sounded in the room.

One. Does it sit on the spine we already have?

Everything we ship runs on one governed control plane. That is not a branding decision. It is the source of our leverage. A new product that reuses the spine costs a fraction of one that needs a new spine, because the hard parts are already built. Governance, identity, the authorization model, the audit trail. Those are the expensive, unglamorous systems, and we only want to build them once.

So the first question is whether the idea stands on what we already have. If it does, we can move fast and the economics work. If it needs a whole new foundation, the real cost is ten times the pitch, and the idea has to be ten times as good to justify it. Most are not.

Two. Is the pain sharp, specific, and expensive to the person who has it?

Vague pain does not convert. A product that helps someone do something a little better than a spreadsheet will lose to the spreadsheet, because the spreadsheet is free and already open. The pain has to be sharp enough that the person feels it by name, specific enough that we can build for exactly it, and expensive enough that solving it is obviously worth paying for.

I look for the problem the customer is already spending money or misery on. If they have hired around it, worked late around it, or lost deals because of it, the pain is real. If they say it would be nice to have, it is not a product. It is a feature request for something they have not decided to care about yet.

Three. Can we be the ones who hold up under scrutiny?

We work in places where the cost of being wrong is high. Defense. Energy. Regulated enterprise. In those rooms, the winner is rarely the flashiest option. It is the one that survives the audit, the security review, the diligence. So the third question is whether this is a domain where governance, traceability, and reliability are the deciding factors, because that is where we win.

If a market rewards moving fast and breaking things, it is not our market, and we should be honest about that instead of pretending our discipline is a fit everywhere. We are built for the domains where someone is going to check your work in detail and hold you to it. When that is the buying criteria, our whole way of building becomes the advantage instead of the overhead.

The point of the questions

The questions are not there to find reasons to say yes. They are there to make no cheap. A fast, clear no is one of the most valuable things a company can produce, because every no protects the focus that every yes depends on. The products that clear all three questions get everything we have. The ones that do not never should have gotten a meeting, and the framework is how we find that out before we have spent three months learning it the hard way.

Anyone can start things. The discipline is in what you refuse to start.