Ubix.Network ecosystem analytics
An internal analytics system for the Ubix.Network ecosystem. It replaced a dozen spreadsheets tied together by formulas, gathered the statistics of every project in one place and hands them on through a role model: reports to the managers, API to the services.
- Client
- Ubix.Network
- Industry
- Blockchain, Fintech
- Services
- Web3 and blockchain, Backend, Frontend, Software, Analytics, Prototyping, MVP development, Web3 experience, Business consulting, Technical audit
- Period
- 2021-2025
How it used to work
The ecosystem holds more than ten projects, each with its own manager. Each of them kept a spreadsheet of their own: spending by employee, by task, by everything else. The spreadsheets were tied by formulas into one shared document, with access rights layered on top so that a manager of one project could not see another project's figures.
While there were few projects, the arrangement held. Then the manual work passed every reasonable mark and the managers stopped running projects: they were filling in spreadsheets. That was the moment the owners decided they needed a system of their own.
What stood in the way of simply counting
A difficulty of its own lay in the money itself. The ecosystem is built on blockchain, part of the settlements happen in cryptocurrency, and the figures in the reports changed on their own: the same expense looked different yesterday and today purely because of the rate. Adding numbers like that up in a spreadsheet and getting a meaningful total is not possible, and this too was sorted out by hand.
What we built
The system collects the data itself and gathers the statistics of every project in one place. From there it hands them on through a role model: part goes as reports to an internal dashboard for managers and owners, part goes by API into the services themselves. In UbiStake a user sees their own report on accruals and airdrops, and those figures come from here.
It counts spending on labour, investment in advertising, the purchase of advertising placements and the other costs of the projects. Exchange-rate differences are accounted for, so the total no longer depends on which day you looked at it.
Where the real work was
Programming took some twenty per cent, no more. The rest was going through the figures, doing the calculations and holding the discussions after which the product itself changed.
It is not enough to know what a service returns and through which API. A report has to show the money straight away and at the same time let you descend to a single entity: not to a department but to a particular employee; not to a whole advertising campaign but to an individual ad and the placement it ran on. Things like that are designed not from a specification but from an understanding of how money is counted in this particular business. That is where business consulting and technical audit came in useful, not only the ability to write code.
A project that never had a finish
This system was never a finished product. New reports appeared, calculation formulas changed, new areas were added. Some things had to be reconsidered after release, others deepened and taken further. Part of the ideas did not take root: some stopped being relevant, others turned out to be tied to one-off events and proved nothing in day-to-day work.
The main goals were met all the same. Collecting the data became automatic instead of manual, the statistics came together in one place, and looking at them became convenient.
Why there are no screens here
The system is internal, and its screens show the money and the people of the ecosystem. We are not at liberty to show that, so this case is text only.
Ubix.Network ecosystem analytics stack
What the project is made of
The agency services it took to launch it.
- ServiceWeb3 and blockchainDevelopment of Web3 solutions that people trust with their money: smart contracts, wallets, trading and staking platforms, decentralised applications.
- ServiceBackendBackend and API development: a server side that holds the load, keeps the data and updates without stopping the service. We take the project as a separate stage or place a devel...
- ServiceFrontendFrontend development and markup to order: we build an interface that holds up equally on a phone and on a wide monitor, opens fast and stays readable on real data. We take the p...
- ServiceSoftwareCustom software development for a specific business task: from a program on an employee desktop to a server service that runs without people. We build what off-the-shelf product...
- ServiceAnalyticsDashboard and monitoring system development: we collect data from different systems into one picture and show what decisions are actually made on.
- ServicePrototypingApp and interface prototyping before a single line of code is written. A clickable prototype shows what a person will do in the product and where they will stop, and it costs se...
- ServiceMVP developmentMVP development is a working version of a product built small, made for one purpose: to test demand on real people rather than in a presentation. Finding out in a few weeks that...
- ServiceWeb3 experienceOur blockchain experience came both from individual commissions and from an ecosystem we ran for years together with its owners and their team. This page is about what we unders...
- ServiceBusiness consultingBusiness consulting answers the question of whether to do it at all and, if so, in what order. We review processes, the product and the figures, work out where you are losing mo...
- ServiceTechnical auditA technical audit of what already runs: code, architecture, infrastructure, security and interfaces. The deliverable is a report with priorities: what to fix now, what can wait,...