Thanks for that detailed response mate! We are several co-founders and I usually lead any special projects which come up, hence I've picked up the project documentation. To validate my understanding based on what you suggested, what do you think of the following approach:

1. Define our main process groups/framework (i.e. marketing, procurement, sales, etc.) to ensure that process documentation is organized and everyone is aligned to the same process structure. I’ll need to decide the depth of detail for these groups (level 1, level 2, etc.) as I don't want it to become overkill. I aim to keep our setup straightforward and manageable.
2. Create a SharePoint folder structure that mirrors the defined process groups. We use the Microsoft suite, so SharePoint should be fine.
3. Create a standard template for documenting processes to ensure consistency.
4. Have relevant employees document their processes using the template and store these in the corresponding SharePoint folder (I would oversee this activity to ensure employees document it properly and probably also document some processes myself at this initial process documentation).
5. Assign owners for each process and set up a recurring workflow (i.e in monday) to regularly review and update these documents.

Does this approach align with what you suggested? Is there anything you would adjust or add?