Client portal and customer account development Client portal

An account where your client, partner or employee solves their own question: sees documents, order status and invoices, files a request and pays online.

Price
from $8,000
Timeline
from 6 weeks

Price and deadline are fixed in the contract before work starts

What is included

  • 01Sign-in by phone or email, roles and permissions
  • 02Documents, invoices and statuses in one place
  • 03Requests and tickets with history
  • 04Online payments
  • 05Integration with your CRM, ERP or 1C
  • 06Notifications by email, SMS or Telegram

Who it is for

  • Companies with a high volume of routine requests
  • Dealer and partner networks
  • Service companies that issue invoices and completion certificates

Three levels and prices

Pick the level that fits the task and budget. The exact scope is assembled in the configurator and fixed in the contract.

Account

Sign-in, profile, requests and statuses, documents, admin panel

$8,000–15,000

≈ UZS 96M · from 6 weeks

Portal

Roles, integrations, reports, notifications

$25,000–40,000

≈ UZS 300M · from 12 weeks

Ecosystem

Several portals, mobile app, analytics

$45,000–80,000

≈ UZS 540M · from 20 weeks

UZS amounts are indicative, at the Central Bank of Uzbekistan rate on 14.11.2026. Contracts are in USD, or in UZS at the rate on the invoice date.

In detail

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.

What the contract says

2%

for every day we are late

If we are late, your invoice drops by 2% a day, up to 10% of the contract. So we only name deadlines we can keep.

1

company per niche per city

For a year we do not take on your competitor in your city. What we build for you does not end up next door.

10%

refund after an outside review

Bring your own engineer. They check the code against the contract. If a contracted item is missing, we refund 10%.

Questions

How much does a client portal cost?

From $8,000, with a timeline from 6 weeks. The price depends on the number of roles, sections and integrations with your systems. The exact amount is fixed in the contract.

Can the portal connect to our back-office system?

Yes, via API or file exchange. The list of integrations is defined during discovery and written into the contract.

How is customer data protected?

Roles and permissions on every action, an audit log, encryption in transit. Security requirements are fixed in the contract.

Do we need a mobile app?

Usually not: the portal works in a phone browser. We add an app once the portal is used daily.

Other solutions

Practice: Web Platforms