The Founders
Harry Max and Wes Bright. The conviction that was present before they could articulate it.
The conviction was present before we could articulate it.
Harry Max
Harry Max has spent 35 years doing the work that Priorities.ai now systematizes.
He has held product leadership roles at companies across the full enterprise-to-startup spectrum — including work at the intersection of product management, organizational design, and decision infrastructure. His framework for the five steps of prioritization emerged from decades of facilitation — of running rooms where the right process produced defensible, held outcomes, and of being in rooms where the wrong process produced lists that evaporated within weeks.
He has seen what happens when the Frame is absent. He has seen what happens when the Cascade is replaced by political dynamics. He has seen what happens when the Plan of Record doesn’t exist and the organization loses its ability to evaluate whether a proposed change is legitimate or not.
He has spent his career trying to give organizations the infrastructure to do this properly. Priorities.ai is that infrastructure.
Wes Bright
Wes Bright has spent his career at the intersection of technology, product, and organizational systems — across enterprises, regulated industries, and startups. His personal experience with the human cost of structural failure shapes everything about how Priorities.ai is designed and positioned.
The decision to build this came from a specific conviction: that the failures of organizational decision-making are not primarily failures of leadership or culture. They are structural failures — the absence of a system that should exist and doesn’t.
He has watched people burn out, become cynical, and leave because the organizations they were committed to could not give them the structural support to do work they believed in. He has watched organizations lose talent they couldn’t afford to lose because the inability to make and hold decisions made the environment untenable.
That is not an abstract organizational problem. It is a human problem with a structural solution.
Priorities.ai is that solution.
On the category
The category claim — Prioritization Infrastructure — is not a marketing positioning. It is a factual description of what the system is.
The pattern is established: data infrastructure (Snowflake, dbt), payment infrastructure (Stripe), identity infrastructure (Okta). In each case, someone had to convince the market that what looked like a spreadsheet problem or a one-time setup was actually load-bearing infrastructure that needed to be built properly.
Prioritization fits the same pattern exactly. The market has been treating it as a spreadsheet problem. The reality is that it is load-bearing — when it fails, everything downstream fails with it.
We are not building a better prioritization tool. We are building the infrastructure category that did not previously exist.
On the work
What Harry and Wes are building together is unusual because both of them have been inside the problem they are solving, from multiple positions within it.
Harry has facilitated the room. He has been the person whose job it was to design the process that produced the defensible answer. He has seen what works and what collapses.
Wes has been the person in the middle — holding the organizational center while priorities shifted around it, trying to maintain the trust of teams who were running out of patience with a system that couldn’t hold its own decisions.
The system they are building is built to serve both of those people.