What drives the price
Three things set the price: how many roles with different permissions work in the portal, how much data it pulls from your systems and how automated the processes inside are. The Account tier covers sign-in, a profile, requests with statuses, documents and a staff panel, so clients stop calling to ask where their order is. Portal adds roles, integrations with back-office systems, reports and notifications, for when partners, dealers and several departments use it. Ecosystem means several connected portals, a mobile app and analytics across all of them. The tiers with prices are in the table below, and the exact list of roles and integrations is written into the contract.
How the work goes
First we list the questions clients and partners currently phone or message your office about, and decide which of them the portal will answer on its own. Next comes the permission matrix: what each role sees, changes and signs. It is agreed before design, because every screen depends on it. Integrations start early: we get test access to your CRM, ERP or 1C and check the exchange on real data. Every two weeks you receive a working version and sign in to it under different roles. Before launch we run security and load testing. Bugs found after launch are fixed free of charge, with no time limit.
Local specifics
Documents for a portal here usually live in 1C, so invoices, reconciliation statements and contract balances are pulled from there rather than uploaded by hand. Sign-in by phone number with an SMS code through Eskiz is more familiar than a password and email. Notifications about new invoices and statuses work best in Telegram, where clients see them sooner than in email. Paying an invoice straight from the portal goes through Payme, Click or Uzum, while companies keep paying by bank transfer with automatic matching. The portal is built in Uzbek and Russian, and documents are shown in the language accounting issued them in. For electronic document flow, Didox and E-imzo can be connected.
Common mistakes and risks
A portal holds the most sensitive data: contracts, amounts, phone numbers, addresses. A typical vulnerability is a document that opens by direct link without checking who owns it, so by iterating numbers anyone can download the files of every client. Cheap and AI-generated portals are often built this way, with permissions checked only in the interface. Another risk is a 1C exchange that breaks silently: the client sees an outdated debt, argues with the manager, and trust in the portal is gone. We check permissions on the server for every request, keep an action log, monitor the exchange and alert on failures. Your engineer may check the code against the contract; if an item is not fulfilled, 10% is refunded.