Contact
Let us talk about your project
Describe the task however you like. I reply within a day, usually faster on working days.
Frequently asked
The things people usually ask before we start. If your question is not here, write to me and I will answer.
Money and timelines
From the estimate. I break the task down line by line: function, time, cost. The total is the sum of the lines, and it is a fixed price for the work rather than a bill for hours. Hours are there to justify the figure: you see how it adds up and can drop anything unnecessary before we start. No separate specification is needed — the estimate works as one.
That is my problem, not yours. Each line carries the minimum realistic time rather than the maximum: if a task might take one to three hours, the estimate says one. Overrunning inside the agreed scope does not increase the bill. The price changes only when the scope itself changes — and then I show you the new line before starting on it.
First I build a part of the work and show it running — only then does any money change hands. From there, two options: half after the demonstration and half on delivery, or a split into stages — four of 25%, say, each one after you have accepted the previous. On longer projects the second suits both sides: you pay for visible results, and I do not disappear into months of work without feedback.
I keep working and show it again, usually a few days later. There is one criterion — the estimate: it lists exactly what I am building, and the demonstration checks that and nothing else. If the result does not match the estimate, I rework it and show it again. The first money arrives only after you have seen a working part, so you never pay blind. But open-ended rework because something is simply not to taste is not part of it: if what we agreed was built and works as agreed, the stage counts as accepted.
No. You get a fixed price for a specific result and pay it regardless of how long it took me: longer is my risk, shorter costs the same. So time counters, desktop screenshots and screen recordings serve neither of us: what is worth checking is the result, and I show that at every stage, before payment. This is about surveillance of the process, nothing else. A task tracker is a different matter: Jira, Trello or whatever your team uses, I will join it without hesitation, because that is where tasks belong.
A small bot or landing page: one to two weeks. A web or mobile application: from a month. I give the exact timeline with the estimate, broken down by stage and with a buffer for the unexpected.
No. An hour of work is an hour of work at the same rate. Small tasks often turn out to be the start of a long collaboration.
How the work runs
You describe the task however you like. I ask clarifying questions, break it down and come back with an estimate: what exactly will be built, how long it takes and what it costs. Once we agree, we begin.
It depends on the project. For a website, a design; while it is being prepared I can get on with the server side. Server and hosting access are needed later, closer to deployment. I name the exact list along with the estimate, so you are not hunting for things you do not need yet.
I send photos and short videos as the work goes. As soon as there is something to show as a whole, I ask for server and domain access and deploy it — from then on you can look for yourself instead of waiting for my messages.
Usually Telegram. If your team uses a different messenger, I will install it and work there, as long as it is an official app from a store. Coming into your task tracker — Jira, Trello, whatever you use — is no problem either: tasks belong where the whole team can see them.
Anything we discussed that I missed or got wrong is fixed free of charge, however many rounds it takes. Small things that were not in the agreement but take a couple of minutes I cover as well, within two or three such fixes. Beyond that, and for anything that is genuinely new work, I price it separately. For example: we agreed the bot would have an AI, so revisions inside that task are free. But "let the AI also send photo reactions" is a new feature — I will price it separately and say so immediately, not afterwards.
Automated tests first, then by hand. Once I am satisfied it is ready, we go through it together. Anything that differs from what we agreed is fixed straight away and free of charge.
Usually I build the whole project myself — which is why you talk to the person doing the work rather than through a manager. I bring in a team in two cases: the deadline is tighter than one person can physically manage, or my queue is full. I run as many projects as still lets me hold the promised deadlines: if the queue is full, I say so straight away and give you a start date.
Anything illegal. Less often, picking up someone else on a codebase: if a project was written without tests or documentation, an honest estimate frequently comes out higher than building it again, and I will say so plainly. Everything else is open to discussion: if a task is not for me, I say so immediately and point you elsewhere where I can.
Handover and paperwork
A deployed and configured project — I handle deployment myself, and it is a line in the estimate. After full payment the source code and the access credentials are yours. Documentation I prepare on request, as separate work: not everyone needs it, and I do not put it on the bill by default.
You do. Exclusive rights to the deliverable pass to the client after full payment, and I claim no royalties. I keep only what existed before the project or is general-purpose: my own utilities and routine functions such as sorting. The business logic of the project, and anything specific to your operation, is not covered by that — I do not reuse it. The work goes into my portfolio either with your permission or anonymised — no company name and nothing that could identify it. If you would rather not have even that, say so and the project appears nowhere.
Yours. Domain, server, payment provider, third-party APIs — all registered to you. That way you do not depend on your contractor: decide to change and there is nothing to ask for. And I am not answerable for what runs on somebody else business.
Two separate cases. If something works differently from what we agreed, or I misunderstood the task, I fix it free of charge, no discussion. Everything else — new features, consultations, help with a breakage that did not come from my code — is paid support at my hourly rate, with the same line-by-line estimate as the main project.
Yes, before we get into the details of a project. Every current project is covered by a non-disclosure agreement — which is why there are no links to code in this portfolio.
I am in UTC+5: that overlaps most of the working day with Europe, and my evening with the US East Coast. Russian is native. English I read and write fluently, so messages, documentation and written briefs are no problem. Listening is weaker, especially fast speech: if a voice call is needed, I ask people to speak at a measured pace and to repeat key decisions in chat. In practice that works out better anyway — the agreements stay in writing, and you can always go back to them.