The idea for Synotate was conceived as the result of a problem my Marketing team faced at ShopKeep and expanded into a public product after discovering the problem was more common than I had expected.
Synotate was a data analysis platform that helped businesses save on time and resources by acting as a central repository of data annotations related to test results and trends found in data analysis.
The abundance of data at our disposal has led to analysis paralysis with significant knowledge gaps within organizations and a fragmented method to share knowledge about data.
Sole-founder and operator. Developer.
Languages / Platforms
- AWS - Elastic Beanstalk
- AWS - Cloudfront
- AWS - S3
- AWS - Elasticache
- AWS - RDS
- DigitalOcean - Droplet
I worked on this project at night and over the weekends for over three and a half years. A long time for a failed project that never gained much traction, but an extremely valuable journey filled mostly with educational lessons on running an online business, legal hurdles, engineering and product development. It started when I discovered a common occurrence in meetings where a question was asked related to a historical trend presented in a report and presentation with no on the spot resolution. No one would seem to have a definitive answer and time was spent searching through email, Slack and Google Drive for hints, ultimately ending up with having to re-analyzing that point in time to come to an answer.
When you consider the amount of meetings in which this happens, you can immediately see how wasteful this lost memory is in terms of resources and money. As a result, I set out to build a platform that would centralize our data findings in one location in order for our company to easily access and share learnings, resulting in better guided business decisions going forward.
From 2016-2018, I worked at night and on weekends, learning new frameworks and building the initial functionality, eventually arriving at the first version, but unable to launch to my team due to legal requirements and sign off from my employer to allow us to use the product internally. An unexpected roadblock that made me quickly learn how long these processes can take. Right around the start of 2019 I had clearance and finally launched the product to the team and world.
Upon launch, I worked on selling the inclusion of this product in my teammates workflow and started to see utilization primarily for tracking campaign performance. After multiple product iterations from early feedback and a solid trajectory from launch, the usage started to decline. Upon interviewing my teammates I discovered that the difficulty with adopting the product was based on the lack of structure around what they would deem worthy of an annotation, when they should be posting and how they can automate some of the creation. This feedback made me realize that it faced the same challenges of a project management tool. The utility in project management tools is its organization and standardization, but without buy-in and habit generation, the utility will not be found.
After trying to figure out how to tackle all of these problems, I felt burnt out by the project and decided to sunset it. I was losing more of the already finite amount of free time I had by trying to manage engineering, marketing and outreach for a product that needed more commitment and ultimately, I felt like between my teammates' feedback and low customer sign ups, I was not going to be able to find product-market fit. While a disappointing way to close out a significant time commitment, the learnings will pay dividends in the future.
- First project I have ever brought from ideation to production
- Discovered the importance of sticking to an MVP
- Learned database best practices, React.js and server architecture
- Just ship it! Get feedback early and often.
- Stay focused on the initial problem your users have and how your product will solve that.
- Buy-in is extremely important. Find this before you start building anything.