Questions
Rates, access, timescales, and what happens if the fix does not work.
The things people ask before hiring. If yours is not here, ask it directly — the answer is usually one email.
Why are your clients not named?
Most of the engagements on this site are covered by a confidentiality or publicity clause, and several involve work I would not describe in public even where the contract allows it — security incidents in particular. So each one is described by sector and country instead. Where a client is happy to be named and to be a reference, I will introduce you directly. That is worth more than a logo on a page anyway.
What does an engagement usually cost?
It depends on which of four shapes it takes: a fixed-fee audit, a fixed-price project, a day rate, or a monthly retainer. The starting figure for each kind of work is on its service page. Whichever applies, the number is agreed in writing before any work starts.
How quickly can you start?
Enquiries get a reply within one working day. Emergency work — a site that is down or a checkout that has stopped — usually starts the same or next working day. Scheduled project work is typically booked one to three weeks out.
What access do you need?
For a diagnosis: a read-only administrator account, SFTP or SSH, and access to the hosting panel and logs. For implementation: write access to a staging environment and a way to deploy. I do not need your payment gateway credentials at any point.
Do you work with our existing developers or agency?
Often, yes. Plenty of engagements are as the outside specialist inside someone else's team — their sprint board, their code review, their release process. I have worked that way through ClickUp and Jira and I am comfortable not being the owner.
What if the fix does not work?
If a fix I implemented does not do what I said it would, I keep working on it at no further cost until it does or until we agree it cannot be done. That does not extend to new problems discovered along the way, which get quoted separately and honestly.
You are in Skopje. Is the time difference a problem?
It has not been so far, for clients in Denmark, the United Kingdom, Georgia and Canada. Central European Time overlaps with the whole UK and Nordic working day and with the North American morning. Availability outside those hours is arranged in advance rather than assumed.
Will I be locked into you afterwards?
No. Code is written to standard WordPress APIs, documented, and handed over with the credentials at the end of the engagement. Any competent WordPress developer can pick it up. A retainer is available if you want one, but the work is built so that you do not need one.
Do you sign NDAs and data processing agreements?
Yes, both, as a matter of course for any engagement that touches customer data. Send yours or ask for mine.
Do you use AI to write the code?
AI tooling runs throughout my development workflow, and it is a large part of how one person delivers at the scope a small team used to. Every line is still reviewed, tested and justified before it ships. If you would prefer it not be used on your codebase, say so at the start.
Can you just tell me if my site is worth saving?
Yes, and sometimes the honest answer is no. A site running an abandoned theme on an unsupported PHP version with eleven overlapping plugins can cost more to rescue than to rebuild. I would rather tell you that in the first conversation than discover it halfway through an invoice.