Available for new projects
Is your business still being run out of Excel and a group chat?
I bring the warehouse, sales and reporting into one system. The picker scans on their phone, the director gets the report ready-made, and nothing disappears into a chat.
- 5
- systems running real businesses
- 4
- client types: web, Android, PWA, Telegram
- 3
- languages: Uzbek, Russian, English
- 1
- point of contact — no middlemen
Sales, week
148,2M
Orders
312
Receivable
29,4M
Sales by day
Excel01
Does any of this sound familiar?
If two of these describe you, the problem is not your people — it is that there is no system.
To learn a stock level you phone the warehouse, because the number in Excel does not match reality
The report is assembled by hand every week, formulas are copied from file to file, and the numbers stop agreeing
Orders get lost in a group chat — who ordered what, and where it stands, is anyone's guess
Expired stock sits in the warehouse and you only find out when a customer sends it back
Who owes how much, and which invoice is settled — there is no reliable answer
Two systems cannot see each other, so data is carried from one to the other by hand
02
Before and after
Every row below comes from systems that actually shipped.
Stock levels
A phone call to the warehouse, or yesterday's spreadsheet
Reporting
Assembled by hand in Excel, taking hours
Orders
Plain text in a chat, with no status to check
Picking
A paper list and memory — the error surfaces at the customer
Receivables
A separate spreadsheet, and who paid when lives in someone's head
Between systems
Data is re-keyed by hand and mistakes slip through unnoticed
Stock levels
On screen in real time, with lot and expiry date
Reporting
One click produces the finished file
Orders
Each one numbered, with its status and history visible
Picking
Barcode on the phone; the system refuses the wrong item
Receivables
An automatic aging report and a client statement
Between systems
Automatic exchange; a failure retries, and nothing is lost
03
What the system looks like
The screens below are drawn with sample data — no real client data is shown.
In the picker's hand
The pick list, the barcode scanner and expiry control. Choose the wrong lot and the system stops you.
On the director's screen
Daily numbers, the sales trend, and a one-click export to Excel.
In the customer's Telegram
Catalogue, cart and checkout — nothing to install, right where the customer already is.
04
Selected work
Each of these runs a real business every day. Client names and internal addresses are withheld.
Logistics & distribution
Warehouse Management System (WMS)
The full warehouse cycle from receiving to dispatch for a large FMCG distributor — four client apps and live sync with an external ERP.
ERP & finance
Multi-tenant ERP platform
One codebase serving many companies: sales, receivables, invoicing and reliable hand-off of orders to the warehouse system.
BI & reporting
Analytics dashboard on top of an ERP
A dashboard that ingests the ERP export, cleans it, and lets people assemble a new report without a developer. Deployed at two distribution companies.
05
What I can do
The kind of work people usually come to me with.
Warehouse & logistics system
Receiving, put-away, picking and stock counts. Barcodes, lot and expiry tracking, a mobile app, offline mode.
ERP & business backend
Sales, clients, payments, invoices and receivables. Roles and data-scope levels, audit logging, migrations.
Reporting & analytics dashboard
I turn the data already in your systems into a dashboard people read. Excel import/export, and a builder so they can assemble their own report.
Telegram bot & Mini App
Orders, catalogue, cart and checkout — where your customers already are. Nothing to install.
Systems integration
Two systems that do not talk — I build reliable exchange over an API, a queue and a worker. Failures retry, nothing is silently lost.
Internal mobile app
An Android app for the field rep, the picker or the sales agent: scanner, offline queue, push notifications.
06
How we work
At every stage you know in advance what you get at the end of it.
- 01
First conversation
30–60 minutes · free
I listen to how you work today and ask questions. If the problem can be solved without a system, I will say so plainly.
- 02
Analysis and proposal
1–2 weeks
I map the process: what gets automated, what stays manual. Timeline and price are set out in a written proposal.
- 03
Build
In stages
At the end of each stage I show you a working piece — no surprises at the end of the month.
- 04
Rollout and training
With a first month of support
I deploy it, train the staff and watch the first month in use. Documentation is part of the scope.
07
Ways to start
You do not have to start with a big project. Most people start small.
Audit
I study your processes and write up where automation would pay off most.
- A process map and a list of bottlenecks
- A recommendation on what to tackle first
- Indicative timeline and budget
- No obligation to continue with me
Pilot module
We close one painful process end to end. Once you see it working, we extend.
- One module: picking, reporting or order intake
- A working product, not a prototype
- Staff training included
- An architecture that is ready to grow
Full system
Warehouse, sales, finance and a mobile app — one system, delivered in stages.
- Multiple modules and a role system
- Integration with your existing ERP or 1C
- An Android mobile app
- Server, deployment and documentation
08
Stack
The tools I reach for daily.
Backend
Frontend
Mobile
Integration & infrastructure
Domain expertise
09
About
I understand the business process first and write code second. How the warehouse actually moves, where stock gets stuck, who needs which report — skip that and the system never lands.
For the past few years my focus has been ERP and WMS: lot and expiry tracking, FEFO, barcode picking, multi-tenant architecture, receivables and invoicing, integrations with third-party ERP systems.
I take a system end to end: from the database schema to the mobile app and the deploy script on the server. When it is needed, user training and documentation are mine too.
- Role
- Full-stack developer
- Location
- Tashkent, Uzbekistan
- Languages
- O'zbek · Русский · English
10
Frequently asked questions
How much does it cost?
It depends on the scope — a single module and a full system differ by a multiple. I give a firm number after the first conversation and the analysis, in a written proposal. The cheapest way to find out up front is the audit.
How long does it take?
A pilot module is usually 4–6 weeks. A full system starts at three months and is split into stages — you see the first working piece within a month.
Who owns the code?
You do. Full access to the repository, the server and the database stays with you. Documentation so another developer can pick it up is part of the scope.
Will it work with our existing 1C or ERP?
Yes. Building reliable exchange between systems is a large part of what I do — two of my current projects sync with an external ERP. If there is no API, we find a way through export files.
My staff are not comfortable with computers
The interface is designed for exactly that. The picker's app is a scanner and two buttons — nothing more. Training the staff is part of the scope.
Is my data safe?
The database lives on your server or on hosting you choose — I do not keep it. Access is limited by role, every action lands in an audit log, and backups are automated.
11
Let's talk about your project
Write a few lines about your process and what is getting in the way. I reply within one working day.
Or reach me directly
Phone+998 90 021 86 97Telegram@JMusayevEmailjalol.musaev7@gmail.comGitHub@jaloliddinmusayevClient names, domains and server addresses are withheld for confidentiality.