Avo provides an incredibly useful interface for designing and updating the schema (event names and properties) of events, which will eventually be analysed through another tool, Amplitude in our case. It also generates typesafe code for engineers to insert straight into the codebase, eliminating the possibility of spelling errors or missed properties. Before Avo, adding tracking with Amplitude Govern and the Amplitude SDK was a mess of spreadsheets, sticky notes, miscommunications, and fixing errors post-release. Now it's often as easy as sending an engineer a link to an Avo branch, and saying "go for it".

With Avo, I really like the version control so no one steps on each others' toes. It's our single source of truth for all things data tracking. We're able to see violations in production as well as push these to other tools. I can easily collaborate with our developers to agree upon our specs and they can pull it into the code-base with a typesafe CLI, so I can trust I'll get the tracking I need on the first try.

The aspect of seamless collaboration with Product, Development and Data Teams. Avo provides clarity for the entire organization and solves a problem that exists for the entire Data industry.