brunovegreville

Great idea, I agree with the premise that a lot of (side-)projects start with basic needs in terms of DB.

Would be interested - to understand how you think about pricing in the future? - to understand how you see recent progress with LLMs impacting this project? I'd love to have the same UX (upload a JSON) but be able to query this JSON with NLP through GPT

Definitely a big inspiration for us! Thanks:)

I agree with your analysis, but I think there is significant impact on features you can build on top of "store files locally", including collaborative features (sharing meeting notes without too much frictions) On a personal note, I prefer the locally stored path as well.

To name a few: - Tight integration between your calendar and the context (notes, actions) related. The notes you take are automatically linked to this calendar event, the attendees, potential past related meetings

- The notes you take in Hera can feed into other tools, for instance Todoist for your next actions.

- Fewer friction points: you click on one button and it opens your Zoom/GMeet/... and your notes where you find back your preparation. Spinning a new page in Notion is not that hard, but you would be surprised by what small friction points do over time.

Your meeting notes are linked together if they are linked to the same "group of meetings" (that we call Streams). So that when you enter your "Weekly Product", Hera gives you a quick access to the outcomes (highlights, next actions) of the previous Weekly Product(s) meetings

Also, Hera tries to understand (nothing fancy or machine learning-related) what you do with your meetings. If you always use the same template of notes in meetings with a title "1o1 John - Bruno", Hera will suggest you to do it for you in the future.

I've logged your feedback, thanks!

Sorry Danny, it's a big mistake on our side, the privacy policy should be crystal clear.

- On calendar's data: we only use the title, description, etc. of the calendars you have chosen to sync in Hera. - On google drive files, I will clarify this right now, but basically we have an export feature to google docs, which is entirely opt-in. If you want to use the feature, the first time of course you need to give us access to a small subset of your GDrive

- We do not and never intend to sell any of these data to anyone. I reword the privacy policy so that's crystal clear:)

Great remark. The recurring fee is mainly tied to the fact that the value you get from Hera should grow over time.

The more meeting notes you write into Hera, the more connected all your meetings will be and the more context Hera will be able to provide you in each meeting.

It's not like a one-time tool that you always use to do the same thing. I am not saying that we won't test one-time price at some point, but it's not in our short-term plans.

Merci!!

Good question, mainly two points: 1. We had deep expertise in Electron and web dev. We are 4 months old so we wanted to validate the problem AND our solution as quickly as possible.

2. Meetings, by essence, have many stakeholders. Some (if not most) of the attendees are not on Hera and this is where having our core product mostly web compatible will proved to be useful - we can easily spin up for instance a public page to share the outcomes of your meeting to people not using hera

Totally get that the safety of your meeting notes is top priority. We have not yet settled on whether we want to choose the "notes stored locally" path or the "fully encrypted on our server" path, mainly because of the impact on features we want to build in the upcoming years.

We will communicate publicly as soon as we take a strong stance.

No problem, thanks for taking the time to comment :)

Totally understandable!