Contact / direct conversation
Describe the goal in a few sentences.
Tell me what should change, who will use it and what already exists. I will help define the technical scope later.
Best for a longer project description, files and initial requirements.
Best for a quick question and the first conversation.
Short brief
What should your message include?
- 01
What problem or idea should the solution address?
- 02
Who will use it: customers, players, a team or administrators?
- 03
Do you already have a website, server, code or configuration?
- 04
Is there a deadline, budget range or part that must be handled first?
What happens next
A clear first conversation, without technical pressure.
You do not need to prepare a formal specification. A real description of the situation is more useful than a list of technical names chosen before the problem is understood.
- 01
I read the context
I check the goal, existing materials and the people who will use the solution.
- 02
I clarify the scope
If something important is missing, I ask a short and specific question instead of guessing.
- 03
I propose a first stage
You receive a practical starting point that can be built, reviewed and refined.
Useful information
What you can expect from me
I will say directly whether the project fits my current skills and availability. If the first version is still being refined, I will describe its current scope clearly rather than present it as a finished product.
Files and information shared in the conversation are used only to understand and discuss the project. The privacy policy explains how contact data is handled.