What actually makes software projects successful?

Almost everything Ben Horowitz says becomes a maxim for software companies (decades of success will do that), but there's one Horowitticism that especially stands out to me: "the best product won't always win the market, but whoever wins the market will be the best product."

It's more than just a way for CROs to ask for more stock options or a market leader to command a premium. Instead, it should tell us about the relationship between products and outcomes.

If we focus on the software-buying journey, this same maxim reads something like this: the best product might not be the one that makes you the most successful, but whatever makes you the most successful will end up being the best product.

In other words: the project is vastly more important than the brand and product supporting it. As a software buyer, you have a limited amount of time to find out who can truly execute alongside you and make your project truly successful. You need to have a structured plan in place to make sure your evaluation answers the most important question: who can actually make me successful at this and how can I make sure they do?

It's all about accountability, and accountability requires transparency.

71% of the time, the easiest seller to buy from is the one that wins competitive deals. Pricing matters. Features matter. Ultimately, though, the most important factor is who can actually make your project successful, so it's critical to measure project execution, so you can choose the vendor who is most dedicated to helping you thrive.