After years of dealing with scattered spreadsheets, outdated Jira tickets, and chaotic Slack threads just to define analytics events, I finally decided to build the tool I always wished existed.
EventDocs.io is a clean, structured space to define, organize, and share your analytics event specs — before implementation begins.
Instead of emailing tracking plans back and forth or guessing what the latest version is, you get a single source of truth your whole team can trust — from product and marketing to dev and data.
It’s 100% documentation-focused:
❌ No SDKs
❌ No data collection
✅ Just well-defined, versioned specs
Think of it like Figma, but for tracking plans.
🧪 I’m actively shaping it with early users. If you’ve ever struggled with messy tracking workflows, I’d love your feedback.
Check it out → eventdocs.io
Two comments here - great idea, added to my bookmarks - and man do I love your site design! I know that's not the point here, but it looks really clean and breathable.
Thanks a lot! I’ve really tried to keep things clean and simple - not just on the landing, but in the tool itself too.
Defining analytics events is already complex enough, so I wanted the UI to feel as simple as possible.
so I wanted the UI to feel as simple as possible - job well done! :-)
Website looks so good already!
Thanks! That really means a lot. Been thinking about adding a few screenshots or a short walkthrough, just to better show how it actually works.
I can help you in AI implementation in different workflows with custom developed POC & MPV.
Thanks! Out of curiosity, what kind of AI workflows have you worked on before?
Procurement & Supply Chain: Demand forecasting, supplier risk analysis, and intelligent procurement assistants.
Sales & Marketing: Lead scoring, customer segmentation, personalized outreach, and churn prediction.
Finance: Automated document processing, fraud detection, and credit risk modeling.
Customer Support: AI chatbots, ticket classification, and response recommendation systems.
HR & Operations: Resume screening, employee attrition prediction, and process automation.
Each implementation typically starts with a custom-developed POC (Proof of Concept) or MVP (Minimum Viable Product), based on the business’s specific KPIs and data availability.
Really interesting product — love the clean design.
Curious: how long did it take you to go from idea to launch?
I’ve been thinking about this for a few years. I’ve been working on apps where tracking specs are managed through spreadsheets or tickets, often going out of sync and hard to maintain.
Started prototyping late last year in my spare time and began sharing it with friends around April.