Why our board disagrees with enterprise scorecards, and why that is the point
Design 22 and speed 21 out of 100. That single decision explains almost every difference between this board and the scorecards written for procurement teams.
By Owen Castellan · Updated 18 Aug 2026
If you have read an enterprise comparison of AI app builders recently, our board will look wrong to you. That is expected, and the reason is published rather than hidden.
The weights are the argument
Agent Verdict weights ten axes to 100 points. Design takes 22 and raw speed takes 21. Together that is 43 points, nearly half the board, allocated to how good the output looks and how fast you get there.
An enterprise scorecard typically allocates those two axes something between 10 and 20 points combined, and gives the difference to governance, compliance, support terms and vendor stability. Both allocations are defensible. They just answer different questions.
Ours answers the question a builder asks on a Tuesday afternoon: which of these gets me to something I would show someone, fastest. An enterprise scorecard answers the question a procurement committee asks in a quarterly review.
What this means for reading our ranking
Three practical consequences:
- A tool that wins reliability and code ownership can still sit second here. That is not a criticism of the tool, it is arithmetic.
- A tool with a thin governance story can sit in S tier, because governance is not on our axis list at all.
- Weekly movement is larger on this board than on scorecards, because design and speed votes are volatile and they carry the most weight.
What we do not do
We do not use stars, because a five point scale compresses the interesting differences into nothing. We do not publish a 0 to 100 index, because a single index invites a false comparison with scorecards built on different axes. We publish a tier band, a community score out of 1000 and the raw vote count, so you can see how much agreement is actually behind a position.
The seeded votes disclosure
Launch scores include votes from our own testing panel, badged Editor panel wherever they appear, because a board with no votes is not a board. Community votes accumulate on top and will outweigh the seed as volume grows. The full methodology, including every weight, is on the scoring page.