Why We Built This
The Founders' Letter. The moral engine of the work.
We are building for the person in the middle.
Not the executive at the top who makes the call that everyone will live with.
Not the engineer who ships the work.
The person in the middle — the VP of Product, the PMO Director, the portfolio owner, the product manager who sits at the center of an unfathomable volume of competing demands and is expected to hold all of them, compare all of them, produce a defensible order from all of them, and then defend that order when someone more senior decides at the next meeting that the order was wrong.
That person deserves better infrastructure.
What we have watched happen
We have watched people we cared about fail — not because they lacked capability, not because they were in the wrong role, but because the structural support required to do the work well did not exist.
We have watched dutiful operators discover that diligence offers no protection. The person who validates assumptions before building, who respects the established operating model, who executes the strategy as it was stated — discovers that when the plan changes without record and the new direction requires abandoning what they built with care, there is no system that names what happened. The organization that punished good work does not know that it punished good work.
We have watched the light go out in people’s eyes. Not all at once. Gradually, over years. The person who was curious and full of ideas at 35 is not the same person at 48. Something happened. Something was taken. The organization that took it never knew, never named it, and would not have known what to do with that knowledge if it had.
We have watched the human cost of unanchored change. Teams that experience frequent, unexplained priority shifts stop investing deeply. They hedge. They contribute at the surface. They protect themselves from the full cost of deep commitment because they have learned, through experience, that deep commitment is not safe.
What we believe is possible
We believe that the structural conditions that produce this cost are addressable. Not through better culture programs. Not through stronger leadership. Through infrastructure — the same way that the structural conditions that produced financial opacity were addressed by accounting infrastructure, and the same way that the structural conditions that made identity management chaotic were addressed by identity infrastructure.
When that structure exists — a clear Frame before the decision, a governed Cascade through which every level contributes its judgment, and a Plan of Record after — three things become possible that are not possible today.
The dutiful operator has armor. The decision they executed was made on the record. The criteria were documented. The values were gathered. The authority was explicit. When the decision is challenged, the record exists to show that the process was legitimate.
Change can be evaluated. When a new priority arrives, the organization has a baseline. The question — is this a signal-informed adjustment or an arbitrary departure? — can be asked and answered with evidence, not just assertion. That question, asked and answered explicitly, changes the organizational dynamics around change.
Contribution reaches the decision. Every level of the organization carries something the other levels don’t have. The system that governs the Cascade — that governs how those contributions reach the decision — is what determines whether organizations make decisions with the information they have, or make decisions as if they have only the information that reaches the executive suite.
What this is not
This is not a roadmapping tool. It does not produce a roadmap. It produces the inputs that make a roadmap defensible.
This is not a collaboration tool. Collaboration is not the problem. Thousands of organizations with excellent collaboration culture have exactly the same prioritization problem because collaboration does not substitute for structure.
This is not an AI that ranks for you. The value of the Plan of Record is precisely that it carries human judgment — the criteria that were chosen, the values that were gathered, the rationale that was recorded. Outsourcing that judgment to an algorithm produces a list with the same properties as a list produced without the Frame: defensible in appearance, hollow in substance.
This is infrastructure. It is the system that should have existed for decades and didn’t.
Why we are building it
We are building it because we have been inside the problem from multiple positions. We have facilitated the rooms where the process worked and the rooms where it failed. We have been the person in the middle trying to hold the organizational center. We have watched the human cost accumulate in people we cared about.
We are building it because the infrastructure to build it now exists. The database capabilities, the API primitives, the governance modeling tools — they exist. What was missing was the conviction that prioritization is an infrastructure problem, not a process improvement problem, and the willingness to build it as such.
We are building it because we believe the people who do this work deserve better equipment. The judgment was always there. The care about the work was always there. What was missing was a structure built to receive it.
That is what we are building.
— Wes Bright and Harry Max, 2026