We study the work
We talk to managers and the people doing the work. We find duplication, delays and data loss.
Technologies
We study how your company works, find where time and money are lost, and build a product that optimises exactly those processes. Technology is a tool, not the goal.
01 / In short
ITNET develops corporate CRM systems, SaaS and web applications: we study workflows, design roles and data, build the product and help roll it out. We choose the stack for the task: PHP/Hyperf and Python/FastAPI for server-side logic, Vue 3/TypeScript for interfaces, geoservices for routes and CI/CD tooling for stable releases.
Our own products IS PORTAL and BUSPORTAL give us hands-on experience with field teams, service requests and operational data.
02 / Process
Technology only makes sense when it removes a specific manual step or helps someone make a decision.
We talk to managers and the people doing the work. We find duplication, delays and data loss.
We define roles, scenarios, data structure, access rights and the required data exchange with other systems.
The team starts working with the first modules. We refine the next ones based on real usage.
We prepare data, train people, check the process and plan further development after launch.
03 / Technologies
In every project, the technology mix is defined by data, load, roles and integrations. Below are our team’s tools — not a list of features automatically available in every product.
01 / Backend
We separate module responsibilities, process events and give teams up-to-date operational data.
02 / Interfaces
Dispatchers, managers and field staff see exactly the actions and data they need in their workflow.
03 / Geodata
For tasks involving routes and geography, we design maps, route calculation and the exchange of job-location data.
04 / Integrations
We define which systems exchange requests, statuses or payments. Connectors are assessed separately for specific APIs and rules.
05 / AI in the process
We apply AI where the data sources, permitted actions and a way for a person to check the result are defined.
06 / Quality
A test environment, automated checks, deployment and monitoring help us maintain the product after launch.
04 / Practice
We show product scenarios and name separately the capabilities that are assessed before implementation.
01 / Telecom
We build systems for large teams and thousands of daily operations. Our ISPORTAL brings service requests, field jobs, work orders, warehouse and execution control together in one platform.
Work orders for service jobs and internet connections completed by installers each month at our three largest clients
20–27K · 10–15K · 8–12K
The ranges reflect seasonal fluctuations in workload. Each of these clients has more than 90 installers whose work is coordinated by the system.We apply this experience when building platforms for our clients — taking into account daily load, seasonal peaks and business growth.
More about ISPORTAL02 / Bus transport
BUSPORTAL combines online ticket sales through your website, dispatcher work, a driver app and GPS monitoring. Manage schedules, seats and buses, and keep track of payments and expenses in one dashboard.
05 / Answers
Short answers about technologies and the limits of a ready-made solution.
We choose technologies for the task, the existing infrastructure and the product’s development plans. We have experience with Python/FastAPI, PHP/Hyperf, Vue 3/TypeScript, data tools, geoservices and CI/CD. These are examples of our stack, not an exhaustive list: where needed, we work with other technologies too.
No. These are our team’s technologies, not a universal feature list of IS PORTAL or BUSPORTAL. We verify the implementation and availability of each specific capability for every product and project.
There are no ready-made connectors. The scope, direction of data exchange, timeline and cost of an integration are defined separately after we study your system.
Take one real process: who creates the request, who carries it out, what data is needed and how the result is recorded. Based on it, we can assess roles, interfaces, integrations and the scope of the launch.

Next step
At the first meeting, we will find out how your team works today and where the losses are. Afterwards, you will get a clear plan: what to automate and in what order.