Write me an email
I reply within one working day. This page covers what to put in the first email, what happens next, and which route is quickest when.
This is the primary channel. I reply within one working day, and every reply is mine — there is no support desk and no template answer.
What to put in the first email
No technical brief is needed, and the solution does not have to be worked out in advance — that is what scoping is for. These four things, in a few sentences, are enough:
- What you want solved. Whatever currently does not work, or is being done by hand — that shows what is needed.
- Whether something already exists. An existing site, a half-built system, a previous developer — the address is enough.
- When you need it. If there is a date that binds you; if there is not, that is also an answer.
- Who I will be working with. Is it your decision, or is there someone else with a say?
If some of them have no answer yet, that is fine: I will ask about the rest. Scoping is the first stage regardless, and that is usually where half of what matters comes out.
What happens next
I reply and ask questions. Usually one or two exchanges. I do not send a quote first: I would rather understand the job, because a template quote does not address what the actual work is in your case.
We also talk. After the first exchange we usually have a call or speak by phone. This is about trust, not speed: you see who you would be handing your system to, and I understand better what is needed.
I send a quote. Itemised: what I will build, how much work broken down by stage, what is not included, what I need from you and when, and what comes afterwards. There is a separate piece on what a quote is made of.
If you say no, that is fine. I will not call you back, send a reminder, or start negotiating. If it becomes relevant later, write — we pick up where we left off.
How the work runs, in eight stages
- 01 Assessment What needs manual work, and what could break.
- 02 Plan What gets built, what connects, what stays out.
- 03 Sign-off on the plan I start building only once you approve.
- 04 Build Separate environment; the live site stays up.
- 05 Testing A real payment, notification and booking.
- 06 Sign-off after testing What you see on the test, we decide together.
- 07 Launch With a backup and a way back.
- 08 Maintenance Updates, backups, monitoring — monthly.
Why email
Because it keeps the project clearer for both of us. What is in writing can be read back: we are not working from memory, and the work does not rest on improvisation. We hold the same description.
This is not rigidity. We talk as well — the conversation is part of the engagement, and it usually happens right after the first exchange. The bulk of the work stays in writing, though, because there it can be gone back to.
Phone
My phone number is not public, but my clients have it. If I maintain your system, you can call: if something breaks, or a question is quicker to talk through, I am on hand. That is part of maintenance, and it holds long-term.
For a new enquiry, though, email is the first step. I do not take on urgent work: I am not an emergency service, and if something has just gone down on a site I do not maintain, I cannot step in immediately. The details are on the page about me.
Where, and in what language
I work from Budapest, and I take on work from anywhere within the European Union, remotely. In Hungarian and English — this page has a Hungarian version as well.
Company details, registration number and hosting provider are in the imprint.
Questions on this topic
How quickly do you reply?
Within one working day. Every reply is mine — there is no support desk and no template answer. If the question is involved, the first reply is usually a question back, because a quote requires understanding the job.
What should I put in the first email?
Four things, in a few sentences: what you want solved — whatever currently does not work, or is being done by hand; whether something already exists (an existing site, a half-built system, a previous developer — the address is enough); when you need it; and who decides on your side. If some of them have no answer yet, that is fine: I will ask about the rest.
Do we need to meet in person?
Not necessarily, but after the first exchange we usually talk — on a call or by phone. This is about trust, not speed: you see who you would be handing your system to, and I understand better what is needed. The bulk of the work stays in email afterwards.
Can I reach you by phone?
My number is not public, but clients have it. If I maintain your system you can call — if something breaks, or a question is quicker to talk through. For a new enquiry, email is the first step.
Do you take on urgent work?
No. I am not an emergency service: if something has just gone down on a site I do not maintain, I cannot step in immediately. My existing clients can reach me by phone, though, because I know their systems.
Can I contact you from abroad?
Yes, from anywhere within the European Union, remotely — which keeps invoicing simple for both sides. I work in Hungarian and English.