You will get a backend, REST or GraphQL API, and database built
Project details
The engine under your product, built properly. I design and build backends in Node and Python: clean API design, a database schema that still makes sense a year later, authentication and roles, and the infrastructure to run it.
I am the only engineer behind my company's entire product line, so these are backends carrying real load, not demos. That includes a multi-tenant SaaS with per-client configuration and metered billing, a payment platform routing four providers, and the internal ERP the company runs on daily with multi-currency payroll and accounting.
Mostly PostgreSQL, Redis and Docker, with Django, FastAPI or Node depending on what fits. You get the source, API documentation, and a deployment your own team can operate without me.
Send me what you're building and I'll tell you which tier it is, and what I would change about the plan.
I am the only engineer behind my company's entire product line, so these are backends carrying real load, not demos. That includes a multi-tenant SaaS with per-client configuration and metered billing, a payment platform routing four providers, and the internal ERP the company runs on daily with multi-currency payroll and accounting.
Mostly PostgreSQL, Redis and Docker, with Django, FastAPI or Node depending on what fits. You get the source, API documentation, and a deployment your own team can operate without me.
Send me what you're building and I'll tell you which tier it is, and what I would change about the plan.
Programming Languages
JavaScript, Python, TypeScriptCoding Expertise
Performance Optimization, SecurityWhat's included
| Service Tiers |
Starter
$149
|
Standard
$650
|
Advanced
$1,800
|
|---|---|---|---|
| Delivery Time | 3 days | 7 days | 14 days |
Number of Revisions | 1 | 2 | 3 |
Design Customization | - | - | - |
Content Upload | - | - | - |
Responsive Design | - | - | - |
Source Code |
Frequently asked questions
About Abdusamadbek
SaaS Product Engineer | Next.js, Python, Stripe, AI, CRM Integrations
Tashkent, Uzbekistan - 11:41 am local time
I'm the only engineer behind my company's entire product line: 40+ systems and integrations in production in under a year. Hiring me gets you one person who takes a product from database schema to deployed URL, not a specialist who hands off half the work and waits.
Recent work:
- Uption, a multi-tenant compliance SaaS for US trucking fleets: AI document intake, per-client configurable workflows, metered Stripe billing, and a CRM integration framework. Piloting with 10+ companies.
- A payment platform routing four providers (Stripe, Click, Payme, Multicard) with signed webhooks, provider switching, and reconciliation. Every payment the company makes runs through it.
- The internal ERP the company runs on daily: roles and permissions, multi-currency payroll, and accounting.
- Production AI, not demos: LLM document processing, vision OCR, and structured extraction across thousands of records.
- 30+ CRM and ERP integrations across Bitrix24, AmoCRM, and MoySklad, plus Flutter and React Native apps.
Stack: TypeScript, Python, React, Next.js, Node, Django, FastAPI, PostgreSQL, Redis, Docker. I reach for whatever the problem needs and pick it up fast.
How I work: I reply quickly, I ask the questions that change the build before I start building, and I tell you when something is a bad idea. My English is fluent (IELTS 7.5), so requirements don't get lost in translation. I'm on GMT+5, which overlaps European hours and US mornings.
New to Upwork, not new to shipping. If hiring someone without reviews here is the worry, start me on a small first milestone and judge the work before committing to the rest.
Tell me what you're building and I'll tell you exactly how I'd ship it.
Steps for completing your project
After purchasing the project, send requirements so Abdusamadbek can start the project.
Delivery time starts when Abdusamadbek receives requirements from you.
Abdusamadbek works on your project following the steps below.
Revisions may occur after the delivery date.
Design the schema and endpoints
I map your data model and API surface first and show it to you before building. Getting this wrong is what makes a backend painful six months later.
Build, document, and test
Endpoints, auth and roles, validation, and background jobs where they belong, with API docs you can hand to any frontend developer without explaining anything.