What drives the price
The price depends on how many flows the first version covers and how many customers it must serve at once. The MVP tier is the product core, sign-in, roles and an admin panel, enough to sell to the first customers and learn what they pay for. Product adds dashboards, integrations and data import and export, without which companies do not move off their spreadsheets. The SaaS tier brings multi-tenancy with data isolation, subscriptions with automatic billing, a public API and white-label for resale under a partner’s brand. Tier prices are in the table below. The scope of each stage is fixed in the contract, and the next stage can be ordered after the first sales.
How the work goes
We start with the data and permission model: who the tenants, users and roles are, and what each can see and change. A mistake at this step is the most expensive one later, so the schema is agreed in writing. Then we design the key flow and build it end to end, from sign-up to the result the customer pays for. We work in two-week cycles: at the end of each you get a working version on a staging environment, not a percent-complete report. Automated tests, logging and zero-downtime releases are in place from day one. Bugs found after launch are fixed free of charge, with no time limit.
Local specifics
Subscriptions here are often paid with Humo and Uzcard cards through Payme, Click or Uzum, while companies pay by bank transfer against an invoice. So billing supports both automatic charges and manual confirmation by an accountant, along with closing documents. B2B customers usually need a 1C exchange for invoices, completion certificates and reference data. The interface is built in Uzbek and Russian from the start rather than translated at the end, which otherwise breaks layouts and emails. Sign-in codes and payment reminders go out by SMS through Eskiz, and event notifications go to Telegram, which customers open more often than email. Plans can be shown in soums, with foreign customers billed in dollars.
Common mistakes and risks
The main SaaS risk is data leaking between customers. If isolation is only an interface filter, changing a number in the address bar reveals the invoices and contacts of another company. Products assembled quickly with AI and no engineering review often look like this: they work in a demo, but the server checks no permissions, keys sit in the code and backups are missing. The second risk is billing that silently fails to renew subscriptions or charges twice. The third is an architecture that cannot take growth. We check permissions on every request and cover isolation with dedicated tests, and your engineer may check the code against the contract: if an item is not fulfilled, 10% is refunded.