Skip to content
RBSX

Software studio · Tashkent

We build software that still works in year two.

RBSX designs and builds CRM systems, internal platforms, and mobile apps for companies that depend on them every day. Not demos. Systems your staff opens at 9am.

Live

Sales pipeline

Open pipeline

128

Closed this month

34

Average cycle

18d

Uptime

99.9%

  • New24
  • Qualified17
  • Proposal11
  • Won7
Illustrative interface

Based in

Tashkent, UZ

We reply in

1 business day

Scope and date

Fixed upfront

Code ownership

Yours from day one

What we build with

  • TypeScript
  • Next.js
  • React Native
  • NestJS
  • PostgreSQL
  • Go
  • Docker
  • AWS

Services

Six things we do properly

We turned down the rest. A short list is how the quality stays where it is.

CRM systems

Sales pipelines, deal automation, and reporting shaped around how your team actually sells, instead of a template you have to work around.

Marketing sites

Fast, indexable sites in Uzbek, Russian, and English. Built to rank and convert, not only to look good in a screenshot.

Mobile apps

One React Native codebase for iOS and Android, with the release pipeline set up so your team can ship without calling us.

Internal platforms

Dashboards, admin panels, and operations tools for the work your spreadsheets stopped being able to handle.

Product design

Flows and interfaces designed in the browser, so the thing you approve is the thing that gets built.

Support and handover

Documentation, monitoring, and a maintenance window. The repository and the infrastructure are in your accounts from day one.

Process

Four stages, in this order

The order matters. Skipping the first one is why projects run late.

  1. 012 weeks

    Scope

    We map the work, name the risks, and write down what is out of scope. You leave with a fixed price and a date.

  2. 022 to 4 weeks

    Design

    Screens and flows reviewed weekly. Nothing enters the build queue until you have clicked through it yourself.

  3. 036 to 16 weeks

    Build

    Weekly releases to a staging URL. You see progress every Friday, not once at the end.

  4. 041 week, then support

    Handover

    Repository, infrastructure, documentation, and a walkthrough with your team. Then an agreed support window.

Selected work

What we have shipped

A sample of recent engagements. Some clients ask us not to publish details, so this list is shorter than the real one.

CRM platform2025

SalesPro CRM

Deal pipeline, quota tracking, and daily sales reporting for a distribution business running twelve regional branches.

Stack

  • Next.js
  • NestJS
  • PostgreSQL
Mobile app2024

EduApp

Course delivery app with offline lessons, so students on weak connections can keep working through a module.

Stack

  • React Native
  • Expo
  • Supabase
Web dashboard2025

FinTech Console

Transaction dashboards with role-based access, audit logging, and exports the finance team stopped rebuilding in Excel.

Stack

  • Next.js
  • Go
  • ClickHouse
Marketing site2024

MedCare

Clinic site with online booking, published in three languages and structured so each service page can rank on its own.

Stack

  • Next.js
  • Sanity
  • Vercel
Operations tool2023

LogiTrack

Dispatch and route planning for a freight operator, with live vehicle positions on a map their dispatchers trust.

Stack

  • React
  • Django
  • PostGIS
E-commerce2025

ShopEase

Storefront rebuild focused on checkout, search, and product pages that Google can read without running JavaScript.

Stack

  • Next.js
  • Medusa
  • Stripe

About

A small team, on purpose

RBSX started in Tashkent in 2020. We stayed small because the work we take on needs the people who scoped it to also write it.

Every project runs with a lead engineer who sat in the first meeting and is still there at handover. There is no account layer between you and the people building the thing.

What that means in practice

You talk to the engineer, not a project coordinator
Weekly releases to a staging URL you can open
Scope changes get priced before they get built
The repository lives in your organisation, not ours
We write the documentation while we build, not after
If we cannot hit your date, we say so before you sign

Team

The people who write the code

Four engineers. The names below are who you will be working with.

Shoxrux Ruzibayev

Backend engineer

Sardorbek Hafizov

Backend engineer, design

Questions

Asked before every project

How long does a project take?

A marketing site runs four to six weeks. A CRM or internal platform runs three to six months. We give you the exact number at the end of the scoping stage, before you commit.

How do you price work?

Fixed price per stage, agreed after scoping. Scope changes are quoted separately before anyone starts building them. We do not bill by the hour on fixed-scope work.

Who owns the code?

You do. The repository and the cloud accounts are created in your organisation at the start, and we work inside them. Nothing is held back at handover.

What happens after launch?

A support window is included with every build. After that you can keep us on a monthly retainer or take it in-house, and we hand over documentation either way.

Do you work with clients outside Uzbekistan?

Yes. We work in Uzbek, Russian, and English, and we run projects remotely across Central Asia and Europe. Contracts can be signed in UZS or USD.

Contact

Tell us what you are trying to build

Send a short description of the problem. We reply within one business day with questions, a rough range, and whether we are the right team for it.

Direct

Fill this in and we will come back within one business day. If you would rather talk first, the phone number and email are on the right.

Start a project

Uzbek number, formatted as you type

We use your details to reply to this message and nothing else.