The ERP software solutions are essential need for any company, regardless of what kind of ERP. Research and practice show that with these software solutions the clients and the providers have broad range of problems and misunderstandings. When one company acquires an ERP or part of it, in predominant number of cases the implementation stage necessitates specific needs, adjustments or alterations that reflect in the ultimate product. Every time the clients feel pressured and conditioned by the provider during each of the implementation or live stages. Also, the impression persists that the solution is overly-expensive especially when modifications and alterations are needed, and they need to come from the same provider. The radical change of the software is excessively pricey and budgets have already been spent for the existing solution. On the other side, the implementer and the provider have the impression that they haven’t been paid enough for all they have done for the user. It is not rare for incorporation of a mediator to regulate the mutual obligations and rights between the customer and the provider, which is another component that increases costs. The client usually pays lump sum for support which is very irritating because no visible efforts are taking place, while on the other side the implementer/provider consider to be charging too little for support when providing flawless software that necessitates lot of funds. Another big problem is when the customer requires additional features and/or modifications and waits for significant duration which costs a lot of money. When any of the additional features/modules are finally functional, the circumstances and context have changed significantly, and they are of no substantial use any more.
It is time to disrupt the situation where one-big-provider is offering overly expensive rigid ERP solution to high-end enterprises in a love-hate relationship.
In order to reduce the misunderstandings between the providers/implementers of the ERP software solutions and the clients, a decentralized system offers several improvements. The EOS operative system, its decentralisation, its dispersion as well as possibility to use smart contracts, gives remarkable opportunities to overcome the above mentioned burning issues. The ERP software solution will be Open Source, which can be updated and maintained by, independent software teams, independent implementation teams, and the clients who are many (many-to-many, not one-to-one). In such a decentralized system for which the perfect solution is EOS, the users will be able to use various implementation teams for the same software solution, also use various teams for software production and various for software updates. If we create a dashboard on which the users will publish their needs as well as state how many tokens will be transferred to the implementer team, the cumulative number of tokens offered from many users with the same needs will be the incentive for the teams to uptake an assignment and fulfill it with best possible quality. That will maintain high level of motivation, quality and user service as well as mechanism for improvement of the ERP on continuous basis. When a team considers the number of tokens sufficient for their work, they will be able to complete the task and obtain the tokens, on the first-come-first-served principles. This allows decentralisation and liberation of the process of acquiring, production and implementation of any software solution. The teams that would work on maintenance and improvement of the software based on user needs or its implementation would have to freeze certain number of tokens and will be in position to uptake tasks that are in number maximum 20 times higher than their frozen tokens. The smart contract will allow distribution of the tokens to the team who has completed the task, if and only if it is done properly and with the expected quality. The teams who receive negative references for bad performance will not be able to uptake future tasks or assignments or will be excluded as teams from the decentralised systems. Such a framework, based on blockchain technology would allow more fair coopetition (collaboration and competition) and position of both providers/implementers and users.
We are building decentralised, community-based, marketplace facilitated modular ERP solutions applicable and affordable for all company sizes. ZERP grows from tradition of ERP solutions to the next stage where smart contracts and blockchain technology are utilised with their best traits.
The ZYGOT token is the core resource that powers the ZERP engine. Its usage will be present in multiple mechanisms throughout the ZERP ecosystem. One modality of usage will work as follows: The users will have to stake certain amount of tokens based on the modules they want to unlock. The tokens will be locked in a smart contract for certain amount of time (e.g. 1 year). If the user decides to unlock the tokens and disable a module, he/she will be ‘penalized’ with certain amount of tokens based on the timeframe of usage. If necessary, the amount of tokens locked for the modules can be voted by the community and recalibrated accordingly. Another modality of use would be: The tokens will fuel the smart contracts that are used as a mechanism for interoperability between different instances of the engine. Examples of these are document exchange between companies, automated contracts between companies (e.g. supplier and consumer), cross-integrations between companies and access management (permissions to federated users and policies) to their databases (extranet). Third modality of use of the tokens is for the general governance throughout the system. The users can vote on variety of properties of the system (module pricing/staking, dispute mechanism, protocol changes, etc..). The tokens will also be used in the ZERP marketplace. Development teams will have to stake a certain amount of tokens in order to be eligible to accept tasks from a certain company (which also uses tokens in order to be able to request/pay a change/addition for their instance).
From the very beginning, Zygot’s vision was to respect certain governing principles. At first, the idea was that those principles are respected internally in the company, and then iteratively expand to the broader community. One of them is transparency. That is why we decided to follow Aragon’s transparency model. As per our Transparency Model, we do quarterly Transparency Reports of our use of funds and about the overall progress of the project. Respecting the above principle, below is the token distribution information: There will be a total of 300.000.000 Zygot tokens. 10% of the tokens are reserved for the early community supporters. Certain requirements/tasks will have to be fulfilled in order for a community member to be eligible to receive the tokens. E.g. vote for exchange listing, join telegram, test the alpha version and give feedback, reddit, etc.. 15% of the tokens will be locked in a transparent manner (smart contract) for the team and will be given in a vested form over 5 years. This decision can be altered by the majority of the token holders in case of transitioning to a DAO form. 60% of the tokens will be sold to private funds/pools as a fundraising mechanism. 15% of the tokens will be held in the company wallet and be used for powering partnerships, advisors, references. Those tokens will also be locked in smart contracts, and the company can only use a certain % per annum (the % can be at least 3% per annum or more (increase as voted by the community)
Due to the current nature of the crypto ecosystem, it is not really straight forward for new users to acquire tokens. They usually need to go to unfamiliar 3rd party exchanges, verify, set up pins and additional security layers. This creates friction and makes our product onboarding more complicated, while our basic principle is fluent, optimized route. That is why, from the very beginning we will implement a mechanism that would provide a way to acquire tokens directly from our website. This would be done in a transparent way, where our backend will buy tokens on the available exchanges on behalf of the user, according current market prices, with no margin or any alteration whatsoever for acting as a kind of intermediary in the process. Since this would be a completely decentralized/open source solution, we (Zygot LTD) do not require a money transmitting license. Besides the ease of access, this would provide more liquidity of the token on the exchanges. Reports including links and audits will be provided, so everyone can monitor this process. This will by no means affect the price decided by the open market.