We just launched HERO 2.0 - collaborative workspace combining the flexibility of text, the structure of databases and the power of integrations.
It's built for teams who write formal, structured documents like legal contracts, technical specs, SOPs, and policies.
This project is the result of many years acting as corporate lawyer and mega-project specialist, navigating through the maze of complex, high-stakes, structure-heavy & interconnected documents - overlapping the legal, financial and technical.
It's all about bridging the disconnect between transactional teams and operational ones.
You can try it now at [myhero.so](http://myhero.so/) and let us know what you think!
Best,
The HERO Team
kevintouati•5mo ago
1. Structure vs. Flexibility – One of our core design choices is keeping strict document hierarchies (sections, clauses, schedules) while still allowing flexible, free-form editing. Do you think this helps or hurts for high-complexity docs?
2. AI Workflows – We’re experimenting with AI tools that can draft clauses, check consistency, and update terms across multiple linked docs in real time. If you’ve tried similar tools, what’s worked well and what’s been a miss?
Also curious: if you currently use Notion, Google Docs, or Word for legal/technical/SOP writing, what’s the biggest pain point you’d want solved?
I’ll be answering questions throughout the day — really appreciate any thoughts, ideas, or even brutal critiques.