Frequently asked questions

One engineer: me. There is no handoff between the person who designs a screen and the person accountable for it in production, because they are the same person, and decisions get made with both jobs in view.

There is a flip side. I run few projects at a time, and a product that genuinely needs several teams is not something one engineer should be selling you. What follows from that: about the studio.

With a brief. Use the form on the contact page to say what the product is, what state it is in and what has to change. That is enough for a substantive answer instead of “let’s get on a call”.

Then comes scoping: a range, and a written list of what the range does not cover. Work does not start before that list is agreed — it decides how a project ends far more reliably than the estimate does.

Yes. Several entries in selected work are published exactly that way: the problem, the approach and the stack are described, the client is not named.

If the agreement rules out even that, the project never appears on this site at all — neither named nor anonymised.

Delivery time is a property of the package, not of the calendar. Each package on the pricing page carries its own range — from a few weeks on compact work to an open-ended monthly retainer.

A specific date arrives with the scoping, alongside the range. Naming one earlier is possible; it is also a number that then has to be defended instead of the work being done.

Because the price follows the scope, and the scope is only known once the brief has been unpacked. The published ranges are an invitation to talk, not a public offer under article 437 of the Russian Civil Code — the figure on the page binds nobody.

What pushes it upwards is listed next to the packages on the pricing page. That is worth more than a bare “from $X” with no account of where the upper end comes from.

Because these are two independent price lists, not one list expressed in two units. The Russian and the international market differ in scope, tax and risk, and an exchange rate explains none of that.

Nothing is converted in either direction: the pricing page here quotes dollars, the Russian tree quotes roubles, and each figure was set for its own market.

Payment is split across stages; the shares are printed on each package card — usually 50 / 50 or 40 / 40 / 20. The accepted methods are listed on the same pricing page.

Settlement details are issued with the invoice and never published on the site. A permanent address on a public page is a target for substitution, not a convenience.

Launch changes the mode of work rather than ending it. The pricing page lists monthly retainers: updates, monitoring, and incident response within an agreed window.

A retainer is optional. Declining one does not turn the product into a black box — everything needed to run it yourself is handed over at delivery either way.

Straight to a server in Russia. The browser posts it past the platform that serves these pages: the primary record is created in a PostgreSQL database on a Russian server, as article 18(5) of 152-FZ requires. The email notification goes out after that write, not instead of it.

A lead is kept for 365 days and then destroyed on a schedule. Every recipient of the data is named in the privacy policy — by legal name and registered address, as article 9(4)(6) requires.

Email the address published in the privacy policy. The answer comes within 10 working days — a deadline set by article 20(1) of 152-FZ, not by studio policy.

Withdrawing consent stops the processing and deletes the lead from the database. There is deliberately no one-click button for it: an email leaves a record on both sides, a button leaves one only on mine.

Not without your consent. No third-party analytics loads by default: the banner asks once, and the decision can be changed at any time on the cookie page.

Declining breaks nothing — the pages are static and behave identically either way. There is one counter, a Russian one; no foreign trackers are loaded at all.

To keep bots out of the mailbox. The widget sees the IP address, the connection parameters and the behaviour inside its own frame — not the contents of the form. The vendor is named in the privacy policy.

If the captcha fails to load, the form says so and offers an email address instead. It cannot quietly submit an unverified lead.

A repository with its commit history, not a zip file. Accounts and credentials issued in your name. Instructions for building and deploying. On infrastructure work, a runbook and at least one restore-from-backup performed together with you.

The full handover list is written out per service on the services page — before the contract is signed, not in an annex to it.

That gets tested before the work ends, not after. The stack is public and conventional; nothing proprietary that only I know how to deploy goes into a project.

Handing the product to another team is a matter of access and documentation, not a series of calls with me. If a project needs my phone number to build, it has not been delivered.