[raiyu]

I would be the wrong person to ask about that, as I tried to stay as far away from the details of that along with the low level details around finance. But basically as a public company there a bunch of regulations around a bunch of internal processes, think of it like having a process for how to create emails, or get rid of emails, or have communications, or do various number of internal things, or how you treat customer data.

It is a bit annoying, but ultimately reviewing how those systems are operated in the business and documenting them, while tedious, is a good idea because it allows you to review your security measures and you can use it as a catalyst to make changes and invest in areas that often get neglected in the product market fit/growth phase of a business.

So instead of looking at it as a burden, it becomes an opportunity to just improve internal controls.

[a_c]

Thank you for your reply. Could you give an example of what kind of process is being documented? Is it something like "how to process a customer refund"? I've worked in places where there were a lot of internal document for different workflows. Each workflow is supported by a set of features of a in-house developed tool. The same set of documents is used for on-boarding new joiners and auditing. Are these the set of documents you referring to? If there is a tool that serve as a "no-code editor for internal processes", do you think it is serving any particular pain points?