An idea
Define the first useful flow and build a working version.
I build web products, Telegram bots and internal tools that take over manual work, accept payments and save your team time. Bring an idea, an existing project or a problem you have not figured out yet.
Tell me what you have in mind. No brief needed.
02 / Ways I can help
You do not have to commit to a large system. The right first step might be fixing payments, understanding an inherited codebase or building one working flow.
Define the first useful flow and build a working version.
Understand the code, join development and add what is missing.
Start with one bug or integration. No lengthy specification required.
Map the workflow and build a tool for the repetitive steps.
Work through legacy code, migrations, monitoring and infrastructure.
If people keep moving the same data between spreadsheets, a CRM and files, we can start with one of those workflows. There is no need to replace every system at once.
02When a website builder or standard CRM cannot handle the logic you need, I can build the backend, connect the services and add an interface where it helps.
03A bot can take payments, start a processing job or give staff access to an internal service. When messages and buttons are not enough, I can add a Mini App or a web interface.
04The previous developer has left, the bot keeps crashing or changing production feels risky? We can start by investigating a specific problem, not promising a full rewrite.
For agencies and integrators
If the standard CRM cannot handle the logic, or a client needs a custom backend, Mini App, scraper or integration, I can join as an external developer. A white-label arrangement is possible; we will agree on communication, scope and responsibilities first.
Bring me into your project ↗03 / How I work
No need to hire a backend developer, a frontend developer and a DevOps engineer separately. I cover every stage, and you can come in at any of them.
A chat or a call: what hurts, who the users are and how things work today. No finished brief needed.
Data, user flows and integrations. The first useful flow is split out so it can ship sooner.
Python, FastAPI or Django, PostgreSQL, Redis. Business logic, roles and background jobs.
A React web app, a Telegram bot or a Mini App. Wherever your users already are.
YooKassa, CRM systems, third-party APIs, S3, scraping and data processing.
I test the key flows and set up the server, Docker, CI/CD, logs and error alerts, so problems surface before users notice them.
After launch I stay on: fixes, new features and growing traffic.
Tell me what you have in mind and I will suggest where to start.
Let’s talk on Telegram ↗04 / The person behind the code
I’m a Python fullstack developer. I work through the problem, design the system, build the backend and connect APIs, with a web or Telegram interface where needed. If the project already exists, I start by understanding how it works today.
You talk directly to the person writing the code. We can start with a small fix, see how we work together and take it from there.
developer.stack
I also work on scraping and data processing. The project’s constraints guide the choice of tools.
05 / FAQ
No. Describe what you want to build or what is not working. I will ask the follow-up questions, and we will write the technical description together.
It depends on the scope. After our first conversation I will give you a cost and time estimate before any work starts. A large project is split into stages, each with a clear result.
Yes. That is how my long-term projects began: one fix or integration first, then ongoing development.
Yes. I start by understanding how it works today and only then suggest changes. I have worked with legacy code and other people’s decisions before.
I can stay on for support: fixes, monitoring and new features. We will agree on the arrangement before work starts.
Yes, as an external developer for the custom technical work, including white-label arrangements.