Three hundred and fifty thousand dollars. An AI and blockchain implementation for a Fortune 25 company that is also an airline. It would have been one of the largest procurement deals I had ever closed.
We spent six months on the preliminaries of that project and deal. I staked every dime I had on the upfront costs, like hiring consultants for pre-production. I could taste the money in my account.
Before the pressure hit, everyone was cool, calm and collected. Then we got close to the closing, and I learned the lesson that shapes how I work today: be true to your systems.
Anything can go wrong, especially at the closing
What went wrong was not the code. The government funding was delayed, then shifted, then cut, all in a two-week span. Six months of work, gone at the closing. The data was not protected the way it needed to be. And there was no contingency plan, no preparedness plan, for the extreme events that rarely happen, until one does.
People are people
The moment the pressure hit, you could sense it and see it: fear, moving through the leaders and executives in the room. Titles don't change that. People are people.
I see the same pattern in AI rollouts everywhere. Projects rarely stall because of the tech. They stall when the culture, the confidence and the habits can't hold under pressure.
Plan for the rare event
Everybody plans for the likely problem. Very few plan for the rare one. The most expensive moment in any project is the decision nobody prepared for. Who owns it? Who decides when the money moves or the data is exposed?
The mode nobody wants to run
Looking back through the G.O.D. Framework, the Generator was never the problem. Everyone loves creating. Very few people want to be the Destroyer: the one who cuts the risky assumption, like "the funding will be there" or "the data is fine," before it cuts you.
Be true to your systems
That project taught me to be true to my systems. Under pressure, people fall back on whatever they practiced. If the system is only on paper, the fear takes over. These are the systems I carry into every engagement now.
- Start with identity and decisions. Then the tools.
- Protect the data before you scale it.
- Write the contingency plan for the event that "never happens."
- Give every decision an owner people can see.
- Train leaders for the pressure, not just the plan.
That is why MAEx starts with mindset, identity and decision-making, and puts the AI frameworks on top. If you are about to put real money into AI or blockchain, I would love to hear what you are building.





















