Show HN: HERO – Notion for Formal Docs

Show HN: HERO – Notion for Formal Docs(myhero.so)

3 points by kevintouati 153 days ago | 1 comment

Hey HN!

I’m Kevin, the founder of HERO.

Thank you so much for checking out our launch today. We built HERO because serious work deserves better tools than paper-based documents built with word processors built in the 90s.

If your team works on contracts, policies, SOPs, technical specs, or any structured, formal documents, you know the pain:

- information buried across multiple files, sections, exhibits, etc. - repeated copy-pasting - outdated definitions - impossible cross-referencing - version chaos - hours wasted searching for the right clause, number, term, or page

HERO solves this by combining the flexibility of text, the structure of a database, and the power of live integrations, all inside one collaborative workspace.

Everything becomes interconnected: sections → definitions → clauses → data variables → linked documents → live values .. And the search is instant, whether you have 10 or 10,000 documents.

With HERO, you save ~2 hours per day (every day):

- No more digging for past clauses - No more re-entering data in multiple documents - No more checking if a definition was updated in all files - No more manually coordinating versions - No more rewriting work that already exists somewhere else - No more switching between Word, PDFs, spreadsheets, emails, and shared drives just to complete one task

When all your structured documents share the same definitions, data, and references and they update everywhere automatically, the time savings compound fast.

If you work in legal, operations, compliance, engineering, or any document-heavy field, HERO gives your team back 10 hours a week you’re currently losing to admin and document chasing.

This came from years of professional experience as a corporate lawyer. We’ve poured a lot of heart, honesty, and hard lessons into building this.

We also recently made to the top #3 product of the day on Product Hunt on a particularly competitive day.

Would love your feedback, questions, or just to hear how your team currently handles this kind of work.

Thanks for being here, it means a lot.

Kevin

alex92634 153 days ago |

Hey HN, I’m Alex. The lead engineer working on this. The main technical challenges revolved around treating documents as structured, interlinked data rather than static text, requiring a real-time system that preserves hierarchy, references, and dynamic variables across files. Doing that while keeping the editing experience fast, collaborative, and predictable demanded custom data models, syncing logic, and rendering pipelines that traditional editors don’t have. We’re very much looking to improve so all feedback is welcome!