Cross-posting here the feedback from Wei at Polkadot Direction channel & our reply to it:

Wei:

I've actually tried to explore on a similar direction like this for my own "enterprise" need, but ended up writing a bunch of automated and manual scripts for what I require (I call the code autovault and autovault-manual).

The problem I realized was that it's quite hard to define the various "enterprise routines" -- you may end up just defining a routine for a single user, but it'll unlikely work with other users because they usually have vastly different requirements and setups. Many of the routines are also tightly integrated with some other internal systems, and they will also be quite hard to generalize (for example, wallet definitions, staking op integrations, etc). You also mentioned things like accounting and taxation, which will also be different across countries and may take quite a large amount of resources to implement.

In general, I'd be quite looking forward to this, especially the code. But my feedback for now is that you might have underestimated the work required getting beyond PoC.

Reply:

Thank you so much Wei for your review & feedback!
It matches well with what we have found from the interviews with several Enterprise entities, that's the way which usually they choose -- writing own scripts to perform dedicated tasks (crowdloan contributions, managing validators/nominators, etc).

I do think that this can be improved by creating an app which focuses on Enterprise/Advanced needs of the community. The goal for the team would be to conduct as much interviews as possible with enterprise entities to form a backlog of "pain points" from existing apps/tools & ideas/wishes how can ideal app look like based on their opinion. Then the team's job is to find a way to address intersections of such -- from our experience most of the enterprise entities would like to have a convenient way of performing MST operations, that would be a point to start with.

As for the taxation -- I see that Omni's role here would be to find a way to integrate with commonly used tools for paying taxes (e.g. https://cointracking.info/ or https://koinly.io/). That's being said, at minimum Omni should provide a way to aggregate from datasources (blockchain/indexers), validated the completeness and correctness of such (e.g. by cross-checking several datasources), and then export required information (e.g. in .CSV) format for the tool to proceed with taxation. Further this can be expanded by more advanced integrations with these tools (expanding supporting list of such and improve the integrations themselves)

I completely agree that it's a challenge to estimate something relatively complex and large-scale project like that, that's the reason why we would like to go step-by-step with our first milestone focused on spending resources for conducting interviews (for requirements elicitation), shaping the software architecture and designing UX/UI. PoC should be considered as an outcome from JS engineers which will work in parallel with the rest of the team on fundamental features (integration with cold wallets, connection to the network, runtime fetch & parsing, etc) while the Omni as a product gets refined & shaped from the interviews & discussions outcomes

Dear councillors & community! ✨

Our team has decided to conduct a public Walkthrough session for the Omni Enterprise proposal on the 24th of January at 15:00 CET.

Please feel free to it add to your calendar 📅

https://calendar.google.com/event?action=TEMPLATE&tmeid=MDQ5bWdtbTd0dTJrZWhlaDNkY2QwNXNlZXIgY180YTVzazQzdXU2cWJhNjlwZjJwa3NkbG5vb0Bn&tmsrc=c_4a5sk43uu6qba69pf2pksdlnoo%40group.calendar.google.com

Everyone is welcome to join, and we would like to answer any questions at the end of the session. The session will be recorded, link to which will be provided afterward