Thanks for checking out HERO 2.0!
I’d love feedback on two areas in particular:
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.
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.
Interesting angle. Does the search use semantic embeddings so it can surface clips by concept rather than filename/metadata? If it nails the retrieval part, that could be the real differentiator.
Absolutely - you can export any selected file, folder or the entire project to .docx or .pdf (or both) effortlessly with only simple clicks and split seconds.
It's already available for you to use in the current version.
Digitally interconnected .. means a way to connect multiple sections and documents across an entire project environment. Currently with MS Word, the idea is to produce static files siloed in the 4 corners of the page. With script, you no longer write on 'paper' but in a dedicated workspace which opens doors to a wide array of 'context-aware' possibilities.
Thanks! We are certainly looking into AI capabilities but are now handful with building the right foundations that will sustain all forms of industry specific LLMs in the future.
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.