About

Telegram bots and apps for business, Mac and phone apps, teams of AI agents: from idea to launch, with checks and honest numbers.

In numbers

  • 2 languagesRussian and English, fluent in both
  • Every nighta copy of the data in every project with a server
  • Auditand a threat model before launch: tournament bot, Shtab, assistant server

How I work

  • Code, access and instructions are yours

    At launch I hand over everything the product needs to live without me: the code, the data, all access and a description of where things are and how to run them. The handover procedure is written down in advance, see below on this page.

  • You see the work as it goes

    You can open interim versions and try them yourself. Changes are made right away, without waiting for the end of the work.

  • Updates are checked before release

    Before a change reaches your customers, the program checks by itself that everything else keeps working.

  • Security as a separate step

    I use modern means of protecting and encrypting data. Before launch I check how an outsider could reach the data, payments or controls, and fix what I find.

What the handover includes

  • The code in a repository on your account; I stay a co-author for as long as you need.
  • The data and a backup copy with you, the bot on your account; the server on yours or, by agreement, on mine, and then you can take it over at any time.
  • All access is yours; my keys can be revoked at any time.
  • A guide to where everything is and how to run it, plus a call to hand everything over step by step.

The rule is simple: what is handed over is what stays yours for good, not what is on loan.

Technologies

For those who care what it is built with.

Telegram bots

  • Python
  • aiogram
  • SQLite

Websites and apps

  • TypeScript
  • React
  • Astro
  • FastAPI
  • PostgreSQL

Mac apps

  • Swift
  • Rust
  • Tauri

Design

  • Figma

How the work goes

  1. Talk and estimate

    You tell me about the task, I ask questions. You get an estimate and a plan.

  2. Prototype or demo

    You see how the product will look and work before the main development starts.

  3. Development

    I show interim versions. You get the product piece by piece and can adjust the course.

  4. Launch

    I deploy and test on real data. You get a working product, the code and all access.

  5. Support

    I stay in touch after launch. You get help if something goes wrong.

The terms

  • We agree in writing: what I do, the stages, the timing, payment by stage.
  • I show interim versions as we go, and I make changes right away.
  • At launch I hand over the code, the data, all access and a guide to where everything is.

Common questions

Will the code and access be mine?

Yes. The code, the data and all access to the bot and the server belong to you. I hand them over at launch, and you can continue with any developer.

What if something breaks after launch?

Write to me. I stay in touch after launch. What support includes and for how long, we agree before the work starts.

How do we agree on the work and payment?

We agree in writing before work starts: what exactly I do, which stages the work has, the timing of each stage and the payment terms.

How much does it cost?

I give an estimate after a short conversation, free of charge. Tell me about the task and I will tell you the cost and where to start.

Can you connect my spreadsheet or accounting system?

Often yes: spreadsheets and many accounting systems can exchange data. I will look at yours and tell you for sure before we start.

Contact

Tell me about your task. I will reply and suggest where to start. I reply within an hour, or in the morning if it is night.