What we do, what we don't, and how we get access

How access is handed over

Access is discussed only after you have accepted the scope and the amount. We start at the first rung that gets the job done. We do not accept passwords over a messenger.

1. 1

   Patch files

   We send finished code and instructions; your developer applies them. No access at all is required. Works for structured data, robots.txt and template changes.

2. 2

   A separate temporary account

   Permissions scoped exactly to the agreed list of work, revoked once you accept the result. The preferred option in most cases.

3. 3

   A branch in your repository

   Every diff is visible and a rollback is one command away. If you use git, this is the fastest and safest route.

4. 4

   FTP or SSH

   A fallback, not the standard. We do not accept root or shared accounts — only a separate account for this job that you close after acceptance.

Payment

• A fixed amount, named before we start. The €25/hour rate is how the scope is costed — you pay for the result, not for hours.
• 50 % before the work starts, 50 % after you accept it.
• We work either directly by invoice or through an escrow platform — your call. Escrow: Freelancehunt (Ukraine) or Upwork: funds are held and released on acceptance, and the platform fee is agreed before the funds are held.
• Invoiced by a registered sole trader in Ukraine, with documents.

How the work runs

• Everything is handled in writing. No calls are required.
• The list of work is written down verbatim before the start — and the result is accepted against that same list.
• One approval channel and no more than two rounds of scope clarification.
• On completion you get a report: what changed, where exactly, and a re-run of the same checks.
• The timeline is named together with the price, before payment.

Terms

• Acceptance: you have five business days from delivery to check the work. If nothing comes back in that window, the job counts as accepted.
• If access shows the job is technically impossible, we stop, show you the cause and ask whether you want a paid diagnosis. Without your consent to that diagnosis there is no invoice at all.
• We back up every file we touch and can roll it back during the acceptance window. A full backup of the site on your hosting stays on your side.
• After acceptance we are not responsible for changes you or anyone else makes to the same files.
• Anything outside the agreed list is a separate task with its own price. Nothing is added to the invoice after the fact.
• The result is measured against the agreed list of fixes, not against the score. The score also depends on things this work does not cover — content, links, competitors.
• The scope is fixed by the invoice: until it is issued and paid, any item can still be removed. If we find that a check was wrong and the item has not been done yet, we drop it from the scope and from the price — whether or not the work has started.
• Access is kept only for the duration of the work and deleted on acceptance. Changing the passwords and closing the temporary account afterwards is on you — and we recommend it.