Bring an idea —leave with a working product.
Web services and APIs, sites and catalogues, Telegram bots and mini apps. I write the backend in Python and Node, the frontend in React and Next.js, design the database and set up the server. One person for the whole cycle: nobody to hand the work to, nobody to point at.
1
Person for the whole cycle
30+
Projects delivered end to end
14
Days to a production launch
0
Projects abandoned halfway
Services and APIs
FastAPI and Node.js, async logic, queues, payment gateways, integrations with AI models and streamed responses. Code you will not be ashamed to open a year later: typed, with migrations and logs, rather than a garland of if-statements around a single handler.
Sites and interfaces
React, Next.js and hand-written markup with no page builder. Catalogues that filter instantly, shopfronts and landing pages that open at once. Honest analytics and real speed on a phone, not a pretty PageSpeed report.
Telegram systems
Bots on aiogram and grammY, mini apps with initData signature auth, payments, roles, broadcasts. One address works both in the messenger and in a browser — I do not keep a separate build.
ITSM PRO
A ticketing system for an iiko dealer, covering both service and retail. Tasks with deadlines, owners, discussion and attachments all live at one address — and the same address opens as a mini app inside Telegram. There is no separate messenger build.
A ticket can be dictated in a single sentence: the speech parser picks out the assignee, the deadline, the priority and the project — from rules and dictionaries, with no external LLM and no per-request fee.
Read the case studyAbove is the idea as a mockup; here is what grew out of it. These are screenshots of systems that run, not drawings. Tap any of them to open it large.
ITSM PRO
Read the case study →Design Market
A shopfront for luxury interior pieces: catalogue, seller accounts, listing moderation, sourcing requests. In this trade the photograph does the selling, so the whole layout serves a large frame and a calm grid.
The catalogue is served as static pages and reindexed on an event — a category page opens in a fraction of a second even with thousands of listings.
Read the case study
Design Market
Read the case study →
Sort
A coffee shop with three locations. The morning queue was eating the takings: someone off a train will not wait eight minutes. It started as a shopfront page with pre-ordering behind it — and half the orders began coming through it.
The next step is an app of its own: pick a drink, size and time, pay, collect by code without queueing. The iOS and Android concept is below.
Read the case studyFour more projects with real screens and a write-up
Four shapes that almost any brief fits into. The clock starts when the scope is agreed, not at the first message.
Landing page or one-pager
3–7 daysA single page that explains the value in ten seconds and leads to an enquiry. Services or menu with prices, a form, a map, a call button. Findable in search, not only by name.
Telegram bot or mini app
1–3 weeksTaking orders, booking with live availability, payment inside the messenger, notifications and a panel for staff. A mini app opens as an ordinary website too — no separate build.
Web service or catalogue
4–9 weeksA catalogue with search and filters, user accounts, roles and permissions, moderation, payments. From a hundred-item shopfront to a marketplace with dozens of sellers.
Integration and automation
from 1 weekWiring your system to someone else's: till, 1C, CRM, payment gateway, Google Sheets. Scrapers, reconciliations, exports and scheduled reports instead of manual work.
I quote the exact timeline and price after going through the brief — usually the same day. If I can see it is cheaper solved without development, I will say so.
Discuss the projectSomething similar?
Send one message: what the business is and what is getting in the way. I answer the same day, and I will say plainly if it is not my kind of job.
Discovery
An hour on Telegram. I work out what is supposed to happen to the user. If the problem can be solved without code, I will say so.
Estimate
A list of screens, a deadline for each and a fixed price. It does not grow afterwards — rework caused by my mistakes is on me.
Build
A working version on your staging server every two or three days. Changes as we go, without approval rounds or presentations.
Launch
I deploy to your server and hand over the repository and the credentials. A month of support is already in the price.
“The client lives in Telegram. So that is where the product should open — not ‘there as well’.”
What does it cost?
The price depends on the number of screens and integrations. I will give you a figure after an hour of discovery — before that, any number would be a lie.
How long does it take?
Timelines per format are in the «What you can order» block above. I count them from the moment the scope is agreed, not from the first message, and fix them in the estimate rather than in chat.
I am not technical
All the better. What I need is an understanding of your business, not a spec written in API terms — I will write that myself and bring it to you for review.
Who owns the code?
You do. The repository, the server, the domain and the bots are registered in your name from day one. If I leave, nothing breaks and there is nothing to buy back.
How fast can we launch?
I put a working prototype of a bot or a mini app together in 48–72 hours. That is enough to test demand and take the first orders without waiting for the full version.
What if the project is confidential?
I work under NDA. Business logic, databases and tokens live in private repositories — they never reach this portfolio or anywhere else.
Do you work under contract?
Yes: registered self-employment, a contract, an invoice and a completion certificate. Payment is split across two or three stages as work is delivered.
Tell me what needs to work.
Send one message on Telegram — what the business is and what is getting in the way. I answer the same day, and I will tell you honestly if the job is not mine.
I usually reply within the hour