@IT Cloud Solutions
A simpler, more efficient solution
to your Growth and Profit-Making needs!
“Investors and Entrepreneurs!
We are doing Deals Now .. ”
Step in at the ground floor and get set for meteoric rises as this ELEVATOR takes you on board our very modern small-to-medium Business Technology “Ship”.
In the Venture360.co Deal Room (“Let’s Talk” button below) you can register and after discussions, view our monthly Business Plan (detailing monthly cash flows for 6.5 years from commencement of coding of Front End).
Basically we are attempting to raise $1.85 mill AUD to complete development of Chubba Morris/convey-IT/Cheirrs, mainly including the initial sales program. The 1.85 million will secure a 49% share in the company, with an expected Return Rate for the 1.85 mill (ie 49% Share) being 43.77% per annum compounding across 6.5 years. The future also bodes well. Firstly, one of the major drivers of profit is the potential margin in the Land Title Registration Market for our convey-IT. Gross Revenue from Land Title Transactions alone, for our company, is predicted to be increasing by more than $14,000 each month, continuously, on the back of direct sales to Solicitors, and evidence-based, conservative & quantitative predictions of word-of-mouth recommendations amongst Solicitors. Further, our company specialises in building and deploying Enterprise Accounting Distributed Applications on BlockChains, and as such we are experienced in building “fully normalised” databases (for connection to blockchains, and otherwise) and in working with teams of front end and middleware developers, employing formal (plain English) use case descriptions, screen mock-ups and data-maps, to convey our customers’ requirements. “Chubba Morris” does not constitute our entire potential, as reference to other pages here will show.
This is far from a “vacuous” plan. We have definite sales strategies and targets, with “Conservative”, “Planned” and “Target” sales success predictions built in as variables, dependent upon various sales success rates across regions and cities.
We have completed coding of the database structure with over 600 tables (in PostgreSQL ) for “Cheirrs“ and “Chubba Morris“ (& soon for “convey-IT“), ready to deploy in connection with Elastos SideChains of our own. Many of the 300+ use case views and trigger functions are yet to be completed but are on track. Although with limited resources, the pilot edition front end UI’s are progressing. We have a fully functioning database/webserver/carrier/blockchain/front end connection, where requests can be issued to the webserver, and responses from the database received and read, as expected. We are currently coding the Business Process Design Interface to define Contract and Business Process Types in the database, which will lead to completion of an initial, and very fundamental Use Case (the Accounting System). We will soon be able to demonstrate this working Use Case from its Front End GUI (in this case the various parties’ g.u.i’s) as a Contract is enacted, via an Elastos TestNet SideChain, through to Back End database information storage, following the rules for multi-party Transactional Accounting.
The above development means we are also on the verge of completing the groundwork for ‘The General’, & for ‘Cheirrs’. Consequently we are nearly in a position, after we have validated the operation of the accounting system, to offer The General as a DApp (Distributed Application) for license, with no preference between the Chubba Morris project (equity-funded) and The General (leased with initial costs). Cheirrs is dependent on the prior commencement of The General (at least one Business Network) or Chubba Morris.
The core Accounting System (our Block ‘n’ Tackle™ ) forms the basis for extensive native integrations within the applications. This includes all systems and tables on the database. It means, say, the Human Resources and Payroll Systems are not divorced from the rest of the system’s data (or each other), as well as many other integrations naturally occurring, including dispensing (where possible) with insecure email communications in favour of the web-socket-safe “Elastos Carrier Worldwide Network” of ultra-secure inter-node communication.
6. Always cash payments to be made to and from actual bank accounts. 7. All parties’ bookkeeping to be done for entirely internal payments; Only bookkeep for the internal party whenever an external party also involved. 8. The Actual Transaction handler or UpdateMaster() function needs to consistently and automatically cope with transactions of any legal (validated) kind involving an unlimited number of parties and where a Tx Date may be any legal (valid) date or Amount, either debit or credit, and must always ensure credits and debits balance appropriately. Note that a transaction occurring earlier than the present (ie essentially every transaction) is to be followed by an update of each financially affected historically subsequent account balance, up to and including all affected present records. This ripple-through effect of transactional functions is essential behaviour and relies on the Elastos BlockChain’s own Update functions. 9. The GUI Form and the need for an identical
Headless Form implies the existence of a General Accounting Journal Object with fields for the ledgers/ accounts /classes/ branches/ programs/ projects/ etc, and amounts, to post to the appropriate CFinance-Class//Objects/Structs/Fields in the Master Ledger. I believe the Accounting Journal needs to be implemented in the node.js Middleware. 10. There needs to be provision for an unlimited number of parties in a single Transaction (ie unique TxNum).>
Take Me To Venture360.co Deal Room