How we built Reo.Dev from an excel sheet based intel product to a full fledged SaaS
Building and launching Reo.Dev was a journey of validating the right problem and then shipping crazily fast
At Reo.Dev we believe shipping velocity is core to any startup and we are very proud of our own shipping velocity. Here is a glimpse of how we built Reo.Dev from an excel sheet based alpha version to a full fledged platform.
Our unique insight was that for developer focused companies, purchase intent resides in developer activity. However, developer activities are usually incognito and scattered across channels such as open source usage, tech docs, dev communities and more. We wanted to build a system where GTM teams could learn which companies have developers interacting with them and also give them intel to convert such accounts.
🛴 August 10th: We launched an alpha version of our product that provides intel on raw excel sheets. Our customers used to give us the list of Github repos which were their own or competitors' - and we used to provide them accounts and LI handles of developers interacting with these repos at better accuracies than the market based on our homegrown algo.
🚲 September 18th: We launched the MVP/ Beta version of Reo.Dev with a functional frontend and user interface. We limited the intent sources to Github and their Developer Docs with basic segmentation. We stripped down any unnecessary feature. Our MVP was functionally basic but it had a very strong intel engine backed by our very strong intel module that detects github activity → Github user id → Converts it to LinkedIn ID with best in industry accuracy → Triangulate data under accounts. Moreover, we launched the product on time 💪
🏍 October 4th: We launched Account List feature. SDRs and AEs with a list of target accounts could upload these lists on Reo.Dev and track their developer activity.
Also we launched an interactive developer activity timeline. This is the most visited product page today.
🛵 October 20th: We now cover Package Manager Installations with coverage of 40+ package managers (best in industry 🎉) . Our customers now know organizations where developers are installing their package managers (Docker, Helm, NPM, Git)
Our segmentation feature got a booster with new attributes.
🚗 November 9th: We learnt our customers are finding it tough to get relevant accounts from hundreds of accounts they see on Reo.Dev. So we launched “Magic Segments” and ‘Surge' to solve this. Engagement soars!
🚋 November 24th: We work through Diwali to launch Technographics: We cover 32000 technologies right from day 1 via inhouse built tech on @OpenAI as not many data providers provided technographics suited for devtool companies. Now our customers can find accounts that have developer activity and also fit their technographics.
🚞 December 14th: Many of our customers want to differentiate accounts active on the docs of their free product / MIT license and paid product/ BSL license. They also want to track key sections of their docs . So we launched ‘source tracking’ - a feature for customers to track accounts active on different documentation versions and pages
🚄 Jan 5th: Our team again worked through the Christmas and New Year to launch some amazing features 🙌 :
- We launched Telemetry APIs! - first time ever any OSS company can push their telemetry data and see accounts (enriched by IPs) that are using the OSS version
- Product Usage Data Integration - Customers can send their product trials and cloud usage data to see one single account picture across product, telemetry, docs, package manager and Github now!
And this is just 3 months of product launch! We hope to ship even faster now.
But nothing like this would have been possible without the amazingly hard working team at Reo.Dev.
I wanted to end it with this video that probably summarises every thing I said 🙂