5 Go-to-Market Lessons from Voxel51’s Journey in AI Infrastructure
Success in developer tools isn’t about following conventional SaaS playbooks. In a recent episode of Category Visionaries, Jason Corso, Chief Scientist of Voxel51, revealed how their team turned internal tooling into a thriving open-source business. Here are the critical GTM lessons from their journey.
- Your Initial GTM Strategy Will Likely Be Wrong
The path to product-market fit often starts with a failed hypothesis. Voxel51 began as a consulting business, building custom video understanding systems for clients. “We actually initially got started trying to become… well, initially we got started as consultants through a grant that we secured from NIST,” Jason explains.
But this approach hit a wall: “When it came time to go and sign a long term production, like, let’s get some business intelligence or production value out of this video understanding system, the users just weren’t ready.” This early failure forced them to rethink their entire approach.
- Listen to Where the Market Actually Is
Instead of pushing forward with their original vision, Voxel51 recognized that their internal developer tools were more valuable than their consulting solutions. As Jason notes, “We ultimately pivoted way earlier in the lifecycle to kind of meet the users where they were at and release the developer tools that we had been building for that consulting work.”
This pivot wasn’t just about changing products – it was about understanding the market’s real readiness level. “It was a little too early to understand and spend money on video as a value prop and the ultimate lifecycle of businesses,” Jason explains.
- Open Source as a Strategic GTM Choice
Rather than taking the traditional SaaS route, Voxel51 made open source central to their strategy. “We give away the full machine learning stack, the software, as long as it is one user, one machine, local data,” Jason shares. This wasn’t just about distribution – it was about building trust and understanding user needs.
The monetization came naturally: “About a year later when we inbounded a question from someone in the community… they kind of gave us the how to establish our go to market.” This led to their enterprise offering, which adds “the multi user capabilities, the enterprise security support, the system versioning like dataset versioning.”
- Build Trust Through Technical Authenticity
In an industry full of hype, Voxel51 chose authenticity. “We never talk about vaporware. We never promise things in our customer discussions,” Jason emphasizes. “We were very careful to build that trust in that relationship over time.”
This extended to their marketing approach: “Nowadays if you look at our website, it’s a very technical website, many links to the documentation directly. There aren’t many like these ‘workflow x’ or ‘workflow y’ landing pages.”
- Leverage Existing Ecosystems
Rather than building everything from scratch, Voxel51 found success by integrating with existing tools and datasets. “What really worked early on in terms of getting us attention was riding the coattails of successful tools,” Jason reveals. This included becoming “the preferred mechanism for accessing a dataset called Google open images.”
This strategy helped overcome the initial slow adoption of their open source release. “In the first months, we had like 20 weekly active users was like a big number for us,” Jason recalls. The integrations with existing ecosystems helped drive that number up significantly.
For technical founders considering their go-to-market strategy, Jason’s final advice is clear: “I think that if you can do open source as a go to market strategy in this, anything related to the AI space, I think it will pay its dividends, maybe not immediately, but in the long term.”
The key takeaway? Building infrastructure requires patience, authenticity, and a willingness to meet developers where they are. Success comes not from forcing your vision on the market, but from building trust through genuine value creation and community engagement.