We're heading to TechCrunch Disrupt!
We were accepted into the TechCrunch Disrupt StartUp Alley and will be there (virtually) come September 21-23 2021.
We're really excited about this opportunity and we're hoping that we can use this to gain brand awareness and some more paying customers!
With more beta customers and more meetings than our introverted selves could ever expect, we again went back and updated our site.
We realized 2 things:
1.) People in tech-adjacent roles (product owners, management, QA) absolutely LOVE Voyage. They are the ones who are feeling the pain points of constant feedback loops and pressure from stakeholders and developers. We needed to adjust our message to make them feel seen and heard.
2.) Voyage isn't just a developer tool. It's a tool for the whole organization so why are we only focused on developers?
We're really excited about how we are differentiating ourselves from similar products.
We added about 10 beta users and launched in some private communities and it seems like we had a lot of issues with our messaging. People's reactions were mixed until we got a chance to verbally communicate with them about what Voyage does. We learned pretty quickly that our storytelling skills were not nearly as good as our programming skills.
Because we had Voyage as an internal solution already, it didn't take that long to build a SaaS product around it. We likely went a little overboard on the features we added but because we're devs ourselves, and from our product experience, we felt like we couldn't launch without some of these features.
We ended up using React and Node.
We had a problem internally where we couldn't get everyone on the same page. Developers would have their own feedback/review loops, then they'd send the feature off to be reviewed by another role/team. This would kick off another review loop where issues were kicked back to devs who then had another review loop.
Just typing that out makes me exhausted. We tried some off-the-shelf solutions like Netlify but it kind of made things more difficult. Netlify is a great solution when only reviewing the front-end but not when you're building data-driven applications.
We built an internal version of Voyage and began chatting with some of our customers about it. Their first response was "great! How much?!". We knew then and there we needed to make Voyage a product.
As the owner of a consulting agency, I've seen the constant feedback loops between devs, tech-adjacent roles, & stakeholders. We needed a way to deploy full-stack apps with databases, services with each Pull Request.