Telegram Mini Apps
Interfaces for sales, catalogs and services inside Telegram. The whole app runs inside the chat: no separate website, no sign-up.
Custom software and automation
Mini Apps for selling, order bots, marketplace monitoring, internal tools and integrations. The uptime of everything I have launched is public — check it before you write.
Bots from $200 · Mini Apps from $1,000 See pricing
Interfaces for sales, catalogs and services inside Telegram. The whole app runs inside the chat: no separate website, no sign-up.
Automating trading strategies through the exchange API. The bot listens to the price feed over WebSocket, works out the position size, and sends orders straight to the exchange.
Parsers and bots for tracking listings. The bot checks new items against the filters you set and sends the full product card to Telegram right away.
Community moderation and channel automation in Telegram. The bot filters spam, runs a reputation system for members, and publishes posts on schedule.
The cases above are what is running right now. The range of work is wider than four cards.
Shops, catalogs, booking and services that open inside the chat. No separate site, no sign-up.
Order intake, support, moderation, scheduled posting, alerts that reach the person who has to act.
Marketplaces, listings, prices, stock and competitors. Checked on a schedule, delivered where you already read.
Tie together the systems you already pay for: CRM, accounting, warehouse, delivery, payments. No retyping between tabs.
Admin panels, order management, dashboards, reports. Rebuilding a CRM that outgrew its shape is the same kind of job.
Backends, client portals and the interface on top, when the task needs more than a chat window.
Simple bot from $200, monitoring of one platform from $300, order bot with admin panel from $500, integration between systems from $800 and Telegram Mini App from $1,000. Internal systems and CRM rebuilds are quoted after the brief. The exact price is fixed before work starts, after we go through the requirements together. Payment is split 50/50: half upfront, half on delivery. Larger projects are divided into milestones. The full breakdown is on the pricing page.
The deadline is agreed together with the feature list and the price, before anything is written, and it is part of the agreement rather than a guess. On longer projects I show working pieces on a test environment along the way, so the wait is not a black box.
A description of the job, links or examples if you have them, and access to whatever the project has to talk to. If a site, bot, mockup or code already exists, send it in the first message. The scope is locked before the start, so new ideas are priced separately.
I deploy the project to the server, we test it in live conditions and I hand over full access. If something breaks in my own code, I fix it. Keeping the server running and adding features afterwards is agreed separately, month to month.
No. Most of what is running right now lives in Telegram, which is why the cases look that way. The same work happens outside it: web services, parsers, internal tools, integrations. The stack is chosen for the task, not the task for the stack.
Yes, that is a normal request. It starts with reading the existing code and saying honestly what can be repaired and what is cheaper to rewrite. Restructuring a system that outgrew its original shape is the same kind of work.
Warsaw, CET. The work is remote, in English, Russian or Polish, in whichever channel suits you. The first message goes to Telegram.
Write anyway. Briefly describe the job — I'll tell you what can be done and where to start.
Write on Telegram