Collaborative workspaces for serious work, combining the flexibility of text, the structure of databases, and the power of integrations. Designed for teams working on formal, structured documents like legal contracts, technical specs, SOPs, and policies, HERO dynamically interconnects files, sections, terms, and data in an integrated environment with lightning-fast search—whether you have 10 or 10,000 project documents.
@lliloulane This currently appeals to many different areas and we have seen use cased being put together across all major industries. We believe this could be most impactful in:
I think it's the best to focus on one use case. Managing legal docs how you showed it in the demo, is already a huge step forward and a big value. Maybe I'd narrow it down.
@pasha_tseluyko thanks Pavel, that’s definitely the plan.. but at the same time, it’s a text editor so you’re working on the documents for the construction of the next nuclear power plant or writing a letter to your grandmother both can happen on the same platform.
Loved it, Kevin! Absolutely agree on this, we deserve better tools cause we need to also enjoy the process, no only the goal. Wish you all the best here!
Not to be the downer here, but I’m trying to understand the real differentiation from Notion and internal databases. Is the magic mostly in automated cross-referencing or is there more that I may be missing?
@himani_sah1 yes! that is one aspect of it.
Whilst Notion is predominantly built for personal notetaking, HERO handles large, complex, heavily formatted formal business documents with the performance, security and scale this requires.
Here are some other aspects as to how this differs:
- Notion does pages within pages, HERO does sections within sections (sub/sections, sub/clauses, sub/paragraphs, schedules/appendices, etc.) to reflect the real structure of formal writing.
- Dynamic Variables: Notion has pages and databases (sometimes a database within a page), HERO can embed specific data points within the text for powerful, fine-grained templating and dynamic content reusability.
- Defined Terms & Acronyms: Reference and auto-manage key terms across large documents and projects.
- Project-Based & Context-Aware: HERO can reference, update, and respond to changes across multiple files in real time for consistency, efficiency & accuracy.
- Footnotes & Cross-Referencing: Native support for citations and internal linking, such as “Section 3.1(a)(i)” or “Part A of Schedule 5” which are essential to formal writing (ie. Legal contracts, technical specifications, operating procedures, etc.).
That being said we also look up to Notion a lot and fully admire the incredible system they built. We now also get a sense of hard it is to get there. :)
Report
I like the concept, but our biggest issue with Notion-style tools has been performance and permissions at scale. How does HERO avoid slowdowns when dealing with really heavy docs (like 200+ page specs)? And do you support granular access controls per section?
@zerotox Hi, thanks :) Yeah performance is key for us, with legal documents often being so large as you mentioned. We have optimized matters to ensure loading and typing remains fluid and fast no matter the size Permissions can currently be limited down to the per document level with mentioned references.
Report
The pitch on 'Notion for formal docs' is solid. Notion always starts lagging for us once we pass the 50-page mark on technical specs. Curious about the underlying editor engine though, is this built on something like Prosemirror/TipTap, or did you roll a custom renderer to handle the cross-referencing logic? We deal with massive docs at SquarePact so performance on long-form text is usually the first thing I test. Congrats on the launch!
@govindsajit you are correct! This is built specifically for the 200-page documents that articulate with 100s of other files, sections, terms, exhibits and appendices with the security, scale and performance this requires.
Search and retrieval is also lightning fast no matter how big your document set is.
HERO brings together text, databases, and integrations into one powerful workspace for managing structured documents like contracts, specs, and policies. How do you see a tool like this changing the way your team collaborates on complex projects?
This is super impressive. What’s the one document workflow you think HERO will save you the most pain on?
HERO
@lliloulane This currently appeals to many different areas and we have seen use cased being put together across all major industries. We believe this could be most impactful in:
Legal contracts (Sales Agreement, Fundraising documents, NDAs, Corporate docs, etc.)
HR operations (employment contracts, offer letters, Employee handbook, Stock Option Plans, etc.)
Compliance policies management (cybersecurity, privacy, AI, etc.)
Technical specifications & documentation
Standard operating procedures
I think it's the best to focus on one use case. Managing legal docs how you showed it in the demo, is already a huge step forward and a big value. Maybe I'd narrow it down.
HERO
Build Check
Loved it, Kevin! Absolutely agree on this, we deserve better tools cause we need to also enjoy the process, no only the goal. Wish you all the best here!
HERO
HERO
@german_merlo1 @kevin_touati
Exactly 💪 thanks for checking us out!
Not to be the downer here, but I’m trying to understand the real differentiation from Notion and internal databases. Is the magic mostly in automated cross-referencing or is there more that I may be missing?
HERO
I like the concept, but our biggest issue with Notion-style tools has been performance and permissions at scale. How does HERO avoid slowdowns when dealing with really heavy docs (like 200+ page specs)? And do you support granular access controls per section?
HERO
@zerotox Hi, thanks :)
Yeah performance is key for us, with legal documents often being so large as you mentioned.
We have optimized matters to ensure loading and typing remains fluid and fast no matter the size
Permissions can currently be limited down to the per document level with mentioned references.
The pitch on 'Notion for formal docs' is solid. Notion always starts lagging for us once we pass the 50-page mark on technical specs. Curious about the underlying editor engine though, is this built on something like Prosemirror/TipTap, or did you roll a custom renderer to handle the cross-referencing logic? We deal with massive docs at SquarePact so performance on long-form text is usually the first thing I test. Congrats on the launch!
HERO
HERO
@govindsajit Indeed it does, however you won't find that problem with us! :)
Thanks for the support.
Spiritory
HERO brings together text, databases, and integrations into one powerful workspace for managing structured documents like contracts, specs, and policies. How do you see a tool like this changing the way your team collaborates on complex projects?
HERO