Client areas, internal systems and integrations
I replace spreadsheets and manual work with a system built around your process. I connect services that do not want to be connected. I build client areas, admin panels and Telegram bots.
I have built systems that run under load and under strict security requirements.
What I do
They replace spreadsheets and manual work. A CRM shaped around your process, not your process bent to fit a ready-made CRM.
I design and write a backend that holds up under load and can still be read afterwards.
I connect what does not want to be connected: CRM, accounting, payment systems, third-party APIs.
Mini Apps and bots with payments. My own product in production — kopim.
How the cost is worked out
There is no fixed price here: two tasks that look alike can differ fivefold. It works like this.
- 01You describe the task in the brief.
- 02Within two working days I return a range and a breakdown by stages. Free.
- 03If the range works for you, I make a detailed estimate of the first stage at a fixed price.
- 04After that, stage by stage, each one ending in a working result.
Where the code lives and who has access
I work in your repository, or in mine with a handover afterwards. Access is the minimum necessary. I am ready to sign an NDA. All data and keys stay with you.
What people ask most
What will it cost?
I give a range within two working days of the brief, free. An exact price comes after a detailed estimate of the first stage. After that every stage is estimated separately and ends in a working result.
Will you take on code written by someone else?
Yes, but I will look at it first. Sometimes extending is more expensive than rewriting, and I will say so directly, with numbers.
What if you disappear?
The code sits in your repository from day one, and documentation is written as the work goes, not at the end. The project can be handed to another developer at any moment — that is the test that everything was done honestly.
Will you sign an NDA?
Yes.
How much time do you actually give a project?
One project at a time, with a report once a week. If I cannot meet the deadline I turn the work down rather than spread myself across several projects.
Who owns the result?
You do, entirely: the code, the access, the documentation, the domain.